hp战x - 845 - G9 无电源时, 半个小时蓝屏5次

黔小墨 · ‎2024-06-24

半个小时蓝屏5次

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [C:\Windows\Minidump\062424-11953-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 (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff800`7ba00000 PsLoadedModuleList = 0xfffff800`7c62a360

Debug session time: Mon Jun 24 17:33:06.850 2024 (UTC + 8:00)

System Uptime: 0 days 0:29:10.690

*********************************************************************

* 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 50, {fffffc007bfe0373, 10, fffffc007bfe0373, 2}

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

7: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

it must be protected by a Probe. Typically the address is just plain bad or it

is pointing at freed memory.

Arguments:

Arg1: fffffc007bfe0373, memory referenced.

Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.

Arg3: fffffc007bfe0373, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

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

DEBUG_FLR_IMAGE_TIMESTAMP: 0

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

fffffc007bfe0373

FAULTING_IP:

+3532336432616362

fffffc00`7bfe0373 ?? ???

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 22937

LAST_CONTROL_TRANSFER: from fffff8007be397ed to fffff8007bdfdb50

STACK_TEXT:

ffffe08f`02e6f068 fffff800`7be397ed : 00000000`00000050 fffffc00`7bfe0373 00000000`00000010 ffffe08f`02e6f310 : nt+0x3fdb50

ffffe08f`02e6f070 00000000`00000050 : fffffc00`7bfe0373 00000000`00000010 ffffe08f`02e6f310 00000000`00000002 : nt+0x4397ed

ffffe08f`02e6f078 fffffc00`7bfe0373 : 00000000`00000010 ffffe08f`02e6f310 00000000`00000002 00000000`00000001 : 0x50

ffffe08f`02e6f080 00000000`00000010 : ffffe08f`02e6f310 00000000`00000002 00000000`00000001 00000000`00000000 : 0xfffffc00`7bfe0373

ffffe08f`02e6f088 ffffe08f`02e6f310 : 00000000`00000002 00000000`00000001 00000000`00000000 00000000`00000000 : 0x10

ffffe08f`02e6f090 00000000`00000002 : 00000000`00000001 00000000`00000000 00000000`00000000 00000003`00000000 : 0xffffe08f`02e6f310

ffffe08f`02e6f098 00000000`00000001 : 00000000`00000000 00000000`00000000 00000003`00000000 00000000`00000000 : 0x2

ffffe08f`02e6f0a0 00000000`00000000 : 00000000`00000000 00000003`00000000 00000000`00000000 00000000`00000000 : 0x1

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

坏坏的笑 · ‎2024-06-25

开机立刻点击F2，分别做一下硬盘和内存的检测看下，可以参考以下文档

HP 电脑 - 硬件故障测试 | HP®客户支持

欢迎来到社区，我是一名志愿者，在这里帮助大家答疑解难。
在论坛回复仅仅是我利用个休息时间的个人行为,不代表HP官方言论。

如果我的回复对您有帮助， 请点击按钮。如果我的回复帮助您解决了问题，别忘了点击，可以帮到其他遇到同样问题的用户。

黔小墨 · ‎2024-06-25

做了, 都没问题, 而且接着充电器, 就不会蓝屏

NAVI_Sasha · ‎2024-06-25

试一下这个工具

HP Image Assistant (HPIA)会通过网络连接惠普服务器，服务器中有和您机器一样型号的一个样本机的记录。通过分析对比，然后得出您和样本机器的差异，提示需要更新安装或缺少的驱动或软件。
HP Image Assistant (HPIA)下载
https://hpia.hpcloud.hp.com/downloads/hpia/hp-hpia-5.1.6.exe

欢迎来到社区，我是一名志愿者，在这里帮助大家答疑解难。
如果我的回复对您有帮助， 请点击按钮。如果我的回复帮助您解决了问题，别忘了点击，可以帮到其他遇到同样问题的用户。

黔小墨 · ‎2024-06-26

你的方法没有用, 我试过了.
我尝了新的方法, 目前能稳定工作几个小时, 还没蓝.

方法如下: 设定使用电池最小处理器状态 80%.

我怀疑电脑在低功率状态下有严重故障, 可能是bios的问题

Lanterns · ‎2024-07-11

我也有这个问题，最近离电会突然断电重启，放着不管它一会儿就蓝屏进不去系统了。我真服了这个破电脑，从22年买回来一堆BUG，各种睡眠睡死唤不醒睡不着的奇葩问题，系统全新安装了好几遍，驱动打了好几遍就是不行。shit惠普以后再也不会买了，等公司购置补贴结束换别的牌子了。

黔小墨 · ‎2024-07-12

症状全中, 巨傻. 所以我把睡眠模式关了, 只用休眠, 另外设置一下无电源最小系统处理器状态, 80%.
我测了半个月, 还没蓝, 凑活用了

ggmouse · ‎2024-07-23

我的win11 也是这个情况，换成PCIG3的三星的SSD就正常，怀疑是BIOS 对PCIG4的SSD 兼容有问题了，但是这个版本BIOS 没办法改PCI 兼容版本。

ggmouse · ‎2024-07-23

怎么关闭睡眠模式？

ganzaoqi · ‎2024-07-24

个人电脑战X-835-G9，症状类似，经常性卡屏、毫无征兆自动重启、花屏。

日常仅是日常办公操作，依然无法正常使用。近期找个这个帖子（【图片】锐龙版CPU笔记本低负载/离电/开机频繁蓝屏死机的原因及解决办法_笔记本吧_百度贴吧 (baidu.com)），这应该就是根本原因了，引用帖子内容：

AMD CPU通病，出厂设置的电压曲线过于极限，所以CPU出厂体质太差或者因为使用年限CPU缩肛后，当出现高频率低电压这种正常波动时，cpu电压不足导致的系统崩溃。

个人目前尝试解决办法：在电源选项中，将cpu最小和最大均设置为80%，近三天日常办公文字操作可正常使用。但不能过渡占用CPU，昨天尝试烤鸡，2分钟风扇狂转，电脑卡死。

现在只希望能正常使用，不再期望高性能，后悔在保修期内没换主板。