Hi everyone,
I run a Windows 8.1 system with all recent updates installed and I have a Synology NAS 412+via iSCSI using native Windows iSCSI initiator.
Recently, I noticed that if I start Windows on laptop in location where the NAS is remote, a little while after logon I get a blue screen 0x9F (DRIVER_POWER_STATE_FAILURE).
Analyzing the memory dump with WinDBG, it points as a probable cause the Windows iSCSI driver (msiscsi.sys) with the output shown at the end of this post.
The corresponding memory dump (both are similar with different type of compression) can be accessed here
Does anyone know how to solve this problem?
Thanks in advance.
0: 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: ffffe001c9402060, Physical Device Object of the stack
Arg3: fffff8018b213960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001c0e228f0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: msiscsi.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53415ed0
MODULE_NAME: msiscsi
FAULTING_MODULE: fffff8011ed97000 msiscsi
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF8018B21AFB0
STACK_TEXT:
fffff801`8b213928 fffff801`8969443a : 00000000`0000009f 00000000`00000003 ffffe001`c9402060 fffff801`8b213960 : nt!KeBugCheckEx
fffff801`8b213930 fffff801`8969435a : ffffe001`c4c51820 00000000`00000008 fffff801`8b213a58 fffff801`89558ed1 : nt!PopIrpWatchdogBugcheck+0xde
fffff801`8b213990 fffff801`895553a8 : 00000000`00000000 fffff801`8b213ae0 00000000`00000001 00000000`00000001 : nt!PopIrpWatchdog+0x32
fffff801`8b2139e0 fffff801`895df4ea : fffff801`8978e180 fffff801`8978e180 fffff801`897e7a00 ffffe001`bfd90880 : nt!KiRetireDpcList+0x4f8
fffff801`8b213c60 00000000`00000000 : fffff801`8b214000 fffff801`8b20e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_disk_IMAGE_msiscsi.sys
BUCKET_ID: 0x9F_3_POWER_DOWN_disk_IMAGE_msiscsi.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_disk_image_msiscsi.sys
FAILURE_ID_HASH: {8b27c4e5-6ed4-ac8a-fe97-7ebabd40f52d}
Followup: MachineOwner
---------
I run a Windows 8.1 system with all recent updates installed and I have a Synology NAS 412+via iSCSI using native Windows iSCSI initiator.
Recently, I noticed that if I start Windows on laptop in location where the NAS is remote, a little while after logon I get a blue screen 0x9F (DRIVER_POWER_STATE_FAILURE).
Analyzing the memory dump with WinDBG, it points as a probable cause the Windows iSCSI driver (msiscsi.sys) with the output shown at the end of this post.
The corresponding memory dump (both are similar with different type of compression) can be accessed here
Does anyone know how to solve this problem?
Thanks in advance.
0: 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: ffffe001c9402060, Physical Device Object of the stack
Arg3: fffff8018b213960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001c0e228f0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: msiscsi.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53415ed0
MODULE_NAME: msiscsi
FAULTING_MODULE: fffff8011ed97000 msiscsi
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF8018B21AFB0
STACK_TEXT:
fffff801`8b213928 fffff801`8969443a : 00000000`0000009f 00000000`00000003 ffffe001`c9402060 fffff801`8b213960 : nt!KeBugCheckEx
fffff801`8b213930 fffff801`8969435a : ffffe001`c4c51820 00000000`00000008 fffff801`8b213a58 fffff801`89558ed1 : nt!PopIrpWatchdogBugcheck+0xde
fffff801`8b213990 fffff801`895553a8 : 00000000`00000000 fffff801`8b213ae0 00000000`00000001 00000000`00000001 : nt!PopIrpWatchdog+0x32
fffff801`8b2139e0 fffff801`895df4ea : fffff801`8978e180 fffff801`8978e180 fffff801`897e7a00 ffffe001`bfd90880 : nt!KiRetireDpcList+0x4f8
fffff801`8b213c60 00000000`00000000 : fffff801`8b214000 fffff801`8b20e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_disk_IMAGE_msiscsi.sys
BUCKET_ID: 0x9F_3_POWER_DOWN_disk_IMAGE_msiscsi.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_disk_image_msiscsi.sys
FAILURE_ID_HASH: {8b27c4e5-6ed4-ac8a-fe97-7ebabd40f52d}
Followup: MachineOwner
---------
My Computer
System One
-
- OS
- Windows 8.1