救救孩子吧.......玩游戏蓝屏了

这个是dmp错误文件的内容,有大手子帮忙看看吗?



Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\123020-6765-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
Machine Name:
Kernel base = 0xfffff807`66c00000 PsLoadedModuleList = 0xfffff807`6782a2b0
Debug session time: Wed Dec 30 18:57:23.187 2020 (GMT+8)
System Uptime: 0 days 14:57:21.844
*********************************************************************
* 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 A, {fffffd40800000c0, 2, 0, fffff80766e14e24}

***** 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_VISTA )

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

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

经典问题，内存超频，蓝屏，先从内存恢复默认着手，再排查其他问题。

Probably caused by : hardware_ram ( PAGE_NOT_ZERO_VISTA )

里头写的

看都不用多看，内存，降到3200-3600一般就能稳

Probably caused by : hardware_ram ( PAGE_NOT_ZERO_VISTA )

Followup: MachineOwner

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

坑爹的.....内存

内存不稳啊。

内存跑过测试么，如果测试没问题，很大概率是显卡的热气把内存温度给顶上来了，降个档位跑吧，跑测试时候甜甜圈和tm5一起开，模拟一下游戏温度场景，

[quote][pid=481199237,24894137,1]Reply[/pid] Post by [uid=42194701]丨Sylvanas[/uid] (2020-12-30 21:08):

内存跑过测试么，如果测试没问题，很大概率是显卡的热气把内存温度给顶上来了，降个档位跑吧，跑测试时候甜甜圈和tm5一起开，模拟一下游戏温度场景，[/quote]恩,跑过TM5,一圈跑完没问题,我先把soc从1.2降到1.15,然后再跑跑看,c9bkv看不到温度,我再跑跑TM5和甜甜圈看,然后再去玩游戏

[quote][pid=481199673,24894137,1]Reply[/pid] Post by [uid=520301]狂龙幽灵[/uid] (2020-12-30 21:11):

恩,跑过TM5,一圈跑完没问题,我先把soc从1.2降到1.15,然后再跑跑看,c9bkv看不到温度,我再跑跑TM5和甜甜圈看,然后再去玩游戏[/quote]降完soc再跑跑aida看下延迟，不过你这设置的确实有点激进，能稳住flck就行了

[quote][pid=481201798,24894137,1]Reply[/pid] Post by [uid=42194701]丨Sylvanas[/uid] (2020-12-30 21:21):

降完soc再跑跑aida看下延迟，不过你这设置的确实有点激进，能稳住flck就行了[/quote]恩，对啊，之前第一次改SOC 1.2v开不了机，后来不知道怎么能开机就这么用了，测了1.15和1.2都一样，跑aida64内存都差不多

[quote][pid=481201798,24894137,1]Reply[/pid] Post by [uid=42194701]丨Sylvanas[/uid] (2020-12-30 21:21):

降完soc再跑跑aida看下延迟，不过你这设置的确实有点激进，能稳住flck就行了[/quote]我调到1.15v，tm5过20分钟报错，现在调1.17再试试

2077是这样的，可以拿来当内存稳定测试软件了，比aida64猛

[quote][pid=481212938,24894137,1]Reply[/pid] Post by [uid=61065632]清风33[/uid] (2020-12-30 22:17):

2077是这样的，可以拿来当内存稳定测试软件了，比aida64猛[/quote]对啊,所以跑完测试没问题就在2077找个人多的地方挂机......

[quote][pid=481210833,24894137,1]Reply[/pid] Post by [uid=520301]狂龙幽灵[/uid] (2020-12-30 22:07):

我调到1.15v，tm5过20分钟报错，现在调1.17再试试[/quote]别调soc了，你放宽时序吧

[quote][pid=481217946,24894137,1]Reply[/pid] Post by [uid=42194701]丨Sylvanas[/uid] (2020-12-30 22:42):

别调soc了，你放宽时序吧[/quote]恩，只能这样了