multiple BSOD on new build

C

Colif

Member
Joined
May 23, 2025
Posts
16
Please find sysnative results
SysnativeFileCollectionApp.zip

I think its bad ram but I am just confirming.
PC is only 2 days old

Current build:
Ryzen 7 9800x3d
Gigabyte Aorus X870 Elite Wifi7 Ice
Samsung 990 Pro 2tb nvme
Samsung 990 Pro 4tb nvme
Powercolor Red Devil RX 7900XT 20gb
NZXT C1000 1kw Gold
32gb Gskill Trident Z5 Royal Neo DDR5 6000 CL28 Ram

I have only actually seen it crash once, last night,
Driver Power State Failure
but system info/windows error reporting shows more.

The reason I think its ram is... one stick doesn't seem to work properly.
Last night was my first time using it and it wouldn't let me change the rgb on it in the RGB Fusion program - it just stayed in rainbow mode
Then hours later (I only had 5 hours sleep the night before and was a little slow) I noticed HWINFO was reporting I was at 99% virtual memory usage, and thought that was odd.
Taskbar then showed that I was only running 16gb of ram.
The stick was completely AWOL.

So I turned PC off and next start it worked again, but I think I got that BSOD while it was attached.
It has been removed now, I am just running on 1 16gb stick but I don't know if BSOD are drivers or Hardware.
I don't think I have had any BSOD today but Sysinfo was showing about 6. I think I would notice a restart.

We thought about running memtest, might on Sunday. Hard to do if the stick isn't responding though.
Never seen ram not work, and then work again. SSD can do that but this is a first for me.

As far as I can tell I haven't crashed all day running on the one stick that hasn't played up. Probably arrange a replacement since I only got the ram last week.
 
I wasn't expecting to be able to attach files directly. Done :)

Also, One Memtest done: (4 passes)
C4hrqE3.jpeg

I sort of knew that stick was okay. Now I know.
 

Attachments

Is that a problem my end?
I ran SFC /scannow just then, showed nothing.
I also ran Repair-WindowsImage -Online -RestoreHealth just to be sure
both came back with no bad results.
Bitdefender full scan found nothing as well
 
I have looked at the results of the reports before so I can see why msinfo32 not working right is a problem.

I will run the collection app again - it skips the services and tracert reports as it says they too long to generate

have another attempt-

its possible installing with a bad stick may have corrupted some things. Windows just can't tell?
 

Attachments

Colif said:
I have looked at the results of the reports before so I can see why msinfo32 not working right is a problem.

I will run the collection app again - it skips the services and tracert reports as it says they too long to generate

have another attempt-

its possible installing with a bad stick may have corrupted some things. Windows just can't tell?
Click to expand...
Same error popup, I tried a different file application from another member on this forum and it took me to his computer info.
So the problem is on your end.
 
okay, thanks.

I will reinstall windows using a known working stick and see if that fixes all the BSOD. You can't see them in system info but I can.

System not acting right, its set up to create minidumps but I only have one. And yet Windows Error Reporting shows 26 in the last two days.
 
You've had a ton of BSODs but only one dump was uploaded. Where are the others? Please don't delete old dumps via any kind of disk cleanup tool.

The one dump you have is a 0x9F bugcheck indicating a power transition problem for a device or its driver. The dump shows us the IRP managing the power transition and we can see the failing driver there.
Rich (BB code): 
4: kd> !irp ffff9c81f15439a0
Irp is active with 19 stacks 16 is current (= 0xffff9c81f1543ea8)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

<snip, snip>

 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffff9c81e67c5d30 00000000 fffff8071298c800-ffff9c81dc1250d0 
           \Driver\USBHUB3    UsbHub3!HUBPDO_WdmPnpPowerIrpCompletionRoutineForAsynchronousCompletion
            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffff9c81e67c5d30 00000000 00000000-00000000 
           \Driver\USBHUB3
            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9c81dc58edc0 00000000 fffff80713b338a0-637e18623f18 Success Error Cancel pending
           \Driver\RtkBtFilter2    RtkBtFilter2
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 ffff9c81dc58edc0 00000000 00000000-00000000    
           \Driver\RtkBtFilter2
 Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9c81dc58cdc0 00000000 fffff8077cb9eca0-ffff9c81f62ad8e0 Success Error Cancel pending
 \Driver\BTHUSB nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff9c81f62ad8e0 

            Args: 00000000 00000000 00000000 00000000
I've highlighted the failing driver; RtkBtFilter2.sys. We can also see the device in this dump by following the device node chain...
Rich (BB code): 
4: kd> !devnode ffff9c81e79a9c10
DevNode 0xffff9c81e79a9c10 for PDO 0xffff9c81e67c5d30
  Parent 0xffff9c81dc38da10   Sibling 0xffff9c81e78a8820   Child 0xffff9c81e7555c40
  InstancePath is "USB\VID_0BDA&PID_8922\00E04C885A01"
  ServiceName is "BTHUSB"
  TargetDeviceNotify List - f 0xffffdd8a7bb73b90  b 0xffffdd8a83a92390
  State = DeviceNodeStarted (0x30a) @ 2025 May 22 14:00:07.409
  Previous State = DeviceNodeEnumerateCompletion (0x30f) @ 2025 May 22 14:00:07.409
  StateHistory[18] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[17] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[16] = DeviceNodeStarted (0x30a)
  StateHistory[15] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[14] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[13] = DeviceNodeStarted (0x30a)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[10] = DeviceNodeStarted (0x30a)
  StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[08] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[07] = DeviceNodeStarted (0x30a)
  StateHistory[06] = DeviceNodeStartPostWork (0x309)
  StateHistory[05] = DeviceNodeStartCompletion (0x308)
  StateHistory[04] = DeviceNodeStartPending (0x307)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x306)
  StateHistory[02] = DeviceNodeDriversAdded (0x305)
  StateHistory[01] = DeviceNodeInitialized (0x304)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  Flags (0x68000138)  DNF_REENUMERATE, DNF_ENUMERATED,
                      DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED,
                      DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS,
                      DNF_NO_UPPER_CLASS_FILTERS
  CapabilityFlags (0x00001e53)  DeviceD1, DeviceD2,
                                Removable, UniqueID,
                                SurpriseRemovalOK, WakeFromD0,
                                WakeFromD1, WakeFromD2
The InstancePath value I've highlighted contains the hardware ID of the device; USB\VID_0BDA&PID_8922. This is a Realktek USB Bluetooth adapter, probably part of a wireless networking card. Note that even though it's a USB device it may be on the motherboard rather than actually plugged in.

The driver at fault doesn't look that old but it would be wise to check for an update...
Code: 
4: kd> lmvm RtkBtFilter2
Browse full module list
start             end                 module name
fffff807`13b20000 fffff807`13b5c000   RtkBtFilter2 T (no symbols)           
    Loaded symbol image file: RtkBtFilter2.sys
    Image path: RtkBtFilter2.sys
    Image name: RtkBtFilter2.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Wed Sep  4 04:22:26 2024 (66D7B652)
    CheckSum:         0003FC7B
    ImageSize:        0003C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

If this really is a USB connected wireless card then uplug it and see whether the BSODs stop. If it's a motherboard device then disable it in Device Manager, reboot, and see whether the BSODs stop.

I can't really comment on the other BSODs you've had, except to say that they have all been 0x9F bugchecks and, from the parameters passed in each of the BSODs, they do look to be identical to the one we have a dump for. I'd be comfortable stating that all 9 BSODs that I can see in the logs were caused by the same USB Bluetooth device or the RtkBtFilter2.sys driver.
 
A BSOD doesn't always generate crash dumps, particularly when for example there are issues with either storage device or RAM. You could find out whether a crash dump was saved from the eventlogs, by searching on 'dump'. I typically do so through the WER section in msinfo32 since I find that easier to use, but since msinfo32 isn't available, I search the eventlogs and found only one record pertaining to the word 'dump' and for the Bugcheck event specifically. There's only one record present.

While we're figuring things out, I do recommend that you use the default SPD speed for your memory of 4800.
Code: 
[Memory Device (Type 17) - Length 100 - Handle 001bh]
  Physical Memory Array Handle  0011h
  Memory Error Info Handle      001ah
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          16384MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM 1
  Bank Locator                  P0 CHANNEL B
  Memory Type                   22h - Specification Reserved
  Type Detail                   4080h - Synchronous
  Speed                         6000MHz
  Manufacturer                  Unknown
  Serial Number                         
  Asset Tag Number              [String Not Specified]
  Part Number                   F5-6000J2836G16G

I do see other events related to crashes, the term 'crashes' here is broadly used and not exclusively referring to BSOD crashes. It also includes other types of abrupt shutdowns like a BSOD, forced shutdown after freeze or unexpected power loss. This resembles 5 crashes you say you had. Can you show us what you saw about Sysinfo indicating there are 6 crashes, so we better understand the situation.

1748081513197.webp
 
i know enough to not use any app that deletes Dumps. I used to try to answer these on another forum you use Ubuysa. I just came here as I figured I get your attention eventually.

I have been wondering why I only have one minidump. And yet
rOIAvdx.jpg

so many here.
I did wonder if it was a driver given it was 2 per startup. Network drivers did come to mind.
And that was when I updated the realtek WIFI drivers this afternoon after noticing I had old ones.
The BT drivers didn't seem to want to install so I had to do it via compatibility. Not sure if it worked or not. I went through the Aorus site for my motherboard and compared the drivers there to what I have. I had installed the latest packages today.

I relied on the person who built it to update a few things. He may have missed some things.

The wireless is part of the board.

We are updating the BIOS to latest version tomorrow and will leave it at defaults after.
Also running memtest on the stick that was acting strange on Thursday.

Will keep you informed :)

PC is currently off. So no new errors will occur until I start it again
 
Last edited:
That looks like it's the exact same thing that Ubuysa posted about, same parameters thus same device object thus same driver.
 
Cool. Hopefully its fixed.
If it comes back I can uninstall WIFI as I don't really use it. I do need Bluetooth so I will keep the antenna
I generally use ethernet anyway
 
only bsod recorded today were from same app.
I have disabled it in windows so shouldn't be running now.
I don't see it in Autoruns, as I went in there to disable it.
7tA58fg.jpeg

Both sticks cause no errors in Memtest.
Bios now on F4
Memory still at 4800 as requested
 
It's possible entries are hidden, click on either of these options in the screenshot (or under Options in the menu) for any option that has a blue background (indicating the corresponding items are hidden).
1748165621005.webp1748165688881.webp
 
Okay, it was in the hidden since its part of windows. Unusual for a Microsoft driver to cause errors.
I have unticked its blue checkmark so it shouldn't auto start. I know if a program wants to run it, it can... but with WIFI disabled it really shouldn't.

I looked at Sys info recently and there have been no new ones in recent restarts since I looked earlier today.

I will watch it for a few days.
Back to two sticks, the other one tested fine in memtest so I am just observing it as well to see if it goes awol again.
 
something funny going on with this PC.
it doesn't want to restart, it gets stuck and doesn't close down properly
its also not making dump files, the only one is still the one Ubuysa scanned

I mistakenly thought that driver was Wireless, not Bluetooth. Now it sort of makes sense, when I tried to install the latest one on the Aorus site, it wouldn't do it the first time and offered compatibility mode and then asked if it worked... I was in a rush and said yes... Bluetooth does work, I have been using it to run my music, but its clearly not working properly. Perhaps I need to uninstall that driver and try again.
I only realised this morning when I was getting no sound. I enabled it in Autoruns again and got sound back again.
Wonders what to do, I have newest drivers as far as I can tell
cglsAYA.jpeg

the chipset is: RTL8922AE
I can't find a realtek website that links to it.

Need to buy a cable I guess to run my speakers digitally. I had been intending to use BT to send sound to my Wiim Ultra and use my headphone amp to get sound.

its still crashing but not causing dumps, but at least I know what it is now.
 
I uninstalled the device and restarted windows to let windows find it again, now on an older version. See if it continues.
The restart bug seems to relate to Gigabyte Command Centre being set to auto start with windows. Hardware monitoring apps seem to cause an 0d error on startup on some boards.
 
Do you really need Gigabyte command centre? In my experience many of these board vendor tools cause niggly issues.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top