Newly built PC continuously triggers BSOD WHEA_UNCORRECTABLE_ERROR

Hi everyone,

I decided to build my own gaming PC about three days ago. I initially wasn't able to post when I turned on the PC, nothing would work and no fans started spinning. I decided to take out the entire build and try to make it work outside the case, it worked. I then re-installed the PC back in the case and it worked as well. I then immediately started experiencing BSOD with the errorcode WHEA UNCORRECTABLE ERROR. This would happen very randomly and can't be pinpointed to anything specific. Sometimes it would BSOD for just being idle. I never put my system under load, never loaded any games or whatsoever. It was a fresh Windows 10 install.

The components I have are:

Motherboard: ASUS ROG Strix X570-E Gaming
CPU: Ryzen 5950X
GPU: MSI Radeon RX580 Armor 8G OC
Cooler: NZXT Z63
RAM: HyperX Predator HX432C16PB3AK2 64GB RAM (2x32GB) 3200Mhz
Storage: Samsung 970 EVO Plus NVMe SSD
PowerSupply: Seasonic Focus GX1000 Gold

I have been looking on the internet and tried troubleshooting it several ways, but unfortunately nothing helped. These are the steps that I have taken so far, so please, read this before re-suggesting the same troubleshooting tactics.

The troubleshooting I already did:
- Booting in safemode and using DDU to uninstall drivers and reinstall through AMD website for GPU.

- Re-installing the drivers for both GPU and MOBO

- Running MemTest86 for both memory sticks separately without any issues.

- Repositioned the GPU in a different PCIe slot and reinstalled it back to the first PCIe.

- Reinstalled the Memory in PC

- Reinstalled the CPU and Z63 AIO Cooler with new Thermal Paste

- Updated BIOS to the latest version

- Running HDTune to check my NVME SSD for issues. No issues

- Running DISM /online /cleanup-image /checkhealth and /restorehealth - no issues.

- Running sfc /scannow - no issues.

- Running chkdsk /scan - no issues.

- Running the Windows-built in RAM test, no errors either.
- Running Prime95 for high power/heat/CPU stress and max power/heat/CPU stress - it passed without issues
- Re-installing Windows 10, didn't help

At this point, I am very very sad I can't get it fixed. Please someone please help me.

I have managed to get the minidump files. Please find it attached in the link below. I'd appreciate it very much if anyone can point me towards the right direction. Thank you for your help.

Moreover, I sometimes randomly get different BSOD's as well. But the biggest problem is with WHEA UNCORRECTABLE ERROR.

1) INTTERUPT_EXCEPTION_HANDLED

2) ATTEMPTED EXECUTE OF NOEXECUTE MEMORY

3) SYSTEM SERVICE EXCEPTION

4) KERNEL SECURITY CHECK FAILURE


Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Hello luckystone,

If you remove files from the logs it sends warning signals. Sure enough, it looks as if you are pirating the operating system rather than paying for a legal license.

Unfortunately no help can be given when we suspect this.

philc43 said:

Hello luckystone,

If you remove files from the logs it sends warning signals. Sure enough, it looks as if you are pirating the operating system rather than paying for a legal license.

Unfortunately no help can be given when we suspect this.

Hi Phil,

I am sorry, I am a bit paranoid with accidentally providing my license key in a log file. My windows is legitimate, I have provided all the logs you need, sorry for the incovenience. Please find attached the link:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Hello again,

Thanks for redoing the logfiles. I can assure you that the product keys are not revealed in the files - we are careful to redact information of this nature.

The only other thing I need to ask you is why you are using KMSpico? If you can answer this question satisfactorily then I think we can make progress.

philc43 said:

Hello again,

Thanks for redoing the logfiles. I can assure you that the product keys are not revealed in the files - we are careful to redact information of this nature.

The only other thing I need to ask you is why you are using KMSpico? If you can answer this question satisfactorily then I think we can make progress.

Hi Phil,

Thank you for getting back to me so promptly. To be honest, I have scavenged the entire web for help and tried many things, including reinstalling Windows several times. This meant unsuccessful attempts of re-activating Windows many times, some of which failed. I found this link to get Windows activated, which turned out to be Virus and my PC blocked it. However, I am running legitimate Windows license and am at the end of my sanity of why my 2k+ PC is crashing on me

Hopefully with your help I can start enjoying my purchase.

OK. Please remove the KMSpico program and any other crack programs (IDM Crack); then redo the logfiles one more time. Once we are sure your system is clear of any potentially harmful files we can start the troubleshooting. Our forum rules are quite clear on this (rule 4).

As it is now late for me, I am sure some of our US analysts will pick up the thread or we can pick this up again tomorrow.

philc43 said:

OK. Please remove the KMSpico program and any other crack programs (IDM Crack); then redo the logfiles one more time. Once we are sure your system is clear of any potentially harmful files we can start the troubleshooting. Our forum rules are quite clear on this (rule 4).

As it is now late for me, I am sure some of our US analysts will pick up the thread or we can pick this up again tomorrow.

Hi Phil,

Thanks once again. Please find attached a new log folder. I'd be a million times grateful if we can resolve this issue.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Some steps that were already performed may be repeated.

Please perform the following steps:


1) Run:

LOGS.bat - Click here to go to the BSOD batch repository to download and run this batch file.


2) Uninstall all VMware software


3) Read these links on Windows driver verifier:

Learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool



Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified




4) For any BSOD:

run the V2 log collector to collect new log files

Code:

vmx86.sys    Tue Nov  3 01:21:38 2020 (5FA10502)

luckystone said:

I am sorry, I am a bit paranoid with accidentally providing my license key in a log file. My windows is legitimate, I have provided all the logs you need, sorry for the incovenience.

Please show us the information that Windows is activated with a digital license, the usual way for Windows 10.

Hello luckystone,

You now have three people trying to help you so it's going to get a little confusing for you because each analyst has different methods and understanding of the problems.

I prefer to look for patterns in the data and find the consistent reason for a crash. In my opinion this is a hardware issue and the error record reported by the CPU for all the 0x124 crashes is the same error:

Code:

Error         : Unknown (Proc 0 Bank 0)

My first suspicion is that the CPU is faulty. I would recommend that you contact your supplier for the CPU and indicate that you have strong reasons to suspect this and ask for a replacement.

However, before you do that it is worth seeing how long you can run your system in Safe Mode. If the CPU is faulty at some point it should crash with the 0x124 bugcheck even in Safe Mode. If it does not crash say within 1 day of using it - I realise you are somewhat limited in what you can do in safe mode but have a go at using it as much as possible - then it would be worth exploring what software/drivers could be causing this. But a crash in safe mode is more strong evidence that the CPU is faulty.