@BlueScreen: #PF Exception 14 in world xxxxx:vmast.xxxxxx IP xxxxxxxxx addr xxxxxxxxxx
search cancel

@BlueScreen: #PF Exception 14 in world xxxxx:vmast.xxxxxx IP xxxxxxxxx addr xxxxxxxxxx

book

Article ID: 381747

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

ESXi PSOD that mentions below entries:

 YYYY-MM-DDTHH:MM:SS.999Z cpu57:2384676)0x4539f2e9bd40:[0x4200041b0824]PShareFrameGetNext@vmkernel#nover+0x0 stack: 0x7
 
 YYYY-MM-DDTHH:MM:SS.000Z cpu57:2384676)0x4539f2e9bd48:[0x4200041b0898]PShareHashTableWalkMatchMPN@vmkernel#nover+0x39 stack: 0x400013a176
 
 YYYY-MM-DDTHH:MM:SS.000Z cpu57:2384676)0x4539f2e9bd50:[0x4200041b2a28]PShare_RemoveHint@vmkernel#nover+0x95 stack: 0xfe1976
 
 YYYY-MM-DDTHH:MM:SS.001Z cpu57:2384676)0x4539f2e9bd90:[0x4200041dab7b]VmMemCow_PShareRemoveHint@vmkernel#nover+0x68 stack: 0xc5c8842e00246322
 
 YYYY-MM-DDTHH:MM:SS.002Z cpu57:2384676)0x4539f2e9bde0:[0x4200041dabc7]VmMemCowPFrameRemoveHint@vmkernel#nover+0x34 stack: 0x400013a176
 
 YYYY-MM-DDTHH:MM:SS.002Z cpu57:2384676)0x4539f2e9be10:[0x4200041dc514]VmMemCowPShareFn@vmkernel#nover+0xb25 stack: 0x0
 
 YYYY-MM-DDTHH:MM:SS.003Z cpu57:2384676)0x4539f2e9bf80:[0x42000412a934]VmAssistantProcessTasks@vmkernel#nover+0x151 stack: 0x0
 
 YYYY-MM-DDTHH:MM:SS.004Z cpu57:2384676)0x4539f2e9bfe0:[0x420004428eca]CpuSched_StartWorld@vmkernel#nover+0x7b stack: 0x0

 YYYY-MM-DDTHH:MM:SS.004Z cpu57:2384676)0x4539f2e9c000:[0x4200040d788b]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0
 
 YYYY-MM-DDTHH:MM:SS.006Z cpu57:2384676)base fs=0x0 gs=0x42004e400000 Kgs=0x0

Environment

ESXi 7.x
ESXi 8.x

Cause

  • Inconsistency/corruption in pshare chain
  • Retrieved invalid MPN from PFrame looks corrupted
  • Corruption by the data of ether frame through vmnic

Resolution

  • Confirm BIOS is up to date
  • Check if there is difference in firmware/bnxtnet driver version and BIOS version between the hosts.
  • Update firmware/bnxtnet driver version if needed
  • Check network device is healthy.
  • Check system board and/or processor
  • For confirmation without hardware replacement, setting dmaMapperPolicy=debug and checking if bad DMA transfer is caught
  • Replace network device if required
  • Replace hardware if required
Powered by Wolken Software