Question BSODs again, have multiple bug check codes.

[lunatrifx]

Hi everyone!

I’m not getting any resolutions with my BSOD problems; to recap, I was the one who said that I had BSODS all of a sudden last week and only became more prominent with Malwarebytes and Windows Defender deep scans.

Now Malwarebytes and Windows Defender seem to be fine after a couple rounds, but the BSODs now come randomly; I got it after I idled in GTA IV. I played for about an hour and a half; this didn’t happen yesterday after I played for two hours.

The error was said to be KMODE_EXCEPTION_NOT_HANDLED, and I got 4 bug checks: 0xFFFFFFFFC0000006, 0xFFFFF805A2C86695, 0xFFFFA7092DFF6D08, and 0xFFFFA7092DFF64F0.

This is tough as I still didn’t get a chance to resolve my last BSOD which said CRITICAL_PROCESS_DIED with bug checks: 0xFFFFE082C5F9B140 and 0x0000000000000000.

I am running MemTest86, the only test I have not run in my troubleshooting. I’m planning on doing my two sticks individually, then both of the together.

Any help would be appreciated!

 

[bba-tcg]

Hi everyone!

I’m not getting any resolutions with my BSOD problems; to recap, I was the one who said that I had BSODS all of a sudden last week and only became more prominent with Malwarebytes and Windows Defender deep scans.

Now Malwarebytes and Windows Defender seem to be fine after a couple rounds, but the BSODs now come randomly; I got it after I idled in GTA IV. I played for about an hour and a half; this didn’t happen yesterday after I played for two hours.

The error was said to be KMODE_EXCEPTION_NOT_HANDLED, and I got 4 bug checks: 0xFFFFFFFFC0000006, 0xFFFFF805A2C86695, 0xFFFFA7092DFF6D08, and 0xFFFFA7092DFF64F0.

This is tough as I still didn’t get a chance to resolve my last BSOD which said CRITICAL_PROCESS_DIED with bug checks: 0xFFFFE082C5F9B140 and 0x0000000000000000.

I am running MemTest86, the only test I have not run in my troubleshooting. I’m planning on doing my two sticks individually, then both of the together.

Any help would be appreciated!

MemTest86 is the best place to start, for sure.

 

[lunatrifx]

I just completed 4 passes with MemTest86, no errors. Now I’m trying to get the dump files on my external drive. I’ll get back to you on this.

 

[Quintessa]

MemTest first (good call), then drivers, then storage. Your BSODs look like classic "RAM or driver is feeding garbage to Windows", not a random Windows corruption.

I just completed 4 passes with MemTest86, no errors. Now I’m trying to get the dump files on my external drive. I’ll get back to you on this.

Other angles worth checking:

• Uninstall Malwarebytes temporarily; even if scans are clean, its real-time hooks can trip kernel crashes.
• Disable Fast Boot & XMP in BIOS for testing; XMP can push marginal RAM over the edge.
• If you can grab the .dmp files from C:\Windows\Minidump, run them through WinDbg (!analyze -v), it will usually name the exact driver crashing.

 

[lunatrifx]

MemTest first (good call), then drivers, then storage. Your BSODs look like classic "RAM or driver is feeding garbage to Windows", not a random Windows corruption.


Other angles worth checking:

• Uninstall Malwarebytes temporarily; even if scans are clean, its real-time hooks can trip kernel crashes.
• Disable Fast Boot & XMP in BIOS for testing; XMP can push marginal RAM over the edge.
• If you can grab the .dmp files from C:\Windows\Minidump, run them through WinDbg (!analyze -v), it will usually name the exact driver crashing.

I did uninstall Malwarebytes through their Support Tool and did a reinstall through that as well. It seems to be no longer a factor (alongside Windows Defender) as full scans don’t seem to hang the computer anymore.

Fast boot has been off previously as BSODs are only there for only half a second (I might get it confused with the “restart on error” box where you can create memory dumps so I’ll check on that later). XMP might also be off (any overclocks, especially GPU, have been reset but I’ll check on this too).

I also was able to use Windbg not on dump files but Watchdog files; it blamed some DX and NVIDIA drivers. I also got a usbxhci.sys driver error. Luckily, NVIDIA just released drivers today so I did a clean install.

I gamed for about 2 hours and it’s pretty stable, no BSODs. But the day before, I did get a BSOD after the same amount of time.

If I do BSOD again, I might be able to get actual memory dumps since I switched the directory to my external SSD.

 

[Quintessa]

XMP might also be off (any overclocks, especially GPU, have been reset but I’ll check on this too).

- If XMP is still on, try one run with JEDEC (stock) speeds. Sometimes BSODs are just marginal IMC + RAM instability.
- “Restart on error” toggle is the one that matters for actually seeing dumps instead of insta-reboots, so double-check that.

I also was able to use Windbg not on dump files but Watchdog files; it blamed some DX and NVIDIA drivers. I also got a usbxhci.sys driver error.

- That paints a picture: NVIDIA driver and USB host controller (usbxhci) were both in the stack.
- USBxHCI.sys BSODs are often motherboard-level (chipset/BIOS), especially on Ryzen boards. Might be worth:

• Chipset driver reinstall.
• USB selective suspend = OFF in power settings (Windows loves to choke on this).

Luckily, NVIDIA just released drivers today so I did a clean install.

Clean driver install + stability for hours is promising, but if you BSOD again, we'll want a fresh minidump to confirm if DX/NVIDIA keep popping up.

I might be able to get actual memory dumps since I switched the directory to my external SSD.

Smart move, just be sure the dump type is "Automatic memory dump" (or "Kernel dump"), and the SSD is always connected.

 

[lunatrifx]

- If XMP is still on, try one run with JEDEC (stock) speeds. Sometimes BSODs are just marginal IMC + RAM instability.
- “Restart on error” toggle is the one that matters for actually seeing dumps instead of insta-reboots, so double-check that.


- That paints a picture: NVIDIA driver and USB host controller (usbxhci) were both in the stack.
- USBxHCI.sys BSODs are often motherboard-level (chipset/BIOS), especially on Ryzen boards. Might be worth:

• Chipset driver reinstall.
• USB selective suspend = OFF in power settings (Windows loves to choke on this).

Clean driver install + stability for hours is promising, but if you BSOD again, we'll want a fresh minidump to confirm if DX/NVIDIA keep popping up.


Smart move, just be sure the dump type is "Automatic memory dump" (or "Kernel dump"), and the SSD is always connected.

I got around to implementing the suggestions you put down, and everything seems to be working great now! I’ll still monitor it since other forums have said issues can be fixed for 2-3 weeks before they come up again.

It more than likely was the graphics driver and I went for a longer gaming session today and with more intensive games (Death Stranding), no slowdowns or BSODs. I’ll do more research if graphics drivers can cause a BSOD that creates a missing boot drive.