蓝屏情况不定时、无规律，有一种情况是涉及到无线键盘切换的时候会出现蓝屏，最近的一次是正常使用时出现。所有的蓝屏在重启后恢复正常，经过卸载驱动或者重装系统均无法解决，日志已经上传，麻烦技术大牛帮忙定位一下具体的问题。 Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\080622-85828-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y argument when starting the debugger. * * using .sympath and .sympath * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff804`38400000 PsLoadedModuleList = 0xfffff804`3902a230 Debug session time: Sat Aug 6 20:40:19.908 2022 (GMT 8) System Uptime: 9 days 12:51:48.537 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y argument when starting the debugger. * * using .sympath and .sympath * ********************************************************************* Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................. Loading User Symbols Loading unloaded module list ....................................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck EF, {ffff9d857b77f280, 0, 0, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y argument when starting the debugger. * * using .sympath and .sympath * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y argument when starting the debugger. * * using .sympath and .sympath * ********************************************************************* Probably caused by : ntoskrnl.exe ( nt 3f8590 ) Followup: MachineOwner ---------
如果您能在您的桌面=建造您个人的文件夹，设名为“您在这里的登入帐号名”（不是邮箱），和把.dmp文件（C:\Windows\Minidump)拷贝放入”您帐号名的文件夹”里，然后上传到以下任何一个网站，之后留个信息说已经上传到哪个网站，我可以帮忙看一看能不能找到些蛛丝马迹。（我也正在帮助其他所有人，所以如果您忘了把文件夹命名成您这里的帐号名，我会不清楚是谁发上来的，从而可能会忽略了您的问题，谢谢您的了解。）1)https://1drv.ms/u/s!AiTKIv57sNr_m17mv31AyUbIZeq.或2)https://app.nihaocloud.com/或3）https://airportal.cn/（上传后，您会得到个连接，请把那连接发上来）（如果您的C:\Windows\Minidump是空白的，须要按左下角的查找》输入“控制面板”》系统和安全》系统》高级系统设置》高级》启动和故障恢复》设置，写入调试信息选择“小内存转储”》重启，那下次蓝屏时电脑会建造文件在C:\Windows\Minidump）======================================可以到您的电脑制造商网站，更新所有的驱动程序看看（或者参考以下步伐）。（Win10给Win10，Win8给Win8，不要下载错误）（建议不要使用第三方软件更新驱动）使用设备管理器卸载设备和驱动程序包：https://docs.microsoft.com/zh-cn/windows-hardwa.更新驱动程序的方法：https://support.microsoft.com/zh-cn/help/402844.
链接：https://pan.baidu.com/s/142RomZU43_uPLgWoMFMccg提取码：6666
您好！您电脑的型号是什么呢？？可以到您电脑制造商的官网，下载所有最新版本的驱动更新一下。（芯片组 网卡 声卡 显卡 BIOS）（建议不要使用第三方软件更新驱动）如果您不了解您电脑的型号，您可按查找》输入“系统信息”（SystemInformation）》在主页的SystemSummary（系统摘要）下，截图或拍张照片上传上来吗？？（以方便我帮您查找您电脑制造商的最新驱动下载链接，然后发那链接给您。）此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
设备名称DESKTOP-M8G9OD6处理器Intel(R)Core(TM)i7-7700HQCPU@2.80GHz2.81GHz机带RAM32.0GB(31.8GB可用)设备IDC25434F1-DCC9-491B-967A-F0EDFA5B0985产品ID00326-10100-10000-AA080系统类型64位操作系统,基于x64的处理器笔和触控手写笔和触控支持10个触控点此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您好！这些只是您电脑的配置，没显示您电脑型号，能都发以上步伐的“系统信息”（SystemInformation）截图上来看看？？此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您好，我将电脑的驱动全部重装了一遍，暂时稳定，如果有新的情况会和您反馈，感谢您的帮助！此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您好！好的，那您观察一阵子看看如何。另外，由于这里的帖子会在48小时内如果没更新，以避免有很多帖子遗留着而导致本站很难管理，系统就会自动关闭与存档了。如果之后您或您的朋友有其他的疑问，子来提问，这里的网友们会与你们一起携手研究与了解您的问题并给予全力的帮助！谢谢您对的支持！
