Lost and Need Help Solving Blue Screen "WHEA_UNCONRRECTABLE_ERROR"

[unhappycampertoday]

Specs:

Windows 10 pro 64bit (new install)

Ryzen 7 5800x

Zotec Mini Gtx 1070ti

MSI B550-A PRO 

Team T-FORCE DARK Z 32GB (2 x 16GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4 25600) Intel XMP 2.0 Desktop Memory Model TDZGD432G3200HC16FDC01

EVGA SuperNOVA 850 G5

Desktop

Problem: Random blue screens with error "WHEA_UNCONRRECTABLE_ERROR" 

 

Hello, I have recently made some upgrades to my PC to install Ryzen 7 5800x. Previously I was running a Ryzen 1700x which was stable for years. 

 

During the upgrade I bought a new PSU(EVGA SuperNOVA 850 G5), Ram(Team T-FORCE DARK Z 32GB), Heat Sink(Cooler Master Hyper 212 RGB), Mother Board(MSI B550-A PRO) and the new CPU Ryzen 7 5800x.

After a fresh install of windows I  installed all my drivers. Shortly after I would randomly get blue screens that would cause a restart.

 

I did some searching around and here's what I have tried.

-Updating Windows

-Installing Drivers

-Testing Memory

-Stress Testing Cpu

-Setting Curve Optimizer to All Cores, positive, 8

-Updating Bios

After updating bios windows broke and spit out 2 more random errors

Once again I reinstalled windows and all the drivers but I am still having blue screens.

Blue screen viewer says its caused by driver "PSHED.dll"

I am completely lost and have no idea how to fix this, any ideas would be very helpful and appreciated! (Dump attached below)

 

Thanks

dump.zip

[Bananasplit_00]

That vcore looks kinda sus, make sure there isn't any auto OC stuff going on

[unhappycampertoday]

9 hours ago, Bananasplit_00 said:

That vcore looks kinda sus, make sure there isn't any auto OC stuff going on

I left everything on stock default settings but I agree it was looking strange. Saw a post some where about locking the voltage to 1.35V and multiplier to 43

I have done this and left my PC downloading games overnight and so far has not crashed and hopefully wont.

Why this might work I have no idea but if it does I will mark it as the solution incase anyone else has issues. The sad part is it wont turbo up to the 4.8GHz doing this.

[Bananasplit_00]

14 hours ago, unhappycampertoday said:

I left everything on stock default settings but I agree it was looking strange. Saw a post some where about locking the voltage to 1.35V and multiplier to 43

I have done this and left my PC downloading games overnight and so far has not crashed and hopefully wont.

Why this might work I have no idea but if it does I will mark it as the solution incase anyone else has issues. The sad part is it wont turbo up to the 4.8GHz doing this.

Maybe comb through the BIOS and look for setting names you think might be auto OC stuff, things like auto core enhancement or similar names and turn them off. Really seems like a motherboard thing to me at least

[Mark Kaine]

22 hours ago, unhappycampertoday said:

Why this might work I have no idea but if it does I will mark it as the solution incase anyone else has issues. The sad part is it wont turbo up to the 4.8GHz doing this.

so its not really a fix…

 

 

whats your old psu, can you try that?

i suspect psu tbh. 

[Mark Kaine]

On 8/9/2021 at 9:43 AM, Bananasplit_00 said:

That vcore looks kinda sus

I mean, is it? My vcore is about the same -in BIOS- goes to 0.9v in windows  at idle though…

 

 

[Bananasplit_00]

2 hours ago, Mark Kaine said:

I mean, is it? My vcore is about the same -in BIOS- goes to 0.9v in windows  at idle though…

 

 

looks like its set to 1.42 in the picture sent, that dosnt seem right to me at least. havent kept up with Ryzen core voltages but last i heard 1.425 was the "safe" roof

[Mark Kaine]

6 hours ago, Bananasplit_00 said:

looks like its set to 1.42 in the picture sent, that dosnt seem right to me at least. havent kept up with Ryzen core voltages but last i heard 1.425 was the "safe" roof

the "setting" should be somewhere else, this is just where the BIOS runs it, close to what it considers "safe"… which is 1.5v on *automatic* settings. So yeah, even if OP set it to 1.35, it might just do that in BIOS anyway. 

 

16 hours ago, Bananasplit_00 said:

Really seems like a motherboard thing to me at least

reading through  it again, i agree it could be motherboard. 

thing is OP replaced pretty much everything, so…

motherboard 

psu 

ram

(cpu)

 

At least Bios was updated, but what about the old psu, how was the Ram "tested"… id check these things first, and then motherboard (rma?)

 

 

[unhappycampertoday]

On 8/10/2021 at 6:14 PM, Mark Kaine said:

the "setting" should be somewhere else, this is just where the BIOS runs it, close to what it considers "safe"… which is 1.5v on *automatic* settings. So yeah, even if OP set it to 1.35, it might just do that in BIOS anyway. 

 

reading through  it again, i agree it could be motherboard. 

thing is OP replaced pretty much everything, so…

motherboard 

psu 

ram

(cpu)

 

At least Bios was updated, but what about the old psu, how was the Ram "tested"… id check these things first, and then motherboard (rma?)

 

 

I got a new PSU, and I used the windows windows memory diagnostic tool to check for memory errors. If I had to guess I think its between the mother board and the CPU because I locked the voltage to 1.35v and the clock speed to 4.3Ghz and it ran stable. Temps seamed kind of high but I have no idea what normal temps look like for this CPU so I might just take the heat sink off, do a quick sanity check to make sure I removed the plastic and then use my old cpu and see what happens. Worst comes to worst I can always return the CPU and Mother board if I find its those parts not liking each other since its not running stable at stock speeds without me pushing it past what's advertised. 

 

My biggest issue is I am struggling to replicate the crashes, its totally random. I've been trying at stock settings stressing cpu under load with games and aida64 and will be fine then the next moment I will just be watching YouTube with a light load and it just blue screens. I'm just so confused because I have zero experience trouble shooting issues like this. Normally my previous PC building issues are just me being a total idiot and like forgetting to plug the pc into the wall or flipping the PSU power switch.

[Mark Kaine]

do you still have the old psu?

 

windows memory diagnostic is unreliable, use memtest64 instead.

 

Also check event viewer for critical errors. There has to be some since it does log BSODs there.

I mean clearly 1 or more parts arent working as they should.  

[unhappycampertoday]

15 hours ago, Mark Kaine said:

do you still have the old psu?

 

windows memory diagnostic is unreliable, use memtest64 instead.

 

Also check event viewer for critical errors. There has to be some since it does log BSODs there.

I mean clearly 1 or more parts arent working as they should.  

I still have the old PSU.

 

I can give memtest64 a try.

 

And there are critical errors that happen after the blue screens reading "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." Which I think is just because it blue screened so the system didn't shutdown properly.

 

I put everything back to stock settings and stock speeds and crashed after about 17 hours, which was so strange since once again it crashed randomly while idling. I was gaming for hours straight under load watching the temps and no issues then I left my PC with only Chrome running and came back to a frozen Bios Splash Screen that started loading once I hit the power button. I checked BOSD and event viewer and sure enough the PC blue screened on idle while I was gone. I should add that it was stable when I fixed the voltage to 1.35 and clock speed but I don't really feel like keeping anything that can't at least run at stock speeds and especially since I'm still not sure what the exact cause is so I don't want to keep anything that may have issues past my return window.

 

At this point I might try mem test for the sake of it and open up the side panel to do one last inspection and make sure everything it where it should be and plugged in and if that yields nothing I might just send the CPU and Motherboard back since Amazon(where I bought it from) has a great return policy and free shipping to send it back. 

 

if it helps here's the blue screen view

 

and here's the event view 

 

 

I appreciate the reply's and any ideas since this has been way over my head