Error: #PF Exception 14 host PSOD

Products

• VMware vSphere ESXi

Issue/Introduction

An ESXi 8.x host experiences a Purple Diagnostic Screen (PSOD) and becomes inaccessible to vCenter.

• Host Crashes with PSOD 

#PF Exception 14 in world World_ID:vmnic8-pollW IP 0x42001194db13 addr 0x42045a800018
Port_IsLockedOnCurrentHor1d@vmkernel#nover+0xa3 stack: 0x453b1f99bde0
vmk_PortPr ivDataGet@vmkernel#nover+0xc9 stack: 0x45db66a8ad42
[e-mail]#1.0.0+0xfe stack: 0x431f1153fde0
[e-mail]#1.0.0+Oxafa stack: 0x0
Port_InputResume@vmkernel#nover+0x1bf stack: 0x42001186cbdd
Net_AcceptRxList@vmkernel#nover+0x25b stack: 0x0
NetPollWor1dCallback@vmkernel#nover+0xb9 stack: 0x41
CpuSched_StartWor1d@vmkernel#nover+0xbf stack: 0x0
Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0

• Backtrace: The crash occurs during a return from a Timer Interrupt.
  
  
• Review of the host logs may show consistent crashes occurring on the same Physical CPU (PCPU) core (e.g., PCPU 45).
  
  
• Standard hardware sensors (iLO/IPMI) typically report no errors or warnings prior to the crash.

Environment

• VMware ESXi 8.x

Cause

A hardware-level fault in a physical processor core causes a Page Fault (#PF) exception when the CPU miscalculates internal register indices or attempts to access an invalid memory boundary. The CPU remains electrically functional, which prevents standard hardware diagnostics from detecting the defect.

Resolution

To resolve the host crash:

1. Review /var/run/log/vmkernel.log or /var/run/log/LogEFI.log to determine if the crashes consistently map to a specific Physical CPU (PCPU).
2. Engage the hardware vendor to replace the physical processor package containing the identified PCPU core.
3. Request the vendor perform targeted CPU instruction stress tests. Standard "Quick Tests" often fail to surface this specific instruction-level miscalculation.
4. Ensure the System BIOS and all component firmware are updated to the latest supported versions. See Download Broadcom Products and Software to download the latest releases.
5. If further assistance is required, see Contact Broadcom Support.