Every few days I experience a BSOD DRIVER_POWER_STATE_FAILURE caused by mscisci.sys:
*******************************************************************************
* *
* 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: ffffe701461d7050, Physical Device Object of the stack
Arg3: fffff98c7c6617d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe701148e6290, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 1
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on LAPTOK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 14
Key : Analysis.Memory.CommitPeak.Mb
Value: 88
Key : Analysis.System
Value: CreateObject
DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffe701461d7050
BUGCHECK_P3: fffff98c7c6617d0
BUGCHECK_P4: ffffe701148e6290
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: msiscsi.sys
MODULE_NAME: msiscsi
FAULTING_MODULE: fffff805256f0000 msiscsi
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff98c`7c661798 fffff805`1f3c2cd7 : 00000000`0000009f 00000000`00000003 ffffe701`461d7050 fffff98c`7c6617d0 : nt!KeBugCheckEx
fffff98c`7c6617a0 fffff805`1f3c2bf1 : ffffe701`12bf9530 00000000`00000080 fffff98c`7c661af8 fffff98c`7c661af0 : nt!PopIrpWatchdogBugcheck+0xdf
fffff98c`7c661810 fffff805`1f0dcc74 : 00000000`00000000 00000000`00000001 fffff98c`00000000 00000000`00000002 : nt!PopIrpWatchdog+0x31
fffff98c`7c661860 fffff805`1f0db264 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff805`1d06a1c8 : nt!KiProcessExpiredTimerList+0x204
fffff98c`7c661990 fffff805`1f216abe : 00000000`00000000 ffff9801`d98c0180 ffff9801`d98cc240 ffffe701`18bb3080 : nt!KiRetireDpcList+0x714
fffff98c`7c661c40 00000000`00000000 : fffff98c`7c662000 fffff98c`7c65c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
IMAGE_VERSION: 10.0.21390.1
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_disk_IMAGE_msiscsi.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5882332e-2e47-a9bd-4094-b6bb2ab2211e}
Followup: MachineOwner
---------
3 latest minidumps:
https://1drv.ms/u/s!AsI8I_GZ78F1gQOTdQg3eucAvqev?e=jAqulY
To reproduce the issue:
1. Configure ISCSI initiator with a remote target
2. Suspend the PC and disconnect from the network
3. Resume PC, wait ~10 minutes
It does not happen every time, has to be repeated many times to trigger the bugcheck.
The problem has occurred since at least Windows 10 20H1, and all subsequent retail versions of Windows 10 pro and Windows 11.
I am not the only one affected, found many reports on the web:
https://answers.microsoft.com/en-us/insider/forum/all/iscsi-driver-causes-blue-screens-on-windows-10/72f7df2d-092b-47b5-9845-7f8524e46d09
https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-with-driverpowerstatefailure-when/d6891a74-39c7-4248-8b5f-77c95f0908d4
https://social.technet.microsoft.com/Forums/WINDOWS/en-US/4b861e69-0b12-4521-818b-c3fa17ed1abd/iscsi-driver-causes-blue-screens-on-windows-10-when-changing-networks?forum=win10itprogeneral
https://techcommunity.microsoft.com/t5/report-an-issue/windows-10-pro-crash-after-wake-up-from-sleep-reason-msiscsi-sys/m-p/2514216
Hardware configuration:
- PC: Lenovo Thinkpad E495, Model 20NE000EPB
- CPU: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx, 2300 MHz, Cores: 4, Threads: 8
- Memory: 24GB
- Local storage: 512GB NVME solid state drive
- iSCSI target: Netgear ReadyNAS Ultra 4 Plus: Linux 4.4.218.x86_64.1
