Recent BSODs - WHEA_UNCORRECTABLE_ERROR

[SergNMerp]

Been having these BSODs lately, with the error 'WHEA_UNCORRECTABLE_ERROR'

First 3 bsods were while playing GTA:O a few weeks ago, all during one week's worth of time
then there were 2 bsods while playing The Long Drive a couple days ago
now there were 3 bsods within 15 minutes of each other while playing ETS2 (first 2 were while navigating the settings trying to setup my controller keybinds, last one was loading into the game itself)

There's almost nothing in Event Viewer about it, there's no minidump files about it, I tried a memory test from a bootable usb (the free passmark one), no errors, I don't know what to do now.
It's not the OS, as I've reinstalled the OS (full drive wipe and reinstall) after the 3 GTA:O bsods (reinstalled for different reason)
its not thermals, this cooler keeps it below 90

I was suspicious of the memory coz I've had issues with it before (had to exchange em at Micro Center a week after I got em, was part of a cpu/mb/ram bundle I got back in late feb, too late to do an exchange now)
slightly suspicious of the motherboard as the motherboard could've also been the cause of the issue in the line above

now I'm slightly suspicious of the cpu as the bsods seem to happen during a spike (either when I click on something in a game or fps drops for something) and it doesn't always happen but it tends to happen when something like that occurs

anyways, specs;
this micro center bundle (7900X, ROG B650E-F, some 2x16gb G.Skill Flare X5 something ram, see the link)
Arctic LF3 360 w/ MX-6 Paste
MSI 6650 XT
RM850x
980 Pro 2TB
idk if anything else is important, using dual monitors if it matters

current bios version is 2613, I know there's an updated version that I have sitting on a thumb drive ready to install but as it's not a stability update, just a performance update, I haven't been too bothered to update it
memory is running at about 4800 instead of the supported 6000 because there was some kinda issue the computer was having (similar to why I exchanged the memory & mobo back in march) if I had it set to 6000
no cpu overclocks to my knowledge, just letting the cpu do the max boost when it wants to, disabled asus's dumb AI overclocking thing idk I just have it at semi-default settings since default settings have the AI overclock enabled or something like that I'm not entirely sure honestly

I'm a little sleep deprived and I'm really sick and f-ing tired of this damn bsod issue so this post is probably gonna be all over the place and is likely missing some key details, my apologies in advance.
especially tired of it since my gaming laptop is at hp's repair center for another issue it's been having so I can't just use that to do what I need to do, and my other computers aren't fit for daily use at the moment

[Blasty Blosty]

Tried reinstalling windows?

[SergNMerp]

Just now, Blasty Blosty said:

Tried reinstalling windows?

y e s .

2 minutes ago, SergNMerp said:

It's not the OS, as I've reinstalled the OS (full drive wipe and reinstall) after the 3 GTA:O bsods (reinstalled for different reason)

 

[Blasty Blosty]

1 minute ago, SergNMerp said:

y e s .

 

Apologies, somehow missed the bold text

 

5 minutes ago, SergNMerp said:

slightly suspicious of the motherboard

I have heard some reports of the board being unstable, but I have the same one and had no issues so far

[SergNMerp]

1 minute ago, Blasty Blosty said:

I have heard some reports of the board being unstable, but I have the same one and had no issues so far

yeah, buncha reviews on the bundle of people having issues as well

after the exchange (of both the board and ram) it had the same issues for a little bit but those cleared up (I believe when I made the ram run at default 4800 instead of supported 6000)

uuuuuhhhhh

might as well do the bios update and maybe try and underclock the cpu maybe?
doubt it's the cpu since I've never had issues with it but a friend pointed out to me the 1.4 voltage or whatever seemed a little bit high, and me being unfamiliar with the 7000 series (previously mainly a iGPU guy, 2400G & 5700G) im not used to the higher temps n whatever for the X cpus

[Blasty Blosty]

2 minutes ago, SergNMerp said:

might as well do the bios update and maybe try and underclock the cpu maybe?
doubt it's the cpu since I've never had issues with it but a friend pointed out to me the 1.4 voltage or whatever seemed a little bit high, and me being unfamiliar with the 7000 series (previously mainly a iGPU guy, 2400G & 5700G) im not used to the higher temps n whatever for the X cpus

Yeah try the latest BIOS

 

I'm not sure about voltages, but I think I do also remember other people thinking they seemed high, guess they are just designed to run that way.

[SergNMerp]

Just now, Blasty Blosty said:

I'm not sure about voltages, but I think I do also remember other people thinking they seemed high, guess they are just designed to run that way.

Yeah, now that I think about it I might remember Steve (GN) mentioning something about it being normal in some video he did a bit ago, not entirely sure

anyways yeah, don't know if it's just ETS2 but I tried again and it bsoded again upon trying to load into the game

will try one more time and when it bsods imma just hard shutdown and do the bios update

[Blasty Blosty]

2 minutes ago, SergNMerp said:

Yeah, now that I think about it I might remember Steve (GN) mentioning something about it being normal in some video he did a bit ago, not entirely sure

anyways yeah, don't know if it's just ETS2 but I tried again and it bsoded again upon trying to load into the game

will try one more time and when it bsods imma just hard shutdown and do the bios update

Are there any games where it doesn't crash?

[Blasty Blosty]

@DoctorNick any suggestions?

[SergNMerp]

20 minutes ago, Blasty Blosty said:

Are there any games where it doesn't crash?

Ones I've been playing lately for a bit without it ever bsoding is really only FS22, I played some Terraria and TF2 with some friends yesterday but those games aren't really intensive enough to potentially cause an issue

TLD usually runs fine, it seemed to only happen during a game freeze (usual for the game as it's severely unoptimized, currently undergoing a year+ long update to optimize the game, but I've never had a bsod or even a simple game crash happen before from these second-long freezes)

[Blasty Blosty]

59 minutes ago, SergNMerp said:

its not thermals, this cooler keeps it below 90

Is this referring to CPU or GPU as well?

[SergNMerp]

1 minute ago, Blasty Blosty said:

Is this referring to CPU or GPU as well?

cpu, haven't checked gpu in a sec but from what i remember it runs fairly cool, I've never seen it get above 70 something even during a 3dmark stress test

[SergNMerp]

aaand yeah, bios update to 2616, zero impact on the bsod

[Bjoolz]

WHEA means a hardware issue with the CPU or a PCIe device. WHEA BSOD + no dump files makes the NVMe SSD the main suspect. When you crash because of storage, the storage drive is usually taken offline so it has nowhere to dump data to. There are other things that can prevent dump file creation like not enough room on the drive with the page file, if you have manually set a size for the page file it could be too small and encrypted storage (The dump process is outside of Windows so it can't access encrypted drives). We have two ways to go forward from here, you can of course do both. On the BSOD screen it dumps data to the page file and it creates the dump file from this on the next boot. So if you have multiple drives, moving the page file to a different drive could allow it to dump data and make you get dump files. NB: Don't use external storage for the page file, these are frequently powered down which would instantly crash the PC. 

 

The second thing is to change a registry setting to have the BSOD screen display more information. If it already hangs on the BSOD screen (As you can't get dump files) then this step is not necessary, but if it reboots normally after a few seconds then go to this guide and on this screen remove the check for automatically restart. To restart manually, just use the power button.

 

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner. If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard, but a faulty SSD is way more common.

 

Again, note that this is only applicable on WHEA BSODs.

[SergNMerp]

  

4 hours ago, Bjoolz said:

WHEA means a hardware issue with the CPU or a PCIe device. WHEA BSOD + no dump files makes the NVMe SSD the main suspect. When you crash because of storage, the storage drive is usually taken offline so it has nowhere to dump data to. There are other things that can prevent dump file creation like not enough room on the drive with the page file, if you have manually set a size for the page file it could be too small and encrypted storage (The dump process is outside of Windows so it can't access encrypted drives). We have two ways to go forward from here, you can of course do both. On the BSOD screen it dumps data to the page file and it creates the dump file from this on the next boot. So if you have multiple drives, moving the page file to a different drive could allow it to dump data and make you get dump files. NB: Don't use external storage for the page file, these are frequently powered down which would instantly crash the PC. 

 

The second thing is to change a registry setting to have the BSOD screen display more information. If it already hangs on the BSOD screen (As you can't get dump files) then this step is not necessary, but if it reboots normally after a few seconds then go to this guide and on this screen remove the check for automatically restart. To restart manually, just use the power button.

 

To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner. If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard, but a faulty SSD is way more common.

 

Again, note that this is only applicable on WHEA BSODs.

Alright, so the first thing, have done that according to the guide, just waiting for the next bsod

second bit, about that, previously when it crashed, the bsod screen was only on my screen for a half second before my computer immediately restarted, so I had to go into control panel and somewhere to disable the automatic restart after a bsod, so that's why I have to manually restart my pc (reset button on my case has finally come in handy for once), so I'll just assume that doesn't apply to my situation here...?

3rd bit, follow that, probably the most simple regedit thing I've had to change, also waiting on the next bsod for that to tell me what it is exactly

as for the bsod, somehow, idk how, but I launched ETS2 a few minutes ago and when I loaded into the game my computer somehow didn't bsod, every single time I tried to load into the game for the past 30 ish hours my computer bluescreened, and now after the regedit thing (I also installed samsung's ssd utility tool off of TechPowerUp and ran that a few times, it says no issues but I haven't tried the long-term tests yet since, well, I don't have the time for that right now), and blahblahblahblahblah

basically saying, this is a little update for what I've done/followed, now just waiting for when my computer decides to bsod again, and then I'll post whatever I find here.

WELL, WELL, WELL.

I was in the middle of editing this post when my computer decided to bsod once again (with ets2 open on my other monitor)
details in a new post because this one's long enough already

Edited July 11, 2024 by SergNMerp
added a missed word, rewrote a thing, and new fun fact :)

[SergNMerp]

 

4 hours ago, Bjoolz said:

The next time you BSOD, you should have these extra numbers in the top left corner. If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard, but a faulty SSD is way more common.

right, so, bsod info time
arg 1 unfortunately appears to be exactly what you said, the 0x000...010
page file or dump file or whatever you linked an article to change the location of the file to a different drive did nothing, same error in Event Viewer "Dump file creation failed due to error during dump creation" , event id 161, source volmgr

actually, looking at the event viewer details for the error above mentions EventData, something something something \Device\HarddiskVolume3 with a giant string of numbers below that

now, alongside the 980 Pro I do have a 2TB Seagate BarraCuda compute HDD for storage of stuff as well as a backup stuff (especially used it for backup when I reinstalled windows a week or so ago), and I think I've had issues with the drive before (long ago, late June 2021, computer often wouldn't boot to windows and BIOS said the drive was empy (1.81 TB free of 1.81 TB or something like that), so I took the drive to micro center and had them see if it would boot; if it did, I would buy a new motherboard, if not, new drive. It booted first try for them so I just got another motherboard, think from a ASRock B450 Pro4 to a Gigabyte Aorus B550 elite v2 or something like that and the problem was seemingly fixed, though upon later examination the Pro4 board seemed to be fine, got it working normally and sold it on ebay.
   I also had issues with the same drive in november of 2022 which is why I bought the 980 pro, because the hdd (C:/ drive at the time) was really really slow for some reason, even after a windows reinstall, so I figured the drive was failing and since the 980 pro was on sale for black friday I figured replace & upgrade it

I've still used the drive since it seems to be perfectly fine for general storage and whatnot, but idk

I don't think a non-C:/ drive would cause a bsod, but I have no idea, especially with how windows is nowadays.

unless HarddiskVolume3 is just a generic term for any storage device, then that could be it, and just to be safe, for the time being I'll disconnect that drive after I move some data that I might need off of it here in a bit.

[Bjoolz]

3 hours ago, SergNMerp said:

 

right, so, bsod info time
arg 1 unfortunately appears to be exactly what you said, the 0x000...010
page file or dump file or whatever you linked an article to change the location of the file to a different drive did nothing, same error in Event Viewer "Dump file creation failed due to error during dump creation" , event id 161, source volmgr

actually, looking at the event viewer details for the error above mentions EventData, something something something \Device\HarddiskVolume3 with a giant string of numbers below that

now, alongside the 980 Pro I do have a 2TB Seagate BarraCuda compute HDD for storage of stuff as well as a backup stuff (especially used it for backup when I reinstalled windows a week or so ago), and I think I've had issues with the drive before (long ago, late June 2021, computer often wouldn't boot to windows and BIOS said the drive was empy (1.81 TB free of 1.81 TB or something like that), so I took the drive to micro center and had them see if it would boot; if it did, I would buy a new motherboard, if not, new drive. It booted first try for them so I just got another motherboard, think from a ASRock B450 Pro4 to a Gigabyte Aorus B550 elite v2 or something like that and the problem was seemingly fixed, though upon later examination the Pro4 board seemed to be fine, got it working normally and sold it on ebay.
   I also had issues with the same drive in november of 2022 which is why I bought the 980 pro, because the hdd (C:/ drive at the time) was really really slow for some reason, even after a windows reinstall, so I figured the drive was failing and since the 980 pro was on sale for black friday I figured replace & upgrade it

I've still used the drive since it seems to be perfectly fine for general storage and whatnot, but idk

I don't think a non-C:/ drive would cause a bsod, but I have no idea, especially with how windows is nowadays.

unless HarddiskVolume3 is just a generic term for any storage device, then that could be it, and just to be safe, for the time being I'll disconnect that drive after I move some data that I might need off of it here in a bit.

 

Microsoft recently added SATA drives to WHEA events in Event Viewer, but I haven't seen a WHEA BSOD by one yet. Let's check if you have any WHEA events and see what they say. In Event Viewer, go to Windows Logs → System and on the right hand side select Filter Current Log. In the Event Sources dropdown menu, select "WHEA-logger". If you have any WHEA events, highlight them, right click and save. Upload the file here. 

[SergNMerp]

16 minutes ago, Bjoolz said:

 

Microsoft recently added SATA drives to WHEA events in Event Viewer, but I haven't seen a WHEA BSOD by one yet. Let's check if you have any WHEA events and see what they say. In Event Viewer, go to Windows Logs → System and on the right hand side select Filter Current Log. In the Event Sources dropdown menu, select "WHEA-logger". If you have any WHEA events, highlight them, right click and save. Upload the file here. 

hmmm, alright

even more suspicious of the HDD because, well, to my understanding, vol3 would be equivalent to what I see in file explorer; of which I had 3 different volumes, first one would be C:/, 2nd would be some random system reserved space I'm not sure how it got there, don't wanna delete it, and then the 3rd volume listed would be the HDD

since the last bsod I unplugged the drive and now there's just one volume listed in file explorer, C:/

anyways, here's that event viewer log file thing you wanted, I selected all of em, as far as I can tell it's all of the bsods ive had since I reinstalled windows (the 2 TLD bsods, the 5 ETS2 bsods from yesterday, and then 2 more from earlier today (currently 4:43 am)

all whea bsods since windows reinstall.evtx

[SergNMerp]

hmmm, yeah I'm pretty sure 'harddiskvol3' would indeed be the hard drive, just had a gander with diskpart and 3 volumes on boot drive, 3rd volume would indeed be the hdd

imma go play some games and see if I get another bsod or not since I don't have the hdd plugged in

as for my c drive only showing 511 megs free, dw about it, free space shown by diskpart here in cmd been bugging for a bit, I don't really pay any attention to it, my ssd is a little less than half full in reality - dunno why diskpart is showing that, did similar when I was putting a linux iso on a thumb drive for my workstation, kept buggin out so I used it to convert the file system and then actually format it with right click menu thing

Edited July 11, 2024 by SergNMerp
added context for seemingly low space according to diskpart

[SergNMerp]

WELL

yeah it bsoded again, playing gta, with the hdd disconnected

same info as before with the other bsods, same \Device\HarddiskVolume3 from volmgr even though there is no 3rd volume, unless it's counting volume 2 as volume 3, 0=1, 1=2, 2=3 kinda thing

 

yeaaaaaa

time to run samsung's long term ssd test while I sleep ig
and maybe try to contact em idk, they say there's a 5 year warranty for the thing and I've had it for almost 2 years, black friday 2022 is when I bought it from micro center

idk I'll wait for ya'lls response about it all before I go contacting samsung ig

whea bsod without extra hdd connected.evtx

[SergNMerp]

seems like this guy has a very similar if not exact same issue, bookmarking here for future reference idk
dunno if this was after the guy messed with his components, and seeing as how I haven't touched the internals of my pc since early march- actually no, since whenever I got the LF3 AIO, which was April 5th, so, few months, only started having these bsods recently, I'll reseat everything except the cpu since that arctic LF3 is a massive pain to mount (the mount being what's essentially a wide leaf spring) and see if that does anything, doubt it will but we'll see

just completed the scan, says all good, so either a reseat, or mobo issue? dunno still, have yet to reseat everything, again will do after I wake up 

[Bjoolz]

4 hours ago, SergNMerp said:

hmmm, alright

even more suspicious of the HDD because, well, to my understanding, vol3 would be equivalent to what I see in file explorer; of which I had 3 different volumes, first one would be C:/, 2nd would be some random system reserved space I'm not sure how it got there, don't wanna delete it, and then the 3rd volume listed would be the HDD

since the last bsod I unplugged the drive and now there's just one volume listed in file explorer, C:/

anyways, here's that event viewer log file thing you wanted, I selected all of em, as far as I can tell it's all of the bsods ive had since I reinstalled windows (the 2 TLD bsods, the 5 ETS2 bsods from yesterday, and then 2 more from earlier today (currently 4:43 am)

all whea bsods since windows reinstall.evtx 68 kB · 0 downloads

This event is pointing to the "NVMe Samsung SSD 980". So that is the main suspect. With storage WHEA, this is quite simple to check yourself as well because it puts the name of the drive into the error code in hex coded ASCII. So just convert the entire RawData field to ASCII (Link) and it will show the name if the drive. It will give you just gibberish at the beginning of the text as nothing else is ASCII, and then the drive at the end. 

 

1 hour ago, SergNMerp said:

just completed the scan, says all good, so either a reseat, or mobo issue? dunno still, have yet to reseat everything, again will do after I wake up 

It could still be the drive, SSDs have chips other than just the storage NAND chips that can go bad. But yes, re-seat the drive. Improper seating is quite common with M.2. If your board has multiple M.2 slot and you are using the one closest to the GPU, move it to one further away as the heat from the GPU can cause overheating. 

[SergNMerp]

3 hours ago, Bjoolz said:

This event is pointing to the "NVMe Samsung SSD 980". So that is the main suspect. With storage WHEA, this is quite simple to check yourself as well because it puts the name of the drive into the error code in hex coded ASCII. So just convert the entire RawData field to ASCII (Link) and it will show the name if the drive. It will give you just gibberish at the beginning of the text as nothing else is ASCII, and then the drive at the end. 

 

It could still be the drive, SSDs have chips other than just the storage NAND chips that can go bad. But yes, re-seat the drive. Improper seating is quite common with M.2. If your board has multiple M.2 slot and you are using the one closest to the GPU, move it to one further away as the heat from the GPU can cause overheating. 

Damn, alright.

I'll reseat it now, might as well move it while I'm at it, and I guess if it happens again, I'll have to contact Samsung warranty, eh?

[SergNMerp]

Aaannnndd yeah, reseated and relocated it, still bsods. Reseated & relocated it again since I needed to have a gander at the S/N for product registration, gonna go ahead and send in a warranty request or whatever the terminology is, would RMA fit best? idk

 

Will most certainly keep the new ssd not at the top slot anymore, seeing as said slot is between the gpu and the cpu, in fact right below the cpu by a couple inches.

[Bjoolz]

1 hour ago, SergNMerp said:

would RMA fit best?

Yes.