This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 27%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
*******************************************************************************
* *
* 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: ffffcd020acf9df0, Physical Device Object of the stack
Arg3: ffffe80e2922f6d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffcd0215cbb010, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffcd02`1b91c040
*** WARNING: Check Image - Checksum mismatch - Dump: 0x47cf1, File: 0x47738 - C:\ProgramData\Dbg\sym\ucx01000.sys\BACB774A46000\ucx01000.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3733
Key : Analysis.Elapsed.mSec
Value: 17170
Key : Analysis.IO.Other.Mb
Value: 2
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 5
Key : Analysis.Init.CPU.mSec
Value: 656
Key : Analysis.Init.Elapsed.mSec
Value: 39546
Key : Analysis.Memory.CommitPeak.Mb
Value: 119
Key : Bugcheck.Code.LegacyAPI
Value: 0x9f
Key : Bugcheck.Code.TargetModel
Value: 0x9f
Key : Failure.Bucket
Value: 0x9F_3_POWER_DOWN_ndis!ndisWaitForKernelObject
Key : Failure.Hash
Value: {72c8f05e-7820-a1d9-f367-64bcbf47c096}
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Version
Value: 10.0.22000.1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffcd020acf9df0
BUGCHECK_P3: ffffe80e2922f6d0
BUGCHECK_P4: ffffcd0215cbb010
FILE_IN_CAB: 052824-19437-01.dmp
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffcd021b91c040
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe80e`30d7ff30 fffff807`38a1d847 : ffff9200`a2091180 fffff807`ffffffff ffff8186`20a00380 00000000`000000ff : nt!KiSwapContext+0x76
ffffe80e`30d80070 fffff807`38a1f6f9 : 00000000`00000003 fffff807`00000000 ffffe80e`30d80250 00000000`00000000 : nt!KiSwapThread+0x3a7
ffffe80e`30d80150 fffff807`38a19614 : 00000000`00000000 ffffcd02`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x159
ffffe80e`30d801f0 fffff807`3dd31031 : ffffe80e`30d803e0 ffffcd02`00000000 ffffe80e`00000000 fffff807`3dc53900 : nt!KeWaitForSingleObject+0x234
ffffe80e`30d802e0 fffff807`3dd4d233 : ffffcd02`155fa8b0 ffffe80e`30d80410 ffffcd02`128c81a0 fffff807`3dd3409a : ndis!ndisWaitForKernelObject+0x21
ffffe80e`30d80320 fffff807`3dd352d2 : ffffcd02`155fa8b0 ffffcd02`128c81a0 fffff807`00000103 00000000`00000000 : ndis!NdisWatchdogState::WaitSynchronously+0x17f4f
ffffe80e`30d80360 fffff807`3dd72268 : ffffcd02`128c81a0 ffffcd02`128c81a0 00000000`00000022 fffff807`3dd1b050 : ndis!ndisWaitForEventThenDisarmWatchdog+0x32
ffffe80e`30d80390 fffff807`3dd33f5f : 00000000`00000000 fffff807`3dd00f38 00000000`00000004 ffffcd02`128c81a0 : ndis!ndisMPauseMiniportInner+0x8198
ffffe80e`30d80440 fffff807`3dd37e03 : 00000000`00000000 ffffe80e`30d80580 ffffcd02`128c9598 ffffcd02`128c9598 : ndis!ndisMPauseMiniport+0x7b
ffffe80e`30d80480 fffff807`3dd37574 : ffffcd02`128c81a0 ffffcd02`128c81a0 ffffcd02`128c9610 ffffcd02`128c9598 : ndis!Ndis::BindEngine::Iterate+0x5bf
ffffe80e`30d80600 fffff807`3dd3bcd6 : ffffcd02`128c9598 ffffe80e`30d80900 00000000`00000000 00000000`00000000 : ndis!Ndis::BindEngine::UpdateBindings+0x98
ffffe80e`30d80650 fffff807`3dd3bbd0 : ffffcd02`128c9598 00000000`00000000 ffff9b27`2b0b188a fffff807`3dc4cc21 : ndis!Ndis::BindEngine::DispatchPendingWork+0x76
ffffe80e`30d80680 fffff807`3dd33eb8 : ffffcd02`128c81a0 ffffe80e`30d80960 ffffcd02`15cbb010 ffffe80e`30d80760 : ndis!Ndis::BindEngine::ApplyBindChanges+0x54
ffffe80e`30d806d0 fffff807`3dc6db5d : ffffcd02`1c2815b0 ffffcd02`128c81a0 ffffcd02`128c81a0 ffffcd02`15cbb010 : ndis!ndisIssueNetEventSetPowerEvent+0x8c
ffffe80e`30d807d0 fffff807`3dc440ed : 00000000`00000000 ffffcd02`128c81a0 ffffcd02`128c81a0 fffff807`3dd3bd2a : ndis!ndisPrepForLowPowerCommon+0x29765
ffffe80e`30d808c0 fffff807`3dc44da1 : 00000000`00000005 ffffcd02`15cbb010 ffffcd02`128c81a0 fffff807`3dc3d5e8 : ndis!ndisPrepForLowPower+0x1d
ffffe80e`30d80910 fffff807`3dc44bca : 00000000`00000000 ffffcd02`00000004 ffffcd02`128c81a0 ffffcd02`15cbb128 : ndis!ndisSetSystemPower+0x1cd
ffffe80e`30d80990 fffff807`3dc468de : ffffcd02`15cbb010 ffffcd02`0acf9df0 ffffcd02`15cbb128 ffffcd02`128c81a0 : ndis!ndisSetPower+0x10a
ffffe80e`30d809f0 fffff807`38bb01b7 : ffffcd02`1b91c040 ffffe80e`30d80ad0 00000000`00000000 ffffcd02`128c8050 : ndis!ndisPowerDispatch+0x11e
ffffe80e`30d80a50 fffff807`38af1b05 : ffffffff`fa0a1f00 fffff807`38baffb0 ffffcd02`1bef93d0 00000000`0000048c : nt!PopIrpWorker+0x207
ffffe80e`30d80af0 fffff807`38c226a4 : ffff9200`a2091180 ffffcd02`1b91c040 fffff807`38af1ab0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffe80e`30d80b40 00000000`00000000 : ffffe80e`30d81000 ffffe80e`30d7a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: ndis!ndisWaitForKernelObject+21
MODULE_NAME: ndis
IMAGE_NAME: ndis.sys
IMAGE_VERSION: 10.0.22000.2110
STACK_COMMAND: .process /r /p 0xffffcd020ab45040; .thread 0xffffcd021b91c040 ; kb
BUCKET_ID_FUNC_OFFSET: 21
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_ndis!ndisWaitForKernelObject
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {72c8f05e-7820-a1d9-f367-64bcbf47c096}
Followup: MachineOwner
---------
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 74%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Please run the V2 log collector and post a share link using one drive, drop box, or google drive.
BSOD - Posting Instructions - Windows 10 Forums (tenforums.com)
BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)
Make sure that links are available without sign in.
https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html
https://www.tenforums.com/tutorials/136792-change-display-language-windows-10-a.html#option1
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 55.00000000000001%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHL%3C/text%3E%3C/svg%3E)
Hello,
The DRIVER_POWER_STATE_FAILURE error with the specific reference to “ndis.sys” indicates a problem with a network driver within the Windows operating system. Here are a few steps you can take to address this issue:
Bug Check 0x9F DRIVER_POWER_STATE_FAILURE - Windows drivers | Microsoft Learn
Update or Roll Back Network Drivers:
Go to the Device Manager by right-clicking on the Start button and selecting “Device Manager.”
Locate the “Network adapters” section, right-click on your network adapter, and select “Update driver.”
Choose automatic update to let Windows search for the latest driver software or download the driver from manufacturer to install.
Check for Windows Updates:
Make sure your Windows operating system is fully updated. Sometimes, new updates include fixes for issues related to drivers and system stability.
Use the Windows Driver Verifier:
The Windows Driver Verifier tool can help in identifying problematic drivers. You can enable it in the Command Prompt with administrative privileges by typing “verifier” and pressing Enter. Follow the on-screen instructions to configure the tool.
Best Regards,
Hania Lian
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
@Hania Lian I tried what you suggested, but it didn't solve the problem.
Please perform the following steps:
.
.
.
1)Free up C: drive space so that there is > 30 GB free space
.
.
.
2)Uninstall any software that has been preventing Windows updates (last recorded update: 2023/10/11)
.
.
.
3)Uninstall all Avast software using the applicable uninstall tool:
https://www.avast.com/en-us/uninstall-utility#pc
https://support.avast.com/en-us/article/uninstall-antivirus-utility/#pc
.
.
.
4)Reset Windows updates:
https://www.elevenforum.com/t/reset-windows-update-in-windows-11.3808/
.
.
.
5)Run Tuneup plus > post a share link
https://www.tenforums.com/bsod-crashes-debugging/162488-batch-files-use-bsod-debugging.html#Part3
.
.
.
6)Create a new restore point:
https://www.elevenforum.com/t/create-system-restore-point-in-windows-11.3602/
.
.
.
7)The BIOS 版本/日期 American Megatrends Inc. 1.05.03RHM2, 2018/4/13
Check the Clevo website for a newer version.
If available upgrade the BIOS.
https://clevo-computer.com/media/pdf/73/14/57/NB50TK1-SM-20180427.pdf
.
.
.
8)The RAM modules are mismatched > it's best to use matching RAM modules
.
.
.
9)For new BSOD after completing all of the above steps > post a new V2 share link into the newest post
.
.
.
10)Make sure that links do not require sign in or logon (publicly available with one click)
.
.
.
Drive: C:
Free Space: 4.2 GB
Total Space: 121.2 GB
File System: NTFS
Model: Phison SATA SSD
I ran Tuneup Plus, but I don't know where the files it generated are located.
There is a pop up with instructions when it completes. The new fike is on the desktop. It can run multiple times.
The link was not able to be viewed.
Make sure that links are available without sign in.
Update the progress with each step from the earlier post.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more