新电脑反复蓝屏折磨我大半个月了，求大神帮忙看看DUMP文件

[kisshasksky]

附上DUMP链接: https://pan.baidu.com/s/1LA8Lritpg6cAJnq8j3AWQg提取码: 2cpr


系统：win10 1903官网镜像u盘安装的
硬件：9700k散片
技嘉z390 elite
技嘉2070 gaming oc
金士顿掠食者3200 8g*2
三星970 evo plus
振华LEADEX G 650W

驱动：系统安装好后自动更新了，N卡官网驱动打不上去，只能用win10商店版

网上查蓝屏问题解决方法能修改的基本都修改了，一开始怀疑是内存原因售后换新了两次，现在是开着xmp3200 runmemtestpro 1000%0错误
cpu跑了pfu 40多分钟没问题，85度左右
磁盘检测无坏块
aida64 默认四项半小时无异常

bios只关了speed shift te……，c-stagebios里没有，防掉压turbo。

CPU电压一般在0.66和1.2v之间变动(节能没关)内存电压开1.34是1.34-1.355，xmp默认的1.35和手动调1.35 easyturn都显示是1.36，电压是1.368-1.38

现在的情况就是经常蓝屏自动重启，开网页也蓝，蓝屏界面0%直接闪一下自动重启，都是显示whea_什么的那个错误代码，偶尔几次能保存到dmp文件解析是显示0x00000124。玩吃鸡半小时到一小时左右也会蓝屏或者直接嗡嗡嗡的卡机声黑屏死机重启

究竟是系统的问题还是主板 cpu或者电压的问题啊？再不行我都想买个pcie usb转接卡装 win7算了哭1咖喱味的win10真……臭

[kisshasksky]

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


Loading Dump File [C:\Documents and Settings\Administrator\桌面\070819-13656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'C:/MyCodesSymbols'
WARNING: Whitespace at start of path element
Symbol search path is: C:/MyCodesSymbols; SRV*C:/MyLocalSymbols*//msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\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 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`6ea00000 PsLoadedModuleList = 0xfffff807`6ee43370
Debug session time: Mon Jul 8 21:02:32.843 2019 (UTC + 8:00)
System Uptime: 0 days 0:15:52.620
Unable to load image \SystemRoot\system32\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
.............
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffda0a383b8028, be000000, c117a}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
***

[lich2005]

你试过把两根内存先拨一根出来，再运行你的游戏看看。

[kisshasksky]

fffff807`6ea00000 fffff807`6f4b2000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: \SystemRoot\system32\ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: ***** Invalid (EADCD02B)
CheckSum: 00979F34
ImageSize: 00AB2000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
下面还一点

[kisshasksky]

引用 2 楼 lich2005 的回复:

你试过把两根内存先拨一根出来，再运行你的游戏看看。

内存换新2次了,都是默频都蓝,4根通道两两都对插过了,回去再试试单根吧 哎

[kisshasksky]

有没有能看懂DUMP的大神啊

[Stunt33112]

楼主解决了吗？和你差不多的配置，也是经常重启，玩游戏卡死重启

[hh448960]

CPU温度高不高？

[夜鹰]

PSHED.dll一般还是硬件故障造成的，不妨先找个同版本的PSHED.dll在PE下替换，或者彻底按照win10向导重新安装并重新安装经数字签名的官方正式版驱动。 若上述方法仍然我无法解决只能继续硬件替换法逐步排查了

[imjiabin]

新电脑，半个月，赶紧找厂家，找客服啊，系统配置你能搞定，硬件故障你怎么知道不是出厂就有问题的额？？自己瞎鼓捣坏了，客服可就不管了...