Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\110622-8078-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 *** 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 = 0xfffff800`75200000 PsLoadedModuleList = 0xfffff800`75e29750 Debug session time: Sun Nov 6 14:49:56.854 2022 (UTC 9:00) System Uptime: 0 days 9:21:37.534 ********************************************************************* * 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 *** 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 3B, {c0000005, fffff80075490cad, ffffa18eae33df10, 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 *** *** *** ************************************************************************* Probably caused by : hardware_ram ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 103529 instance(s) of page corruption, target is likely to have memory corruption.
Hi,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,嗨，瑞先生，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，
Microsoft(R)WindowsDebuggerVersion6.12.0002.633X86Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile
嗨，瑞先生，minidump分析，表明内存损坏。要解决此问题，请尝试以下步骤并跳过您已经尝试过的步骤：1-如果您要对PC进行超频，请尝试以它们的正常速度运行所有东西（CPU、GPU、系统内存）。看看问题是否仍然可以重现。或者，关闭XMP配置文件或将其设置为自动。2-使用免费实用程序MemTest86测试RAM，然后运行完整的8次扫描以测试您的RAM是否存在物理错误：https://www-tenforums-com.translate.goog/tutori.3-运行Windows内存诊断：https://www-howtogeek-com.translate.goog/260813.4-如果您愿意这样做，请取出所有系统内存条，检查它们是否有任何明显的缺陷，然后将它们重新插入插槽。确保它们正确安装在插槽中。如果您安装了多根系统内存并且您怀疑其中一根有故障，则可以尝试的一件事是一次仅使用一根内存模块重现该问题。这将帮助您隔离故障模块。5-尝试为您的主板刷新最新版本的系统BIOS。从制造商的网站下载最新版本的BIOS，以提高与各种内存模块的兼容性。6-以管理员身份运行命令提示符并键入这些命令，然后在每个命令后按回车键：DISM.exe/在线/Cleanup-image/ScanhealthDISM/在线/Cleanup-Image/RestoreHealthsfc/scannow7-从设备管理器更新所有驱动程序或下载然后安装制造商网站中提供的最新驱动程序。如果您需要进一步的帮助，请告诉我并让我更新。______________________________________________________________________标准免责声明：有非Microsoft网站的链接。这些页面似乎提供了准确、安全的信息。请
