Como resolver travamento com tela azul? leitura codigo dump

Luedson Back · 8 de janeiro de 2023

Bom dia, estou tendo problema com um computador novo AMD Ryzen 4600 - rx 6600 - 16gb

Aleatoriamente o pc trava e da tela azul, eu não consigo achar o problema. tenho um básico conhecimento mas nada que eu consiga me virar sozinho.

Fiz um despejo de memória e executei, mas não sei ler o codigo. Se alguém conseguir me ajudar eu ficarei grato.


Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\lueds\OneDrive\Área de Trabalho\despejo de memória\010823-7703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`63800000 PsLoadedModuleList = 0xfffff803`6442a290
Debug session time: Sun Jan  8 09:08:00.081 2023 (UTC - 3:00)
System Uptime: 0 days 0:30:34.719
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`63bf92a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff803`6a47ec90=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff803644fb320, 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                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2499

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2519

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 2921

    Key  : Analysis.Init.Elapsed.mSec
    Value: 25448

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  010823-7703-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff803644fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  cod.exe

STACK_TEXT:  
fffff803`6a47ec88 fffff803`63c5be7a     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`644fb320 : nt!KeBugCheckEx
fffff803`6a47ec90 fffff803`63ad844d     : 00000632`d16f8ad1 fffff803`623c7180 00000000`00000246 00000000`0001caae : nt!KeAccumulateTicks+0x186c4a
fffff803`6a47ecf0 fffff803`63ad89f1     : ffffb479`8ce0000b 00000000`00011164 fffff803`623c7180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff803`6a47ed40 fffff803`63ad2863     : fffff803`623c7180 00000000`00000000 fffff803`64431828 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff803`6a47ee80 fffff803`63adb222     : fffff803`6a477640 fffff803`6a4776c0 fffff803`6a477600 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff803`6a47ef30 fffff803`63a08aa5     : 00000004`45aa89c3 fffff803`644f3a20 fffff803`644f3ad0 ffffc480`e51e6500 : nt!HalpTimerClockInterrupt+0xe2
fffff803`6a47ef60 fffff803`63bfb23a     : fffff803`6a4776c0 fffff803`644f3a20 00000004`3d0d9b66 ffffc480`e4baa180 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`6a47efb0 fffff803`63bfba07     : 00000004`38770745 00000000`00000004 00000000`00000000 00001f80`00000201 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff803`6a477640 fffff803`63ad21b8     : 00000000`00000000 fffff803`00000000 00000004`38699907 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`6a4777d0 fffff803`63ad1cbc     : 00000000`00000000 ffff8605`aeafed10 ffff8605`aeafed90 ffff8605`aeafd610 : nt!PpmSnapPerformanceAccumulation+0xe8
fffff803`6a477880 fffff803`63adb640     : 00000000`00000000 fffff803`6a477ea0 00000000`00000000 fffff803`63ace6d0 : nt!PpmCheckSnapAllDeliveredPerformance+0x1ac
fffff803`6a477a50 fffff803`63adb106     : 00000000`3faaaaab 00000000`00000000 fffff803`6a477cb0 fffff803`6a477ea0 : nt!PpmCheckRun+0x40
fffff803`6a477ac0 fffff803`63adbfae     : 00000000`00000000 fffff803`6a477ea0 ffffffff`ffffff00 fffff803`63adbf00 : nt!PpmCheckStart+0x106
fffff803`6a477b60 fffff803`63a348fe     : fffff803`623ca240 ffff8605`a9ec9000 00000000`00000000 ffff8605`00000002 : nt!PpmCheckPeriodicStart+0x3e
fffff803`6a477bb0 fffff803`63a33be4     : fffff803`623c7180 00000000`00000000 00000000`0000002a 00000000`0000ff9f : nt!KiExecuteAllDpcs+0x30e
fffff803`6a477d20 fffff803`63c01795     : 00000000`00000000 fffff803`623c7180 ffffc480`e51e6500 00000187`b7b27238 : nt!KiRetireDpcList+0x1f4
fffff803`6a477fb0 fffff803`63c01580     : ffffffff`ffffffb4 fffff803`63c00cf1 00000000`01000010 00000000`00000286 : nt!KxRetireDpcList+0x5
ffff9685`3c47dac0 fffff803`63c00d05     : 00000187`b7b27238 fffff803`63bfa9b1 00000187`b79fe2f0 ffff8605`b2c85540 : nt!KiDispatchInterruptContinue
ffff9685`3c47daf0 fffff803`63bfa9b1     : 00000187`b79fe2f0 ffff8605`b2c85540 00007ffa`e25b2a70 00000000`00000020 : nt!KiDpcInterruptBypass+0x25
ffff9685`3c47db00 00007ff6`d6ec0674     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiChainedDispatch+0xb1
0000003f`c49fd6c0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`d6ec0674


SYMBOL_NAME:  nt!KeAccumulateTicks+186c4a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2364

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  186c4a

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------

rodrigo.dcvieira · 8 de janeiro de 2023

1 hora atrás, Luedson Back disse:

Aleatoriamente o pc trava e da tela azul, eu não consigo achar o problema. t

teste a memória com o memtest

https://www.memtest86.com/

como é um pc novo, memórias novas tb podem apresentar defeitos e sao causa desses travamentos aleatórios sem motivos

Luedson Back · 8 de janeiro de 2023

@rodrigo.dcvieira Fiz o teste por 10mim e não acusou nenhum erro. Vou deixar rolando o teste pela madrugada e ver se acusa algo, mas, aparentemente não é a memória.