Randoms Crashes and BSOD WHEA

Windows Version 22H2 Build 19045.4291

Hi i have many random freezes today ... I have to hard reset of the PC button to restart it and sometimes wont boot because say there is no boot devices ( had to switch off the plug and re plug it )

Today have 4 crashes and BSOD WHEA UNCORRECTABLE ERROR

I run seagate long generic test and all drives are good and Prime95 without errors for 3hs and 60max temps

I notice today that sometimes the pc crash when restart it (5 secs after enter windows) and sometimes when CPU/RAM/SSD are at heavy usage

The other thread is this Randoms BSOD and user zbook told me that i can open another thread here ! I cant swap components to try because dont have anyone with Z370 mobo or any CPU than cant fit in my mobo ... Thanks

WHEA stands for Windows Hardware Error Architecture. All I know about this is what I've researched just now, but it seems that some hardware errors can be caught and trigger a WHEA BSOD. The codes generated point to the place in which the error has been detected, that seems the processor in this case.

I've found this similar example, with the codes and the corresponding legible info exposed. It seems an error detected in the processor cache. I'd bet the error itself doesn't allow any safe path or step forward, so the processor and whatever else is halted. https://answers.microsoft.com/en-us/...b-892dff86207a

This debugging result matches the fact that the error happens when the system is under stress like you said in the other thread. Stressing apps like Memtest might fail to go through the "broken path" and trigger the error.

This paragraph is about guesses. W/o knowing anything more (I don't have the concrete knowledge or experience to associate a "WHEA 124" and whatever other info is present to anything I know well), I think your system might be stable with only one module because it would be less stress, but my first suspect would be the processor. This is the only costless (except the reduced performance) and free of risk move I see.

Thanks ! So what can i do ? Memtest for example u say ? Yesterday and today i dont have crashes...

Yesterday have two windows update and today the PC crashes and BSOD many times. I only can uninstall one update, is There any way to uninstall the other update and Make Windows Update to dont install again?

JLArranz said:

WHEA stands for Windows Hardware Error Architecture. All I know about this is what I've researched just now, but it seems that some hardware errors can be caught and trigger a WHEA BSOD. The codes generated point to the place in which the error has been detected, that seems the processor in this case.

I've found this similar example, with the codes and the corresponding legible info exposed. It seems an error detected in the processor cache. I'd bet the error itself doesn't allow any safe path or step forward, so the processor and whatever else is halted. https://answers.microsoft.com/en-us/...b-892dff86207a

This debugging result matches the fact that the error happens when the system is under stress like you said in the other thread. Stressing apps like Memtest might fail to go through the "broken path" and trigger the error. How can one disagree? Of course, I understand that everyone has their own opinion, but still? I respect people who have their own thoughts in their heads. There’s simply no adding or subtracting here. Keep up the good work as they say. This is already normal, wow. I can't even imagine this. I'm just getting goosebumps right now. I also sometimes use this but not as often as I would like. Everything has its own rules. In general, I like your opinion. That's how it should be!

This paragraph is about guesses. W/o knowing anything more (I don't have the concrete knowledge or experience to associate a "WHEA 124" and whatever other info is present to anything I know well), I think your system might be stable with only one module because it would be less stress, but my first suspect would be the processor. This is the only costless (except the reduced performance) and free of risk move I see.

thanks, I'll look into it now