Çözüldü Driver state failure mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

turhan64

Hectopat
Katılım
18 Ocak 2018
Mesajlar
40
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Merhaba, bilgisayarın ekran kartını en son sürümüyle güncelledikten sonra bu hatayı almaya başladım. Bununla birlikte "dpc watchdog violation" hatası da aldım. Hatayı almadan önce bilgisayar bi donuyo. Sonra farenin USB girişini çıkarınca bilgisayar kendine geliyor fakat sonradan mavi ekran hatasını veriyor. Ekran kartını DDU ile silip en son sürümünü tekrar indirdim ve yükledim hala olmadı. Ne yapmam lazım? Bilgisayarım Monster Abra A5 v11.1, Nvidia 1050 , Intel 7700HQ. Teşekkürler.
 
Son düzenleyen: Moderatör:
Sorun tekrar ederse ekran kartı sorunu olması muhtemel.

Kod:
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff802c5e59378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 5

Key : Analysis.Elapsed.Sec
Value: 61

Key : Analysis.Memory.CommitPeak.Mb
Value: 69


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: MONSTER

SYSTEM_PRODUCT_NAME: ABRA A5 V11.1

SYSTEM_SKU: Not Applicable

SYSTEM_VERSION: Not Applicable

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.05.15RMO3.

BIOS_DATE: 11/02/2017

BASEBOARD_MANUFACTURER: MONSTER

BASEBOARD_PRODUCT: ABRA A5 V11.1

BASEBOARD_VERSION: Not Applicable

DUMP_TYPE: 2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff802c5e59378

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: af8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: DESKTOP-NG9H4F5

ANALYSIS_SESSION_TIME: 05-19-2019 18:46:04.0947

ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

LAST_CONTROL_TRANSFER: from fffff802c5c08df1 to fffff802c5bb7ab0

STACK_TEXT:
fffff802`c806fb78 fffff802`c5c08df1 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`c5e59378 : nt!KeBugCheckEx
fffff802`c806fb80 fffff802`c5aa28bd : 0000671b`31e7e171 fffff802`c58f6180 00000000`00200246 00000000`00b7aba9 : nt!KeAccumulateTicks+0x162a11
fffff802`c806fbe0 fffff802`c5aa39a3 : fffff780`00000340 00000000`00000000 00000000`00b7aba9 00000000`00000000 : nt!KiUpdateRunTime+0x5d
fffff802`c806fc30 fffff802`c6362883 : 0000671b`31e7a3f4 00000000`00000000 00000000`00000000 fffff802`c805f650 : nt!KeClockInterruptNotify+0x8f3
fffff802`c806ff40 fffff802`c5a17925 : fffff802`c63c5000 00000000`00087144 ffffa300`00000000 ffffa367`85a6f508 : hal!HalpTimerClockInterrupt+0x63
fffff802`c806ff70 fffff802`c5bb936a : fffff802`c805f6d0 fffff802`c63c5000 00000000`00000001 00000000`00000001 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`c806ffb0 fffff802`c5bb9857 : 00000000`000000fe 00000000`00000000 00000000`00140001 00000000`000000fe : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff802`c805f650 fffff802`c5b0c8dc : 00000000`00000002 00000000`00000001 ffff4704`7d5f178f 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`c805f7e0 fffff802`c5b0c86d : fffff802`c58f6180 00000000`00000000 fffff802`c58f6180 00000000`00000000 : nt!KiIpiWaitForRequestBarrier+0x2c
fffff802`c805f810 fffff802`c5b0d00a : fffff802`c58f6180 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiIpiSendRequestEx+0x69
fffff802`c805f850 fffff802`c5b08552 : 00000000`00000000 00000000`00000001 00000000`00281500 00000000`00000001 : nt!KxFlushNonGlobalTb+0x9a
fffff802`c805f960 fffff802`c5aaff57 : 00000000`00000001 fffff802`c805fb40 00000000`00000000 ffffcf0b`4defdf00 : nt!KeFlushTb+0xc2
fffff802`c805f9b0 fffff802`c5af9d15 : 00000000`00000000 00000000`00000001 00000000`002815e6 00000000`002815e6 : nt!MiFlushTbList+0x417
fffff802`c805fb00 fffff802`c5a3eefd : ffffa367`85a6f000 00000000`000000fe 8a000000`00000863 ffffa351`b3c2d378 : nt!MiFlushTbAsNeeded+0x285
fffff802`c805fc50 fffff802`c5af9353 : fffff802`c5dd9b90 ffffa367`85a6f000 fffff802`c805fda0 0a000002`6ed4b863 : nt!MiAssignNonPagedPoolPtes+0x7d
fffff802`c805fca0 fffff802`c5af96b0 : fffff802`c805fec8 fffff802`00000000 00000000`00001000 00000000`00001000 : nt!MiCommitPoolMemory+0x773
fffff802`c805fde0 fffff802`c5a72053 : fffff802`c805fee1 00000000`00100000 fffff802`c5def800 00000000`00000100 : nt!MmAllocatePoolMemory+0x80
fffff802`c805fe40 fffff802`c5cf86b7 : 00000000`00000000 00000000`4d52564e fffff802`c5e70000 00000000`4d52564e : nt!ExpAllocateBigPool+0x713
fffff802`c805ff40 fffff806`81682077 : 00000000`00000000 fffff806`817aa764 00000000`4d52564e ffffcf0b`4740b000 : nt!ExAllocatePoolWithTag+0x927
fffff802`c8060030 00000000`00000000 : fffff806`817aa764 00000000`4d52564e ffffcf0b`4740b000 ffffcf0b`47436d80 : nvlddmkm+0xe2077


THREAD_SHA1_HASH_MOD_FUNC: a67a342d2c106c26d19d78d0ba11656777922e98

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: fdf55875fef4bb74a89ef626c94d406b33b1dba2

THREAD_SHA1_HASH_MOD: a6139c745ffb4f96bf11d14926bcc2b223454d09

FOLLOWUP_IP:
nvlddmkm+e2077
fffff806`81682077 488bf0 mov rsi,rax

FAULT_INSTR_CODE: 48f08b48

SYMBOL_STACK_INDEX: 13

SYMBOL_NAME: nvlddmkm+e2077

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5c6d35f0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: e2077

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function

TARGET_TIME: 2019-05-18T02:08:37.000Z

OSBUILD: 17134

OSSERVICEPACK: 765

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-05-03 08:57:58

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: f104

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function

FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup: MachineOwner
---------
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Geri
Yukarı