系统版本：Windows11 22000.168问题：锁屏关闭屏幕时偶尔会断电自动关机DMP文件： Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\090121-9437-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 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 22000 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff801`5ba00000 PsLoadedModuleList = 0xfffff801`5c629710 Debug session time: Wed Sep 1 09:25:06.551 2021 (GMT 8) System Uptime: 0 days 16:17:47.234 ********************************************************************* * 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 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 ................................................. Cannot read PEB32 from WOW64 TEB32 0002811c - Win32 error 0n30 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {58, 2, 1, fffff80165d96f9f} Unable to load image BTHport.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for BTHport.sys *** ERROR: Module load completed but symbols could not be loaded for BTHport.sys Unable to load image Wdf01000.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Wdf01000.sys *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : hardware_ram ( PAGE_NOT_ZERO_VISTA ) Followup: MachineOwner --------- *** Memory manager detected 164124 instance(s) of page corruption, target is likely to have memory corruption.
您好，了解到您的问题，
链接：https://pan.baidu.com/s/1ZW08q460QIa832TN4JI9qg提取码：djd1此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
今天上午的，又断电了链接：https://pan.baidu.com/s/1zFBUg9d2UOssu1rI3O8LiQ提取码：m06x此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
尊敬的Microsoft产品和服务客户，上午好！LingGao，很荣幸有机会为您提供帮助。麻烦您尝试通过设备品牌官网下载对应设备型号的蓝牙驱动程序的安装包，覆盖安装到设备中，安装完毕后重启设备，按照平常的使用习惯继续使用一段时间设备，看一下是否还会蓝屏。
尊敬的Microsoft产品和服务客户，上午好！LingGao，很荣幸有机会为您提供帮助。麻烦您尝试通过设备品牌官网下载对应设备型号的蓝牙驱动程序的安装包，覆盖安装到设备中，安装完毕后重启设备，按照平常的使用习惯继续使用一段时间设备，看一下是否还会蓝屏。
您好，根据您的日至文件分析，并非是您所说的CSRGAIA设备导致，主要是BTHport.sys故障导致MicrosoftAnswers本站欢迎您！此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
那我之前已经在设备官网更新了最新的蓝牙驱动，目前还没解决，该如何处理？此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
此问题可能是由于设备中硬件发生异常、损坏，或设备过热导致的。如果您的设备是品牌机的话，不建议您自行进行拆机检修与维护，因为这可能会使保修失效。建议您携带设备与购买凭证前往品牌售后服务部门进行全面的硬件检修，以确认是哪一部分硬件出现了异常导致的设备蓝屏。
此问题可能是由于设备中硬件发生异常、损坏，或设备过热导致的。如果您的设备是品牌机的话，不建议您自行进行拆机检修与维护，因为这可能会使保修失效。建议您携带设备与购买凭证前往品牌售后服务部门进行全面的硬件检修，以确认是哪一部分硬件出现了异常导致的设备蓝屏。
win11版本和win10版本机制不同的，对其了解不多，很有可能是版本原因导致非常抱歉，主要处理Windows10家庭版和专业版在日常使用中遇到的问题，关于Windows11的问题，目前win11版本还有待完善，建议您可以通过点击徽标键 F进入用户反馈中心进行反馈，同时您可到“Windows预览体验计划本站”里提问，以便质询更合适的领域专家及更有效的为您解决问题：Windows预览体验计划本站：https://answers.microsoft.com/zh-hans/insider/f.
