win10 蓝屏查看dmp文件反应：Probably caused by : hardware_ram ( PAGE_NOT_ZERO )

sakuya401 2022-11-25 19:36:14

现象大概是从我开始使用虚拟机的时候，开了两台虚拟机，学习hive+Hadoop+presto等的学习，有时候虚拟机在使用途中就会蓝屏，有时候是虚拟机关闭后，空余了一会儿会蓝屏；

由于笔记本是板载内存，也没办法加内存条，麻烦各位大佬看看到底是不是虚拟机引起的问题，或者是别的问题。

下面是我笔记本的配置：

下面是两台虚拟机的配置：

下面是蓝屏的图片说明：

以下是dmp的文件内容：

Loading Dump File [C:\Windows\Minidump\112522-13593-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 <symbol_path> 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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff807`5aa00000 PsLoadedModuleList = 0xfffff807`5b62a290
Debug session time: Fri Nov 25 18:45:25.698 2022 (GMT+8)
System Uptime: 1 days 22:17:51.385
*********************************************************************
* 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 <symbol_path> 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
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {ffffd50c4ed79158, ffffffffc000026e, 2f129d860, fffff807a588b010}

Unable to load image MessageTransfer.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MessageTransfer.sys
*** ERROR: Module load completed but symbols could not be loaded for MessageTransfer.sys
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* 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 <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware_ram ( PAGE_NOT_ZERO )

Followup: MachineOwner
---------

*** Memory manager detected 183844 instance(s) of page corruption, target is likely to have memory corruption.

下面是点击了!analyze -v的详细内容

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffffd50c4ed79158, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000026e, error status (normally i/o status code)
Arg3: 00000002f129d860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff807a588b010, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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: fffff8075aa00000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

ERROR_CODE: (NTSTATUS) 0xc000026e - <Unable to get error code text>

BUGCHECK_STR: 0x7a_c000026e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 2ce24

LAST_CONTROL_TRANSFER: from fffff8075acf1c69 to fffff8075adf8fa0

STACK_TEXT:
ffffaa0c`0f64eb48 fffff807`5acf1c69 : 00000000`0000007a ffffd50c`4ed79158 ffffffff`c000026e 00000002`f129d860 : nt+0x3f8fa0
ffffaa0c`0f64eb50 00000000`0000007a : ffffd50c`4ed79158 ffffffff`c000026e 00000002`f129d860 fffff807`a588b010 : nt+0x2f1c69
ffffaa0c`0f64eb58 ffffd50c`4ed79158 : ffffffff`c000026e 00000002`f129d860 fffff807`a588b010 fffff807`5ace4b27 : 0x7a
ffffaa0c`0f64eb60 ffffffff`c000026e : 00000002`f129d860 fffff807`a588b010 fffff807`5ace4b27 00000000`00000001 : 0xffffd50c`4ed79158
ffffaa0c`0f64eb68 00000002`f129d860 : fffff807`a588b010 fffff807`5ace4b27 00000000`00000001 ffffad0b`9b6d9010 : 0xffffffff`c000026e
ffffaa0c`0f64eb70 fffff807`a588b010 : fffff807`5ace4b27 00000000`00000001 ffffad0b`9b6d9010 ffffad0b`b7759640 : 0x2`f129d860
ffffaa0c`0f64eb78 fffff807`5ace4b27 : 00000000`00000001 ffffad0b`9b6d9010 ffffad0b`b7759640 ffffad0b`9914e7d0 : MessageTransfer+0x22b010
ffffaa0c`0f64eb80 00000000`00000001 : ffffad0b`9b6d9010 ffffad0b`b7759640 ffffad0b`9914e7d0 00000000`00000000 : nt+0x2e4b27
ffffaa0c`0f64eb88 ffffad0b`9b6d9010 : ffffad0b`b7759640 ffffad0b`9914e7d0 00000000`00000000 fffff807`5acb9c92 : 0x1
ffffaa0c`0f64eb90 ffffad0b`b7759640 : ffffad0b`9914e7d0 00000000`00000000 fffff807`5acb9c92 ffffaa0c`00000000 : 0xffffad0b`9b6d9010
ffffaa0c`0f64eb98 ffffad0b`9914e7d0 : 00000000`00000000 fffff807`5acb9c92 ffffaa0c`00000000 fffff807`00000000 : 0xffffad0b`b7759640
ffffaa0c`0f64eba0 00000000`00000000 : fffff807`5acb9c92 ffffaa0c`00000000 fffff807`00000000 fffff807`a588b010 : 0xffffad0b`9914e7d0

STACK_COMMAND: kb

SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

下面是用解析器解析出的数据