BSOD Errors: BTHport.sys

[msigtc]

I have been experiencing intermittent BSODs (once every week or so), and the logs always look pretty similar, but I'm not sure how to address the issue. I made a pastebin for the last log and was really hoping someone here could take a look and help me out. I think it is suggesting an issue with one of the BlueTooth drivers (BTHport.sys) or something called ACPI? (the computer is running Windows 11 Home). More details about the computer can be found here: Profile 42274a01 | Specified and I have run the SysnativeFileCollection app and attached the zip below.

· OS - Windows 11 Home
· x86 (32-bit) or x64 ? x64
· What was the original installed OS on the system? Windows 10?
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Pre-Installed
· Approximate age of system (hardware) < 1 year
· Approximate age of OS installation (if you know)< 1 year
· Have you re-installed the OS? No
· CPU: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics
· Video Card: NVIDIA GeForce RTX 4050 Laptop GPU and AMD Radeon 780M Graphic
· System Manufacturer: ASUS ROG Flow x13
· Exact model number (if laptop, check label on bottom): GV302X
Laptop or Desktop? Laptop

Any suggestions would be very appreciated!

Thanks so much.

 

[ubuysa]

Hello, and welcome to the forum!

From the dumps, both BSODs failed for the same reason. They're both a 0x9F stopcode (DRIVER_POWER_STATE_FAILURE) which happens when a device, or its driver, fails to complete a power transition (from idle low power to running high power) in a reasonable time. The dump provides us with both the address of the IRP handling the power transition and the address of the Device Object which represent the device involved.

The IRP reveals that the driver that was managing the transitioning device was WdmCompanionFilter.sys, a Windows Driver Model driver, which means this could be any device or driver using the WDM libraries.

>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 ffff900a6aae0de0 00000000 00000000-00000000    pending
           \Driver\WdmCompanionFilter
            Args: 00000000 00000001 00000004 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff900a6414de00 00000000 fffff80473e76120-ffff900a5c713340 Success Error Cancel pending
           \Driver\ksthunk    nt!PopRequestCompletion
            Args: 00000000 00000001 00000004 00000000

The Device Object address shows us information about the device, in particular the address of the Device Node...

3: kd> !devobj ffff900a6ad180a0
Device object (ffff900a6ad180a0) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\usbccgp DriverObject ffff900a5f083e10
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00003040
SecurityDescriptor ffffb300cc0440e0 DevExt ffff900a6ad181f0 DevObjExt ffff900a6ad18760 DevNode ffff900a7715da00
ExtensionFlags (0000000000)
Characteristics (0x00000180)  FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffff900a66711e10 \Driver\ACPI
Device queue is not busy.

The Device Node describes the actual device and its capabilities...

3: kd> !devnode ffff900a7715da00
DevNode 0xffff900a7715da00 for PDO 0xffff900a6ad180a0
  Parent 0xffff900a6003a940   Sibling 0xffff900a69d317a0   Child 0000000000
  InstancePath is "USB\VID_3277&PID_0018&MI_00\7&ae5a96&0&0000"
  ServiceName is "usbvideo"
  State = DeviceNodeStarted (0x30a) @ 2024 Mar 30 18:14:59.079
  Previous State = DeviceNodeStarted (0x30a) @ 2024 Mar 30 18:14:59.068
  StateHistory[11] = DeviceNodeAwaitingQueuedDeletion (0x310)
  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)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x0)
  StateHistory[14] = Unknown State (0x0)
  StateHistory[13] = Unknown State (0x0)
  StateHistory[12] = Unknown State (0x0)
  Flags (0x28000138)  DNF_REENUMERATE, DNF_ENUMERATED,
                      DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED,
                      DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS
  CapabilityFlags (0x00100690)  Removable, SilentInstall,
                                SurpriseRemovalOK, WakeFromD0,
                                SecureDevice

It's the hardware identifiers in the "InstancePath" above that describes the actual device. The USB\VID_3277&PID_0018 identifiers would appear to be your built-in webcam. You can see at the bottom of the above that the camera is capable of "WakeFromD0", which means it's capable of entering the D0 low power state and being woken from that when accessed. The 0x9F bugcheck would suggest that the camera (or the driver) has had problems waking from D0.

There isn't a specific driver for your webcam listed on the Asus driver website for your laptop model and no recent driver updates there either. If you have the Windows Fast Startup feature enabled (it's enabled by default) I would disable that. Windows Fast Startup hibernates the kernel on a shutdown and restores it on a reboot. Some third-party drivers don't play well with that. Fast Startup is a performance aid for HDDs and if your system drive is an SSD then Fast Startup is not needed.

If there is a Windows camera troubleshooter then run that. There is also an Asus help page with details on how to fix common webcam issues so I would suggest you take a look at those.

It may also be a problem caused by an app that uses the webcam, so check what webcam apps are running, especially any that run in the background.

 

[msigtc]

Dear ubuysa,

First, thank you so much for the thorough and interesting reply! I definitely did not know how to navigate the logs well enough to even have the webcam be on my radar as a possible culprit. Very interesting stuff and I really appreciate the time you took to reply.

I've looked into a few things on my end and, you were correct - the system did have fast startup enabled by default. I have disabled that.

In terms of webcam apps, I only have a few that use the camera at all (Chrome, Discord, and Zoom are the only ones that spring to mind readily). I did notice that the BSODs tended to occur when I was working in Chrome, but not doing anything related to the webcam at all, so I'm not sure what prompted the error. Every time I have used an app that accesses the camera, it seems to work as expected (turns on/turns off/etc).

I checked the Device Manager for the webcam instance (the device instance path USB\VID_3277&PID_0018&MI_00\7&AE5A96&0&0000 led me to the USB2.0 FHC UVC WebCam). Under General it says the device is working properly and, under events, there haven't been any timestamped issues since 2023-04-09.

Fingers crossed it was the fast startup feature causing issues. I'll update if the BSOD returns after making this change :)

 

[ubuysa]

Please keep us updated. Fast Startup can be a problem for may third-party drivers. I always recommend that if you have an SSD boot drive (even a SATA SSD) you don't need Fast Startup.

 

[msigtc]

Please keep us updated.

Hi ubuysa,
It was a very nice couple weeks but the computer did BSOD again on me this morning and the dump looked similar to what we saw before. I was hoping you might be able to take a look and see if anything sticks out to you? I reran the SysnativeFileCollection app, which I believe captures the BSOD dump file. Thanks so much for all your help!

 

[ubuysa]

From this one dump your problem would seem to be your webcam again. In the device node output we see this entry...

 InstancePath is "USB\VID_3277&PID_0018&MI_00\7&ae5a96&0&0000"

These are the hardware ids that identify the device as a Sonix Integrated Camera, that will be your webcam. There don't appear to be any drivers specific to the webcam on the Asus support website for your laptop, although there is a recent BIOS update. I wouldn't suggest updating the BIOS until you've exhausted all other possibilities. IMO BIOS updates should be the last thing you try.

It's possible that the cause may be an application that uses the camera and which is blocking it somehow. Try rebooting and ensuring that all camera apps are not active (check for apps that auto-start with Windows).

As a test you could try disabling the webcam in Device Manager and run with it disabled long enough to see whether you still get BSODs. I can also see that you already have a numnber of devices disabled; one that might have an impact on the webcam is this one...

ASUS System Control Interface v3    ACPI\ASUS2018\2&DABA3FF&0    This device is disabled.

I don't know what the 'Asus System Control Interface' actually does but laptops are highly integrated devices and it's not impossible that you actually need this enabled.

The Asus support website contains a number of FAQs, one of which I've suggested already, but you might want to look through this one: MyAsus System Diagnostics