Windows stops with PFN_LIST_CORRUPT code

Environment

• Red Hat OpenShift Container Platform 4.x
• Red Hat OpenShift Virtualization 4.x
• Advanced Micro Devices (AMD) CPUs

Issue

• Microsoft Windows running on OpenShift Virtualization has random BSODs with PFN_LIST_CORRUPT code.

Resolution

• Check with your hardware vendor to apply the latest firmware, that includes microcode version 0xb002151 or higher.

Root Cause

Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

• The following AMD CPU issues may trigger the issue:
  • 1617 Speculative Translation Table Access is Used for TLB (Translation Lookaside Buffer) Entry Generation
  • 1621 Spurious Page Fault May Occur for Some Initial Page Allocation Mappings
  • More details see Content from docs.amd.com is not included.AMD Revision Guide for AMD Family 1Ah Models 00h-0Fh Processors
• This was investigated in This content is not included.Private RHEL-88195 - Multiple BSODs on Windows virtual machines with message "Stop code: PFN LIST CORRUPT".

Diagnostic Steps

• In the guest console, look for PFN_LIST_CORRUPT (0x4E) in BSOD.
• Open the crashdump with WinDbg and check the stop code

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.