Soran
windows 11 使用vs2022的时候蓝屏

Soru
-
******************************************************************************* * * * 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: fffff8005891c340, 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: 5343 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 16821 Key : Analysis.IO.Other.Mb Value: 1 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 24 Key : Analysis.Init.CPU.mSec Value: 452 Key : Analysis.Init.Elapsed.mSec Value: 17912 Key : Analysis.Memory.CommitPeak.Mb Value: 150 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Timestamp Value: 2022-05-06T12:50:00Z Key : WER.OS.Version Value: 10.0.22621.1 FILE_IN_CAB: 010923-25500-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8005891c340 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: ffffa50c9f766870 -- (.trap 0xffffa50c9f766870) Unable to read trap frame at ffffa50c`9f766870 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: chrome.exe STACK_TEXT: ffffe100`ea48ec68 fffff800`57e2419f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`5891c340 : nt!KeBugCheckEx ffffe100`ea48ec70 fffff800`57e22fd4 : 000035d0`e9a7fe9e ffffe100`ea474180 00000000`000a6ca7 00000000`00000000 : nt!KeAccumulateTicks+0x23f ffffe100`ea48ecd0 fffff800`57e21463 : fffff800`5885fd08 00000000`00000000 ffffe100`ea474180 ffffa50c`9f766870 : nt!KiUpdateRunTime+0xf4 ffffe100`ea48ee90 fffff800`57e208ea : fffff800`5885fd08 ffffcf06`60932430 ffffcf06`60932430 00000000`00000000 : nt!KeClockInterruptNotify+0x763 ffffe100`ea48ef40 fffff800`57f4609e : 00000018`daa99a4c ffffcf06`60932380 ffffe100`ea474180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a ffffe100`ea48ef70 fffff800`5802a85a : ffffa50c`9f7668f0 ffffcf06`60932380 ffffcf06`7a432a30 ffffcf06`91a2f8e0 : nt!KiCallInterruptServiceRoutine+0x19e ffffe100`ea48efb0 fffff800`5802b0c7 : 00000000`8cefce2d 00000000`00040000 ffffa50c`9f766b30 fffff800`58373e1b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffa50c`9f766870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 SYMBOL_NAME: nt!KeAccumulateTicks+23f MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.963 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 23f FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Followup: MachineOwner ---------
Tüm Yanıtlar
-
您好,
DPC_WATCHDOG_VIOLATION (133) 表示DPC监视器已执行,同时检测到系统在中断请求级别(IRQL)DISPATCH_LEVEL或更高时花费了很长的时间。
您可以尝试投射NT地址显示有关它的信息:dt nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK fffff8005891c340,也可以使用 !dpcs 命令显示排队的DPC。
通常此代码是由错误的驱动程序引起的,可以尝试执行以下操作进行故障排除:
- 禁用当前显卡驱动程序,并联系制造商获取最新的显卡驱动程序
- 在事件查看器中检查系统日志以获取其他错误信息,这些错误信息可能有助于识别导致此问题的驱动程序
- 配置驱动程序验证程序管理器:Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Best Regards,
Wesley Li
Please remember to mark the replies as answersif they help.
-
-