暗影精灵9plus蓝屏

xyfyb — Sun, 29 Oct 2023 04:01:14 GMT

以前没有这种情况，最近开始隔一两天蓝屏一次然后立即重启，下面是windbg分析的dmp文件：

Loading Dump File [C:\Users\11846\OneDrive\Desktop\102823-9140-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 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff804`78a00000 PsLoadedModuleList = 0xfffff804`79612fc0
Debug session time: Sat Oct 28 20:01:30.391 2023 (UTC + 8:00)
System Uptime: 0 days 9:06:57.063
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 FC, {ffffb107622df940, 8a0000078ca52963, ffffb107622df660, 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 171708 instance(s) of page corruption, target is likely to have memory corruption.

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffb107622df940, Virtual address for the attempted execute.
Arg2: 8a0000078ca52963, PTE contents.
Arg3: ffffb107622df660, (reserved)
Arg4: 0000000000000000, (reserved)

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

DEBUG_FLR_IMAGE_TIMESTAMP: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xFC

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 29ebc

LAST_CONTROL_TRANSFER: from fffff80478ec3282 to fffff80478e28700

STACK_TEXT:
ffffb107`622df4a8 fffff804`78ec3282 : 00000000`000000fc ffffb107`622df940 8a000007`8ca52963 ffffb107`622df660 : nt+0x428700
ffffb107`622df4b0 00000000`000000fc : ffffb107`622df940 8a000007`8ca52963 ffffb107`622df660 00000000`00000000 : nt+0x4c3282
ffffb107`622df4b8 ffffb107`622df940 : 8a000007`8ca52963 ffffb107`622df660 00000000`00000000 00000000`00000000 : 0xfc
ffffb107`622df4c0 8a000007`8ca52963 : ffffb107`622df660 00000000`00000000 00000000`00000000 ffffb107`622df580 : 0xffffb107`622df940
ffffb107`622df4c8 ffffb107`622df660 : 00000000`00000000 00000000`00000000 ffffb107`622df580 fffff804`78ebcbc9 : 0x8a000007`8ca52963
ffffb107`622df4d0 00000000`00000000 : 00000000`00000000 ffffb107`622df580 fffff804`78ebcbc9 00000000`00000011 : 0xffffb107`622df660

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 171708 instance(s) of page corruption, target is likely to have memory corruption.

回复：暗影精灵9plus蓝屏

y2kim — Mon, 30 Oct 2023 08:17:56 GMT

有没有自己添加、升级、改造内部硬件

机器平时外接什么设备，除了电源

如果有，还原最初的硬件，除了电源，其他外部设备都不接

如果都没有

先看机器是否长时间运行测试无异常，判断有没有存在硬件故障。

开机按F2进入白色背景画面HP PC Hardware Diagnostics UEFI。

开机按F2进入的如果不是白色背景，要重新下载安装UEFI诊断工具。

https://h30318.www3.hp.com/pub/softpaq/sp144501-145000/sp144997.exe

没有操作系统，用其他电脑下载运行工具，制作安装到USB，安装过程有选择的选项。故障机接USB开机按F2。

白色背景菜单中选择-系统测试-广泛测试-循环运行直到出现错误。

建议晚上休息前，不用机器的时候进行，跑一晚上。

开始进行之后可以不用管电脑放一边。

了解更多

HP 电脑 - 硬件故障测试

该主题

暗影精灵9plus蓝屏

回复： 暗影精灵9plus蓝屏

回复：暗影精灵9plus蓝屏