附上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真……臭
uj5u.com熱心網友回復：
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 ***
***
uj5u.com熱心網友回復：
你試過把兩根記憶體先撥一根出來，再運行你的游戲看看。uj5u.com熱心網友回復：
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
下面還一點
uj5u.com熱心網友回復：
記憶體換新2次了,都是默頻都藍,4根通道兩兩都對插過了,回去再試試單根吧 哎
uj5u.com熱心網友回復：
有沒有能看懂DUMP的大神啊uj5u.com熱心網友回復：
樓主解決了嗎？和你差不多的配置，也是經常重啟，玩游戲卡死重啟uj5u.com熱心網友回復：
CPU溫度高不高？uj5u.com熱心網友回復：
PSHED.dll一般還是硬體故障造成的，不妨先找個同版本的PSHED.dll在PE下替換，或者徹底按照win10向導重新安裝并重新安裝經數字簽名的官方正式版驅動。若上述方法仍然我無法解決只能繼續硬體替換法逐步排查了
uj5u.com熱心網友回復：
先用驅動精靈軟體升級能升級的所有驅動試試。uj5u.com熱心網友回復：
新電腦，半個月，趕緊找廠家，找客服啊，系統配置你能搞定，硬體故障你怎么知道不是出廠就有問題的額？？自己瞎鼓搗壞了，客服可就不管了...轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/56117.html
標籤：Windows客戶端使用
上一篇：一個網站被劫持的問題