Błąd zasilania urządzenia lub źle napisany sterownik. Problem pojawia się głównie podczas przechodzenia do/z trybu gotowości, hibernacji czy zamykania systemu.
Jaki masz zasilacz? Próbowałeś może go podmienić dla próby? Analiza dumpa z załadowanymi symbolami mówi:
Niestety WUDFRd.sys to nic innego jakDRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800c5ae990, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800d8507d0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800d8507d0
DEVICE_OBJECT: fffffa800ba194f0
DRIVER_OBJECT: fffffa800bd014a0
IMAGE_NAME: WUDFRd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5010aabe
MODULE_NAME: WUDFRd
FAULTING_MODULE: fffff880095a2000 WUDFRd
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff8000313b6d2 to fffff800030d0fc0
STACK_TEXT:
fffff800`00b9c388 fffff800`0313b6d2 : 00000000`0000009f 00000000`00000003 fffffa80`0c5ae990 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`030dbc3c : fffff800`00b9c4d8 fffff800`00b9c4d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`00b9c430 fffff800`030dbad6 : fffff800`03278f20 00000000`0004eecb 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`030db9be : 0000000b`bdf1814d fffff800`00b9cb18 00000000`0004eecb fffff800`03247be8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`030db7a7 : 00000003`e71c97c2 00000003`0004eecb 00000003`e71c9774 00000000`000000cb : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`030c8cca : fffff800`03243e80 fffff800`03251cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_IMAGE_WUDFRd.sys
BUCKET_ID: X64_0x9F_IMAGE_WUDFRd.sys
Followup: MachineOwner
---------
Driver Description: Windows Driver Foundation - User-mode Driver Framework Reflector
Lecz to jest wrzucane domyślnie jeśli analizator nie znajduje właściwego problemu, a przynajmniej tak piszą ludzie po forach i zalecają użycie Driver Verifier oraz przed tym jeszcze:
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.