System: win10 1903 website image u disk installed
Hardware: 9700 k pieces
Gigabyte z390 elite
Gigabyte 2070 gaming oc
Kingston predators 3200 8 g * 2
Samsung evo 970 plus
Zhenhua LEADEX G 650 w
Driver: system installed automatically updated, N card website drive dozen don't go up, can only use win10 store version
Internet blue screen problem solving methods to modify the basic modification, a began to suspect that was the cause of the memory after change new twice, is now open xmp3200 runmemtestpro 1000% 0 error
CPU run pfu no problem, more than 40 minutes of about 85 degree
Disk test without bad block
Aida64 default four and a half hours without exception
The BIOS just closed the speed shift te... No, c - stagebios, drop pressure turbo,
CPU voltage changes generally between 0.66 and 1.2 v (energy saving open) memory voltage is 1.34 1.34 1.355, XMP 1.35 and 1.35 easyturn manually adjustable are shown by default is 1.36, the voltage is 1.368 1.38
Now situation is often blue screen automatically restart, open a web page also blue, blue screen interface 0% flash directly automatic restart, is show whea_ what the error code, occasionally a few times can save the DMP file parsing is show 0 x00000124, playing half an hour to an hour or so the chicken will buzz blue screen or black screen sound CARDS crash restart
Whether it is a problem of system or the motherboard or CPU voltage problem? Not again I want to buy a pcie usb adapter card is installed Windows 7 well cry 1 curry win10 true... Smelly
CodePudding user response:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading the Dump File (C: \ Documents and Settings \ Administrator \ \ desktop. 070819-13656-01 DMP]
The Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'C:/MyCodesSymbols'
WARNING: Whitespace at the start of the path element
Symbol search path is: C:/MyCodesSymbols; The SRV * C:/MyLocalSymbols *//msdl.microsoft.com/download/symbols
The Executable search path is:
Unable to load the image \ SystemRoot \ system32 \ ntoskrnl exe, Win32 error 0 n2
* * * WARNING: Unable to verify timestamp for ntoskrnl. Exe
* * * ERROR: Module load completed but symbols could not be the loaded for ntoskrnl. Exe
Windows 7 the Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1 amd64fre. 19 h1_release. 190318-1202
The Machine Name:
The Kernel base=0 xfffff807 ` 6 ea00000 PsLoadedModuleList=0 xfffff807 ` 6 ee43370
The Debug session time: 8 21:02:32 Mon Jul., 843, 2019 (UTC + 8)
The System Uptime: 620
0 days 0:15:52.Unable to load the image \ SystemRoot \ system32 \ ntoskrnl exe, Win32 error 0 n2
* * * WARNING: Unable to verify timestamp for ntoskrnl. Exe
* * * ERROR: Module load completed but symbols could not be the loaded for ntoskrnl. Exe
Loading the Kernel Symbols
...
.
.
Loading User Symbols
Loading unloaded the module list
.
* * * WARNING: Unable to verify timestamp for Hal. DLL
* * * ERROR: Module load completed but symbols could not be the loaded for Hal. DLL
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
* Bugcheck Analysis *
* *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The Use! Analyze the -v to get the detailed was 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 the loaded for mssmbios. Sys
* * * * * the Kernel symbols are WRONG. Both 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 (to the 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 * * *
* * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * *
* * * * * *
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull