Are these common "WHEA Uncorrectable Error" crashes only under certain conditions?
Are these common "WHEA Uncorrectable Error" crashes only under certain conditions?
Hello, I'm experiencing a persistent Whea uncorrectable error, often accompanied by a machine check exception or BSOD. Initially it was occasional, but later it became frequent or even entered a loop. After a complete clean installation from Windows 10, the issue resolved after about five hours. Subsequently, BSODs reappeared more often, lasting roughly 5 to 10 minutes occasionally. There were no major changes in behavior once the system started, except possibly due to updates in Windows 10 or NVIDIA drivers.
In a clean Windows 11 setup:
- Idling in Microsoft Edge for over two hours without issues, then opening Control Panel triggered a BSOD within ten minutes, sometimes almost instantly while performing tasks.
- Installing Discord, Steam, or Malwarebytes during idle time caused BSODs when online, though not with just one app installed.
- Leaving the PC off for several hours resulted in no BSOD until 30 minutes or longer.
- Regular crashes after about five to ten minutes while idle and without any installations occurred.
- During stress tests using Prime95 for three hours, no BSOD was observed.
- Never experienced a BSOD when idle on the start screen or when Edge was launched.
Diagnostic attempts included:
- Running Win Mem Diagnostic Tool multiple times.
- Performing Intel processor diagnostics.
- Using Prime95 for approximately four hours.
- Checking CrystalDiskInfo for SSD health before and after reinstalling Windows, monitoring temperatures and voltages (PSU not checked).
- Testing one RAM module only; others were likely behind the CPU cooler. Verified proper installation of the cooler but confirmed no issues with the RAM itself.
- Cleaning the installation, using default BIOS from UEFI, clearing CMOS via CLRTC pin per manufacturer instructions, enabling/disabling XMP settings, reinstalling NVIDIA drivers, removing the headphone jack and Ethernet cable, ensuring all connections were secure inside the case, and testing the PC in different power outlets.
System specifications:
- Intel i5 10600KF (never overclocked), Deepcool Neptwin white cooler;
- Asus PRIME Z490-V-SI (latest BIOS, BSOD occurred over two years after the latest update);
- Crucial Ballistix White, 16GB, DDR4, 3200MHz, CL16, Kit of 2 (8GB each), not overclocked beyond 3200;
- MSI RTX 3060 Gaming X 12G (not overclocked);
- Xilence 550W, performance X, 80+ Gold.
All components are less than three years old.
Windows 11 Home (unactivated) version - 23H2, build - 22631.3296
Data transfer speeds and event logs.
Hello, and welcome to the forum!
You were wise to run all those hardware tests because a machine check exception 0x124 BSOD is most usually a hardware problem. However, there are some rare occasions whean a bad driver can cause a 0x124 machine check and I think that may be the case here.
All four dumps are similar. At first sight they appear identical, but after closely examining the raw call stack they're not quite identical. All fail whilst both networking and storage operations were in progress, possibly buffering an audio or video stream.
Whilst the actual sequence of function calls leading up to the bugcheck does vary slightly in each dump, they all call the same third-party driver; mwac.sys. This is the Malwarebytes Web Access Control driver, the version you have seems recent, dating from December 2023...
Code:
3: kd> lmvmmwac
Browse full module list
start end module name
fffff802`6a7c0000 fffff802`6a7eb000 mwac T (no symbols)
Loaded symbol image file: mwac.sys
Image path: mwac.sys
Image name: mwac.sys
Browse all global symbols functions data
Timestamp: Thu Dec 14 12:49:35 2023 (657ADDBF)
CheckSum: 0003DF43
ImageSize: 0002B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
Malwarebytes is generally a very robust product, as long as it's kept updated. I would first suggest that you look for an update to Malwarebytes, if it still BSODs after updating I would fully uninstall Malwarebytes (this can be done from normal Programs & Features).
If the BSODs continue after fully uninstalling Malwarebytes (and rebooting) then please download and run the
SysnativeBSODCollectionApp
. Upload the zip file that results. Also, please do not reinstall Malwarebytes or any other non-Microsoft product until your BSOD issue has been resolved.
This will give us all the troubleshooting data that we might need. The SysnativeBSODCollectionApp does not collect any personally identifying data, it's perfectly safe, and it's used by many well-respected help forums. You can look at the files in the zip file before upload if you wish, but please don't change or delete anything. Details on what these files contain can be found
here
.
BSODs continue to occur, and I verified by updating and uninstalling Malwarebytes. I checked the driver's date change and confirmed it was removed from the folder. Since BSODs don't happen when the PC is idle, I had to take certain actions. To help, I saved a text file detailing the steps I took, including variable changes, for all five BSOD dumps after following your instructions. Additionally, I added two more dumps in an extra folder before proceeding as requested.
There are some interesting points about your disk configuration...
The System Reserved area now has a driver letter assigned (D), which is unusual. Typically, this partition isn't meant for regular user access—it mainly holds boot files, BitLocker data, and recovery tools. Why was it given a drive letter? It’s just a small detail I noticed first.
You appear to have two drives with Windows-style partitions. Your system drive © is the Samsung 870 SATA SSD, but the Seagate 500GB HDD also shows a similar structure. The larger partition there is your F drive. Having both Windows partitions available at once can lead to complications.
Another observation is that all these dumps stop working when the processor wakes up. Here’s a sample call stack from one dump, read from bottom to top...
The drive windows can't be accessed. It's an older drive from a previous computer. There are files there that my family occasionally needs—documents, photos, and sometimes a program they used. I left the drive untouched because I haven't copied them elsewhere, but I always see "Maybe you didn't copy it, check your PC." 😊
This machine has never recognized it as a bootable Windows drive since I first got it, and I don't remember why. It was only the SSD, the C drive, that was present when I reinstalled Windows and during many BSODs. Later, I moved the E: and F: drives back.
I'm not sure about the D: drive—it's reserved for the system. I haven't touched my SSD in disk management or elsewhere. There are two files visible now: "bcdbackup" and a recovery text file from 2016.
I've turned off C-States in the UEFI. Now I'm trying to monitor it.
Thank you very much for the help so far!
Hello, after adjusting the c-states and setting 8-10% minimum power with 99% maximum, I experienced occasional BSODs, though the system remained fully functional. Unfortunately, even at 99% minimum power, the PC still faced frequent BSODs within about three minutes, often restarting or entering system recovery mode. Windows would occasionally revert itself, but sometimes I had to shut it down completely to regain access to Windows. There haven't been any noticeable changes in the PC that would trigger BSODs now. Still, if I launch a more demanding game quickly, those crashes would likely occur again. If it runs quietly in the background, I might still see a BSOD. Perhaps with a very intense game, it wouldn’t happen, but I definitely don’t want this to be the solution for the problem.
I have two dumps. The one with the smaller file size was taken during a BSOD loop involving some unusual behavior with recovery or diagnostics, so maybe it doesn’t represent the current situation well. Of course, both dumps were recorded at 99% minimum power and c-states disabled.
I’m aware of an AMD issue where voltage adjustments were made as a temporary fix. I’m curious whether I’ll need to interact with the UEFI in the future. I don’t fully trust what’s happening there, especially with ASUS’ auto settings.
dumps
Edit: Also, this is the first time Windows has been performing regular diagnostic repairs after BSODs. Once I was without audio, checking power settings revealed an error (File system error (-144...), and similar issues). I had to endure several BSODs before Windows diagnosed and resolved the problem again.
It appears there may be a CPU-related issue at hand. The two dumps seem remarkably similar, and I’ll go into detail about what’s occurring here...
The call stack functions as a push-down structure, storing return addresses and parameters for kernel function invocations, since it operates in a push-down manner—read from the bottom up.
Code:
6: kd> k
# Child-SP RetAddr Call Site
00 ffffac00`62b49908 fffff804`446ff1eb nt!KeBugCheckEx
01 ffffac00`62b49910 fffff804`470710c0 nt!HalBugCheckSystem+0xeb
02 ffffac00`62b49950 fffff804`4480eb2f PSHED!PshedBugCheckSystem+0x10
03 ffffac00`62b49980 fffff804`44700c1a nt!WheaReportHwError+0x38f
04 ffffac00`62b49a50 fffff804`44701070 nt!HalpMcaReportError+0xb2
05 ffffac00`62b49bc0 fffff804`44700f04 nt!HalpMceHandlerCore+0x138
06 ffffac00`62b49c20 fffff804`447011a9 nt!HalpMceHandler+0xe0
07 ffffac00`62b49c60 fffff804`44700362 nt!HalpMceHandlerWithRendezvous+0xc9
08 ffffac00`62b49c90 fffff804`44702b1b nt!HalpHandleMachineCheck+0x62
09 ffffac00`62b49cc0 fffff804`44769539 nt!HalHandleMcheck+0x3b
0a ffffac00`62b49cf0 fffff804`4462a43e nt!KiHandleMcheck+0x9
0b ffffac00`62b49d20 fffff804`4462a053 nt!KxMcheckAbort+0x7e
0c ffffac00`62b49e60 fffff804`6a4e41b2 nt!KiMcheckAbort+0x2d3
0d fffffe0d`29ebf498 fffff804`6a4e5870 intelppm!C1Halt+0x2
0e fffffe0d`29ebf4a0 fffff804`6a4e15c4 intelppm!C1Idle+0x30
0f fffffe0d`29ebf4d0 fffff804`444e1456 intelppm!AcpiCStateIdleExecute+0x24
10 fffffe0d`29ebf500 fffff804`444e0fcb nt!PpmIdleExecuteTransition+0x426
11 fffffe0d`29ebf950 fffff804`4461cf44 nt!PoIdle+0x68b
12 fffffe0d`29ebfb40 00000000`00000000 nt!KiIdleLoop+0x54
It’s evident that the initial function call corresponds to 'idle loop', tasked with locating tasks for the processor. This occurs when there are no threads ready to run, prompting searches for DPCs, timer updates, and other background operations.
Following this, the system transitions to 'PoIdle' due to the absence of useful work. Subsequently, 'PpmIdleExecuteTransition+0x426' is invoked to signal the Power Manager to place the processor in a lower power state. Two Intel-specific driver calls (intelppm.sys) are executed to enter the C1 low-power mode.
Finally, an Intel-specific halt function (intelppm!C1Halt+0x2) is triggered, which halts the processor entirely. This halting action appears to be the root cause, as evidenced by the immediate machine-check failure right after it.
This sequence strongly suggests a CPU-related malfunction. It’s advisable to run the Intel Processor Diagnostic Tool, or at minimum, boot into Safe Mode with networking and monitor for any abnormal behavior. If the issue persists, consulting hardware specialists for potential BIOS adjustments might be necessary.
Yeah, thanks for Your help. I've tried the voltage changes with some help, but it doesn't seem to affect things. Maybe if go way higher with the voltage, but, eh. I'll be upgrading my PC soon to 7800x3D, so i'll give up.
In safe mode it still crashed, and i kinda have a hard time doing the intel diagnostics again. The BSODs started to get much worse, but that was before i tried voltage changes. I'd have to turn on prime95 stress test after turning on the PC so i don't get a BSOD in the first 10 sec after getting to windows. Then i could do some stuff on the PC. I'd launch a game, then turn off the stress test to game.
Curiously, for the very first time i started also getting watchdog BSODs sometimes , when the BSODs started getting even worse before trying voltage changes.
But yeah, time for an upgrade. Thanks for Your help. I managed to squeeze couple months of the PC thanks to You.