DPC_WATCHDOG_VIOLATION Mavi ekran hatası

mardabuzbuz

Femtopat
Katılım
11 Ekim 2020
Mesajlar
9
Daha fazla  
Cinsiyet
Erkek
Yeni satın aldığım bilgisayarda mavi ekran hatası aldım. Minidump dosyaları ektedir. Daha önce mavi ekran aldığımda Windows'u güncellemem söylendi yaptım uzun bir süre mavi ekran almamıştım.

MINIDUMP
 
Son düzenleyen: Moderatör:
Memtest86 ile bellek testi yapınız. Yeni sistem alan herkese bozuk bellekler veriyorlar sanırım.
Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff804190fb320, 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 checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7702

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-J7A11VA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 14860

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff804190fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff2852f453500 -- (.trap 0xfffff2852f453500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000a7adcb48 rbx=0000000000000000 rcx=fffff2852f453728
rdx=ffffa9817a7f5080 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804186bee17 rsp=fffff2852f453690 rbp=000000052ceed300
r8=fffff2852f4538e8  r9=0000000000000000 r10=0000000000000000
r11=fffff2852f4538c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff804`186bee17 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8201`9d4e8c88 fffff804`18887a98     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`190fb320 : nt!KeBugCheckEx
ffff8201`9d4e8c90 fffff804`1872b7cd     : 0000b3af`1d10feb0 ffff8201`9d4cf180 00000000`00200246 00000000`00586012 : nt!KeAccumulateTicks+0x15dda8
ffff8201`9d4e8cf0 fffff804`1872bd71     : 00000000`00000000 00000000`0034acff ffff8201`9d4cf180 00000000`00001001 : nt!KiUpdateRunTime+0x5d
ffff8201`9d4e8d40 fffff804`18726823     : ffff8201`9d4cf180 00000000`00000000 fffff804`19031a08 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffff8201`9d4e8e80 fffff804`1872e382     : fffff285`2f453500 fffff285`2f453580 fffff285`2f453500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffff8201`9d4e8f30 fffff804`1862ecd5     : 000000d2`b57abb00 ffffa981`6dac8ac0 ffffa981`6dac8b70 ffff702a`46a79173 : nt!HalpTimerClockInterrupt+0xe2
ffff8201`9d4e8f60 fffff804`187f604a     : fffff285`2f453580 ffffa981`6dac8ac0 fffff285`2f453b10 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8201`9d4e8fb0 fffff804`187f65b7     : fffff285`2f453500 00000000`00000000 ffffa981`7a7f5080 fffff804`187f65c4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff285`2f453500 fffff804`186bee17     : ffffffff`ffffffd1 fffff804`186c603e 00000000`00000010 00000000`00200282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff285`2f453690 fffff804`186c603a     : 00000000`00200282 fffff804`186c5141 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x17
fffff285`2f4536c0 fffff804`186bf4fd     : 00000000`00349b35 fffff285`2f453b10 00000000`00000080 ffff8201`9d4cf180 : nt!KiDeferredReadySingleThread+0xc3a
fffff285`2f4538b0 fffff804`186bf8e0     : ffff8201`9d4cf180 00000000`00000000 ffffa981`7bd04200 00000000`00000002 : nt!KiReadyThread+0x4d
fffff285`2f4538e0 fffff804`186e4b6d     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00349b35 : nt!KiProcessExpiredTimerList+0x290
fffff285`2f4539d0 fffff804`187f810e     : ffffffff`00000000 ffff8201`9d4cf180 ffff8201`9d4da1c0 ffffa981`7650b080 : nt!KiRetireDpcList+0x5dd
fffff285`2f453c60 00000000`00000000     : fffff285`2f454000 fffff285`2f44e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KeAccumulateTicks+15dda8

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  15dda8

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------
RAM'ler farklı marka veya kit değilseler iade edin.
 
Son düzenleyen: Moderatör:
Sistemi sıfır mı aldın ikinci el mi? Sıfırsa direkt bu rehberi uygula.

İkinci el ise:
-Prime95 testi.
-CrystalDiskInfo, HD Sentinel ve HD Tune Pro kurup "Health" kısmının ekran görüntülerini paylaş.

Ek olarak bu testleri varsa iki disk için paylaş. Tek disk için paylaşma.
 

Geri
Yukarı