0x00000133蓝屏故障

匿名
2024-02-23T04:00:12+00:00

配置信息如下


操作系统: Windows 10 企业版 64位

  处理器: 英特尔 Core i5-9400F @ 2.90GHz 六核
    主板: 微星 B360M MORTAR (MS-7B23)(B360 芯片组)
    内存: 16 GB ( 金泰克 DDR4 2666MHz 8GB x 2 )
  主硬盘:  东芝 -RC500 (500 GB / 固态硬盘)
    显卡: NVIDIA GeForce RTX 2060 SUPER ( 8 GB / 索泰 )
  显示器: LG GSM5BD3 LG ULTRAGEAR ( 27.2 英寸 )
    声卡: 瑞昱 ALC892 @ 英特尔 High Definition Audio 控制器
         NVIDIA GeForce 7800 GS @ NVIDIA High Definition Audio 控制器
    网卡: 英特尔 Ethernet Connection  I219-V / 微星

以下是蓝屏文件

--------------------------------------------------------------------------

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: 0000000000000001, The system cumulatively spent an extended period of time at

DISPATCH\_LEVEL or above. 

Arg2: 0000000000001e00, The watchdog period (in ticks).

Arg3: fffff8007c8fb320, 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: 3156 

Key  : Analysis.Elapsed.mSec 

Value: 12558 

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

Key  : Analysis.Init.Elapsed.mSec 

Value: 90608 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 91 

Key  : Bugcheck.Code.LegacyAPI 

Value: 0x133 

Key  : Failure.Bucket 

Value: 0x133\_ISR\_nt!KeAccumulateTicks 

Key  : Failure.Hash 

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

Key  : WER.OS.Branch 

Value: vb\_release 

Key  : WER.OS.Version 

Value: 10.0.19041.1 

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8007c8fb320

BUGCHECK_P4: 0

FILE_IN_CAB: 022324-18218-01.dmp

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffe18f316a72f0 -- <link alt=".trap 0xffffe18f316a72f0" cmd=".trap 0xffffe18f316a72f0"><u>(.trap 0xffffe18f316a72f0)</u></link>

NOTE: The trap frame does not contain all registers.

<col fg="emphfg">Some register values may be zeroed or incorrect.</col>

rax=00000000002bf0fc rbx=0000000000000000 rcx=0000000000000010

rdx=ffff9e010d173190 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8007becf65e rsp=ffffe18f316a7480 rbp=ffffe48026ca0180

r8=0000000000000000 r9=0000000000000026 r10=0000000000000000

r11=0000000000000003 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz na pe nc

nt!KiTransitionSchedulingGroupGeneration+0x2ee:

fffff800`7becf65e 498bd2 mov rdx,r10

Resetting default scope

BLACKBOXBSD: 1 (<link alt="!blackboxbsd" cmd="!blackboxbsd"><u>!blackboxbsd</u></link>)

BLACKBOXNTFS: 1 (<link alt="!blackboxntfs" cmd="!blackboxntfs"><u>!blackboxntfs</u></link>)

BLACKBOXPNP: 1 (<link alt="!blackboxpnp" cmd="!blackboxpnp"><u>!blackboxpnp</u></link>)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffe48026cb9e18 fffff8007c037996 : 0000000000000133 0000000000000001 0000000000001e00 fffff8007c8fb320 : nt!KeBugCheckEx

ffffe48026cb9e20 fffff8007be539e3 : 0001c3e2a3e3692a ffffe48026ca0180 0000000000000000 ffffe48026ca0180 : nt!KeAccumulateTicks+0x1e1756

ffffe48026cb9e80 fffff8007be534ca : ffff9e0fe82d80e0 ffffe18f316a7370 fffff8007f571500 0000000200006001 : nt!KeClockInterruptNotify+0x453

ffffe48026cb9f30 fffff8007bf00825 : ffff9e0fe82d80e0 ffffe48026cb9f40 0000000000000010 ffffe29d741c3778 : nt!HalpTimerClockIpiRoutine+0x1a

ffffe48026cb9f60 fffff8007bfff6da : ffffe18f316a7370 ffff9e0fe82d80e0 00000000002bf0fc 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5

ffffe48026cb9fb0 fffff8007bfffee7 : ffffffffd98382d7 ffff9e010fd7b090 ffff9e010fd7b460 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffffe18f316a72f0 fffff8007becf65e : ffff9e01012ca460 ffff9e01012ca090 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffe18f316a7480 fffff8007becf0a9 : ffffe48026ca0100 ffff9e0fe835c000 ffffe79263bddb00 fffff80000000000 : nt!KiTransitionSchedulingGroupGeneration+0x2ee

ffffe18f316a7520 fffff8007becd4ce : ffffe48026ca0180 0000000000000000 000000000811666f 0000000000000000 : nt!KiGroupSchedulingGenerationEnd+0x55

ffffe18f316a7570 fffff8007becca58 : 0000000000000000 ffffe18f316a7610 0000041000001200 ffffe18f316a7620 : nt!KiGroupSchedulingQuantumEnd+0xce

ffffe18f316a7600 fffff8007c005b76 : ffffffffffffff00 fffff8007c004f8f 0000000000000010 0000000000000246 : nt!KiQuantumEnd+0x148

ffffe18f316a7700 fffff8007c004fa8 : ffff9e0fe835c080 0000000000000000 0000000000000000 0000000000000000 : nt!KiDispatchInterruptContinue+0x16

ffffe18f316a7730 fffff8007be4085f : 000000010007e0dd 0000000000000003 0000000000000000 0000000000000000 : nt!KiDpcInterrupt+0x2e8

ffffe18f316a78c0 fffff8007bf24673 : ffffe48000000000 ffffe48000000000 ffff9e0f00000000 0000000000000000 : nt!KiCommitThreadWait+0x14f

ffffe18f316a7960 fffff8007bfb5786 : ffffe48026ca32ae 0000000000000080 ffff9e0fe835c080 ffffb607e7bed8a0 : nt!KeWaitForGate+0xcb

ffffe18f316a79b0 fffff8007bf078e5 : ffff9e0fe835c080 ffff9e0fe835c080 0000000000000080 ffffb607f36fc7a0 : nt!KiExecuteDpc+0x86

ffffe18f316a7b10 fffff8007c0064b8 : ffffe48026ca0180 ffff9e0fe835c080 fffff8007bf07890 fffff8054b4c6aa4 : nt!PspSystemThreadStartup+0x55

ffffe18f316a7b60 0000000000000000 : ffffe18f316a8000 ffffe18f316a1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nt!KeAccumulateTicks+1e1756

MODULE_NAME: <link alt="lmvm nt" cmd="lmvm nt"><u>nt</u></link>

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3930

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1e1756

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


</DmlText>

***moved from Windows / Windows 10 / 性能和维护***

Windows 商业版 | 面向 IT 专业人士的 Windows 客户端 | 性能 | 其他

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用,但不能添加评论或回复,也不能关注问题。 为了保护隐私,对于已迁移的问题,用户个人资料是匿名的。

0 个注释 无注释
{count} 票

1 个答案

排序依据: 非常有帮助
  1. 匿名
    2024-02-26T05:44:40+00:00

    您好

    感谢您在微软论坛的发帖。

    从您所提供的Dump信息来看,蓝屏报错代码为0X133,这里提供一篇官方文档作为参考:Bug 检查 0x133 DPC_WATCHDOG_VIOLATION - Windows drivers | Microsoft Learn,此 bug 检查指示 DPC 监视程序已执行,要么因为它检测到单个长时间运行的延迟过程调用(DPC),要么是因为系统长时间在DISPATCH_LEVEL或更高版本的中断请求级别(IRQL)上花费了时间。

    此蓝屏通常是由驱动引起的,由于缺少更多信息,我们只能建议您对系统驱动进行更新升级,或者联系微软技术支持以提供更多帮助。

    Best Regards,

    Zack Lu

    0 个注释 无注释