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 !

Hello,

Please follow the BSOD - Posting Instructions so we can get the all the files necessary.

EDIT: I just noticed you uploaded it after I replied. I will take a look.

-Gamer

Coming up with an hardware issue.

First make sure you have all of your device drivers installed along with any windows updates.

Please run the following:

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through https://www.sevenforums.com/crash-lo...-what-try.html and use the following hardware checks to supplement that link.
If you are overclocking any hardware, please stop.
If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Run all but the advanced tests with SeaTools for HDDs.

SeaTools for WindowsSeaTools for DOS

Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.

• Real Temp is a good CPU temperature monitor.
• Speccy - System Information - Free Download will monitor all hardware temperatures.
• HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.

• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
• Run Prime95 - Stress Test Your CPU to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through https://www.sevenforums.com/crash-lo...-what-try.html for the crash.

Coutesy of: writhziden

Please post back results.

Thanks for response, my PC operates normally since the crash last time. I've update the intel GPU driver then. How about the genuineintel that noticed in the result, is it the cause ?

BugCheck 124, {7, ffffd20dbfe5c038, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner

We focus more on the BugCheck code than the "Probabaly Caused by". Sometimes we get lucky and the "Probably caused by" is correct and the issues get fixed quick, but sometimes not.If you do get a new crash, post up the files again, and we will debug those also and see if it is the same error or not.

HonorGamer said:

We focus more on the BugCheck code than the "Probabaly Caused by". Sometimes we get lucky and the "Probably caused by" is correct and the issues get fixed quick, but sometimes not.If you do get a new crash, post up the files again, and we will debug those also and see if it is the same error or not.

Ok, hope it a software fault only. Thank for your assistance ! :)

You're Welcome!