PC wakeup from sleep problem.

Winterlight · January 1

Offten I have problem with PC wake up from sleep problem. Trying wakeup it crash to to BSOD with errors like this uncoractable error 0x124 or kmode_exception_not_handled 0x1e any idea what can course this problem ? PC work stable and don't have any problems or crash to BSOD while not in sleep mode. I found that with Ryzen 5xxx CPU could be problem than PSU power in sleep mode go to low that is not enough to wakeup stable this CPU and someone recommend change in BIOS power supply idle control from auto to typical current idle does it worth try due I no idea actualy what this settings mean and do.

Bjoolz · January 1

54 minutes ago, Winterlight said:

Trying wakeup it crash to to BSOD with errors like this uncoractable error 0x124 or kmode_exception_not_handled 0x1e any idea what can course this problem ?

Sleep on Windows is just incredibly broken. The WHEA_Uncorrectable_Error is concerning though. WHEA is the Windows Hardware Error Architecture. This system relies on the CPU's internal error detection which is then reported to Windows. The CPU monitors itself and PCIe devices. Except for NVMe storage, Windows duct taped that onto WHEA through driver reporting. Because this is sleep related, my main suspect would be the NVMe/NVMe driver.

Could you go to Event Viewer → Windows Logs → System and find a Kernel-Power event related to the WHEA crash? If you sort the list by 'Level' so that you have all the Critical events at the top, it will be much easier to find the Kernel-Power events as they should line up. Just click on the Level column to sort them (And click again to sort in the other direction). If you click the Details tab in the bottom half where it shows info about the event, it should show BugCheckCode for the WHEA event. Virtually every else this is reported in hexadecimal which is 0x124, but for some unknown reason event viewer uses decimal. 0x124 in decimal is 292. So 292 is the BugCheckCode you are looking for.

Once you find it, right click on it and save it. Upload the .evtx file here.

Winterlight · January 1

The only thing I found from critical error is kernel power event 41

If you mean BugCheckCode it show 30

Bjoolz · January 1

5 minutes ago, Winterlight said:

The only thing I found from critical error is kernel power event 41

If you mean BugCheckCode it show 30

Yes, Kernel-Power is only 41 (Or 6008 in some niche cases). It is indeed the BugCheckCode that needs to be 292, meaning it's from the WHEA BSOD. You need to go through all of the Kernel-Power events because only some of the BSODs are WHEA ones.