BSOD/ Shutdown after sleep

Sorry for the delay - I have now looked at the crash dump that was dated from Feb 26.

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: fffffa80036a8060, Physical Device Object of the stack
Arg3: fffff80000b9c528, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8008780c10, The blocked IRP

The device Object is: "PCI\VEN_11AB&DEV_4354&SUBSYS_02AA1028&REV_13\4&2ac8d8a2&0&00E2"
ServiceName is "yukonw7"

This is your Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller

This is the device which is causing your BSOD on power down/sleep. The driver is yk62x64.sys and needs updating if you can find a newer one or if it was an update that started this happening you need to revert back to the previous driver.

Details of your installed driver extracted from the crash dump are shown below. You will see it is from Sept 28, 2009

0: kd> lmvm yk62x64
Browse full module list
start end module name
fffff880`0490a000 fffff880`0496f000 yk62x64 T (no symbols)
Loaded symbol image file: yk62x64.sys
Image path: \SystemRoot\system32\DRIVERS\yk62x64.sys
Image name: yk62x64.sys
Browse all global symbols functions data
Timestamp: Mon Sep 28 09:19:31 2009 (4AC07193)
CheckSum: 0006B55C
ImageSize: 00065000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

Sorry for MY delay...
Thanks for looking deep into the issue. That driver from 2009 was pre-installed. I just looked at the Dell driver upgrades and there is no new one, but on Marvell they have some newer year versions--a few too many choices I have to choose from:

Kernel 2.6.x Linux Driver Install Package for Yukon Devices 10.93.3.3
03/27/12 Windows Server 2008 SP2 64-bit Driver 11.45.4.3
03/27/12 Windows 7 & Server 2008 R2 32-bit Driver 11.45.4.3
03/27/12 Windows Setup Installer (32- and 64-bit) for Yukon Controllers 11.45.4.3
03/27/12 Windows 7 & Server 2008 R2 x64 (64-bit)

These are the ones out of a dozen that have something to do with my 7- 64 bit system, which one is the one?

I promised to write back in a week and as it is 6 days without any problems, I am wondering to still go ahead with a newer driver?

I would suggest that if you are no longer getting the 0x9F bugcheck then leave things as they are. If you get the 0x9F BSOD again please post a new set of logs and I will confirm if it is the same problem and then we can decide what to do.

Hello, I'm back with the same problem even though it is a new laptop (Lenovo) and a different Win7 (Pro).
Error states "the system has rebooted without shutting down first; source-Kernel Power, event-41. The event manager has critical, warning and error reports which I do not fully understand. Basically, I get a forced reboot after waking the laptop from "sleep".

I am enclosing the latest CBS log at this link M-PC-09-Jan-22_110837_58.zip - pCloud

Thanks in advance.

This is the file that the log says is causing the problem- Wdf01000.sys Windows process - What is it?

These are the additional events reported for each BSOD

08-Jan-22 9:54 PM Windows Error Reporting Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: USB\VID_0FE6&PID_9702&REV_0101&MI_01
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Users\m\AppData\Local\Temp\DMIE9C6.tmp.log.xml

These files may be available here:
C:\Users\m\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_8dc899f25ed8a7a6a963a84dc aadf9b94aa8d141_cab_1738e9d5

Analysis symbol:
Rechecking for solution: 0
Report Id: 90c2d2aa-5758-11ec-bbad-ad7d2f50d9f6
Report Status: 0

08-Jan-22 9:54 PM Windows Error Reporting Fault bucket , type 0
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft Windows.NetworkDiagnostics.1.0
P2: Default
P3: 1.0.0.0
P4: Default
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Users\m\AppData\Local\Temp\msdt\_D2203935-732B-465A-B0AE-EA1C5193D47C_\PkgC38D.cab

These files may be available here:
C:\Users\m\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_Microsoft Window_bd5996727e9ea1acda90841fa2c99a88df4fb9d6_cab_0f74c503

Analysis symbol:
Rechecking for solution: 0
Report Id: 0e86b67a-38a8-11ec-85a6-a0a8cd95ed26
Report Status: 0
09-Dec-21 1:19 PM Windows Error Reporting Fault bucket , type 0
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: 80070422
P2: UpdateServiceManager->get_Services
P3: FallbackCheck
P4: 6.1.7601.18170
P5: MpSigDwn.dll
P6: 6.1.7600.16385
P7: Windows Defender
P8:
P9:
P10:

Attached files:
C:\Windows\Temp\MPTelemetrySubmit\client_manifest.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_80070422_87c69956995838063dd50a856e471e c5e12865e_cab_17dedc89

Analysis symbol:
Rechecking for solution: 0
Report Id: b118fd03-58f2-11ec-a7fa-005056c00008
Report Status: 4

The only PNP device I see which is not available is your printer driver. Perhaps you might disconnect it before you put your system to sleep.

W2, welcome aboard again (from almost a year) and thanks for your help.

The WDF01000.sys id a driver framework which allows communication between hardware and connected devices. In my primitive experience with the Event Log and CBS file I also found this error, and the PNP issue you mentioned. I could not access the WDF via DOS-to update it, so this gave me a red flag. I found a download for it and am willing to install it.

Second, the PNP device listed in the Device Manager is a "generic monitor" which is working correctly, and I do find drivers for it when plugged in. Also the printer has a driver when installed.

I think I will install the WDF, and your thoughts are welcomed.

from what i can find, its not your monitor its either your ethernet or usb to ethernet cable

USB\VID_0FE6&PID_9702&REV_0101&MI_01

Most likely the ethernet to USB adapter that constantly blinks out when resuming from sleep, but I don't think that would cause a BSOD?

I mentioned the printer because it's listed in the Components. If it's not attached or installed, I don't know how it's being seen unless you used a backup of your old system to install on the new system.

See this- USB\VID_0FE6&PID_9702&MI_01 | Device Drivers

for what torchwood was talking about.

I cloned my old HDD to my new SSD. There is no printer in the Device Manager but in Control Panel "Printers".

I will try the WDD install soon.