[SOLVED] WHEA_UNCORRECTABLE_ERROR - Hellllp! FIX: I changed my faulty m.2 SSD with a new one (also a new gpu).

Hit the BSOD 5 or 6 times after enabling verifier -> rebooting -> launching destiny 2 and starting to do something in the game. No dump files generated but new Sysnative logs are attached!
 

Attachments

In the startup and recovery settings, can you change automatic dump to kernel memory dump and save it to %SystemRoot%\MEMORY.DMP. Then try driver verifier again.
 
I changed my system failure settings as you mentioned, hit a BSOD again -> no dump file generated :( Were you wanting me to BSOD 5 times then generate the Sysnative logs again?

system failure settings.PNG
 
Change dump file setting to to %SystemRoot%\MEMORY.DMP.
 
Sorry, i missed that. Updated the dump file path, hit the BSOD, no file generated.

system failure settings.PNG

Checking event viewer i am still getting Event ID 161 volmgr - Dump file creation failed due to error during dump creation. I assume this is why im not getting any dump files when im hitting that WHEA BSOD error?

Event Log ID 161.PNG
 
Today a friend was over and brought his GPU. I hooked it up and started the game and didnt BSOD. I was only able to use it for about 10-15 minutes, but i didnt BSOD the whole time. Does this mean my GPU is bad???
 
I was about to ask if you had any spare components available.

I would suggest that you try a different PCIe slot, performance may be impacted when doing this. A faulty GPU doesn't really explain why your computer cannot generate a dump file, but a problem with the motherboard does which is what I'm starting to suspect here.
 
I contacted Nvidia support yesterday to ask them about this. They had be try moving my gpu to another slot and try again. Still BSOD. Had be try changing some Nvidia settings. Still BSOD. Had me use their clean up tool. Still BSOD. Then they had me download and run a GPU stress test. I ran it for 15-20 seconds and my PC crashed, No BSOD. Then tried again in case it was a fluke, 10 seconds and it crashed it again. I let support know and waiting for a response.
 
Should receive an email in the next 24 hours to strat the RMA process. Will post back on how everything goes. Maybe this thread can help someone else in the future too.
 
finally got my RMA taken care of and received a new GPU (assume its refurbished). I just installed it, went to boot up to play a game, and unfortunately i am still BSODing... Assuming this means that my GPU is NOT the problem.. any further assistance would be much appreciated.
 
Need you to post new Sysnative logs, nobody can provide any decent suggestion without data.
 
Can definitely post new logs later today, but I'm still not generating dump logs.. still getting even if 161 like in post #25 too.
 
Hi!

I found errors in your logs about fast startup: open a command prompt as administrator, paste there the following command (and run it :-)):
Code: 
powercfg /h off
It won't give you a reply, but you will see, in your system drive, that hiberfil.sys disappeared.

Please uninstall NZXT CAM and ASUS AI SUITE altogether, possibly with revo uninstaller (there's also the portable version).

Then re-try the things you do to get bsods.
 
In your System log is this entry...
Code: 
Event[8054]:
  Log Name: System
  Source: volmgr
  Date: 2022-12-22T19:04:37.6670000Z
  Event ID: 49
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-QF9VLCQ
  Description:
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
Are you running with no paging file? Or, are you running with a manually configured paging file? WHEA writes dumps intitially to the paging file and if there is no paging file, or if it's not big enough, then no dump is created. Please set your paging file to 'System Managed'.

There is a 0xC4 (DRIVER_VERIFIER_DETECTED_VIOLATION) BSOD in your System log. Do you have Driver Verifier enabled? It would have been useful to see this dump...
Code: 
Event[3410]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2022-12-24T13:26:04.8170000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-QF9VLCQ
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c4 (0x0000000000000083, 0x00000000406640c5, 0x0000000000000024, 0x0000000000040664). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 0199af8c-83b2-4425-957c-1b6de1a7263d.
There is also a 0x50 (PAGE_FAULT_IN_NONPAGED_AREA) BSOD in your System log. These are almost always caused by a bad third-party driver...
Code: 
Event[6663]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2022-12-22T22:09:00.9060000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-QF9VLCQ
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffff87049fa76df0, 0x0000000000000000, 0xfffff80a88128933, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 38d6fad6-fa26-4a95-8d01-cd3a5326ec33.


In addition, in your System log, I can see the following error sequence - though I only see them once...
Code: 
Event[9637]:
  Log Name: System
  Source: Microsoft-Windows-UserPnp
  Date: 2022-12-21T13:23:48.4470000Z
  Event ID: 20003
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-QF9VLCQ
  Description:
Driver Management has concluded the process to add Service NVDisplay.ContainerLocalSystem for Device Instance ID PCI\VEN_10DE&DEV_2206&SUBSYS_146710DE&REV_A1\4&2AE1B128&0&0019 with the following status: 0.

Event[9638]:
  Log Name: System
  Source: Microsoft-Windows-UserPnp
  Date: 2022-12-21T13:23:45.8700000Z
  Event ID: 20003
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-QF9VLCQ
  Description:
Driver Management has concluded the process to add Service nvlddmkm for Device Instance ID PCI\VEN_10DE&DEV_2206&SUBSYS_146710DE&REV_A1\4&2AE1B128&0&0019 with the following status: 0.

Event[9639]:
  Log Name: System
  Source: Service Control Manager
  Date: 2022-12-21T13:23:45.5500000Z
  Event ID: 7031
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-QF9VLCQ
  Description:
The NVIDIA LocalSystem Container service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 6000 milliseconds: Restart the service.

Event[9640]:
  Log Name: System
  Source: Service Control Manager
  Date: 2022-12-21T13:23:45.5500000Z
  Event ID: 7023
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-QF9VLCQ
  Description:
The NVIDIA LocalSystem Container service terminated with the following error:
A generic command executable returned a result that indicates failure.
This makes me wonder whether the problem may be graphics card, or graphics driver, related? Given the large number of crashes in the System log I'm wondering whether this isn't more likely to be a hardware problem? In the absence of any other information I would be tempted to try and borrow another graphics card to test. Remember to use DDU to remove the existing drivers and then install the right driver for the testing card.
 
@ubuysa, just FYI that you're looking at data that's not all that interesting anymore since we've deduced that already previously.

@WellYes, do you remember the bugcheck that was shown?
 
@xilolee - I ran that command to turn off hibernation. Uninstalled nzxt cam and Asus ai suite. Retested and BSOD still.

@axe0 if by bug check you mean the bsod error, it is still the WHEA_UNCORRECTABLE_ERROR.

Yesterday I was wondering if why I wasn't creating dump files was a drive issue (even though everything has shown them in good health). I uninstalled my m.2 drive (my drive with windows) - installed windows on my HDD - installed destiny 2 - and was able to play for 5 minutes without bsoding. Since I usually bsod about a minute in, I went ahead and stopped.

Due to this, it makes me think that my m.2 could be bad? However, earlier in my testing I used a friend's GPU and I did not BSOD either - which led me to believe my GPU was the issue.. Now I have a new GPU (since it was RMA'd) and still BSOD. Does this make sense?? If my m.2 was bad wouldn't it of BSOD while using my friends GPU too?
 
Just to elaborate a bit, a bugcheck is the process behind the BSOD screen you see, bugcheck error and BSOD error are interchangeable synonyms in the typical context of the error code that is given.

Could you try a different M.2 port and see how that goes. I am starting to suspect the motherboard here. Multiple hardware components causing problems is not common.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top