旧梦花已残丶 2025-02-05 22:39 采纳率: 0%
浏览 25

Windows 11系统绿屏

主要症状,睡眠时重新点亮屏幕,进入系统,会画面卡死,然后突然就绿屏了

img

扒得蓝屏日志文档,使用的是Windows11 系统,莫名识别成了Windows10

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: fffff8014c51d340, 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: 2780

    Key  : Analysis.Elapsed.mSec
    Value: 25980

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_DPC_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8014c51d340

FILE_IN_CAB:  020525-15234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ‘ h.exe

FAULTING_THREAD:  0000000000000017

STACK_TEXT:  
ffff9580`c75699e8 fffff801`4ba37bb5     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9580`c75699f0 fffff801`4ba37281     : 00005f2e`2325594b 00000000`002a3c36 00000000`002a3c35 00000000`00000000 : nt!KeAccumulateTicks+0x3d5
ffff9580`c7569a50 fffff801`4ba3488f     : 00000000`00000018 00000000`00001388 00000000`002a3c00 00000000`00192c94 : nt!KiUpdateRunTime+0xd1
ffff9580`c7569c00 fffff801`4ba35478     : 00000000`00000000 00000000`00000000 ffff9580`c754f180 00000000`00000000 : nt!KiUpdateTime+0x63f
ffff9580`c7569ea0 fffff801`4ba34d3a     : fffff801`4c45fe58 00000000`00000001 00000000`00000001 00000000`00000000 : nt!KeClockInterruptNotify+0x228
ffff9580`c7569f40 fffff801`4bb15f8c     : 00000064`b26a5173 ffffc28a`feb5b500 ffffc28a`feb5b5b0 fffff801`4bc16e6b : nt!HalpTimerClockInterrupt+0x10a
ffff9580`c7569f70 fffff801`4bc170ca     : fffffa82`e9b17630 ffffc28a`feb5b500 fffff801`51bc8368 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffff9580`c7569fb0 fffff801`4bc17997     : 00000000`00000001 00000000`00000000 00000000`80000000 fffff801`4bc179a4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffa82`e9b175b0 fffff801`4babb36c     : ffffffff`ffffffd1 fffff801`4bb8bd5f 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffa82`e9b17740 fffff801`4bb8bd5f     : ffffc28a`febf4050 00000000`000006a8 ffffc28a`feafe170 00000000`00000f44 : nt!KeYieldProcessorEx+0x1c
fffffa82`e9b17770 fffff801`4ba117ec     : 00000000`00000000 00000000`1b413ba8 ffff9580`00000000 ffff9580`c75524d0 : nt!ExpGetPoolTagInfoTarget+0xff
fffffa82`e9b177c0 fffff801`4ba107f4     : 00000000`00000004 fffffa82`e9b17e00 ffff9580`c754f180 00000000`00014e01 : nt!KiExecuteAllDpcs+0x42c
fffffa82`e9b17d00 fffff801`4bc1e735     : 3162bd07`01ef944b 00000000`00000000 ffff9580`c754f180 00000000`00000018 : nt!KiRetireDpcList+0x1b4
fffffa82`e9b17fb0 fffff801`4bc1e6df     : fffffa82`ee75f9b9 fffff801`4ba142d5 ffffc28b`25fc1080 fffff801`4bec6e36 : nt!KxSwapStacksAndRetireDpcList+0x5
fffffa82`ee75f920 fffff801`4ba142d5     : ffffc28b`25fc1080 fffff801`4bec6e36 00000000`00000077 00000000`00000000 : nt!KiPlatformSwapStacksAndCallReturn
fffffa82`ee75f930 fffff801`4bc1dae5     : ffffc28b`25fc1080 000000e2`2a7fdfd0 00000000`00000000 00000000`00000000 : nt!KiDispatchInterrupt+0xd5
fffffa82`ee75fa20 00007ff6`ca6c78bb     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x365
000000e2`2a7feb70 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`ca6c78bb


STACK_COMMAND:  ~23 ; .cxr ; kb

SYMBOL_NAME:  nt!KeAccumulateTicks+3d5

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4805

BUCKET_ID_FUNC_OFFSET:  3d5

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
  • 写回答

4条回答 默认 最新

  • 专家-赤兔[在线] 优质创作者: 编程框架技术领域 2025-02-05 22:40
    关注

    以下回复引自免费微信小程序:皆我百晓生。 如问题解决,还请采纳。如仍有疑问,请回复留言或私信博主,以便获得更精准的帮助。

    1. 确认是否为WINDOWS11的“睡眠时重新点亮屏幕”行为导致的“画面卡死”,如果是的话,尝试关闭此行为。
    2. 如果不是,可能是因为内存不足或者硬件配置过高引起的。建议检查显卡驱动、内存和硬盘等设备是否存在异常。
    3. 可以尝试重启电脑,看看能否解决问题。
    4. 对于硬件问题,可以尝试更换电源适配器或清理灰尘,看是否能解决问题。
    5. 如果以上方法都不能解决问题,可能是操作系统的问题,建议联系微软技术支持寻求帮助。
    评论

报告相同问题?

问题事件

  • 创建了问题 2月5日