BSOD only while gaming, no dump created

[BeastChan23]

Hey folks I've been having issues with my system as of earlier this week where there was a power outage, a nearby transformer blew during a thunderstorm.
I've had my system behind a surge protector for years.

However I noticed issues when I couldn't play any games anymore, I'd get a bluescreen referring to WHEA Uncorrectible.
I also noticed before then my secondary drive would not let me access it anymore, I couldn't get past the root directory after a few minutes of the system being booted.
So I figured the drive died. it's a WD SN750 I've had since about 2018 or so. Swapped it out with a Intel 670p since it's just a secondary drive and I just use it for games, nothing important. Installed Solidigm software and updated firmware.

I could finally access files normally again, so installed games, and ran them. Still blue screens with the same error after about a minute or two in game.
Still no dump.

Took the old WD SN750 drive and did a clean install of Windows 11, rinse and repeat after trying to run a game, blue screens, but error is briefly flashed on screen so I don't know if it's any different. No dump.
Wiped drive and installed Windows 10, and had the exact same issue. I noticed an Intel device having issues in the log in regards to the driver, updated Intel NIC driver, did not resolve the issue.

Booted into motherboard and disabled Intel NIC and Thunderbolt.
Issue disappeared, and could finally launch and play games again.

So I reinstalled the original boot drive, installed a clean copy of Windows 10, and while installing applications with Ninite, I got a bluescreen again, same error. No dump.

RMA'd the drive and sent in the mail yesterday, as I imagine that also died during the outage.

Reinstalled WD SN750 and running fine for a few days.
Tried to do my daily gaming chores today, and after 5 minutes I ge the same blue screen error, no dump yet again.

I've run CPU, GPU and memory stree tests without any issues.
Chkdsk reports no issues with any of my drives, and SMART reports the drives are healthy.
I'm completely out of ideas other than Motherboard or CPU being the problem here.


Ryzen 5900x - Undervolted via PBO -30 offset
Crucial 2x16GB of ram (32GB)
ADATA S70 Blade 1TB/WD SN750 1TB/Intel 670p 2TB/Crucial MX500 2TB
Gigabyte RTX 3080 Vision OC
Gigabyte B500 Vision D-P, BIOS F16a, F16b
Corsair RM750w

At this point I'm even considering getting a new board and CPU, but I'd rather not spend around $500 if possible at the moment
Cannot provide any dumps since they fail the generate every single time, Perf Mon does not generate a report after 20+ minutes of waiting.

[Hinjima]

2 minutes ago, BeastChan23 said:

Hey folks I've been having issues with my system as of earlier this week where there was a power outage, a nearby transformer blew during a thunderstorm.
I've had my system behind a surge protector for years.

However I noticed issues when I couldn't play any games anymore, I'd get a bluescreen referring to WHEA Uncorrectible.
I also noticed before then my secondary drive would not let me access it anymore, I couldn't get past the root directory after a few minutes of the system being booted.
So I figured the drive died. it's a WD SN750 I've had since about 2018 or so. Swapped it out with a Intel 670p since it's just a secondary drive and I just use it for games, nothing important. Installed Solidigm software and updated firmware.

I could finally access files normally again, so installed games, and ran them. Still blue screens with the same error after about a minute or two in game.
Still no dump.

Took the old WD SN750 drive and did a clean install of Windows 11, rinse and repeat after trying to run a game, blue screens, but error is briefly flashed on screen so I don't know if it's any different. No dump.
Wiped drive and installed Windows 10, and had the exact same issue. I noticed an Intel device having issues in the log in regards to the driver, updated Intel NIC driver, did not resolve the issue.

Booted into motherboard and disabled Intel NIC and Thunderbolt.
Issue disappeared, and could finally launch and play games again.

So I reinstalled the original boot drive, installed a clean copy of Windows 10, and while installing applications with Ninite, I got a bluescreen again, same error. No dump.

RMA'd the drive and sent in the mail yesterday, as I imagine that also died during the outage.

Reinstalled WD SN750 and running fine for a few days.
Tried to do my daily gaming chores today, and after 5 minutes I ge the same blue screen error, no dump yet again.

I've run CPU, GPU and memory stree tests without any issues.
Chkdsk reports no issues with any of my drives, and SMART reports the drives are healthy.
I'm completely out of ideas other than Motherboard or CPU being the problem here.


Ryzen 5900x - Undervolted via PBO -30 offset
Crucial 2x16GB of ram (32GB)
ADATA S70 Blade 1TB/WD SN750 1TB/Intel 670p 2TB/Crucial MX500 2TB
Gigabyte RTX 3080 Vision OC
Gigabyte B500 Vision D-P, BIOS F16a, F16b
Corsair RM750w

At this point I'm even considering getting a new board and CPU, but I'd rather not spend around $500 if possible at the moment
Cannot provide any dumps since they fail the generate every single time, Perf Mon does not generate a report after 20+ minutes of waiting.

Are you able to download Bluescreenview? It will log what files caused the issue during BSOD.  WHEA Uncorrectible usually indicates a hardware failure.

[BeastChan23]

1 hour ago, Hinjima said:

Are you able to download Bluescreenview? It will log what files caused the issue during BSOD.  WHEA Uncorrectible usually indicates a hardware failure.

Absolutely nothing is captured.

[Bjoolz]

4 hours ago, BeastChan23 said:

However I noticed issues when I couldn't play any games anymore, I'd get a bluescreen referring to WHEA Uncorrectible.

WHEA means an issue with the CPU or a PCIe device. When you don't get dump files and get WHEA crashes, the main suspect is the NVMe drive as that uses PCIe.

 

If you want to make sure, do the following: "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. I want a picture of this.

 

If the top line says "Arg1: 0x0000000000000010" then it's the NVMe drive. Note that it can't tell the difference between the drive itself, the board or the slot. The SSD being way more common. 

 

If you get something else than that string at Arg1, take a picture of the BSOD screen.

[BeastChan23]

11 hours ago, Bjoolz said:

WHEA means an issue with the CPU or a PCIe device. When you don't get dump files and get WHEA crashes, the main suspect is the NVMe drive as that uses PCIe.

 

If you want to make sure, do the following: "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. I want a picture of this.

 

If the top line says "Arg1: 0x0000000000000010" then it's the NVMe drive. Note that it can't tell the difference between the drive itself, the board or the slot. The SSD being way more common. 

 

If you get something else than that string at Arg1, take a picture of the BSOD screen.

Thanks, will do this after work, I forgot to mention with the original SSD (Adata) after the BSOD I'd get kicked to BIOS as the drive was no longer detected. However with the WD drive this doesn't occur.

[Bjoolz]

4 hours ago, BeastChan23 said:

Thanks, will do this after work, I forgot to mention with the original SSD (Adata) after the BSOD I'd get kicked to BIOS as the drive was no longer detected. However with the WD drive this doesn't occur.

And I noticed that it did not come across that well in the original post, so just to be clear, when I say NVMe here, that's what it blames. It could equally be the motherboard/port. It's just that a bad SSD is more common. 

[BeastChan23]

1 hour ago, Bjoolz said:

And I noticed that it did not come across that well in the original post, so just to be clear, when I say NVMe here, that's what it blames. It could equally be the motherboard/port. It's just that a bad SSD is more common. 

I understand, I'd imagine it's likely the board, as it happens with both a gen 3, and gen 4 drive, but much more quickly with the gen 3 drive as I didn't even need to be running a game for it to crash last time I tried it.
Still I RMA'd the gen 4 drive already and will hopefully get a replacement if they find anything wrong with it.
I messaged Gigabyte in regards to the motherboard but I am still waiting for a response.

At any rate, got the error to pop up again, had to set the game's graphics higher today for some reason as opposed to it crashing with my normal settings all day yesterday.

[Bjoolz]

On 5/16/2023 at 12:01 AM, BeastChan23 said:

I understand, I'd imagine it's likely the board, as it happens with both a gen 3, and gen 4 drive, but much more quickly with the gen 3 drive as I didn't even need to be running a game for it to crash last time I tried it.
Still I RMA'd the gen 4 drive already and will hopefully get a replacement if they find anything wrong with it.
I messaged Gigabyte in regards to the motherboard but I am still waiting for a response.

At any rate, got the error to pop up again, had to set the game's graphics higher today for some reason as opposed to it crashing with my normal settings all day yesterday.

Yeah, it blames the NVMe. If your board has multiple M.2 slots you could try the other one. 

[BeastChan23]

6 minutes ago, Bjoolz said:

Yeah, it blames the NVMe. If you board has multiple M.2 slots you could try the other one. 

I should probably note, this happens regardless of which drive has the game installed on. Both NVME, and a SATA SSD

I suppose I could swap the boot drive to the secondary slot, will give it a shot

[Bjoolz]

9 hours ago, BeastChan23 said:

I should probably note, this happens regardless of which drive has the game installed on. Both NVME, and a SATA SSD

I suppose I could swap the boot drive to the secondary slot, will give it a shot

If it still crashes you can try updating the BIOS of the motherboard and the firmware of the SSD. If it still crashes after that a faulty SSD is the main suspect (The NVMe), but it could be the board. Faulty SSD is way more common.

[BeastChan23]

Board is on the latest version BIOS.

The issue has happened with more than one SSD, including a new one.

Gonna go to my local micro center and get a new board, still haven't heard back from gigabyte, and the SSD I RMA'd arrived at Adata's office yesterday, will have to wait and see what they say.

If the issue still happens with a new board then I can certainly say it's the SSD's at fault, but is still odd to me all of them would go out, and even a new one would also have issues.

[BeastChan23]

Swapped out motherboard, no issues yet, should do further testing though.

[BeastChan23]

Bringing this back from the dead as the issue still hasn't been resolved.
RMA'd motherboard, they claimed nothing was wrong and sent it back, got it this past weekend, swapped out the motherboard and returned the perfectly functioning replacement board I was using temporarily.

Day 1 with old motherboard, everything seems fine, even plays games without blue screens.
Day 2 Realtek NIC dies

Day 3 (today) Intel NIC dies, WIFI is also not available anymore, it's like those devices were ripped out and no longer exist.

Installing new drivers doesn't resolve the issue, made sure both NICs are enabled in BIOS, but noticed the Realtek NIC doesn't have any options in the BIOS anymore, and neither NIC shows a MAC address.

At this point I'm blaming Gigabyte for the board having these issues, but they claimed nothing was wrong with it.