BSOD 0x124_4_GenuineIntel_PCIEXPRESS_UNSUPPORTED_REQUEST_IMAGE_GenuineIntel.sys

[zking6]

I have been receiving the following BSOD error in event viewer periodically throughout the past 2 weeks. I have ran chkdsk, ran memory diagnostic, updated all drivers including chipset and bios, but still receiving this error, can anyone help in narrowing this down? Dump file analyzed with windbg below.



OS Name Microsoft Windows 11 Home
System Model Z690 GAMING X DDR4
Processor 12th Gen Intel(R) Core(TM) i5-12600KF, 3700 Mhz, 10 Core(s), 16 Logical Processor(s)
Version 10.0.22621 Build 22621
BIOS Version/Date American Megatrends International, LLC. F28c, 11/9/2023



************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.125 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120723-10015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`55000000 PsLoadedModuleList = 0xfffff800`55c134a0
Debug session time: Thu Dec 7 12:55:55.778 2023 (UTC - 5:00)
System Uptime: 0 days 19:57:22.409
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols

Loading unloaded module list
................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`55416ae0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`58290c50=0000000000000124
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: ffff9584c2f67028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2937

Key : Analysis.Elapsed.mSec
Value: 7362

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 156

Key : Analysis.Init.Elapsed.mSec
Value: 6681

Key : Analysis.Memory.CommitPeak.Mb
Value: 104

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x124_4_GenuineIntel_PCIEXPRESS_UNSUPPORTED_REQUEST_IMAGE_GenuineIntel.sys

Key : Failure.Hash
Value: {b18ac8da-121f-91e6-9956-cf4674a1bbda}


BUGCHECK_CODE: 124

BUGCHECK_P1: 4

BUGCHECK_P2: ffff9584c2f67028

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 120723-10015-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff800`58290c48 fffff800`554fe9cb : 00000000`00000124 00000000`00000004 ffff9584`c2f67028 00000000`00000000 : nt!KeBugCheckEx
fffff800`58290c50 fffff800`52ba10c0 : ffff9584`c2f67028 fffff800`58290d59 ffff9584`c2f67028 ffff9584`c2f3b9c0 : nt!HalBugCheckSystem+0xeb
fffff800`58290c90 fffff800`5560dfe6 : ffff9584`c2f67028 fffff800`58290d59 ffff9584`c2f67028 ffff9584`c2f3b960 : PSHED!PshedBugCheckSystem+0x10
fffff800`58290cc0 fffff800`5560e3d5 : 00000000`00000000 00000000`00000000 ffff9584`c2f67028 ffff9584`c2f614d4 : nt!WheaRecoveryBugCheck+0x56
fffff800`58290cf0 fffff800`58a6ec35 : ffff9584`c2f614d4 ffff9584`c2f614d4 00000000`00000000 00000000`00000406 : nt!WheaReportHwError+0x3d5
fffff800`58290dc0 fffff800`58a691d1 : 00003000`00000130 ffff9584`c2f3b150 00000000`00000000 ffff9584`c2f40720 : pci!PciRpRcecHandleAerInterrupt+0x2e9
fffff800`58290e20 fffff800`58a69946 : ffff8281`49fd8b00 fffff800`58290ed0 ffff8281`49fd8bf0 fffff800`553a2049 : pci!ExpressRootPortAerInterruptRoutine+0xa1
fffff800`58290e90 fffff800`58a69a09 : ffff8281`49fd8b40 fffff800`55488a0d 00000000`00000000 fffff800`58281a00 : pci!ExpressRootPortInterruptRoutine+0x46
fffff800`58290ef0 fffff800`5533fa01 : ffff9584`beefc040 ffff9584`cf3770c0 00000000`000005da fffff800`58281a70 : pci!ExpressRootPortMessageRoutine+0x9
fffff800`58290f20 fffff800`55324bfd : ffff9584`cf3770c0 fffff800`552b8bcc fffff800`50e4f180 ffff8281`49fd8b40 : nt!KiInterruptMessageDispatch+0x11
fffff800`58290f50 fffff800`554189bf : fffff800`58281a70 ffff8281`49fd8b40 ffff9584`cf3770c0 fffff800`5541fed0 : nt!KiCallInterruptServiceRoutine+0x16d
fffff800`58290f90 fffff800`55418c87 : 000000a7`4922068f ffff9584`00000000 000000a7`4569b9ae 00000000`00000000 : nt!KiInterruptSubDispatch+0x11f
fffff800`582819f0 fffff800`5541b89a : 00000000`00000000 fffff800`50aec790 fffff800`55d4d700 ffff9584`cf3770c0 : nt!KiInterruptDispatch+0x37
fffff800`58281b80 00000000`00000000 : fffff800`58282000 fffff800`5827b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_4_GenuineIntel_PCIEXPRESS_UNSUPPORTED_REQUEST_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b18ac8da-121f-91e6-9956-cf4674a1bbda}

Followup: MachineOwner

 

[ChatGPT]

The BSOD error you're experiencing is a WHEA_UNCORRECTABLE_ERROR (124), which indicates a fatal hardware error. The specific error source reported in this case is a PCI Express error. Here are some steps you can take to narrow down the cause of the error:

1. Check for hardware issues: Run diagnostic tests on your hardware components, such as the CPU, RAM, and GPU. You mentioned running a memory diagnostic, but it would be beneficial to run more comprehensive tests if possible.
2. Update firmware and drivers: Make sure all your drivers, including chipset and BIOS, are up to date. Check the manufacturer's website for the latest versions. Additionally, update the firmware for your motherboard if available.
3. Check for overheating: Monitor the temperature of your CPU and GPU during normal usage and when running intensive tasks. Excessive heat can cause stability issues. Ensure that the cooling system is functioning properly, and consider cleaning any dust accumulation on fans and heat sinks.
4. Check the system logs: Review the system logs in Event Viewer for any additional error messages or warnings that could provide more information about the cause of the BSOD error. If the issue persists after performing these steps, it may be helpful to provide more information about any recent hardware or software changes, and any specific activities or applications that trigger the BSOD error. Additionally, providing the full analysis of the dump file using a tool like WinDbg can provide further insight into the error. Please note that detailed hardware troubleshooting may require assistance from a professional or contacting the technical support for your computer or specific hardware components.

 

[SavorySilicon]

Thank you, I understand you said this issue happens intermittently. Could you please try to describe when this usually happens, and what you are doing? Are you playing a game, or is it during startup?

 

[dianawolws]

You've already done a commendable job updating drivers and running diagnostics, which is like the digital equivalent of crossing the I's and dotting the T's (yes, you read that right ). However, this persistent error is like a stubborn ghost in the machine, refusing to leave its haunted abode.
Here's a bit of levity for our situation: They say if you listen closely to the fan of a computer experiencing a BSOD, you can hear it softly whispering, "Turn it off and on again." But in our case, it seems more like it

 

[ChatGPT]

It seems like you're working on troubleshooting a BSOD issue with the error code 0x124_4_GenuineIntel_PCIEXPRESS_UNSUPPORTED_REQUEST_IMAGE_GenuineIntel.sys. This error often points to a hardware issue, specifically something related to PCI Express (likely a driver, firmware, or hardware failure) and the processor (Intel-based in this case).
If you can provide details regarding when the BSOD occurs, it helps significantly to narrow down the root cause. If you're asking for insights into someone's activities during the crash, let me outline what tends to correlate with this error:

---

Common Scenarios for 0x124 BSOD:​

1. Under Load (e.g., Gaming, Video Rendering):
   • Crashes occurring while gaming, running benchmarks, or performing resource-intensive tasks suggest issues related to power management, temperatures, or overclocking (intentional or manufacturer defaults).
2. Random/System Idle:
   • If the crash occurs when the system is idle, the fault might be due to hardware instability, possibly on the motherboard/PCIe bus.
3. Startup/Boot:
   • Errors during boot often indicate BIOS/firmware incompatibilities or initial hardware handshake problems, like GPU or SSD communication over PCIe.

---

Steps to Narrow Down the Cause:​

1. Check Event Viewer:
   • Look for critical events leading up to the crash (use the time of the BSOD). Keyword searches like WHEA-Logger or Kernel-Power may give hints.
2. Hardware-Specific:
   • If you’re using components like PCIe-based SSDs, GPUs, or add-on cards, one of them could be failing or incompatible due to a driver/firmware issue.
3. Run Hardware Diagnostics:
   • Use Intel’s Processor Diagnostic Tool: Download it here.
   • Run Memtest86 for RAM.
   • Test disks with tools like CrystalDiskInfo or manufacturer-provided utilities.
4. Update Drivers/Firmware:
   • Ensure the BIOS is the latest version.
   • Update chipset and PCIe-related drivers from your motherboard manufacturer.
   • Install the most recent Intel INF driver package.

---

Additional Causes to Investigate:​

• Overclocking Instability:
  • Verify if the system BIOS is applying overclock profiles (even "auto" ones); revert to defaults and perform stress tests.
• Power Supply Issues:
  • An insufficient or unstable PSU can cause such crashes, especially if GPU or CPU demand spikes.
• Thermal Problems:
  • Use HWMonitor to check the temperatures of the CPU, motherboard, and GPU before and after crashes to ensure no thermal throttling or overheating.

---

Once you can determine what activities seem to trigger the issue (gaming, file transfer, startup), more focused troubleshooting can be applied. If you still have the crash dumps stored, those files could also provide glaring evidence of the source of failure.
Let me know more details, and we’ll dive right into solving this mystery!