question

KrzysztofZalewski-5185 avatar image
0 Votes"
KrzysztofZalewski-5185 asked Docs-4663 answered

iSCSI DRIVER_POWER_STATE_FAILURE after resume from sleep and absence of ISCSI target

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

windows-10-generalwindows-11
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Reza-Ameri avatar image
0 Votes"
Reza-Ameri answered

Try open start and search for feedback and open Feedback Hub app and report this issue.
Check with the Lenovo's support.
Try perform a Clean Boot and see if the problem persist?
Take a look at:
https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive:

https://www.windowsq.com/t/bsod-posting-instructions.17/
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html


.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KrzysztofZalewski-5185 avatar image
0 Votes"
KrzysztofZalewski-5185 answered

@Reza-Ameri, @Docs-4663
Thank you very much for your answers.

Try open start and search for feedback and open Feedback Hub app and report this issue.

![145048-image.png][1]
I will report the issue once I get Feedback Hub working for me.

Check with the Lenovo's support.
Try perform a Clean Boot and see if the problem persist?

I will check this out on Tuesday night, before then I won't have an access to my iSCSI target.

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive

The report can be found here: https://1drv.ms/u/s!AsI8I_GZ78F1gQOTdQg3eucAvqev?e=jAqulY -> LAPTOK-(2021-10-29_20-00-24).zip

[1]: /answers/storage/attachments/145048-image.png

image.png (8.2 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered

The logs were in a foreign language and could not be scanned or read.

Please modify the default language to English and post a new V2.

https://www.tenforums.com/tutorials/3813-add-remove-change-display-language-windows-10-a.html
https://www.tenforums.com/tutorials/136792-change-display-language-windows-10-a.html



Please search for and post share links:

C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20211015-0029.dmp
C:\WINDOWS\LiveKernelReports\UcmUcsiCx.sys\UcmUcsiCx.sys-20211006-1156.dmp
C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20211008-1236-01.dmp
C:\WINDOWS\LiveKernelReports\USBXHCI\USBXHCI-20211008-1236.dmp



Once the language is changed run these commands and post share links into this thread:

sfc /scannow
dism /online /cleanup-image /restorehealth
chkdsk /scan
wmic recoveros set autoreboot = false
wmic recoveros set debuginfotype = 7
wmic recoveros get autoreboot
wmic recoveros get debuginfotype
wmic computersystem where name="%computername%" set automaticmanagedpagefile=true
wmic computersystem where name="%computername%" get automaticmanagedpagefile
bcdedit /enum {badmemory}


For any new BSOD run V2 (posting minidumps is no longer necessary).

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.