Question Finding problem for WHEA Uncorrectable Error

blue4fun

Distinguished
Feb 2, 2012
2
0
18,510
I moved my setup to the other side of my room, and ever since I've been getting WHEA Uncorrectable errors. The first time happened when I loaded into a comp overwatch game with wuthering waves open + on a discord call. I could trigger crashes pretty consistently in this situation for a while. Not sure if it matters, but the games are on different drives.

I've updated all my drivers, ran windows memory diagnostic and scanned both nvme drives with Samsung magician, neither of which showed any problems. I also reseated the ram, which didn't help. Temps look fine too. I disconnected and reconnected the 24 pin power connector and 8 pin cpu power cable, and the problem seemed to subside, though that may have been a coincidence. I just got a new desk so I moved my PC around a bit, and the problem came right back. This time it happened while I was downloading a game on my main drive and playing wuthering waves while on a discord call. It happened again later during a comp overwatch match on call as well.

I have dump files for the most recent ones, as they weren't making dump files until I changed the paging file settings to 'system managed' on my second drive.

https://files.catbox.moe/wslmhx.dmp

https://files.catbox.moe/n9risn.dmp

https://files.catbox.moe/4swwqr.dmp

https://files.catbox.moe/vq5r9p.dmp

Here is my sysinfo file.

The above was a reddit post from about 2 weeks ago that no one responded to :( The crashes persist.

Since then, I have ran all 3 prime95 tests for an hour or longer with no issue. I also ran memtest86 for at least one pass on all four sticks of ram individually, as well as separate tests for each slot. All tests showed no errors. I ran Crystal Disk Mark on both drives multiple times with no issues or crashes.

Other info:
3 volmgr errors are listed in event viewer before each crash: 161, 45 and 46. These all occur on my C: drive. If I set my D: drive to have a paging file, I get minidumps, except for the past couple crashes.

Not sure what else to do to figure out which part is the problem. Since the dumps reference a driver error, should I try a windows repair/reinstall?
 
Last edited: