多次出现蓝屏DPC WATCHDOG VIOLATION  尝试过重置可是没用以下为错误代码:Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff806`02400000 PsLoadedModuleList = 0xfffff806`0302a290 Debug session time: Sat Oct 1 21:18:21.105 2022 (UTC 8:00) System Uptime: 0 days 2:02:55.938 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .......... Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ....... Loading User Symbols Loading unloaded module list .................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806`027f8fa0 48894c2408 mov qword ptr [rsp 8],rcx ss:fffff806`092b3b10=0000000000000133 0: 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: fffff806030fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvle.inf_amd64_68dd88dc33421cd4\nvlddmkm.sys, Win32 error 0n2 ************************************************************************* *** *** *** *** *** 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: 3218 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 82851 Key : Analysis.Init.CPU.mSec Value: 1593 Key : Analysis.Init.Elapsed.mSec Value: 36928 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: fffff806030fb320 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff806092b3cf0 -- (.trap 0xfffff806092b3cf0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff80602798500 rbx=0000000000000000 rcx=0000000000001883 rdx=0000000000001883 rsi=0000000000000000 rdi=0000000000000000 rip=fffff806027985b9 rsp=fffff806092b3e88 rbp=ffffa38a3cca8a20 r8=fffff806092b3f00 r9=0000000000000001 r10=fffff806027985b0 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!HalpAcpiPmRegisterReadPort 0x9: fffff806`027985b9 418800 mov byte ptr [r8],al ds:fffff806`092b3f00=00 Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: fffff806`092b3e88 fffff806`02797b89 : 00000000`00000010 ffffa38a`3cef6000 ffffa38a`3d0d7310 00000000`00000548 : nt!HalpAcpiPmRegisterReadPort 0x9 fffff806`092b3e90 fffff806`0794680a : 00000000`00000003 ffffb480`645b8280 fffff806`092b3f98 00000000`00000f43 : nt!HalpAcpiPmRegisterRead 0x39 fffff806`092b3ec0 fffff806`07945d84 : 00000000`00000000 ffffb480`645b8dc0 00000000`00000f43 fffff806`00400a02 : ACPI!ACPIReadGpeStatusRegister 0x66 fffff806`092b3f00 fffff806`02608a45 : ffffb480`645b8dc0 ffffa38a`3ccafd70 ffffb480`645b8e70 ffff1886`ad7cf6eb : ACPI!ACPIInterruptServiceRoutine 0x54 fffff806`092b3f40 fffff806`027fa7cf : fffff806`092a40a0 ffffb480`645b8dc0 fffff806`092a4500 00000938`9c78ab87 : nt!KiCallInterruptServiceRoutine 0xa5 fffff806`092b3f90 fffff806`027faa97 : 00000000`ffffffff 00000000`00000000 00000040`00000040 00000000`00000000 : nt!KiInterruptSubDispatch 0x11f fffff806`092a4020 fffff806`269bf778 : 00000000`00611ec0 00000000`00611ec0 ffffa38a`4aa6f000 fffff806`092a4500 : nt!KiInterruptDispatch 0x37 fffff806`092a41b0 fffff806`26ab3e19 : ffffa38a`46897000 ffffa38a`46897a40 00000000`00611ec0 ffffa38a`4a962b00 : nvlddmkm 0x8f778 fffff806`092a41e0 fffff806`26ef7329 : 00000000`00000000 ffffa38a`468bf000 fffff806`092a4280 00000000`00000000 : nvlddmkm 0x183e19 fffff806`092a4260 fffff806`26a169cd : 00000000`00000000 00000000`00000000 fffff806`00000000 1719f454`84483bbc : nvlddmkm 0x5c7329 fffff806`092a42c0 fffff806`26a2a441 : 00000000`00000000 ffffa38a`46890002 ffffffff`ffff0002 fffff806`26a29b20 : nvlddmkm 0xe69cd fffff806`092a4300 fffff806`26a29b8e : ffffa38a`46897000 ffffa38a`46897000 ffffa38a`4aa6f000 00000000`00000000 : nvlddmkm 0xfa441 fffff806`092a4340 fffff806`26a29f6e : ffffa38a`5a125210 fffff806`269b6c69 ffffa38a`5a125218 ffffa38a`5a125201 : nvlddmkm 0xf9b8e fffff806`092a43a0 fffff806`26a2a89d : 00000000`00000002 fffff806`092a45b0 00000000`00000002 fffff806`26ab52c1 : nvlddmkm 0xf9f6e fffff806`092a4410 fffff806`26a16ea6 : fffff806`092a45b0 fffff806`269e2e2a ffffa38a`46897000 ffffa38a`4aa6f000 : nvlddmkm 0xfa89d fffff806`092a4470 fffff806`269bf97e : ffffa38a`46897000 ffffa38a`4aa6f000 ffffa38a`46ac0180 fffff806`02722d7a : nvlddmkm 0xe6ea6 fffff806`092a44b0 fffff806`0263489e : fffff806`00c79240 ffffa38a`3cde9000 fffff806`092a4a40 fffff806`00c76180 : nvlddmkm 0x8f97e fffff806`092a4760 fffff806`02633b84 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e fffff806`092a48d0 fffff806`027fcb3e : 00000000`00000000 fffff806`00c76180 fffff806`03127a00 ffffa38a`4d299380 : nt!KiRetireDpcList 0x1f4 fffff806`092a4b60 00000000`00000000 : fffff806`092a5000 fffff806`0929e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e STACK_COMMAND: .trap 0xfffff806092b3cf0 ; kb SYMBOL_NAME: nvlddmkm 8f778 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys BUCKET_ID_FUNC_OFFSET: 8f778 FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86} Followup: MachineOwner ---------

看似显卡驱动导致,您可到以下的连接,下载您电脑最新版本的显卡驱动更新一下:(建议不要使用第三方软件更新驱动)Nvidia驱动下载:https://www.nvidia.com/Download/index.aspx?lang=cn如果您不了解您电脑的显卡型号,您可按左下角的查找》输入dxdiag》在“系统”下,点击“保存所有信息”按钮》设名为“您在这里的登入帐号名”(不是邮箱)》存档到桌面》然后上传到以下的任何一个连接吗??(之后留个信息说已经上传到哪个网站)1)https://1drv.ms/f/s!AiTKIv57sNr_c6F0FlWaJ3OyQTg或2)https://cowtransfer.com/(上传后,您会得到个连接,请把那连接发上来)或3)https://app.nihaocloud.com/u/d/4923135c313743fb.


看似显卡驱动导致,您可到以下的连接,下载您电脑最新版本的显卡驱动更新一下:(建议不要使用第三方软件更新驱动)Nvidia驱动下载:https://www.nvidia.com/Download/index.aspx?lang=cn如果您不了解您电脑的显卡型号,您可按左下角的查找》输入dxdiag》在“系统”下,点击“保存所有信息”按钮》设名为“您在这里的登入帐号名”(不是邮箱)》存档到桌面》然后上传到以下的任何一个连接吗??(之后留个信息说已经上传到哪个网站)1)https://1drv.ms/f/s!AiTKIv57sNr_c6F0FlWaJ3OyQTg或2)https://cowtransfer.com/(上传后,您会得到个连接,请把那连接发上来)或3)https://app.nihaocloud.com/u/d/4923135c313743fb.


您好!是的,您安装完毕之后,观察一两天看看如何。此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


好的安装好了,到时候如果有问题再联系你好吗?谢谢啦此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


您好!不客气,另外,由于这里的帖子会在48小时内如果没更新,以避免有很多帖子遗留着而导致本站很难管理,系统就会自动关闭与存档了。如果之后您或您的朋友有其他的疑问,子来提问,这里的网友们会与你们一起携手研究与了解您的问题并给予全力的帮助!谢谢您对的支持!


今天上午又发生了蓝屏以下为错误信息:又要麻烦了嘿嘿Microsoft(R)WindowsDebuggerVersion10.0.25136.1001AMD64Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile


您好!您电脑的型号是什么呢??可以到您电脑制造商的官网,下载所有最新版本的驱动更新一下。(电源驱动 蓝牙 芯片组 网卡 声卡 显卡 BIOS)(建议不要使用第三方软件更新驱动)如果您不了解您电脑的型号,您可按查找》输入“系统信息”(SystemInformation)》在主页的SystemSummary(系统摘要)下,截图或拍张照片上传上来吗??(以方便我帮您查找您电脑制造商的最新驱动下载链接,然后发那链接给您。)此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


好的找到了我给你发过去,帮忙找一下吧谢谢哈此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


您好!您可到以下的连接,输入您的主机编号,下载所有最新版本的驱动更新一下,然后重启电脑:(蓝牙 芯片组 网卡 声卡 显卡 BIOS)(建议不要使用第三方软件更新驱动)Lenovo:https://think.lenovo.com.cn/support/driver/main.


点赞(17) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部