Question Four BSODs in the past 20 minutes ?

Toggle sidebar Toggle sidebar
Puddzz

Puddzz

Nov 26, 2024
7
0
10
As title says, I've had four BSODs in the past 20 mins or so, and I have a feeling it's my USB HDD, but it happened when it was unplugged. It could also have been my M.2 SSD enclosure which was still plugged in but I don't know.

Dump files: https://www.mediafire.com/file/qrf4r3gciko7c9k/Minidump.rar/file

System Specs
Motherboard: Gigabyte 650 Aorus Elite
CPU: Amd Ryzen 7 7800X3D
GPU: Gigabyte Gaming OC Geforce RTX 4090 24GB
RAM: Corsair Vengenace RBG 32GB (2 x16GB) DDR6-6000 cl30
PSU: MSI A1000g PCIe5 1000w 80+ Gold
OS: Windows 11
Storage:
Corsair mp600 G5 m.2-2280 PCie 4. x4 NVMe - 376gb filled
Corsair MP600 Core XT 2tb M.2-2280 PCIe 4.0 x4 - 1204gb filled
Corsair MP600 Core XT 2tb M.2-2280 PCIe 4.0 x4 - 1257gb filled
External
USB HDD: WD 4TB Elements portable external hard drive, USB 3.0 interface - about 2.7gb filled
USB m.2 Enclosure: Beikell M.2 NVME Enclosure - Kingston NV2 PCIe 4.0 NVMe m.2 - barely filled.

Both externals unplugged right now.

Whole system is about a year old.
 
Last edited:
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

= = = =

Dump files are useful and there are members here that are well versed in reading and understanding the dump files.

In the meantime, take a look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or even informational events being captured just before or at the time of the BSODs.

Post accordingly.
 
Ralston18 said:
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

= = = =

Dump files are useful and there are members here that are well versed in reading and understanding the dump files.

In the meantime, take a look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or even informational events being captured just before or at the time of the BSODs.

Post accordingly.
Click to expand...

Updated post. Sorry. Just wanted to get the post up before another BSOD happened.
 
Look for error codes.

If the BSODs just started then it is very likely that there will be some correspondng log entries.

Reliability History/Monitor is end user friendly and the timeline format may reveal patterns and, perhaps in your case, some sudden change that, in turn, is now causing problems.

Event Viewer requires more time and effort to navigate and understand. However, it can help as well.

FYI:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Log entries can be clicked for more details. The details may or may not prove helpful.

= = = =

Another possiblity is that something is coming loose.

Power down, unplug, open the case.

Carefully clean out dust and debris.

Verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place.

Use a bright flashlight to inspect for signs of damage: bare conductor showing, pinched or kinked wires, browned or blackened areas, melting, loose or missing screws, swollen components, corrosion, signs of moisture, etc..
 
From Reliability History:
Code: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffd70f8e0a3420, 0xffff9a84006e7b68, 0xffffd70fac5729a0). A dump was saved in: C:\Windows\Minidump\112624-24546-01.dmp. Report Id: c1ac953d-ff80-4d26-965a-3f15f59bdf93.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff9084587b9d60, 0xffffec0324247178, 0xffff908462eed810). A dump was saved in: C:\Windows\Minidump\112624-18562-01.dmp. Report Id: 2e523d07-a0b2-4fd0-bee0-2901ed117321.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffc80a5891cc90, 0xffffa181b683fb68, 0xffffc80a8ff03010). A dump was saved in: C:\Windows\Minidump\112624-32531-01.dmp. Report Id: 8dc504fd-1b0b-4946-bcff-e6d8d84369b3.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe607f6ec4ca0, 0xffffb28839087b68, 0xffffe60808e98670). A dump was saved in: C:\Windows\Minidump\112624-20375-01.dmp. Report Id: 95bfacbc-2b6d-4a13-84c7-2b0814942649.
 
Code: 
C:\Windows\System32>DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.4460

No component store corruption detected.
The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\System32>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.4460

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\System32>

Also log file for the sfc scan: https://www.mediafire.com/file/aro5bysl7rzpd9b/CBS.log/file
 
You're right that the problem is a USB device, but it's not your external HDD it's your USB wireless adapter. The dumps are all similar, all fail because a USB device failed a power transition request. From the dump we can see the IRP that managed the power trasisition and the driver that hung. Here's part of that output...
Rich (BB code): 
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffffe607f6ec4ca0 00000000 fffff8056ca1cf60-ffffe607fab2e0d0   
           \Driver\USBHUB3    UsbHub3!HUBPDO_WdmPnpPowerIrpCompletionRoutineForAsynchronousCompletion
            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffffe607f6ec4ca0 00000000 00000000-00000000   
           \Driver\USBHUB3
            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe607f74eb7e0 00000000 fffff805d6a9d540-19f7f3449ff8 Success Error Cancel pending
\Driver\RtkBtFilter RtkBtfilter
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 ffffe607f74eb7e0 00000000 00000000-00000000   
 \Driver\RtkBtFilter
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe607f70a7af0 00000000 fffff805660060f0-ffffe608128b67a0 Success Error Cancel pending
           \Driver\BTHUSB    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe608128b67a0   

            Args: 00000000 00000000 00000000 00000000
The RtkBtfilter.sys driver is the problem driver here, and it's hung during a Bluetooth operation (note the BTHUSB.sys driver call). The version you have installed is quite old now, dating from 2022...
Rich (BB code): 
4: kd> lmvm RtkBtfilter
Browse full module list
start             end                 module name
fffff805`d6a40000 fffff805`d6b14000   RtkBtfilter T (no symbols)          
    Loaded symbol image file: RtkBtfilter.sys
    Image path: RtkBtfilter.sys
Image name: RtkBtfilter.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Wed May 11 13:35:23 2022 (627B916B)
    CheckSum:         000D7CD1
    ImageSize:        000D4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

From the dump we can also obtain the address of the device node that describes the actual device, here's part of that output...
Rich (BB code): 
4: kd> !devnode ffffe607fab738a0
DevNode 0xffffe607fab738a0 for PDO 0xffffe607f6ec4ca0
  Parent 0xffffe607fa41d9a0   Sibling 0xffffe607f9511bf0   Child 0xffffe60805792810  
  InstancePath is "USB\VID_0BDA&PID_0852\00e04c000001"
  ServiceName is "BTHUSB"
  TargetDeviceNotify List - f 0xffffa183cdd02390  b 0xffffa183d227c690
  State = DeviceNodeStarted (0x30a) @ 2024 Nov 26 11:22:25.175
  Previous State = DeviceNodeEnumerateCompletion (0x30f) @ 2024 Nov 26 11:22:25.175
The USB\VID_0BDA&PID_0852 hardware IDs indicate the actual device. This is for a Realtek based USB WiFi/Bluetooth adapter - though it's probably badged as something else (TP-Link perhaps?). It's not impossible that it's the adapter itself that's at fault.


In summary, first look for an updated driver for this USB wireless adapter and if none is available condider replacing the adapter.
 
  • Like
Reactions: Ralston18
+1 for log files.

= = = =

Just a comment on the USB WiFi/Bluetooth adaper:

I have found that such adapters (especially wireless network adapters) tend to get very warm and even hot as they begin to fail.

Before booting up feel the adapter. Should simply be "room temperature" or so.

After booting up, continually keep carefully checking the adapter to determine if it is heating up.

A USB extension cable may prove helpful with both checking the adapter and keeping it cooler.

If an extension cable does not help cool things down and if an updated driver is not available then, indeed, replace the adapter.
 
Thanks for the replies and in depth analysis.
The thing is, I don't have a USB WiFi/Bluetooth adapter. My motherboard comes with WiFi but it's not USB. So I'll try updating that.

The only thing that I can think of that's USB and Bluetooth that was connected was a Xbox or Ps5 controller that was connected via my keyboard USB.

Oh and my pebble speakers can technically be connected via Bluetooth, but aren't right now. They are connected via USB

Edit: No idea how to update my bluetooth driver. Tried the motherboard manufactures driver and none of them show the driver being updated to the latest date. So imma just turn off bluetooth. I'm not using it at the moment anyways and pray.
 
Last edited:
the Bluetooth driver is usually updated with the normal wireless card driver.

All I'm able to determine from the dumps is that the problem is with the Bluetooth component of a Realtek based wireless card - but many vendors use Realtek components. Also, I can't tell just from the dumps what network connections you're using.

Can you please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
 
From there I can see that you appear to be running the Windows Subsystem for Linux (WSL) and it has its own virtual network connection that ultimately runs on your on-board LAN connection...

Here's your on-board LAN connection...
Code: 
Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Realtek Gaming 2.5GbE Family Controller
   Physical Address. . . . . . . . . : 74-56-3C-C6-A6-DA
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2a02:c7c:6a9a:5000:b009:780:f594:3793(Preferred) 
   IPv6 Address. . . . . . . . . . . : fdbf:b157:448c:0:62c4:8792:9a33:c6cd(Preferred) 
   Temporary IPv6 Address. . . . . . : 2a02:c7c:6a9a:5000:cd4:f904:9adc:bde2(Preferred) 
   Temporary IPv6 Address. . . . . . : fdbf:b157:448c:0:cd4:f904:9adc:bde2(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::2921:4adc:2e0:93e%2(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.128(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 27 November 2024 20:20:00
   Lease Expires . . . . . . . . . . : 29 November 2024 08:20:00
   Default Gateway . . . . . . . . . : fe80::8275:1fff:fe9f:a291%2
                                       192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 41178684
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2C-ED-D1-CF-74-56-3C-C6-A6-DA
   DNS Servers . . . . . . . . . . . : fdbf:b157:448c:0:8275:1fff:fe9f:a290
                                       192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
That's probably the one that the RtkBtfilter.sys driver will be running Bluetooth on, so that's the one I'd look for an update from on the motherboard vendor's website.

Here's your WSL virtual network connection...
Code: 
Ethernet adapter vEthernet (WSL (Hyper-V firewall)):

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
   Physical Address. . . . . . . . . : 00-15-5D-55-E5-F7
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d1d5:a302:4f94:df88%38(Preferred) 
   IPv4 Address. . . . . . . . . . . : 172.25.176.1(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 637539677
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2C-ED-D1-CF-74-56-3C-C6-A6-DA
   NetBIOS over Tcpip. . . . . . . . : Enabled
This doesn't appear to have a default gateway configured so may not be able to reach the Internet. Then again, what I know about WSL can be written on a postage stamp, so it may use the LAN connection for Internet access.

TBH, I would prefer that this WSL connection wasn't there at all. Is it at all possible for you to stop or disconnect WSL and see whether these BSODs still happen?
 
That might explain things for sure. I have a docker container running that has lan cababilities. I haven't used that one since the last BSOD and haven't had a BSOD since then. Although I have only been watching youtube videos and just a little bit of AI generating to see if my GPU would explode or something lol.

I know nothing about linux either, just docker was the easier way to setup that particular thing. Not a huge loss to have to stop using it.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom