这个是蓝屏的dump文件。 Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\080622-9500-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff800`46e00000 PsLoadedModuleList = 0xfffff800`47a2a270 Debug session time: Sat Aug 6 15:17:00.690 2022 (UTC 8:00) System Uptime: 0 days 0:04:02.811 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .................. Loading User Symbols Loading unloaded module list .......... Cannot read PEB32 from WOW64 TEB32 0000a5b3 - Win32 error 0n30 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {ffffb18c1a804b00, d, 0, fffff8004720a152} Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 42419 instance(s) of page corruption, target is likely to have memory corruption. 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffb18c1a804b00, memory referenced Arg2: 000000000000000d, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8004720a152, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd ffffb18c1a804b00 CURRENT_IRQL: d FAULTING_IP: nt!memmove 92 fffff800`4720a152 0f100411 movups xmm0,xmmword ptr [rcx rdx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System BAD_PAGES_DETECTED: a5b3 LAST_CONTROL_TRANSFER: from fffff80047209169 to fffff800471f71b0 STACK_TEXT: ffff8189`9ae5f3e8 fffff800`47209169 : 00000000`0000000a ffffb18c`1a804b00 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx ffff8189`9ae5f3f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch 0x69 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 42419 instance(s) of page corruption, target is likely to have memory corruption. 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: ffffb18c1a804b00, memory referenced Arg2: 000000000000000d, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8004720a152, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: ffffb18c1a804b00 CURRENT_IRQL: d FAULTING_IP: nt!memmove 92 fffff800`4720a152 0f100411 movups xmm0,xmmword ptr [rcx rdx] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System BAD_PAGES_DETECTED: a5b3 LAST_CONTROL_TRANSFER: from fffff80047209169 to fffff800471f71b0 STACK_TEXT: ffff8189`9ae5f3e8 fffff800`47209169 : 00000000`0000000a ffffb18c`1a804b00 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx ffff8189`9ae5f3f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch 0x69 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO Followup: MachineOwner --------- *** Memory manager detected 42419 instance(s) of page corruption, target is likely to have memory corruption.
欢迎咨询本站！。建议参考以下链接，检测一下内存和硬盘：https://answers.microsoft.com/zh-hans/windows/f.
