您好。上一次重启的windbg如下Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\033022-13125-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 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff806`70200000 PsLoadedModuleList = 0xfffff806`70e2a2d0 Debug session time: Wed Mar 30 10:04:25.999 2022 (UTC 8:00) System Uptime: 0 days 1:27:25.688 ********************************************************************* * 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 00019f38 - Win32 error 0n30 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 133, {1, 1e00, fffff80670efa320, 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 *** *** *** ************************************************************************* Probably caused by : hardware_ram ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 106296 instance(s) of page corruption, target is likely to have memory corruption. 10: kd> Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\033022-13125-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff806`70200000 PsLoadedModuleList = 0xfffff806`70e2a2d0 Debug session time: Wed Mar 30 10:04:25.999 2022 (UTC 8:00) System Uptime: 0 days 1:27:25.688 Loading Kernel Symbols请问应该怎么解决,上次蓝屏是因为联发科网卡驱动,现在是这个.
您好，修复命令您可以重启电脑后多尝试几次，如果一直不行，建议您对系统进行一下无损修复（非重装操作，不会影响到您当前的系统环境及应用）：如果您的设备运行的是家庭版或专业版Windows10，可参考以下链接：https://answers.microsoft.com/zh-hans/windows/forum/windows_10-update/使用mediacreationtool无/f7c63824-b74d-4214-bb8a-b1deef4b099e通过以下链接可以下载MediaCreationTool媒体创建工具（点击链接中的“立即下载工具”按钮，运行下载好的MediaCreationTool.exe文件即可）https://www.microsoft.com/zh-cn/software-download/windows10————————————————————————————————mtkwl6ex.sys，不能确定是驱动还是硬件本身存在问题，但是通常是驱动问题，您可以先试试更新网卡驱动或更换不同网卡版本的驱动。我在网上为您找了一个类似的例子，您可以参考一下：突然断网，卡起，然后蓝屏，mtkwl6ex.sys【华硕吧】_百度贴吧(baidu.com)
您好，
腾讯微云文件分享(weiyun.com)百度链接：https://pan.baidu.com/s/1iSfiCCepIBUtG1dQSzqPEQ提取码：2lee麻烦您帮忙看看吧!此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
ntoskrnl.exe显示说这个错误,不知道怎么解决此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您好，您分享的weiyun链接我无法打开，然后看到了您在其它贴百度网盘中的dump文件，显示导致蓝屏的进程为：mtkwl6ex.sys（网卡驱动）。ntoskrnl.exe是windows操作系统的一个重要内核程序文件，您可以试试以下方法看是否存在系统文件损坏的情况：右击开始按钮>点击"命令提示符"（以管理员身份运行），输入：Dism/Online/Cleanup-Image/ScanHealth这条命令将扫描全部系统文件并和官方系统文件对比，扫描计算机中的不一致情况。Dism/Online/Cleanup-Image/CheckHealth这条命令必须在前一条命令执行完以后，发现系统文件有损坏时使用。DISM/Online/Cleanup-image/RestoreHealth这条命令是把那些不同的系统文件还原成官方系统源文件。完成后重启，无论以上是否成功，键入以下命令：sfc/SCANNOW
您好,DISM/Online/Cleanup-image/RestoreHealth进度到62.5%卡住告诉我错误:0x800f081f找不到源文件此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
mtkwl6ex.sys（网卡驱动）出问题应该怎么解决是驱动还是硬件呢?此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您好，修复命令您可以重启电脑后多尝试几次，如果一直不行，建议您对系统进行一下无损修复（非重装操作，不会影响到您当前的系统环境及应用）：如果您的设备运行的是家庭版或专业版Windows10，可参考以下链接：https://answers.microsoft.com/zh-hans/windows/forum/windows_10-update/使用mediacreationtool无/f7c63824-b74d-4214-bb8a-b1deef4b099e通过以下链接可以下载MediaCreationTool媒体创建工具（点击链接中的“立即下载工具”按钮，运行下载好的MediaCreationTool.exe文件即可）https://www.microsoft.com/zh-cn/software-download/windows10————————————————————————————————mtkwl6ex.sys，不能确定是驱动还是硬件本身存在问题，但是通常是驱动问题，您可以先试试更新网卡驱动或更换不同网卡版本的驱动。我在网上为您找了一个类似的例子，您可以参考一下：突然断网，卡起，然后蓝屏，mtkwl6ex.sys【华硕吧】_百度贴吧(baidu.com)
