por favor, tenha paciência se eu postar outra pergunta sobre este assunto, mas isso está começando a me matar.
As especificações completas do meu bloco de notas estão aqui: link
Eu notei BSOD freqüente quando em gerenciamento de energia "equilibrado" ou na energia da bateria. Então eu habilitei MiniDumps e inicialmente achei o driver wi-fi e basic-video como implicado. Então eu colocá-los em "desempenho máximo", enquanto no poder "equilibrado" e fiquei com apenas ntoskrnl.exe como causa provável no próximo BSOD.
Depois que eu habilitei os Dumps de memória completos, no WinDbg eu li isso depois de mais um driver_power_state_failure:
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
Machine Name:
Kernel base = 0xfffff801'7dc07000 PsLoadedModuleList = 0xfffff801'7ded1350
Debug session time: Thu Apr 23 19:20:19.120 2015 (UTC + 2:00)
System Uptime: 0 days 6:35:19.836
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe00065601730, ffffd000576ad930, ffffe00068274800}
Probably caused by : pci.sys
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffe00065601730, Physical Device Object of the stack
Arg3: ffffd000576ad930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00068274800, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe000645f69b0
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4
MODULE_NAME: pci
FAULTING_MODULE: fffff80130d92000 pci
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFD000576B4FB0
STACK_TEXT:
ffffd000'576ad8f8 fffff801'7de03586 : 00000000'0000009f 00000000'00000003 ffffe000'65601730 ffffd000'576ad930 : nt!KeBugCheckEx
ffffd000'576ad900 fffff801'7de034a6 : ffffe000'69bfaf08 00000000'ffffffff ffffe000'69bfaf48 fffff801'7dc4d190 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000'576ad960 fffff801'7dc49760 : 00000000'00000000 ffffd000'576adab0 ffffe000'69bfaf40 fffff801'00000002 : nt!PopIrpWatchdog+0x32
ffffd000'576ad9b0 fffff801'7dd5e7ea : ffffd000'57683180 ffffd000'57683180 ffffd000'5768f3c0 ffffe000'639f55c0 : nt!KiRetireDpcList+0x4f0
ffffd000'576adc60 00000000'00000000 : ffffd000'576ae000 ffffd000'576a8000 00000000'00000000 00000000'00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_image_pci.sys
FAILURE_ID_HASH: {a89ab2d1-2459-89ee-9990-558bbc68ffab}
Followup: MachineOwner
Neste ponto, eu não tenho ideia do que posso fazer para evitar essa falha (além de ficar sempre conectado à rede elétrica e do "desempenho máximo" na gestão de energia.
Arquivos DUMP reais aqui: link
Obrigado por qualquer ajuda.