☰

蓝屏错误：DRIVER_POWER_STATE_FAILURE

tag-icon • tag-icon windows-7 64-bit bsod
蓝屏错误：DRIVER_POWER_STATE_FAILURE

最近，我在 Windows 7 64 位 SP1 计算机上遇到了 BSOD，需要帮助来解决这个问题。

这些 BSOD 通常发生在我的计算机空闲一段时间（大约几个小时）时。

最新的 Minidump 文件在这里：https://drive.google.com/file/d/0B8ZIGjkREqeqT0FnMzNVdUVYMTA/edit?usp=sharing。

使用 WinDbg 调试文件显示如下：

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006a92730, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006a92730

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff80003cdbda0 -- (!locks fffff80003cdbda0)

Resource @ nt!PiEngineLock (0xfffff80003cdbda0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80003cdbda0
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80003acd5f2 to fffff80003adaa8a

STACK_TEXT:  
fffff880`03578480 fffff800`03acd5f2 : fffffa80`06a92730 fffffa80`06a92730 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`035785c0 fffff800`03ade99f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`03578650 fffff800`03b98957 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`035786f0 fffff800`03ea351e : fffff800`03cdbb60 fffffa80`0e455740 fffffa80`0d553270 fffffa80`0e4558e8 : nt!PnpDeviceCompletionQueueRemoveCompletedRequest+0x37
fffff880`03578750 fffff800`03ea37a4 : fffffa80`0e455740 fffffa80`0a78004d fffffa80`0a785970 00000000`00000001 : nt!PnpStartDeviceNode+0x16e
fffff880`035787e0 fffff800`03ec6eb6 : fffffa80`0e455740 fffffa80`0a785970 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`03578810 fffff800`03ec7448 : fffff800`03cd9720 00000000`00000000 00000000`00000001 fffff800`03d42258 : nt!PipProcessDevNodeTree+0x296
fffff880`03578a80 fffff800`03bda827 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`03578ad0 fffff800`03ae1261 : fffff800`03bda500 fffff800`03dcec01 fffffa80`06a92700 fffff800`03c7d2d8 : nt!PnpDeviceActionWorker+0x327
fffff880`03578b70 fffff800`03d7373a : 00000000`00000000 fffffa80`06a92730 00000000`00000080 fffffa80`069e0890 : nt!ExpWorkerThread+0x111
fffff880`03578c00 fffff800`03ac88e6 : fffff880`03389180 fffffa80`06a92730 fffff880`033940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03578c40 00000000`00000000 : fffff880`03579000 fffff880`03573000 fffff880`03576a20 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8006a92730 ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80003adadb2 - nt!SwapContext_PatchXSave+2
    [ 01:21 ]
    fffff80003adae96 - nt!SwapContext_PatchXRstor+2 (+0xe4)
    [ 09:29 ]
2 errors : !nt (fffff80003adadb2-fffff80003adae96)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption

使用 BlueScreenView 进行调试显示如下：https://drive.google.com/file/d/0B8ZIGjkREqeqc29jYXlsS29yZEk/edit?usp=sharing

考虑到这可能是驱动程序问题，我尝试运行驱动程序验证程序，但我的计算机在 Windows 启动屏幕上不断崩溃。崩溃时没有创建任何小型转储文件。

如果有人能帮助我解决这个问题就太好了。

谢谢大家！

答案1

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80003adadb2 - nt!SwapContext_PatchXSave+2
    [ 01:21 ]
    fffff80003adae96 - nt!SwapContext_PatchXRstor+2 (+0xe4)
    [ 09:29 ]
2 errors : !nt (fffff80003adadb2-fffff80003adae96)

MODULE_NAME: memory_corruption

这表明您的 Windows 内核部分已损坏。这可能是由于 RAM 损坏（RAM 损坏）或 HDD 上的文件本身已损坏而导致的。

所以你应该跑memtest86+检查 RAM，如果没问题，运行chkdsk /f修复 NTFS 文件系统问题并运行证监会/扫描检测并修复损坏的 Windows 文件。

相关内容