İyi akşamlar. Birkaç gündür mavi ekran hatası alıyorum. Yardımcı olabilecek var mı? Teşekkürler.
Minidump Yandex
Minidump Yandex
Son düzenleyen: Moderatör:
DPC Watchdog Violation Mavi Ekran Hatası
- Konuyu başlatan uakaraca
- Başlangıç Tarihi
- Mesaj 1
- Görüntüleme 584
-
- Etiketler
- minidump bluescreen
- Katılım
- 8 Aralık 2013
- Mesajlar
- 31.927
- Makaleler
- 25
- Çözümler
- 633
Ekran kartı sürücü sorunu gibi duruyor. Klasik cevabımızı verelim:
DDU ile NVIDIA sürücüsünü güvenli modda kaldırın. Normal modda en güncel sürümünü yükleyin.
DDU ile NVIDIA sürücüsünü güvenli modda kaldırın. Normal modda en güncel sürümünü yükleyin.
Kod:
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: ffffc20260315060, Physical Device Object of the stack
Arg3: ffffa708e667f7b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc202605a8cf0, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffc202`676a0040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 6
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-K01TCKK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 30
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffc20260315060
BUGCHECK_P3: ffffa708e667f7b0
BUGCHECK_P4: ffffc202605a8cf0
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffc202676a0040
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa708`e780e7c0 fffff803`7443c77d : ffff9701`47458180 fffff803`ffffff00 ffff9701`ffffffff 00000000`0000003f : nt!KiSwapContext+0x76
ffffa708`e780e900 fffff803`7443b604 : ffffc202`676a0040 00000000`00000000 ffffa708`00000000 00000000`00000000 : nt!KiSwapThread+0xbfd
ffffa708`e780e9a0 fffff803`7443ada5 : 00000000`00000001 00000000`00000000 00000036`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144
ffffa708`e780ea40 fffff803`7aa5033c : ffffc202`606dc190 fffff803`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x255
ffffa708`e780eb20 ffffc202`606dc190 : fffff803`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1d033c
ffffa708`e780eb28 fffff803`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000000c0 : 0xffffc202`606dc190
ffffa708`e780eb30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`000000c0 00000000`00000001 : 0xfffff803`00000000
STACK_COMMAND: .thread 0xffffc202676a0040 ; kb
SYMBOL_NAME: nvlddmkm+1d033c
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
BUCKET_ID_FUNC_OFFSET: 1d033c
FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8b257f08-e34e-7c26-3880-084b82f90c48}
Followup: MachineOwner
---------
