(Solved) BSOD WHEA_UNCORRECTABLE_ERROR

Question

Solution: Looks like I had a bad or incompatible GPU that was causing this issue. Putting in a different GPU seems to have solved the problem.

All edits to the post are visible in italics or strikethrough, as applicable.

Have Tried:

• Memtest (check RAM integrity), all results good
• CrystalDiskInfo (check storage integrity), all results good
• Uninstall graphics drivers and AMD's Adrenaline software and reinstall without Adrenaline (only driver), no change
• Driver Verifier (check driver integrity), discussed below

I somewhat frequently get the BSOD with stop code WHEA_UNCORRECTABLE_ERROR. It's been happening for over a year since I replaced all system hardware except the PSU and GPU. Sometimes several times a day, sometimes only once in a month. It has never occurred while I'm in the middle of a game (which is what the PC is mainly used for), but I can't identify any specific trigger for it. Sometimes when I'm in Word/Excel/PowerPoint, sometimes when I'm in Chrome just idling browsing the internet. In fact, I just got another while writing this post the instant I hit "Enter" after typing a search query in the Chrome URL bar (specifically, "how to sanitize windows minidump"). This seems a little familiar, so it might've happened upon trying to reach a page in Chrome previously but I can't say for certain. Don't know if it's relevant, but while the screen immediately cut to BSOD, the search was successfully sent to Google's servers because it was stored in my Google History when I tried to pull it up on my phone.

I've run whatever diagnostics I can find for my system hardware and things have been consistently coming back clean (including memtest and CrystalDiskInfo). I finally tried Driver Verifier from this very helpful post and got a stop code from nldrv.sys (from NetLimiter 4). Since I wasn't using the software regularly, I just uninstalled it. Unfortunately, the problem repeated itself a few days later, so I ran driver verifier again, this time getting DRIVER_VERIFIER_DETECTED_VIOLATION with no driver listed (nothing in parentheses after the code). Afterward, when the computer tried to enter Automatic Repair, it stalled and then threw another BSOD for DPC_WATCHDOG_VIOLATION. The third attempt got it into Automatic Repair and I was able to revert to my restore point. (Unrelated: it's frustrating that Windows 10 abandoned the ability to boot into Safe Mode from the boot menu)

I have a minidump from after the most recent WHEA_UNCORRECTABLE_ERROR and the msinfo export (and now another pair from the one that happened while writing this post). It didn't create a minidump after the DRIVER_VERIFIER_DETECTED_VIOLATION BSOD, but I have a full dump (a hair over 16GB). I'm unclear on how I can/should safely share these with the relevant experts, so please let me know what I can do. Unsure how/if I should be sanitizing them first before sharing. A zip of the minidump, msinfo export (.txt) and msinfo save (.nfo) after the most recent BSOD (occurred while posting this) is availablehere.

I'm certainly also open to any other suggestions about things to check or diagnostics to run. It's been a while since I ran the whole gamut, so there are likely several things I'm forgetting that I've already tried, but I don't mind trying again. I've had little luck with Reliability Monitor or Event Viewer as they appear to just say that "Windows was not properly shut down" without saying anything about why, but I may just not have enough experience reading them to know what to look for.

Thanks in advance!

Answer 1

The drivers did not fix the problem, but I believe I've found the solution. I got my hands on a used GPU and swapped it for the one I had. It's been working for several weeks and so far no blue screens. The GPU, PSU, and case were the only parts I reused in my PC rebuild before this all started and the GPU was working just fine before. Perhaps it's an incompatibility issue with the specific GPU I was using. Would need to test it in a different system to check, but I don't have another system lying around, so it'll probably remain a mystery. I'll update if I get another blue screen, but I think this problem is finally solved.

Answer 2

I've talking about DRIVER_VERIFIER_DETECTED_VIOLATION BSODs you've mentioned. These BSODs occur when driver verifier detects misbehaviour of some driver.

Dump says "A fatal hardware error has occurred".

Answer 3

I've amended the original post to include a link to the minidump and msinfo after the most recent WHEA_UNCORRECTABLE_ERROR that occurred while I was making the original post. Can you clarify what you are referring to when you ask for the "memory dumps (driver verifier especially)"? Are you looking for the 16GB full memory dump from after the most recent driver verifier crashes I referred to in my original post?

Answer 4

Hi Igor, thanks for the quick response. I've amended the original post to reflect that CrystalDiskInfo is what I used. That was a human memory malfunction . I'm reviewing the link you provided now and will post again once I've successfully uploaded the relevant files.

Answer 5

Hi,

I'm Independent Advisor not Microsoft employee or support person. I have deep enough Windows knowledge and you may trust me. It's a pleasure for me to help others and I'll do all my best to help you.

To check drive's health one nee to use CrystalDiskInfo tool not CrystalDiskMark.

Please share memory dumps (driver verifier especially) to OneDrive for analysis.

https://answers.microsoft.com/en-us/windows/for...