Question New build keeps crashing

Nov 3, 2019
4
0
10
0
MSI MPG Z390 Gaming Edge AC
i9-9900KF 3.6GHz
RAM: HyperX Predator HX440C19PB3AK2/16 DDR4 16Go (Kit 2x8Go ), 4000MHz CL19 DIMM XMP - RGB
GPU: EVGA GeForce RTX 2080 Super Black Gaming, 8GB GDDR6, 08G-P4-3081-K
PSU: Cooler Master 750
5 Fans
Water Cooling
Samsung SSD 860 Evo (1To)
Seagate ST2000M001 (2To)

I keep getting BSOD (whea_uncorrectable_error) but not just that one. It also freezes every now and again and there's no other option than unplugging to reboot.

All drivers are up to date. All Windows 10 updates installed.

Minidumps:
http://s000.tinyupload.com/?file_id=98214970652204738586
http://s000.tinyupload.com/?file_id=02435395765921121922
http://s000.tinyupload.com/?file_id=85943227162839151589
http://s000.tinyupload.com/?file_id=06347781141820409958

Anyone can help me please? Thanks in advance :)
 
Last edited:

PC Tailor

Distinguished
Herald
I have run the dump file(s) and you can see the full report(s) here:

https://pste.eu/p/WLvp.html (WHEA)
https://pste.eu/p/nKGI.html (IRQL)

Summary of findings:
WHEA_UNCORRECTABLE_ERROR
"A WHEA ERROR is almost solely hardware based. It is possible in rare circumstances for this to be a driver, however it is very unlikely. It is often caused by:
  • Component overheating
  • Unstable overclocking or XMP profile
  • Faulty hardware"
DRIVER_IRQL_NOT_LESS_OR_EQUAL
"Typically this is driver based, as it is when a module tries to access an invalid address when the IRQL is too high.

If a driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

It is recommended that you view the third party modules to see which drivers may be misbehaving."
Some things to consider:
  • What is your PSU model exactly?
  • WHEA is usually hardware, it CAN be software, but is usually software.
  • Are you running any OC/XMP at all?
  • Do you have latest BIOS installed?
I did notice e1d68x64 in one of the dump files:
Code:
fffff803`0da08450 00000000`00000000 : 00000000`00000801 00000000`00000001 ffffc08c`26abad00 00000000`00000801 : e1d68x64+0x1967f
This is an Intel Ethernet Driver - and the dump also suggest Windows NDIS Internet interface could be to blame, which would lead me more to Internet drivers perhaps.
If Driver Verifier still pulls out a microsoft driver or WHEA, then you are likely on hardware diagnosis (which you can see some guides on this in the report above) but just let me know.

- Intel PPM is also appearing in the stack text prior to the crash, which could be indicative of a WHEA error, so following this it may be worth running a CPU test to check if the CPU appears to be working normally. (Such as Intel Processor Diagnostic).
 
Last edited:
Nov 3, 2019
4
0
10
0
Thank you for the help :)

Answers to your questions:

The PSU is a master cooler V750.
I am not running OC/XMP. Should I?
I do have the latest BIOS installed.
Ran the CPU test, all pass.

In terms of temperatures, everything is running between 35°C and 40°C
 
Last edited:

PC Tailor

Distinguished
Herald
And what about the Intel Internet drivers?

You can use the report I posted to check all third party modules running at the time of the crash and which ones may be out of date. Just WHEA is usually hardware.

Do you have any additional pcie devices or peripheral devices like headphones etc?

Following that I would continue with the driver verifier guide I linked :)
 
Nov 3, 2019
4
0
10
0
I'm running driver verifier atm, it says to keep it running for at least 24hrs so I'll let you know what comes out of it.

Weird that old drivers should be showing up, though as I freshly installed everything (after re-downloading from the appropriate sites such as Norton so if there are drivers dating back to 2018, they are the newest ones available anyway). Same for the Internet Intel drivers, I downloaded the latest before re-installing.

If it is hardware, how can I find out which component is to blame?
 
Last edited:

PC Tailor

Distinguished
Herald
I'm running driver verifier atm, it says to keep it running for at least 24hrs so I'll let you know what comes out of it.

Weird that old drivers should be showing up, though as I freshly installed everything (after re-downloading from the appropriate sites such as Norton so if there are drivers dating back to 2018, they are the newest ones available anyway). Same for the Internet Intel drivers, I downloaded the latest before re-installing.

If it is hardware, how can I find out which component is to blame?
We can perform various software tests however none of them are guaranteed. The only sure fire way of identifying hardware faults is by replacing the hardware and retesting unfortunately.

Let me know how driver verifier goes. If it identifies a microsoft driver, it's much more likely a hardware problem.
 
Nov 3, 2019
4
0
10
0
Driver verifier hasn't thrown out anything particular.
I've played around with the RAM (moving it etc), no difference. I've also replaced the SATA cables, still no difference.
Regarding peripherals, I have my speakers plugged in to the headphones socket at the front. For some reason I can't get anything out from the back output.
I also have a Focusrite Scarlett 2i2 3rd Gen in (I switched from a 1st Gen a couple of days ago - made no difference - drivers are obviously the latest) but this might be a clue: I get BSOD a LOT when recording using Ableton Live 10 (Latest version).
 

ASK THE COMMUNITY

TRENDING THREADS