Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\a\Desktop\101522-28234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 22000 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`22c00000 PsLoadedModuleList = 0xfffff803`238297b0
Debug session time: Sat Oct 15 22:44:08.108 2022 (UTC + 8:00)
System Uptime: 27 days 20:07:35.974
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`2301acf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa07`dd88af90=000000000000001a
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffff3ffae54678
Arg3: 0000000000080000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3061
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 22024
Key : Analysis.IO.Other.Mb
Value: 6
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 31
Key : Analysis.Init.CPU.mSec
Value: 718
Key : Analysis.Init.Elapsed.mSec
Value: 360489
Key : Analysis.Memory.CommitPeak.Mb
Value: 99
Key : Bugcheck.Code.DumpHeader
Value: 0x1a
Key : Bugcheck.Code.Register
Value: 0x1a
Key : Dump.Attributes.AsUlong
Value: 100c
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.InsufficientDumpfileSize
Value: 1
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Dump.Attributes.RequiredDumpfileSize
Value: 0x52b9b021
Key : MemoryManagement.PFN
Value: 80
FILE_IN_CAB: 101522-28234-01.dmp
DUMP_FILE_ATTRIBUTES: 0x100c
Insufficient Dumpfile Size
Kernel Generated Triage Dump
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41792
BUGCHECK_P2: ffffff3ffae54678
BUGCHECK_P3: 80000
BUGCHECK_P4: 0
MEMORY_CORRUPTOR: ONE_BIT
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: WmiPrvSE.exe
STACK_TEXT:
fffffa07`dd88af88 fffff803`22e9f54d : 00000000`0000001a 00000000`00041792 ffffff3f`fae54678 00000000`00080000 : nt!KeBugCheckEx
fffffa07`dd88af90 fffff803`22eaba3a : 00000000`00000000 ffffff3f`fae54678 00000000`00000000 00000000`00000000 : nt!MiDeleteVa+0x155d
fffffa07`dd88b090 fffff803`22eabd59 : 00000000`00000000 ffffaa87`ac40a700 ffffff7f`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x30a
fffffa07`dd88b120 fffff803`22eabd59 : 00000000`00000000 ffffaa87`ac40a700 ffffff7f`00000000 00000000`00000010 : nt!MiWalkPageTablesRecursively+0x629
fffffa07`dd88b1b0 fffff803`22eabd59 : fffffa07`00000000 ffffaa87`ac40a700 fffffa07`00000000 00000000`00000020 : nt!MiWalkPageTablesRecursively+0x629
fffffa07`dd88b240 fffff803`22f4a181 : 00000000`00000000 ffffaa87`ac40a700 00000000`00000000 00000000`00000030 : nt!MiWalkPageTablesRecursively+0x629
fffffa07`dd88b2d0 fffff803`22e9df10 : fffffa07`dd88b480 00000000`00000001 ffffff7f`00000002 ffffff7f`00000000 : nt!MiWalkPageTables+0x381
fffffa07`dd88b3d0 fffff803`22e7e202 : ffffaa87`acc24900 fffff803`22e7e041 fffffa07`dd88b780 ffffaa87`00000000 : nt!MiDeletePagablePteRange+0x5d0
fffffa07`dd88b6e0 fffff803`233293e9 : 00000000`00000000 fffffa07`dd88b799 ffffaa87`ac40a080 ffffaa87`acc24900 : nt!MiDeleteVirtualAddresses+0x52
fffffa07`dd88b730 fffff803`2339f479 : ffffaa87`ac40a080 ffffaa87`acc24900 ffffaa87`00000000 00007df5`cdc30000 : nt!MiDeleteVad+0x199
fffffa07`dd88b800 fffff803`2339f007 : ffffaa87`acc24900 ffffaa87`aaf469a0 ffffaa87`abc0f080 00000000`00000000 : nt!MiUnmapVad+0x49
fffffa07`dd88b830 fffff803`2339ee7d : ffffaa87`acc24400 ffffaa87`acc24400 ffffaa87`abc0f080 ffffaa87`ac40a080 : nt!MiCleanVad+0x2f
fffffa07`dd88b860 fffff803`23365a4b : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffaa87`ac40a080 : nt!MmCleanProcessAddressSpace+0x10d
fffffa07`dd88b8e0 fffff803`233b332b : ffffaa87`ac40a080 ffffcd07`5c0130a0 ffffaa87`ac40a080 00000000`00000000 : nt!PspRundownSingleProcess+0x207
fffffa07`dd88b970 fffff803`232c3fb1 : 00000000`00000000 ffffaa87`ac40a001 ffffaa87`abc0f080 00000005`31558000 : nt!PspExitThread+0x613
fffffa07`dd88ba60 fffff803`2302d375 : ffffaa87`000012b8 ffffaa87`abc0f080 ffffaa87`ac40a080 ffffaa87`ac40a080 : nt!NtTerminateProcess+0xf1
fffffa07`dd88bae0 00007fff`7eee4104 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000005`3131fac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`7eee4104
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
--------- Hi,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,嗨,苏基穆,迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面,然后通过OneDrive或GoogleDrive共享它们,以便分析并指出导致崩溃的文件。问候,
我只找到两个DMP文件https://t14jh-my.sharepoint.com/:u:/g/personal/chen_t14jh_onmicrosoft_com/EfD7roU5dXNHvNnnCD4nbfUBbcAzzkVRs0d7N7UC_jNBUA?e=VtmyuB此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
嗨,苏基穆,感谢您分享小型转储文件。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-从设备管理器更新所有驱动程序或下载然后安装制造商网站上提供的最新驱动程序。8-如果问题仍然存在,请启用驱动程序验证程序2天或直到您获得另一个BSOD并共享minidump文件以指示导致问题的文件:https://www-tenforums-com.translate.goog/tutori.不要忘记在2天后禁用它,因为它会导致其他问题。如果您需要进一步的帮助,请告诉我并让我更新。______________________________________________________________________标准免责声明:有非Microsoft网站的链接。这些页面似乎提供了准确、安全的信息。请