Question Windows BSOD

Toggle sidebar Toggle sidebar
R

Rui Neves

Distinguished
Sep 20, 2014
1,133
22
19,315
I had a BSOD today ,the dump file of windows says that this time the culprit is BTHport.sys , After a google research I foud out that is bluetooth related , I have a bluetooth adapter for a long time already and never had this issues , could be a software problem or can be also related to the adapter itself ?

What Can I do in case of software issue ?

PC specs :
AOC monitor with 21" and freesync , 75hz
Gigabyte b450 gaming X
AMD Ryzen 5 3600
Kingston HyperX FURY DDR4 (with RGB) at 3200mhz with XMP profile 1 enabled
XFX RX 580 GTS XXX 4gb
Bitfenix formula gold 550w
3 hdd´s from WD , 1 wd green , 1wd black ,1 wd blue
1 ssd ( kingston a400 120gb)



DUMP FILE TEXT :

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Documentos\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 100

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff80354600000 PsLoadedModuleList = 0xfffff80355229bc0
Debug session time: Tue Feb 22 21:54:33.882 2022 (UTC + 0:00)
System Uptime: 0 days 0:15:18.513
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
8: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffc00f5f435d90, Physical Device Object of the stack
Arg3: fffffa096a08b7d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc00f6ca2da20, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffffc00f5f2be040 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2280 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2374 Key : Analysis.Init.CPU.mSec Value: 3046 Key : Analysis.Init.Elapsed.mSec Value: 63183 Key : Analysis.Memory.CommitPeak.Mb Value: 152 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 DUMP_FILE_ATTRIBUTES: 0x1000 BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffc00f5f435d90 BUGCHECK_P3: fffffa096a08b7d0 BUGCHECK_P4: ffffc00f6ca2da20 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffc00f5f2be040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: fffffa096a01b140 fffff803549327f7 : ffffe68100000000 0000000000000000 0000000000000020 0000000000000000 : nt!KiSwapContext+0x76 fffffa096a01b280 fffff803549346a9 : ffffc00f0000000a ffffc00f00000001 fffffa096a01b460 fffffa0900000000 : nt!KiSwapThread+0x3a7 fffffa096a01b360 fffff8035492e5c4 : ffffc00f00000000 ffffc00f00000000 ffffc00f00000000 0000000000000000 : nt!KiCommitThreadWait+0x159 fffffa096a01b400 fffff803644bac05 : ffffc00f66c67110 fffff80300000000 0000000000000000 ffffc00f66c67c00 : nt!KeWaitForSingleObject+0x234 fffffa096a01b4f0 fffff803644baa18 : ffffc00f66c670a8 0000000000000001 0000000000000001 0000000000000001 : BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopReaderAndWriter+0xa1 fffffa096a01b530 fffff803644a4e70 : ffffc00f66c67050 0000000000000003 ffffc00f66c670a8 ffffc00f66cd4e00 : BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopInternal+0x60 fffffa096a01b590 fffff803644a4f57 : 0000000000000003 fffffa096a01b800 0000000000000000 ffffc00f00000000 : BTHport!Microsoft::Bluetooth::BthCoreCx::Fdo::EvtCxDevicePreD0Exit+0x17c fffffa096a01b600 fffff803561a5730 : 000000000000031a ffffc00f66cb5cc0 fffff803561b6700 0000000000000000 : BTHport!Microsoft::Bluetooth::BthCoreCx::Fdo::EvtCxDevicePreD0ExitThunk+0x17 fffffa096a01b630 fffff80356159461 : ffffc00f66c787a0 0000000000000000 ffffc00f66c67a28 fffff8035612b812 : Wdf01000!FxPnpDeviceD0Exit::InvokeCxCallback+0x30 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 328] fffffa096a01b690 fffff80356156dae : ffffc00f66c67ce8 ffffc00f66cd4c90 ffffc00f66c67770 000000000000031c : Wdf01000!FxPrePostCallback::IssuePreCxCallbacksStateless+0x53 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 478] fffffa096a01b6c0 fffff8035612d0b1 : 0000000000000000 0000000000000003 0000000000000003 ffffc00f66c67770 : Wdf01000!FxPrePostCallback::InvokeStateless+0x29886 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 414] fffffa096a01b6f0 fffff8035612e75b : 0000000000000000 fffffa096a01b890 fffff803561b6740 0000000000000000 : Wdf01000!FxPkgPnp::PowerGotoDxIoStoppedCommon+0xf1 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3100] fffffa096a01b760 fffff80356136b66 : 000000000000031c fffff803561b6ee0 ffffc00f66c67770 0000000000000000 : Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0xb [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 2842] fffffa096a01b790 fffff80356136d20 : 0000000000000340 ffffc00f66c67770 ffffc00f66c67770 0000000000000340 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x142 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699] fffffa096a01b8e0 fffff803561359ee : ffffc00f66c67770 0000000000000000 0000000000000000 fffff8035612b800 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xdc [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1613] fffffa096a01b960 fffff8035612c839 : 0000000000000000 ffffc00f66c67770 fffffa096a01bad0 0000000000000016 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x142 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1394] fffffa096a01b9f0 fffff8035612c655 : ffffc00f66c67770 fffffa096a01bab8 0000000000000004 0000000000000000 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x6d [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 350] fffffa096a01ba40 fffff8035612b458 : ffffc00f66c67770 0000000000000016 fffffa096a01bac0 fffff803549a1d29 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x25 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 120] fffffa096a01ba70 fffff80356123d82 : ffffc00f6ca2da20 ffffc00f6ca2da20 0000000000000000 0000000000000016 : Wdf01000!FxPkgPnp::Dispatch+0xd8 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 771] fffffa096a01bae0 fffff803549abb67 : 0000000000000000 ffffc00f5f2be040 ffffc00f6ca2da20 0000000000000000 : Wdf01000!FxDevice::DispatchWithLock+0x152 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] fffffa096a01bb50 fffff803548478f5 : 0000000000000000 fffff803549ab960 0000000000000000 00000000000000d8 : nt!PopIrpWorker+0x207 fffffa096a01bbf0 fffff80354a1a2d4 : ffffe681e5560180 ffffc00f5f2be040 fffff803548478a0 0000000000000000 : nt!PspSystemThreadStartup+0x55 fffffa096a01bc40 0000000000000000 : fffffa096a01c000 fffffa096a016000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34 STACK_COMMAND: .thread 0xffffc00f5f2be040 ; kb SYMBOL_NAME: BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopReaderAndWriter+a1 MODULE_NAME: BTHport IMAGE_NAME: BTHport.sys BUCKET_ID_FUNC_OFFSET: a1 FAILURE_BUCKET_ID: 0x9F_3_BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopReaderAndWriter OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {644091bf-7273-4fa6-d16e-e0ab5661024d} Followup: MachineOwner --------- 8: kd> lmvm BTHport Browse full module list start end module name fffff80364340000 fffff803`64516000 BTHport (pdb symbols) C:\ProgramData\dbg\sym\bthport.pdb\09D5CB23FF3F156326D7DFDBD25E9CA91\bthport.pdb
Loaded symbol image file: BTHport.sys
Mapped memory image file: C:\ProgramData\dbg\sym\BTHport.sys\73E4D2AC1d6000\BTHport.sys
Image path: \SystemRoot\System32\drivers\BTHport.sys
Image name: BTHport.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 73E4D2AC (This is a reproducible build file hash, not a timestamp)
CheckSum: 001D7BA6
ImageSize: 001D6000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
 
Sort by date Sort by votes
Rui Neves said:
I had a BSOD today ,the dump file of windows says that this time the culprit is BTHport.sys , After a google research I foud out that is bluetooth related , I have a bluetooth adapter for a long time already and never had this issues , could be a software problem or can be also related to the adapter itself ?

What Can I do in case of software issue ?

PC specs :
AOC monitor with 21" and freesync , 75hz
Gigabyte b450 gaming X
AMD Ryzen 5 3600
Kingston HyperX FURY DDR4 (with RGB) at 3200mhz with XMP profile 1 enabled
XFX RX 580 GTS XXX 4gb
Bitfenix formula gold 550w
3 hdd´s from WD , 1 wd green , 1wd black ,1 wd blue
1 ssd ( kingston a400 120gb)



DUMP FILE TEXT :

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Documentos\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 100

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff80354600000 PsLoadedModuleList = 0xfffff80355229bc0
Debug session time: Tue Feb 22 21:54:33.882 2022 (UTC + 0:00)
System Uptime: 0 days 0:15:18.513
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
8: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffc00f5f435d90, Physical Device Object of the stack
Arg3: fffffa096a08b7d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc00f6ca2da20, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffffc00f5f2be040 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2280 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2374 Key : Analysis.Init.CPU.mSec Value: 3046 Key : Analysis.Init.Elapsed.mSec Value: 63183 Key : Analysis.Memory.CommitPeak.Mb Value: 152 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 DUMP_FILE_ATTRIBUTES: 0x1000 BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffc00f5f435d90 BUGCHECK_P3: fffffa096a08b7d0 BUGCHECK_P4: ffffc00f6ca2da20 DRVPOWERSTATE_SUBCODE: 3 FAULTING_THREAD: ffffc00f5f2be040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: fffffa096a01b140 fffff803549327f7 : ffffe68100000000 0000000000000000 0000000000000020 0000000000000000 : nt!KiSwapContext+0x76 fffffa096a01b280 fffff803549346a9 : ffffc00f0000000a ffffc00f00000001 fffffa096a01b460 fffffa0900000000 : nt!KiSwapThread+0x3a7 fffffa096a01b360 fffff8035492e5c4 : ffffc00f00000000 ffffc00f00000000 ffffc00f00000000 0000000000000000 : nt!KiCommitThreadWait+0x159 fffffa096a01b400 fffff803644bac05 : ffffc00f66c67110 fffff80300000000 0000000000000000 ffffc00f66c67c00 : nt!KeWaitForSingleObject+0x234 fffffa096a01b4f0 fffff803644baa18 : ffffc00f66c670a8 0000000000000001 0000000000000001 0000000000000001 : BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopReaderAndWriter+0xa1 fffffa096a01b530 fffff803644a4e70 : ffffc00f66c67050 0000000000000003 ffffc00f66c670a8 ffffc00f66cd4e00 : BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopInternal+0x60 fffffa096a01b590 fffff803644a4f57 : 0000000000000003 fffffa096a01b800 0000000000000000 ffffc00f00000000 : BTHport!Microsoft::Bluetooth::BthCoreCx::Fdo::EvtCxDevicePreD0Exit+0x17c fffffa096a01b600 fffff803561a5730 : 000000000000031a ffffc00f66cb5cc0 fffff803561b6700 0000000000000000 : BTHport!Microsoft::Bluetooth::BthCoreCx::Fdo::EvtCxDevicePreD0ExitThunk+0x17 fffffa096a01b630 fffff80356159461 : ffffc00f66c787a0 0000000000000000 ffffc00f66c67a28 fffff8035612b812 : Wdf01000!FxPnpDeviceD0Exit::InvokeCxCallback+0x30 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpcallbacks.cpp @ 328] fffffa096a01b690 fffff80356156dae : ffffc00f66c67ce8 ffffc00f66cd4c90 ffffc00f66c67770 000000000000031c : Wdf01000!FxPrePostCallback::IssuePreCxCallbacksStateless+0x53 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 478] fffffa096a01b6c0 fffff8035612d0b1 : 0000000000000000 0000000000000003 0000000000000003 ffffc00f66c67770 : Wdf01000!FxPrePostCallback::InvokeStateless+0x29886 [minkernel\wdf\framework\shared\irphandlers\pnp\cxpnppowercallbacks.cpp @ 414] fffffa096a01b6f0 fffff8035612e75b : 0000000000000000 fffffa096a01b890 fffff803561b6740 0000000000000000 : Wdf01000!FxPkgPnp::PowerGotoDxIoStoppedCommon+0xf1 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3100] fffffa096a01b760 fffff80356136b66 : 000000000000031c fffff803561b6ee0 ffffc00f66c67770 0000000000000000 : Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0xb [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 2842] fffffa096a01b790 fffff80356136d20 : 0000000000000340 ffffc00f66c67770 ffffc00f66c67770 0000000000000340 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x142 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699] fffffa096a01b8e0 fffff803561359ee : ffffc00f66c67770 0000000000000000 0000000000000000 fffff8035612b800 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xdc [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1613] fffffa096a01b960 fffff8035612c839 : 0000000000000000 ffffc00f66c67770 fffffa096a01bad0 0000000000000016 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x142 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1394] fffffa096a01b9f0 fffff8035612c655 : ffffc00f66c67770 fffffa096a01bab8 0000000000000004 0000000000000000 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x6d [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 350] fffffa096a01ba40 fffff8035612b458 : ffffc00f66c67770 0000000000000016 fffffa096a01bac0 fffff803549a1d29 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x25 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 120] fffffa096a01ba70 fffff80356123d82 : ffffc00f6ca2da20 ffffc00f6ca2da20 0000000000000000 0000000000000016 : Wdf01000!FxPkgPnp::Dispatch+0xd8 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 771] fffffa096a01bae0 fffff803549abb67 : 0000000000000000 ffffc00f5f2be040 ffffc00f6ca2da20 0000000000000000 : Wdf01000!FxDevice::DispatchWithLock+0x152 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447] fffffa096a01bb50 fffff803548478f5 : 0000000000000000 fffff803549ab960 0000000000000000 00000000000000d8 : nt!PopIrpWorker+0x207 fffffa096a01bbf0 fffff80354a1a2d4 : ffffe681e5560180 ffffc00f5f2be040 fffff803548478a0 0000000000000000 : nt!PspSystemThreadStartup+0x55 fffffa096a01bc40 0000000000000000 : fffffa096a01c000 fffffa096a016000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34 STACK_COMMAND: .thread 0xffffc00f5f2be040 ; kb SYMBOL_NAME: BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopReaderAndWriter+a1 MODULE_NAME: BTHport IMAGE_NAME: BTHport.sys BUCKET_ID_FUNC_OFFSET: a1 FAILURE_BUCKET_ID: 0x9F_3_BTHport!Microsoft::Bluetooth::BthCoreCx::HciTransport::StopReaderAndWriter OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {644091bf-7273-4fa6-d16e-e0ab5661024d} Followup: MachineOwner --------- 8: kd> lmvm BTHport Browse full module list start end module name fffff80364340000 fffff803`64516000 BTHport (pdb symbols) C:\ProgramData\dbg\sym\bthport.pdb\09D5CB23FF3F156326D7DFDBD25E9CA91\bthport.pdb
Loaded symbol image file: BTHport.sys
Mapped memory image file: C:\ProgramData\dbg\sym\BTHport.sys\73E4D2AC1d6000\BTHport.sys
Image path: \SystemRoot\System32\drivers\BTHport.sys
Image name: BTHport.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 73E4D2AC (This is a reproducible build file hash, not a timestamp)
CheckSum: 001D7BA6
ImageSize: 001D6000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
Click to expand...
If you have had the wifi doungle for a long time it maybe no longer compatible with the system
 
Upvote 0 Downvote
See if this solution works for you... seems the same driver was failing.

[SOLVED] - DRIVER_POWER_STATE_FAILURE (9f)

Have had problems with this for some time, hope somone could help me here. I have no clue what to read in the text below. *** * Bugcheck Analysis * * *** DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time...
forums.tomshardware.com forums.tomshardware.com

onespeedbiker said:
This is caused by Intel Rapid Storage Technology driver. Assuming you are not using a RAID array, you can delete the utility. https://appuals.com/fix-iastora-sys-blue-screen/
Click to expand...
 
Upvote 0 Downvote
Chicano said:
See if this solution works for you... seems the same driver was failing.

[SOLVED] - DRIVER_POWER_STATE_FAILURE (9f)

Have had problems with this for some time, hope somone could help me here. I have no clue what to read in the text below. *** * Bugcheck Analysis * * *** DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time...
forums.tomshardware.com forums.tomshardware.com
Click to expand...
??? my dump says BTHport.sys and you gave me a link about the iaStorA.sys . I am not using raid and not even ever installed that software , my computer is all AMD .
 
Upvote 0 Downvote
i think windows told your bluetooth driver to go to a low power state and it just did not respond. What to do depends on the age of the device itself. if it is a older device, often the original driver had this feature turned off by default. When you update you might get a fixed version from microsoft that turns the feature on and exposes hardware problems in the device or the bios.

Most people would just go into windows control panel device manager, find the device, right click for properties, find the power management tab and tell the system not to turn off the device to save power. ( just to keep the system from bugchecking)

otherwise, you could update the bios (if the problem is there) or downgrade the driver to the one provided by the motherboard (if this came with the motherboard) Problem is that there was a reason microsoft upgraded the driver.
I would guess the system tells the driver to go to low power mode after 15 min idle

note: i could not find the bluetooth hardware info on the motherboard page. so if it is a addon you would have to specify the vendor and model to find out what hardware spec/chip is on the device.
 
Last edited:
Upvote 0 Downvote
hi , first of all thanks for your answer , I tried after the BSOD disable the power saving option and updated the bios hoping that fixes the issue .
Unfortunately I use an BT adapter and it is nor built in in the MB , the adapter show that supports until windows 10 and it´s plug and play , since I am using windows 11 could be an issue , but was working fine until now even on windows 11 . the adapter is this one "https://www.conceptronic.net/concep...40NANO_Bluetooth_4.0_Class_1_USB_Adapter.pdf/"
 
Upvote 0 Downvote
Rui Neves said:
hi , first of all thanks for your answer , I tried after the BSOD disable the power saving option and updated the bios hoping that fixes the issue .
Unfortunately I use an BT adapter and it is nor built in in the MB , the adapter show that supports until windows 10 and it´s plug and play , since I am using windows 11 could be an issue , but was working fine until now even on windows 11 . the adapter is this one "https://www.conceptronic.net/concep...40NANO_Bluetooth_4.0_Class_1_USB_Adapter.pdf/"
Click to expand...
for the usb adapter you have to tell windows not to put the USB port into low power mode. (or the bios on some machines)

i think it uses this chipset and driver
Software | CSR8510 | Qualcomm

you might be able to get the driver from another vendor that uses the same hardware

(or just buy a more current bt device)
i see drivers on the internet but they are from 2012.

USB drivers are hidden when you remove the device but they are still loaded and can cause problems. You can go into windows control panel device manager but you have to select show hidden devices to see the driver being installed on each usb port.

you need to do this and remove each driver associated with each port. USB can have a different version of a driver installed on different USB ports. it gets pretty screwy to debug
 
Last edited:
Upvote 0 Downvote
Rui Neves said:
well I did not find any driver for windows 11 , maybe it´s better to get one that is ready for windows 11 if it happens again .
Click to expand...
hardware vendors generally do not keep updating the drivers after a few years.
bluetooth 4.0 is six versions old (it came out in 2010)

version 4.0, 4.1,4.2, 5.0, 5.1,5.2, and now 5.3 is the currently released version.
Bluetooth - Wikipedia
 
  • Like
Reactions: Rui Neves
Upvote 0 Downvote
Upvote 0 Downvote
Chicano said:
The point tried to make, is the dump file says it's a storage driver, and both BHTport.sys and iaStorA.sys are Windows storage drivers. I doubt the blue tooth device or its driver are the cause.
Click to expand...
I don't see nothing wrong with my storage drivers, at least I think so , I have the most recent chipset drivers ( not sure if it installs storage driver related) and have all Windows updates , the only driver that I manually install are GPU and sound drivers besides the chipset drivers . At the moment of the BSOD I had an external HDD connected and the HDD have a pretty generic usb case but never gave me problems before either ... Is pretty much like the BT adapter , both are pretty generic.
so both cases could make sense in some sporadic way to cause a BSOD since Windows 11 is so recent and that adapters could not be ready too support it .

But what you are saying is against other information on internet that refer this file as a bluetooth bus driver , so I am confuse tbh 😅😅

" https://www.computerhope.com/cgi-bin/process.pl?p=bthport.sys"

"https://answers.microsoft.com/en-us...-10-bsod/2e898b03-4362-4a4f-bd27-64ac354cec3a"
 
Upvote 0 Downvote
Rui Neves said:
At the moment of the BSOD I had an external HDD connected and the HDD have a pretty generic usb case but never gave me problems before either ... Is pretty much like the BT adapter , both are pretty generic.

But what you are saying is against other information on internet that refer this file as a bluetooth bus driver , so I am confuse tbh 😅😅

" https://www.computerhope.com/cgi-bin/process.pl?p=bthport.sys"

"https://answers.microsoft.com/en-us...-10-bsod/2e898b03-4362-4a4f-bd27-64ac354cec3a"
Click to expand...
You said it yourself, generic drivers are Windows drivers...
What I said is the Dump file you showed says Windows drivers are causing the issue, and I don see the contradiction: The information I found on the Internet coincide with what you say, because I also found that blue tooth drivers are both from Windows and also from the device manufacturer, and it's like it always has been, Microsoft recommends using their drivers, and device manufacturers recommend using theirs... but in this case and according to the Dump file, Windows drivers same as always are causing the issue.

I also found a fix that suggest doing repair for this issue, that involves repairing the Windows installation running the System File Checker (SFC /Scannow) which checks for system files including drivers and replaces them as necessary... but I don't see much of a problem in installing the device manufacturer drivers, and if the problem persists, proceed with to fix the Windows issue...

Google find on DRIVER_POWER_STATE_FAILURE (9f)
What causes DRIVER_POWER_STATE_FAILURE?
A stop code “driver power state failure” blue screen of death error is usually caused by a power control issue with a device connected to your PC. ... If a device driver is out-of-date or faulty, Windows' ability to control power settings for connected devices might be affected.
Click to expand...


This Fix is related to the BTHport.sys issue.
 
Upvote 0 Downvote
Chicano said:
You said it yourself, generic drivers are Windows drivers...
What I said is the Dump file you showed says Windows drivers are causing the issue, and I don see the contradiction: The information I found on the Internet coincide with what you say, because I also found that blue tooth drivers are both from Windows and also from the device manufacturer, and it's like it always has been, Microsoft recommends using their drivers, and device manufacturers recommend using theirs... but in this case and according to the Dump file, Windows drivers same as always are causing the issue.

I also found a fix that suggest doing repair for this issue, that involves repairing the Windows installation running the System File Checker (SFC /Scannow) which checks for system files including drivers and replaces them as necessary... but I don't see much of a problem in installing the device manufacturer drivers, and if the problem persists, proceed with to fix the Windows issue...

Google find on DRIVER_POWER_STATE_FAILURE (9f)



This Fix is related to the BTHport.sys issue.
Click to expand...

Your contradition is that you refer as storage drivers ... and most of the posts on internet refer as a BT driver issue , there´s a difference there ...

It´s strange anyone the problem being BT driver issue , but is what system says , and I don´t have a better ideia , and the machines are usually right xD.



DRIVER_POWER_STATE_FAILURE (9f) code is more global .... is more a generic code .... the specific file that cause the error says that is a BT driver issue , that´s why I was refering to the file and not the code ... the code says almost nothing as can be 100 different devices causing the issue there , the file seems to limit the error to one , that why I´ve read the dump file , otherwise I did not had to read that ...



most of the BT adapter manufacturers says that since the lauch of windows 8.1 and foward is plug and play , but some of them are not windows 11 ready (officially ) as mine is not , if you go to ASUS website for example , there´s one adapter that says ready to windows 11 and no driver for win 11 , just plug and play .... nothing I can do there ... even the one I ordered is like that .... but is more recent anyway.
I always have caution to install all drivers that I know that usually windows will install a very outdated version , like amd chipset drivers, realtek sound drivers , GPU drivers , and specific devices that need one , since I don´t use HDD´s in raid mode is all what I need usually and is what most manufacturers provide anyway since windows 8.1.

Windows just seem to stop having drivers from most manufactures for this type of usb adapters since windows 8.1. Just have to pray to the new adapter that I bought solve the issue for being more recent or Microsoft updates their drivers on windows 11.



Thanks for the support , I will follow that solutions if it happens again , the new adapter is suppose to be at my house tomorrow , I hope it fixes the issue being more recent , if don´t at least I have a bt adapter with 5.0 version now xD.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom