BugCheck Event ID 1001 error

Question

BugCheck Event ID 1001 error

Anonymous

Lately, my PC has been freezing and rebooting randomly and I have been going through the Event Viewer to see what is happening, unfortunately a lot these error messages and dump files are a bit hard for me to understand. But here is the Event Viewer message:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80241efb320, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 15109b83-2a6a-4e7a-84b5-ee34518e7534.

I ran the DMP file through windbg and this is what it stated:

20: 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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80241efb320, 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: 2202

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2190

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    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

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80241efb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff8c0a14ffef10 -- (.trap 0xffff8c0a14ffef10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=a8c7ec40e85f0000
rdx=00000000000c00e1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80241530935 rsp=ffff8c0a14fff0a0 rbp=ffffffffffffffff
 r8=00000000000008d2  r9=00000000000000e1 r10=0000fffff8024152
r11=ffffbe794a000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeFlushProcessWriteBuffers+0xa9:
fffff802`41530935 8b86802d0000    mov     eax,dword ptr [rsi+2D80h] ds:00000000`00002d80=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  Discord.exe

STACK_TEXT:  
ffffce81`c9d9ac88 fffff802`4162a998     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`41efb320 : nt!KeBugCheckEx
ffffce81`c9d9ac90 fffff802`41450fed     : 00000986`9940435a ffffce81`c9d47180 00000000`00000246 00000000`0002ff98 : nt!KeAccumulateTicks+0x1dcbc8
ffffce81`c9d9acf0 fffff802`41451591     : 00000000`0002e100 00000000`0001c985 ffffce81`c9d47180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffce81`c9d9ad40 fffff802`4144b403     : ffffce81`c9d47180 00000000`00000000 fffff802`41e318c0 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffce81`c9d9ae80 fffff802`41453e02     : ffff8c0a`14ffef10 ffff8c0a`14ffef90 ffff8c0a`14ffef00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffce81`c9d9af30 fffff802`414d9405     : 00000007`26379719 ffff8f08`30ee40c0 ffff8f08`30ee4170 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffce81`c9d9af60 fffff802`415fa36a     : ffff8c0a`14ffef90 ffff8f08`30ee40c0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffce81`c9d9afb0 fffff802`415fa8d7     : 00000000`00000000 fffff802`41f2f1f0 fffff802`3e650578 fffff802`414462aa : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8c0a`14ffef10 fffff802`41530935     : ffff8c0a`14fff0e8 ffff8c0a`14fff0e0 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8c0a`14fff0a0 fffff802`41822df3     : 00000000`00000000 ffff8c0a`14fffb40 00000000`00000001 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xa9
ffff8c0a`14fff0e0 fffff802`417fd0e7     : ffff8c0a`14fff778 ffff8c0a`00010400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x183
ffff8c0a`14fff740 fffff802`417fc297     : 00000000`00000020 ffffb96b`832473d9 ffff8f08`5017f080 00000000`1207ea94 : nt!ExpQuerySystemInformation+0xd07
ffff8c0a`14fffa80 fffff802`4160a2b8     : 00000000`00000000 00007ffd`3acb5540 ffff8c0a`14fffb40 ffff8f08`45959540 : nt!NtQuerySystemInformation+0x37
ffff8c0a`14fffac0 00007ffd`3b86d604     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`11ffe3c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`3b86d604

SYMBOL_NAME:  nt!KeAccumulateTicks+1dcbc8

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1dcbc8

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

20: kd> .trap 0xffff8c0a14ffef10
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=a8c7ec40e85f0000
rdx=00000000000c00e1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80241530935 rsp=ffff8c0a14fff0a0 rbp=ffffffffffffffff
 r8=00000000000008d2  r9=00000000000000e1 r10=0000fffff8024152
r11=ffffbe794a000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeFlushProcessWriteBuffers+0xa9:
fffff802`41530935 8b86802d0000    mov     eax,dword ptr [rsi+2D80h] ds:00000000`00002d80=????????
20: 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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80241efb320, 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: 1952

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1942

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    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

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80241efb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff8c0a14ffef10 -- (.trap 0xffff8c0a14ffef10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=a8c7ec40e85f0000
rdx=00000000000c00e1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80241530935 rsp=ffff8c0a14fff0a0 rbp=ffffffffffffffff
 r8=00000000000008d2  r9=00000000000000e1 r10=0000fffff8024152
r11=ffffbe794a000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeFlushProcessWriteBuffers+0xa9:
fffff802`41530935 8b86802d0000    mov     eax,dword ptr [rsi+2D80h] ds:00000000`00002d80=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  Discord.exe

STACK_TEXT:  
ffffce81`c9d9ac88 fffff802`4162a998     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`41efb320 : nt!KeBugCheckEx
ffffce81`c9d9ac90 fffff802`41450fed     : 00000986`9940435a ffffce81`c9d47180 00000000`00000246 00000000`0002ff98 : nt!KeAccumulateTicks+0x1dcbc8
ffffce81`c9d9acf0 fffff802`41451591     : 00000000`0002e100 00000000`0001c985 ffffce81`c9d47180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffce81`c9d9ad40 fffff802`4144b403     : ffffce81`c9d47180 00000000`00000000 fffff802`41e318c0 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffce81`c9d9ae80 fffff802`41453e02     : ffff8c0a`14ffef10 ffff8c0a`14ffef90 ffff8c0a`14ffef00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffce81`c9d9af30 fffff802`414d9405     : 00000007`26379719 ffff8f08`30ee40c0 ffff8f08`30ee4170 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffce81`c9d9af60 fffff802`415fa36a     : ffff8c0a`14ffef90 ffff8f08`30ee40c0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffce81`c9d9afb0 fffff802`415fa8d7     : 00000000`00000000 fffff802`41f2f1f0 fffff802`3e650578 fffff802`414462aa : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8c0a`14ffef10 fffff802`41530935     : ffff8c0a`14fff0e8 ffff8c0a`14fff0e0 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8c0a`14fff0a0 fffff802`41822df3     : 00000000`00000000 ffff8c0a`14fffb40 00000000`00000001 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xa9
ffff8c0a`14fff0e0 fffff802`417fd0e7     : ffff8c0a`14fff778 ffff8c0a`00010400 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x183
ffff8c0a`14fff740 fffff802`417fc297     : 00000000`00000020 ffffb96b`832473d9 ffff8f08`5017f080 00000000`1207ea94 : nt!ExpQuerySystemInformation+0xd07
ffff8c0a`14fffa80 fffff802`4160a2b8     : 00000000`00000000 00007ffd`3acb5540 ffff8c0a`14fffb40 ffff8f08`45959540 : nt!NtQuerySystemInformation+0x37
ffff8c0a`14fffac0 00007ffd`3b86d604     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`11ffe3c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`3b86d604

SYMBOL_NAME:  nt!KeAccumulateTicks+1dcbc8

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1dcbc8

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

Can someone help me understand the basics of what is happening here?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

DYARI BARHAM 34,936 Independent Advisor

Hi Peter,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

Regards,

0 comments

Share via

BugCheck Event ID 1001 error

1 answer