Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\071022-8765-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\Symbols Executable search path is: 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 Machine Name: Kernel base = 0xfffff805`04000000 PsLoadedModuleList = 0xfffff805`04c2a2b0 Debug session time: Sun Jul 10 22:04:37.973 2022 (UTC 8:00) System Uptime: 0 days 13:07:33.726 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 0001b4dc - Win32 error 0n30 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 13A, {11, ffffc008e2e02100, ffffc008f63e0ba0, 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 111836 instance(s) of page corruption, target is likely to have memory corruption. 10: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Unknown bugcheck code (13a) Unknown bugcheck description Arguments: Arg1: 0000000000000011 Arg2: ffffc008e2e02100 Arg3: ffffc008f63e0ba0 Arg4: 0000000000000000 Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: fffff80504000000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x13A CURRENT_IRQL: 0 BAD_PAGES_DETECTED: 1b4dc LAST_CONTROL_TRANSFER: from fffff8050458eb4c to fffff805043f7dd0 STACK_TEXT: ffff9203`a9e1ae68 fffff805`0458eb4c : 00000000`0000013a 00000000`00000011 ffffc008`e2e02100 ffffc008`f63e0ba0 : nt 0x3f7dd0 ffff9203`a9e1ae70 00000000`0000013a : 00000000`00000011 ffffc008`e2e02100 ffffc008`f63e0ba0 00000000`00000000 : nt 0x58eb4c ffff9203`a9e1ae78 00000000`00000011 : ffffc008`e2e02100 ffffc008`f63e0ba0 00000000`00000000 ffff9203`a9e16000 : 0x13a ffff9203`a9e1ae80 ffffc008`e2e02100 : ffffc008`f63e0ba0 00000000`00000000 ffff9203`a9e16000 ffffc008`f63e0ba0 : 0x11 ffff9203`a9e1ae88 ffffc008`f63e0ba0 : 00000000`00000000 ffff9203`a9e16000 ffffc008`f63e0ba0 fffff805`0458ebac : 0xffffc008`e2e02100 ffff9203`a9e1ae90 00000000`00000000 : ffff9203`a9e16000 ffffc008`f63e0ba0 fffff805`0458ebac 00000000`00000011 : 0xffffc008`f63e0ba0 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware_ram BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- *** Memory manager detected 111836 instance(s) of page corruption, target is likely to have memory corruption. 10: kd> lmvm hardware start end module name 10: kd> lmvm hardware start end module name 10: kd> lmvm hardware start end module name 10: kd> lmvm hardware start end module name
xuyangzhu你好戴夫，我会帮你的。1您的minidump只是表明大量内存(RAM)损坏没有列出特定的设备驱动程序最好的选择是下载广泛可用的免费实用程序MemTest86，然后运行完整的4遍扫描以测试您的RAM是否存在物理错误2如果没有发现RAM错误，请检查您的PC是否正在生成任何minidump文件，我将检查这些文件是否提供对系统崩溃潜在原因的任何洞察。打开Windows文件资源管理器。导航到C:\Windows\Minidump将所有小型转储文件复制到您的桌面上，然后将其压缩。将zip文件上传到云端（OneDrive、DropBox等），然后选择共享这些文件并获取共享链接。然后在此处发布zip文件的链接，以便为您查找。___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
MemTest86的使用对于我来说可能太过于困难，我将分享minidump文件，以下是链接链接：https://pan.baidu.com/s/1MzqT_HOIsGo3I8oHFk5jpQ提取码：s4eg此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
xuyangzhu你好我无法从百度云盘下载，请使用其他云服务进行上传。___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
由于政策原因，很多外国的云服务无法使用，感谢你的服务。此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
