win11 联想笔记本 一直蓝屏重启 很久了，试了网上及社区的各种各样的方式还是不行。 Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\102122-12218-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Machine Name: Kernel base = 0xfffff804`08a00000 PsLoadedModuleList = 0xfffff804`096133d0 Debug session time: Fri Oct 21 20:12:06.964 2022 (UTC 8:00) System Uptime: 0 days 0:19:22.704 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................... Loading User Symbols Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff804`08e280f0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffd48b`a3df5c50=000000000000001e 14: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: 0000000000040082, The address that the exception occurred at Arg3: 0000000000000008, Parameter 0 of the exception Arg4: 0000000000040082, Parameter 1 of the exception 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: ExceptionRecord *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: ContextRecord *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4171 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 123558 Key : Analysis.IO.Other.Mb Value: 3 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 4 Key : Analysis.Init.CPU.mSec Value: 217 Key : Analysis.Init.Elapsed.mSec Value: 7906 Key : Analysis.Memory.CommitPeak.Mb Value: 98 Key : Bugcheck.Code.DumpHeader Value: 0x1e Key : Bugcheck.Code.Register Value: 0x1e 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: 102122-12218-01.dmp BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: 40082 BUGCHECK_P3: 8 BUGCHECK_P4: 40082 EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 0000000000040082 WRITE_ADDRESS: fffff8040971c468: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse 0000000000040082 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: PowerToys.exe TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000) Unable to read trap frame at ffff8000`00000000 STACK_TEXT: ffffd48b`a3df5c48 fffff804`08c104fb : 00000000`0000001e ffffffff`c0000005 00000000`00040082 00000000`00000008 : nt!KeBugCheckEx ffffd48b`a3df5c50 fffff804`08e3b1fc : 00000000`00001000 ffff8006`81c93080 ffff8000`00000000 ffff8006`81c937c0 : nt!KiDispatchException 0x7eb ffffd48b`a3df6330 fffff804`08e36fc2 : 00000000`00000000 fffff804`08e3a8d0 00000000`00000001 00000000`00000000 : nt!KiExceptionDispatch 0x13c ffffd48b`a3df6510 00000000`00040082 : ffffd48b`a3df6600 00000000`00000000 00000000`00000000 fffff804`0d763713 : nt!KiPageFault 0x442 ffffd48b`a3df66a0 ffffd48b`a3df6600 : 00000000`00000000 00000000`00000000 fffff804`0d763713 ffff8006`9262c8b0 : 0x40082 ffffd48b`a3df66a8 00000000`00000000 : 00000000`00000000 fffff804`0d763713 ffff8006`9262c8b0 ffffd48b`a3df6779 : 0xffffd48b`a3df6600 SYMBOL_NAME: nt!KiDispatchException 7eb MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.674 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 7eb FAILURE_BUCKET_ID: AV_nt!KiDispatchException OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {00781d15-b897-afab-75cd-f83221cbf387} Followup: MachineOwner ---------
欢迎访问本站！。建议卸载一下PowerToys，然后执行一下干净启动，排除其他干扰：https://support.microsoft.com/zh-cn/help/929135.先卸载设备中全部的第三方反病毒软件与系统优化软件(例如360、联想电脑管家、360桌面、腾讯电脑管家、腾讯桌面、鲁大师，代理，加速器，虚拟机等)。然后鼠标右键单击开始菜单→运行（RUN）→输入：msconfig（按下Enter键）点击上面的“服务”勾选下面的“隐藏所有Microsoft服务”（请务必勾选）点击“全部禁用”。然后鼠标右键单击开始菜单→任务管理器，（点击底部“详细信息”），点击顶部”启动”，鼠标右键单击“状态”显示为“已启动”的项，选择“禁用”。（禁用所有启动项。）然后鼠标右键单击开始按钮（图标的按钮）→"WindowsPowerShell(I)（管理员)(A）”→输入：（WIndows11中可能显示Windows终端（管理员））sfc/SCANNOW（按下Enter键）Dism/Online/Cleanup-Image/ScanHealth（按下Enter键）Dism/Online/Cleanup-Image/CheckHealth（按下Enter键）DISM/Online/Cleanup-image/RestoreHealth（按下Enter键）完成后重启电脑，再次输入：sfc/SCANNOW（按下Enter键）看下是否恢复正常。
试过了还是不行~一样的。此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
感谢，若是方便，建议分享一下最新的dmp文件，以便了解情况。建议查看一下是否有.dmp文件，方便的话可以上传一下，以便分析：鼠标右击开始菜单→运行→输入：SYSDM.CPL（按下Enter键）切换到“高级”选项卡→“启动和故障恢复”下面的“设置”→“写入调试信息”下面选择“小内存转储（256KB）”→“小转储目录”输入：%SystemRoot%\Minidump→点击“确认”，然后重新启动计算机。在蓝屏或者突然重启等再次异常出现后，可以在C:Windows\minidump查找.dmp文件，将文件上传至任意网盘并将链接至此贴当中。（蓝屏出现时，屏幕上通常会有进度，确保100%才能收集到信息）（若是文件过大，请勿上传百度网盘，下载会限速导致很慢。上传时请看下文件日期，以防上传不相干的文件。）
Microsoft(R)WindowsDebuggerVersion10.0.25200.1003AMD64Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile
