BSOD BUGCHECK_CODE: 133

  • Thread starter Thread starter Aleksander Kalicki
  • Start date Start date
A

Aleksander Kalicki

Guest
Dear,

I cant figure out what exactly could cause bsod. No OC beside auto turbo mode,, sometimes problems with sound (external Sound Blaster) but hard to say if thats the core of all issues.


Report below :

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`24600000 PsLoadedModuleList = 0xfffff800`2522a2b0
Debug session time: Sat Jan 2 18:41:50.195 2021 (UTC + 1:00)
System Uptime: 4 days 1:11:03.831
Loading Kernel Symbols
...............................................................
...........Page 1a7ee3 not present in the dump file. Type ".hh dbgerr004" for details
.....................................................
................................................................
.
Loading User Symbols

Loading unloaded module list
...................
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff800`249f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb000`8e37ee20=0000000000000133
2: 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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff800252fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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: 2718

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 9184

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

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: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff800252fa320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffff878c12c37650 --
(.trap 0xffff878c12c37650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffff878c12c37868
rdx=ffff878c15c13650 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80024844558 rsp=ffff878c12c377e0 rbp=ffffc20fb27c70c0
r8=ffff878c15c13480 r9=ffff878c15c13490 r10=0000fffff8002498
r11=ffff9fffe1800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KeYieldProcessorEx+0x8:
fffff800`24844558 488bd9 mov rbx,rcx
Resetting default scope

BLACKBOXBSD: 1 (
!blackboxbsd)


BLACKBOXNTFS: 1 (
!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb000`8e37ee18 fffff800`24a3a988 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffb000`8e37ee20 fffff800`2486f9a3 : 000162d5`d03be8ab ffffb000`8e365180 00000000`00000000 ffffb000`8e365180 : nt!KeAccumulateTicks+0x1c8788
ffffb000`8e37ee80 fffff800`2486f48a : ffffc20f`a12a20e0 ffff878c`12c376d0 00007fff`e35e2000 00000000`00000001 : nt!KeClockInterruptNotify+0x453
ffffb000`8e37ef30 fffff800`24927ef5 : ffffc20f`a12a20e0 00000000`00000000 00000000`00000000 ffff9eab`d77735c1 : nt!HalpTimerClockIpiRoutine+0x1a
ffffb000`8e37ef60 fffff800`249f722a : ffff878c`12c376d0 ffffc20f`a12a20e0 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb000`8e37efb0 fffff800`249f7797 : 000005fe`4865918a ffffa927`4b83ad11 ffff878c`15c13490 fffff800`249f77a4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff878c`12c37650 fffff800`24844558 : 00000000`00000010 00000000`00000286 ffff878c`12c37808 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff878c`12c377e0 fffff800`24984b63 : 00000000`00010001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x8
ffff878c`12c37810 fffff800`2480781e : ffffb000`8e368240 00000000`818d6cf7 00000000`00000004 ffffb000`8e365180 : nt!KiSwapDirectoryTableBaseTarget+0x53
ffff878c`12c37860 fffff800`24806b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffff878c`12c379d0 fffff800`249f92ee : ffffffff`00000000 ffffb000`8e365180 ffffb000`8e370240 ffffc20f`a7191040 : nt!KiRetireDpcList+0x1f4
ffff878c`12c37c60 00000000`00000000 : ffff878c`12c38000 ffff878c`12c32000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: nt!KeAccumulateTicks+1c8788

MODULE_NAME:
nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1c8788

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}

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

2: kd> !blackboxbsd
Stream size mismatch (expected = 192, read = 176)
2: kd> !blackboxntfs

NTFS Blackbox Data

0 Slow I/O Timeout Records Found
0 Oplock Break Timeout Records Found
2: kd> lmvm nt
Browse full module list
start end module name
fffff800`24600000 fffff800`25646000
nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\4EF9A5375F61FE84B7EAEF54BF025C0E1\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\C129B8081046000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe




Continue reading...
 

Similar threads

H
Replies
0
Views
10
HongxiangLi1
H
H
Replies
0
Views
13
Hammad_Awan
H
Replies
0
Views
23
ソンウンホ
Back
Top