New
#1
PC hung while watching youtube, then reset itsefl without error code
Hi everyone, I've just build my PC for 1 month.
CPU i3-8100
MAIN Asrock B360M Pro4
RAM Crucial Ballistix Sport 8GB 2666MHz
SSD Samsung 960EVO 250GB
HDD WD Blue 250GB
PSU Seasonic S12II 520W
Last night, my PC hung while I was watching a stream session on youtube. Then, about 30-45 seconds later it self-reset without any error code show up on the screen and recorded a dump file in minidump folder. I used Windows Debugging Tool to analyze the dmp file and received the result below:
Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\062518-5734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`04807000 PsLoadedModuleList = 0xfffff803`04bc11f0
Debug session time: Mon Jun 25 01:23:40.319 2018 (UTC + 7:00)
System Uptime: 0 days 0:00:03.111
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
...
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {7, ffffd20dbfe5c038, 0, 0}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000007, BOOT Error
Arg2: ffffd20dbfe5c038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17134.112 (WinBuild.160101.0800)
DUMP_TYPE: 2
BUGCHECK_P1: 7
BUGCHECK_P2: ffffd20dbfe5c038
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x124_GenuineIntel
CPU_COUNT: 4
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: b
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: KALASHNIKOV
ANALYSIS_SESSION_TIME: 06-25-2018 15:56:02.0155
ANALYSIS_VERSION: 10.0.17134.12 amd64fre
STACK_TEXT:
ffffe204`ca5ca4b0 fffff803`04c9c991 : 00000000`00000000 ffffd20d`bfe5c010 ffffd20d`bf6d9bc0 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffffe204`ca5ca9e0 fffff803`04acff88 : ffffd20d`bfe5c010 fffff803`049134c1 00000000`00000000 ffffd20d`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffe204`ca5caa10 fffff803`04ad0c0b : fffff803`04bb24e0 ffffd20d`bf6d9bc0 ffffd20d`bf6d9bc0 fffff803`04e12990 : nt!WheapProcessWorkQueueItem+0x48
ffffe204`ca5caa50 fffff803`04849315 : 00000000`00000200 ffffd20d`c09b7040 fffff80c`76437cc0 ffffd20d`bf6d9bc0 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffffe204`ca5caa80 fffff803`048ebcb7 : ffffd20d`c09b7040 00000000`00000080 ffffd20d`bf6d3440 ffffd20d`c09b7040 : nt!ExpWorkerThread+0xf5
ffffe204`ca5cab10 fffff803`049a67d6 : ffffaa01`68779180 ffffd20d`c09b7040 fffff803`048ebc70 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffe204`ca5cab60 00000000`00000000 : ffffe204`ca5cb000 ffffe204`ca5c4000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e1ca14ad460db17fee32f4b133c79439b72309bb
THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x124_GenuineIntel__UNKNOWN_PRV
BUCKET_ID: 0x124_GenuineIntel__UNKNOWN_PRV
PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel__UNKNOWN_PRV
TARGET_TIME: 2018-06-24T18:23:40.000Z
OSBUILD: 17134
OSSERVICEPACK: 112
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-06-08 16:00:00
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17134.112
ANALYSIS_SESSION_ELAPSED_TIME: 4c0
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_genuineintel__unknown_prv
FAILURE_ID_HASH: {a7406f97-70d3-5fd4-2647-1fafa47ede59}
Followup: MachineOwner
---------
Please check it for me, I don't know whether it's a hardware fault or not. Appreciate your help, thanks !