Question "Unexpected Shutdown" lasting several days as reported by Bugcheck
Question "Unexpected Shutdown" lasting several days as reported by Bugcheck
Sorry, the timing was a bit off for these dumps. They all point to a 0x9F error, meaning the device didn't finish its power switch on time. The parameters provide both the IRP handling the request and the failing device's address.
The power management unit is showing it’s using Netwtw10.sys, which is the Intel WiFi driver...
Rich (BB code):
4: kd> !irp ffffe309ab4028f0
The IRP is running with 7 stacks, and the current one is 5. No Mdl info—no system buffer used.
Thread 00000000: IRP stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
...
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 0 ffffe309abe18050 00000000 00000000-00000000
Can't load Netwtw10.sys, Windows error 0n2
*** WARNING: Timestamp check failed for Netwtw10.sys
Driver: Netwtw10
Arguments: 00000000 00000001 00000004 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffe309ac062700 00000000 fffff8020ed2cf80-ffffe309b1085248 Success Error Cancel pending
Driver: nt!PopRequestCompletion
Arguments: 00000000 00000001 00000004 00000000
That confirms the issue is with a wireless adapter. The device address reveals its identity...
Rich (BB code):
4: kd> !devnode ffffe309a86cea20
Device node 0xffffe309a86cea20 is linked to PDO 0xffffe309a85bc360
Parent: 0xffffe309a858dc40, Sibling: 0xffffe309a85c3a20, Child: 0xffffe309b4f97b20
InstancePath: PCI\VEN_8086&DEV_A0F0 & SUBSYS_00748086&REV_20\3&11583659&0&A3
ServiceName: Netwtw10
State: DeviceNodeStarted (0x30a) on 2023-12-17 12:16:21
Previous State: DeviceNodeEnumerateCompletion (0x30f) same time
...
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
Flags: DNF_ENUMERATED, DNF_IDS_QUERIED, DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
CapabilityFlags: WakeFromD3
The device IDs in the InstancePath confirm it's an Intel AX201 wireless card.
First, verify the driver—its Netwtw10.sys is several months outdated...
Rich (BB code):
4: kd> lmvmnetwtw10
View full module list
Start | End | Module Name
fffff802`20330000 fffff802`20894000 Netwtw10 T (no symbols)
Loaded symbol image file: Netwtw10.sys
Image path: Netwtw10.sys
Explore all global symbols, functions, data
Timestamp: Sun Aug 6 17:51:52 2023 (64CFB388)
CheckSum: 004F843E
ImageSize: 00564000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
From resource tables:
I recommend updating the driver—check the Lenovo site for your laptop model or Intel support. If the updated driver still causes the crashes, you may need to inspect the hardware card itself. Wireless adapters are usually replaceable, though they can be tricky and sometimes fail.
Thanks for updating the driver and restarting. Later, I restarted the laptop again. Event Viewer showed errors around 12:01pm and 12:09pm. A new minidump file was created. The Event Viewer indicated a name resolution timeout for client.wns.windows.com, with no DNS servers responding. Client PID 6440 was involved. The driver logged RTD3, and all connected devices were removed from the driver's state, which likely triggered DeviceDisconnected events. The driver exited RTD3, and now connected devices are generating DeviceConnected events. The previous shutdown at 11:54:24 AM on 5/12/2024 was unexpected. I don’t see the shutdown in Event Viewer. The system rebooted after a bugcheck (error 0x0000009f). A dump was saved at C:\Windows\Minidump\051224-18187-01.dmp. Report ID: 44c83df4-28d6-4620-a70b-8cd83bec28c8. The OS started at 2024-05-12T12:16:09. The last shutdown failed, but the latest boot succeeded. EFI time zone bias is 2047, daylight flags are off, and firmware time is 2024-05-12T12:09:20.
The latest dump matches the previous ones exactly. The issue lies with the Intel AX201 wireless adapter, which is failing the power transition. Updating the driver didn’t resolve the problem, so it’s likely the card itself is faulty. I’ve noticed Intel laptop wireless cards often malfunction; I once had one fail in my own machine and several others have done the same since then.
Open Device Manager, right-click your AX201 and choose Properties. Check the Power Management section and make sure the option to allow the computer to turn off this device is unchecked.
I also observe that the netwtw10.sys version you’re using is from February 22, 2024, whereas the most recent driver available on the Lenovo website is from August 17, 2021. It’s unclear where the updated version came from. If a Windows Update was applied, it should be acceptable. Laptops often require customized drivers for compatibility and power efficiency. A generic Intel driver won’t include those adjustments, which could lead to issues.
You might try downloading the Lenovo driver from their site, uninstalling the existing AX201 driver (by removing it in Device Manager and checking the box to also remove the driver), and then installing the new one.
We’re certain the Lenovo driver will work perfectly with your laptop, so if you’re still seeing the BSOD with the 0x9F error code, it’s probably the AX201 card that needs replacing.
A replacement AX201 is available online for about $20 and changing drivers is straightforward.
Before GPU issues, a suggestion was made to install from Intel, and I downloaded one or two of those software and drivers. It seems the "newer" Intel drivers for network might have helped, and after switching back to the Lenovo 2022 win11 driver, Windows updates worked fine. I'll check if this resolves the problem. Thanks.
Still occurring
https://mega.nz/folder/MpATmL4L#3RV4W2_yX4I8UcQpV_vOoA
appears to be the Wi-Fi adapter, or not? Should I examine the minidump? I only limited the event viewer.
The minidump indicates the issue stems from ntoskrnl.exe.
Reset and/or resume counts don’t align with expected values after hibernation/resume.
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {a6bc66bc-6d1a-476a-a7aa-5e602015543e}, reported an event Fatal error: The miniport failed during power transition to operational power.
6062 - Lso was triggered
Secure Boot update encountered an error: The update couldn’t modify a Secure Boot variable. Error – Secure Boot is not enabled on this machine.
For details, refer to: https://go.microsoft.com/fwlink/?linkid=2169931
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {a6bc66bc-6d1a-476a-a7aa-5e602015543e}, logged Fatal error: Power transition failed.
6062 - Lso was triggered
Attempting name resolution for go.microsoft.com timed out. No DNS servers responded. Client PID 2644.
TCP/IP could not establish a connection because the local endpoint was recently used for the same remote one. This usually happens when connections open and close quickly, exhausting local ports and forcing reuse of a port. To reduce risk of data loss, TCP/IP needs a minimum interval between connections from the same local to remote endpoint.
Power Manager has asked to suppress all input (INPUT_SUPPRESS_REQUEST=1).
Name resolution for client.wns.windows.com timed out after no DNS servers responded. Client PID 6612.
The last system shutdown at 12:30:56 PM on 5/31/2024 was unexpected. Dump file creation failed due to an error during the process.
The system restarted without a clean shutdown. This issue might arise if the system stopped responding, crashed, or lost power unexpectedly.
Driver \Driver\WUDFRd failed to load for device PCI\VEN_8086&DEV_9A03&SUBSYS_380517AA&REV_01&3&11583659&0&20.
Driver \Driver\WudfRd failed to load for device HID\Vid_8087&Pid_0AC2\6&1bba3d2d&0&0000.
Driver \Driver\WudfRd failed to load for device HID\Vid_8087&Pid_0AC2\6&9008c88&0&0000.
Driver \Driver\WUDFRd failed to load for device {DD8E82AE-334B-49A2-AEAE-AEB0FD5C40DD}.
DetectionVerification\5&ed8e0ec error occurred.
The driver \Driver\WUDFRd failed to load for device USB\VID_1C7A&PID_0576\16D807E3.
File System Filter 'Mrvdp' (Version 6.2, 2021-10-13T09:39:11Z) does not allow bypassing IO.
Supported features: 0x4.
Another error occurred during Secure Boot update: the system reported that Secure Boot is not enabled.
More info: https://go.microsoft.com/fwlink/?linkid=2169931
Permission settings for the application do not allow Local Launch for the COM Server app with CLSID Windows.SecurityCenter.WscDataProtection and APPID.
Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from LocalHost using LRPC in the app container.
Unavailable SID (unavailable). This permission can be adjusted via Component Services admin tool.
An error was found.
Error code: 0x145, Sub error code: 0xA9
Another error detected.
Error code: 0x145, Sub error code: 0x1CA
Counts after hibernation/resume didn’t match expectations.
Updated the download folder again – it happened right after I powered down and then crashed upon restarting.
yeah it's been working much better now. It might have gotten some humidity or condensation recently, but overall it's functioning great. I found an ax201 for around $11. I also had a couple of reboots again, so I might upgrade to a new laptop eventually. It seems like the bugcheck is still present, and I'm trying to view a minidump. Not sure if that means the exact issue is the same.
That's a strange comment, we don't often see statements like this. What happened to make you think there might be moisture inside? That would be very bad.
These dumps are all the same, all are 0x9F DRIVER_POWER_STATE_FAILURE bugchecks and all are for the Netwtw10.sys driver again - which I can see has been updated since last time. One thing I do note is that you appear to be using Mullvad Wireguard? There are Wireguard drivers loaded and they too are quite old, dating from 2021...
Code:
2: kd> lmDvmmullvad_wireguard
Browse full module list
start end module name
fffff800`57150000 fffff800`571ea000 mullvad_wireguard (deferred)
Image path: mullvad-wireguard.sys
Image name: mullvad-wireguard.sys
Browse all global symbols functions data
Timestamp: Wed Dec 1 14:13:35 2021 (61A766EF)
CheckSum: 0007BB3B
ImageSize: 0009A000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
It's not beyond the realms of possibility that this is what's causing the delayed power transitions. It might be worth uninstalling it and see whether the 0x9F BSODs stop.