-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Printers
- Printer Setup, Software & Drivers
- HP Scanjet 3000s4

Create an account on the HP Community to personalize your profile and ask a question
05-05-2025 06:37 AM
hello We had this scanner attached to a HP ProDesk 600 G2 MT running windows 10 22H2 and it has been working perfectly . The driver version was 41.6.2420.22231. We need to upgrade the machine to windows 11 and connected it a HP elite Mini 805 G8 desktop running windows 11 24H2 Driver version 51.5.5392.21347 . Since then the Machine has been blue screening, especially after it has been running for a while . it losses connect to the scanner . Ee has disallowed all the Power control on the USB ports and Up dated to the latest Drivers for the scanner . Gave the users running the scanner full admin rights.
Blue screen error DRIVER_POWER_STATE_FAILURE (9f)
* *
* 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: ffff8387ceff1970, Physical Device Object of the stack
Arg3: ffffae0e022ef650, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8387e7a68050, The blocked IRP
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\drivers\RtkBtFilter2.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RtkBtFilter2.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1281
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2676
Key : Analysis.Init.CPU.mSec
Value: 2171
Key : Analysis.Init.Elapsed.mSec
Value: 26883
Key : Analysis.Memory.CommitPeak.Mb
Value: 116
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Timestamp
Value: 2024-03-31T14:35:00Z
Key : WER.OS.Version
Value: 10.0.26100.1
FILE_IN_CAB: 042425-18937-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff8387ceff1970
BUGCHECK_P3: ffffae0e022ef650
BUGCHECK_P4: ffff8387e7a68050
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: UsbHub3.sys
MODULE_NAME: UsbHub3
FAULTING_MODULE: fffff8021cc40000 UsbHub3
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffae0e`022ef5f8 fffff802`8198b68d : 00000000`0000009f 00000000`00000003 ffff8387`ceff1970 ffffae0e`022ef650 : nt!KeBugCheckEx
ffffae0e`022ef600 fffff802`8198b48c : ffff8387`cc5ac280 ffffae0e`022efa68 ffff8387`e2895d78 ffffae0e`022ef7d9 : nt!PopIrpWatchdogBugcheck+0x1f5
ffffae0e`022ef6e0 fffff802`8174d9fa : ffffe701`00000001 ffffae0e`00000001 ffffae0e`00000000 fffff802`00000002 : nt!PopIrpWatchdog+0xc
ffffae0e`022ef710 fffff802`8174e513 : fffff802`113a8280 fffff802`81893f1f 00000003`37f2e70b fffff802`113ab660 : nt!KiProcessExpiredTimerList+0x26a
ffffae0e`022ef840 fffff802`8172d191 : ffffe701`dcb9f180 00000000`00000028 ffffe701`dcb9f180 00000000`00000002 : nt!KiTimerExpiration+0x2e3
ffffae0e`022ef970 fffff802`81a7c96e : ffffe701`dcb9f180 ffffe701`dcb9f180 00000000`00000000 fffff802`0de4b800 : nt!KiRetireDpcList+0xaf1
ffffae0e`022efc00 00000000`00000000 : ffffae0e`022f0000 ffffae0e`022e9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
IMAGE_VERSION: 10.0.26100.3624
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_RtkBtFilter2_IMAGE_UsbHub3.sys
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {17beae65-fdd8-e8fe-ce2d-4bb16bccde08}
Followup: MachineOwner