Eu tenho experimentado muitos BSODs nas últimas semanas.
O código de parada é sempre 0x9F (driver_power_state_failure).
Eu salvei quatro despejos de memória dos últimos três dias e usei o WinDbg do Windows SDK para compará-los. Os detalhes de depuração geralmente são os mesmos (veja a parte inferior desta postagem).
Observando os IDs do intervalo, isso mostra que o nvlddmkm.sys tem algo a ver com isso. Este é um driver da NVidia, e quando eu pensei sobre isso, as BSODs começaram a aparecer depois de atualizar o meu driver da versão 325 para 347.
Sempre antes de tal BSOD aparecer, eu posso ver no Gerenciador de Tarefas que o thread do sistema (NT Kernel & System) usa até 25% da minha CPU de 4 segmentos. Depois de alguns minutos, meu PC não responde no sentido mais literal: a tela congela. No entanto: quando eu estava ligando para o Skype antes de um BSOD, eu ainda podia ouvir a outra pessoa enquanto a tela estava congelada. Outros 8-10 minutos após o congelamento, o BSOD surge.
Eu já reinstalei o Windows da partição de restauração do fabricante. Também atualizei os drivers da NVidia para a versão mais recente (algumas vezes, usando instalações limpas).
Eu posso fornecer os mais recentes depósitos, minidespejos ou outras informações, se necessário.
Especificações do PC:
- Acer Aspire V3-771
- x64 do Windows 7 Home Premium
- RAM DDR3 de 8 GB
- Intel Core i5-3210M 2.5GHz, núcleo dual, 4 segmentos
- ecrã LCD Full HD (1920x1080, 32 bits, 60 Hz)
- NVidia GeForce GT 650M
As informações a seguir foram Copiadas / Pastadas do WinDbg. Todos os 4 despejos de memória pareciam iguais, exceto pelo rastreamento de pilha.
0: 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: fffffa8007ed0a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800d8e1e10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f
MODULE_NAME: pci
FAULTING_MODULE: fffff88000f5a000 pci
DEFAULT_BUCKET_ID: WIN7_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: FFFFF8000480EFB0
fffff800'00b9c388 fffff800'02f41b92 : 00000000'0000009f 00000000'00000003 fffffa80'07ed0a10 fffff800'00b9c3d8 : nt!KeBugCheckEx
fffff800'00b9c390 fffff800'02edccfc : fffff800'00b9c4c0 fffff800'00b9c4c0 00000000'00000000 00000000'00000001 : nt! ?? ::FNODOBFM::'string'+0x33af0
fffff800'00b9c430 fffff800'02edcb96 : fffff800'03083140 00000000'00324674 00000000'00000000 00000000'00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800'00b9c4a0 fffff800'02edca7e : 00000077'aca84f27 fffff800'00b9cb18 00000000'00324674 fffff800'03051108 : nt!KiProcessExpiredTimerList+0xc6
fffff800'00b9caf0 fffff800'02edc867 : 0000001d'25ead5c1 0000001d'00324674 0000001d'25ead5e0 00000000'00000074 : nt!KiTimerExpiration+0x1be
fffff800'00b9cb90 fffff800'02ec8bca : fffff800'0304de80 fffff800'0305bcc0 00000000'00000002 fffff880'00000000 : nt!KiRetireDpcList+0x277
(...the top always looks like this, the rest of the stack mostly has some nvlddmkm in it)
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.17514
FAILURE_BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
BUCKET_ID: X64_0x9F_3_nvlddmkm_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x9f_3_nvlddmkm_image_pci.sys
FAILURE_ID_HASH: {86b85873-d822-8588-0151-5cf4191a225f}
Followup: MachineOwner
---------
0: kd> !devobj fffffa8007ed0a10
Device object (fffffa8007ed0a10) is for:
NTPNP_PCI0017 \Driver\pci DriverObject fffffa80072b5e70
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00001040
Dacl fffff9a1002db971 DevExt fffffa8007ed0b60 DevObjExt fffffa8007ed0f88 DevNode fffffa8007ecb8c0
ExtensionFlags (0000000000)
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) fffffa8007ecbe40 \Driver\ACPI
Device queue is not busy.
0: kd> !irp fffffa800d8e1e10
Irp is active with 4 stacks 3 is current (= 0xfffffa800d8e1f70)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
[ 0, 0] 0 2 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 ffffffffc000000e
[ 16, 0] 0 2 fffffa8007ed0a10 00000000 fffff88005bdc328-fffffa800d096650
\Driver\pci nvlddmkm
Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 fffffa800ae7b040 00000000 00000000-00000000 pending
\Driver\nvlddmkm
Args: 00000000 00000001 00000001 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa800e30a4a0
Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa800ae7b040
Device object (fffffa800ae7b040) is for:
\Driver\nvlddmkm DriverObject fffffa800ad60060
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
DevExt fffffa800ae7b190 DevObjExt fffffa800ae7bb48
ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8007ecbe40 \Driver\ACPI
Device queue is not busy.