Question WHEA UNCORRECTABLE ERROR [BSOD] - occurs more frequently with reduced PC usage.

[CRCE]

I have been getting a WHEA UNCORRECTABLE ERROR BSOD for a while now. Probably for more than a year. I've tried on occasion to identify the issue, without success.

One of the reasons I've struggled to find the issue, and had a lack of will to do so; is because the issue is far and away more frequent when I am using my PC less, or when I don't use it for a while.

If I go on holiday I return to frequent BSOD's of death with this error on day one, then by the second day after returning they're reduced, and usually a few/couple of days after getting back I am not getting errors any longer.

Recently I've been rather busy so my PC usage at home has hit a long time low, which seemingly has led to more frequent errors, as I am often not using my PC for a few days at a time. Then I come back to a few days of issues, and then I don't use it again for a bit - repeat. So now I'd finally like to solve this.

My temperatures are good, and I've recently applied new thermal paste to help with that. I also today ran a few stress tests on my GPU (FurMark), and RAM (y-cruncher & memtest86). I cannot seem to solve the issue.

I know this error is attached to hardware, so I've re-seated my PC parts, and in previous bouts of this issue have seemingly seen reductions in this error. However, it's hard to tell what is causing it still.

Hard gaming and stressing the system do not seem to connect to it too much? I seemingly BSOD randomly and as the PC pleases, and sometimes get hours of gaming in, and then BSOD while doing very little at all.

I am happy to provide any further information. I have attached my DxDiag, and can provide any other system/hardware information. I am mainly looking for good ways to diagnose this issue. Because I'll happily replace the part that needs replacing, but I don't want to go out buying PC part after PC part to find out what is broken.

DxDiag

 

[Bob.B]

I have been getting a WHEA UNCORRECTABLE ERROR BSOD for a while now. Probably for more than a year. I've tried on occasion to identify the issue, without success.

One of the reasons I've struggled to find the issue, and had a lack of will to do so; is because the issue is far and away more frequent when I am using my PC less, or when I don't use it for a while.

If I go on holiday I return to frequent BSOD's of death with this error on day one, then by the second day after returning they're reduced, and usually a few/couple of days after getting back I am not getting errors any longer.

Recently I've been rather busy so my PC usage at home has hit a long time low, which seemingly has led to more frequent errors, as I am often not using my PC for a few days at a time. Then I come back to a few days of issues, and then I don't use it again for a bit - repeat. So now I'd finally like to solve this.

My temperatures are good, and I've recently applied new thermal paste to help with that. I also today ran a few stress tests on my GPU (FurMark), and RAM (y-cruncher & memtest86). I cannot seem to solve the issue.

I know this error is attached to hardware, so I've re-seated my PC parts, and in previous bouts of this issue have seemingly seen reductions in this error. However, it's hard to tell what is causing it still.

Hard gaming and stressing the system do not seem to connect to it too much? I seemingly BSOD randomly and as the PC pleases, and sometimes get hours of gaming in, and then BSOD while doing very little at all.

I am happy to provide any further information. I have attached my DxDiag, and can provide any other system/hardware information. I am mainly looking for good ways to diagnose this issue. Because I'll happily replace the part that needs replacing, but I don't want to go out buying PC part after PC part to find out what is broken.

DxDiag

Why are you running an old version of w10?

You might want to update the bios and also the chipset driver if it's old.

 

[ubuysa]

I've seen 0x124 BSODs when idle before, sometimes it's because older processors seem to have problems transitioning from the low power C3 (or higher) state to the C0 running state. It does seem from my experience to be more common on AMD CPUs rather than Intel.

The way to test (and mitigate) for this is to find the C-State settings in your BIOS and disable all C-States for all processors. That will stop them entering a lower power C-State. If the BSODs stop then that was your problem and disabling C-States is the only fix.

If you can't disable C-STates then you can achieve a similar effect by going into the active Windows power profile (probably Balanced) and locate the Processor Power Management entry. Change BOTH the minimum AND maximum processor power to 99% (100% might work, and might not, but I know that 99% does). This also stops Windows trying to reduce the C-State of of the processors.

The only downside to disabling C_States is that a bit more heat will be generated when idle and you'll consume a little more power when idle too.

See whether that helps. If not then please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.