Question Frequent BSODs Especially when Gaming on Voice Chat

[FCASandChill]

My computer has been BSODing frequently lately. Sometimes it won't for a couple weeks but other times it will several times in a single day. This first started happening a while back after upgrading my GPU but has gotten more frequent lately.

Here's a link to some minidump files: https://drive.google.com/file/d/1SV3bLzYVWVebAi0dpJ6-ZoNQ5aDYfeEh/view?usp=sharing
Here's a link to the full dump file: https://drive.google.com/file/d/1x2X_3I6aIkNS1YGPbHP6KdhwFJ0Hc-Dl/view?usp=sharing

I've noticed that it happens more frequently while using discord voice chat and gaming, but it'll happen sometimes when not gaming too.

I tried running PRIME95 for hours without any errors and have swapped out the GPU and RAM with other parts I have and neither fixed the issue.

Here's my system specs:
AMD Ryzen 5 3600
AMD Radeon RX 6700 XT
Samsung SSD 850 EVO 250GB (I have the operating system on the 250GB SSD, and a lot of my games are on the 500 GB one)
Samsung SSD 850 EVO 500GB
16GB RAM (2x8 not sure on the type or model, but I think it's DDR4 2133.. I can open up the PC and look if it's important)
750W Power Supply (forget the brand but I can check if it's important)

If you have any ideas or things I could try, it'd be greatly appreciated.
Thanks!

 

[Lutfij]

Welcome to the forums, newcomer!

750W Power Supply (forget the brand but I can check if it's important)
750W is the advertised wattage of the unit. yes we'll need to know the make and model of the PSU as well as it's age.

16GB RAM (2x8 not sure on the type or model, but I think it's DDR4 2133.. I can open up the PC and look if it's important)
All you need to do is pass on the ram's stickered info and we can find the rest. You can also try and take a screenshot of CPU-Z's memory/SPD tabs.

You forgot to mention the make and model of your motherboard. Please include the BIOS version as well.

Since you're on Windows 10, what version(not edition) of the OS are you on?

 

[ubuysa]

Notwithstanding the excellent advice above, all three minidumps clearly reference a USB 3.0 device - and possibly a human interface device (HID) attached to a USB 3.0 port. We see both the usbxhci.sys driver (the Windows USB 3.0 root driver) and the hidusb.sys driver (the Windows human interface device root driver). We also see the Wdf01000.sys driver, this is the Windows Driver Foundation (WDF) root driver. Many third-party drivers (like HID drivers) are written using WDF libraries, these are managed by the Wdf01000.sys driver.

However, two of the dumps have bugcheck codes of 0x133 with an argument 1 value of 1, these can only be debugged with the full kernel dump. There is only ever one of these saved - for the most recent BSOD - and fortunately the kernel dump you uploaded is for one of these bugchecks. The bad news is that detailed analysis of this dump shows that Wdf01000.sys was the driver contributing most to the long running DPCs, with dxgkrnl.sys (the Windows DirectX kernel driver) a pretty distant second. No other drivers seem to have had a major contirubution to this BSOD. Unfortunately then, the kernel dump doesn't really help muich because we can't see what third-party driver(s) Wdf01000.sys was managing.

The one minidump that isn't a 0x133 is a 0x1E - KMODE_EXCEPTION_NOT_HANDLED, which indicates that a kernel mode function took an exception from which we were not able to recover. The exception was a 0xC0000005 (a memory access violation) caused by a stackpointer error in a Windows function (nt!KiTryUnwaitThread)...

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_nt!KiTryUnwaitThread

There are a number of potential causes, some of them hardware and some of them third-party driver related. I suggest that, the best thing to do right now is to respond to the hardware questions asked by @Lutfij, and also look for updated drivers for all HID devices you have. I also think it's worth running a memory test, just to eminiate RAM as a possible cause. Here's how to do that...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough).
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86, and do another four iterations. Even a single bit error is a failure.

I did look through the loaded drivers in your dumps for any third-party drivers that are old or that are unusual. One that is unnusual is Hamdrv.sys, a driver for the LogMeIn remote access product. This driver is very old, dating from 2015...

8: kd> lmDvmHamdrv
Browse full module list
start             end                 module name
fffff805`84210000 fffff805`8421e000   Hamdrv     (deferred)         
    Image path: \SystemRoot\System32\drivers\Hamdrv.sys
    Image name: Hamdrv.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Mar 30 16:28:42 2015 (55194F8A)
    CheckSum:         0000E45B
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would contact the vendor customer support and ask about an updated version of this driver and/or the product. I'm not claiming that this is the cause, there is no evidence of that, but this is a VERY old driver.

Once we have a full and complete list of your hardware, and if Memtest86 clears your RAM, we will look at other troubleshooting steps.

 

[FCASandChill]

Welcome to the forums, newcomer!

750W Power Supply (forget the brand but I can check if it's important)
750W is the advertised wattage of the unit. yes we'll need to know the make and model of the PSU as well as it's age.

16GB RAM (2x8 not sure on the type or model, but I think it's DDR4 2133.. I can open up the PC and look if it's important)
All you need to do is pass on the ram's stickered info and we can find the rest. You can also try and take a screenshot of CPU-Z's memory/SPD tabs.

You forgot to mention the make and model of your motherboard. Please include the BIOS version as well.

Since you're on Windows 10, what version(not edition) of the OS are you on?

The power supply is Corsair CX750. I'm not sure on the exact age, but I think approximately 7 years.



The motherboard is ASRock AB350 Pro4.

Welcome to the forums, newcomer!

750W Power Supply (forget the brand but I can check if it's important)
750W is the advertised wattage of the unit. yes we'll need to know the make and model of the PSU as well as it's age.

16GB RAM (2x8 not sure on the type or model, but I think it's DDR4 2133.. I can open up the PC and look if it's important)
All you need to do is pass on the ram's stickered info and we can find the rest. You can also try and take a screenshot of CPU-Z's memory/SPD tabs.

You forgot to mention the make and model of your motherboard. Please include the BIOS version as well.

Since you're on Windows 10, what version(not edition) of the OS are you on?

The power supply is Corsair CX750. I'm not sure on the exact age, but I think approximately 7 years. I have a spare PSU lying around I could try swapping out if you think that's the issue.

Here is a picture of the RAM stickered info:
https://drive.google.com/file/d/1htuY6K8kahmQpDaoDbZeEfkF5fmGEYie/view?usp=drivesdk

The motherboard is ASRock AB350 Pro4. The BIOS version is P5.8

The windows version is 10.0.19045

Please let me know if there's anything else that would be helpful!

 

[FCASandChill]

Notwithstanding the excellent advice above, all three minidumps clearly reference a USB 3.0 device - and possibly a human interface device (HID) attached to a USB 3.0 port. We see both the usbxhci.sys driver (the Windows USB 3.0 root driver) and the hidusb.sys driver (the Windows human interface device root driver). We also see the Wdf01000.sys driver, this is the Windows Driver Foundation (WDF) root driver. Many third-party drivers (like HID drivers) are written using WDF libraries, these are managed by the Wdf01000.sys driver.

However, two of the dumps have bugcheck codes of 0x133 with an argument 1 value of 1, these can only be debugged with the full kernel dump. There is only ever one of these saved - for the most recent BSOD - and fortunately the kernel dump you uploaded is for one of these bugchecks. The bad news is that detailed analysis of this dump shows that Wdf01000.sys was the driver contributing most to the long running DPCs, with dxgkrnl.sys (the Windows DirectX kernel driver) a pretty distant second. No other drivers seem to have had a major contirubution to this BSOD. Unfortunately then, the kernel dump doesn't really help muich because we can't see what third-party driver(s) Wdf01000.sys was managing.

The one minidump that isn't a 0x133 is a 0x1E - KMODE_EXCEPTION_NOT_HANDLED, which indicates that a kernel mode function took an exception from which we were not able to recover. The exception was a 0xC0000005 (a memory access violation) caused by a stackpointer error in a Windows function (nt!KiTryUnwaitThread)...

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_nt!KiTryUnwaitThread

There are a number of potential causes, some of them hardware and some of them third-party driver related. I suggest that, the best thing to do right now is to respond to the hardware questions asked by @Lutfij, and also look for updated drivers for all HID devices you have. I also think it's worth running a memory test, just to eminiate RAM as a possible cause. Here's how to do that...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough).
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86, and do another four iterations. Even a single bit error is a failure.

I did look through the loaded drivers in your dumps for any third-party drivers that are old or that are unusual. One that is unnusual is Hamdrv.sys, a driver for the LogMeIn remote access product. This driver is very old, dating from 2015...

8: kd> lmDvmHamdrv
Browse full module list
start             end                 module name
fffff805`84210000 fffff805`8421e000   Hamdrv     (deferred)        
    Image path: \SystemRoot\System32\drivers\Hamdrv.sys
    Image name: Hamdrv.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Mar 30 16:28:42 2015 (55194F8A)
    CheckSum:         0000E45B
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would contact the vendor customer support and ask about an updated version of this driver and/or the product. I'm not claiming that this is the cause, there is no evidence of that, but this is a VERY old driver.

Once we have a full and complete list of your hardware, and if Memtest86 clears your RAM, we will look at other troubleshooting steps.

Okay, thanks a bunch! I'll try running Memtest86 tonight and let you know the results. I'll try updating some drivers too.

 

[FCASandChill]

I ran Memtest86 and it did end up having an error! I replaced the RAM with some other RAM I had lying around then ran the test 2 more times and it passed both. That said, I had tried swapping out the RAM before and the PC was still crashing. I'll report back in a week or so to let you know if there have been any crashes and if so, I'll upload the dump file.

Thanks again for the help!