Aug 3, 2020
1
0
10
0
I recently purchased a computer about 3 months ago. Ever since I have been getting frequent BSOD when I play Dota 2 and randomly when using the computer. I have even BSOD while watching NETFLIX.

Other times the computer has BSOD without me touching it at all.

I have gone back and forth 2-3 times every week getting it checked and fixing but the technician cannot find any issues. However, the BSOD continues.

What I have done so far:
Windows Memory Diagnostic Testing - No errors found
Disk Fragmented
Switched Ram with another computer - still BSOD
Motherboard - ASRock Phantom Gaming 6 Z390 - switched to Gigabyte Z390 - Still crashed with BSOD
Graphics Card - Replaced it and switched upgrading it to better current - GEForce GTX 1660 Super
Power Supply - had issues with it not turning on, changed from a 450 > 650 > now 850 Corsair Gold Certified
C Drive - Upgraded brand new Kingston 500GB SSD M.2 on motherboard to a Samsung 500GB SSD M.2 - still BSOD
Hard Drive and SSD - I have 2 SSDs both 2 TB, 1TB old HDD and 120GB (used to have windows installed but is now a normal hard drive)
Power Point - running direct connection to power supply from another power point with extension cord

Current Computer Specs:
Processor - Intel(R) Core(TM) i7-8700k CPU @ 3.70GHz 3.70 GHz
Ram - 2 x 16GB Corsair RGB Ram
Motherboard - ASRock Phantom Gaming 6 Z390
Graphics Card - GeForce GTX 1660 Super
System Type - 64 Bit Operating System
Windows - Windows 10 Home

I have recently been searching how to fix this BSOD because it is too frequent and everything is BRAND NEW! All parts are brand new!

I have not changed the CPU or the current RAM with the shop yet as the technician says there is nothing wrong with them.

I have just ran the windbg to try identify the source but I am a little confused, I think it is the CPU but temperatures in BIOS show 45 degrees CPU, M/B 31 degrees, CPU voltage 1.056.

Here is the code that I have debugged, any help or confirmation of the main issue would be of great help.

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080320-8578-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80259c00000 PsLoadedModuleList = 0xfffff8025a82a310
Debug session time: Mon Aug 3 17:34:51.931 2020 (UTC + 10:00)
System Uptime: 0 days 6:11:48.619
Loading Kernel Symbols
...............................................................
................................................................
................................................................

Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80259fddb60 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8025e2478f0=0000000000000124
0: 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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffd9896a278028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000080005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

fffff8025a80f2a8: Unable to get Flags value from nt!KdVersionBlock
fffff8025a80f2a8: Unable to get Flags value from nt!KdVersionBlock
*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
* *
*
fffff8025a80f2a8: Unable to get Flags value from nt!KdVersionBlock
*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *
* *
*
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4484

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-NR3SHTO

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 37556

Key : Analysis.Memory.CommitPeak.Mb
Value: 94

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

Key : WHEA.MCiStatus.Code
Value: 0xb200000000080005

Key : WHEA.MCiStatus.McaError
Value: 0x0005

Key : WHEA.MCiStatus.ModelError
Value: 0x0008

Key : WHEA.MCiStatus.Reserved
Value: 0x00000000


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd9896a278028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 80005

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8025e2478e8 fffff8025a0bfd5a : 0000000000000124 0000000000000000 ffffd9896a278028 00000000b2000000 : nt!KeBugCheckEx
fffff8025e2478f0 fffff802567815b0 : 0000000000000000 ffffd9896a278028 ffffd989629dd5b0 ffffd9896a278028 : nt!HalBugCheckSystem+0xca
fffff8025e247930 fffff8025a1c401e : 0000000000000000 fffff8025e2479d9 ffffd9896a278028 ffffd989629dd5b0 : PSHED!PshedBugCheckSystem+0x10
fffff8025e247960 fffff8025a0c1681 : ffffd9896a2b8070 ffffd9896a2b8070 ffffd989629dd600 ffffd989629dd5b0 : nt!WheaReportHwError+0x46e
fffff8025e247a40 fffff8025a0c19f3 : 0000000000000000 ffffd989629dd600 ffffd989629dd5b0 0000000000000000 : nt!HalpMcaReportError+0xb1
fffff8025e247bb0 fffff8025a0c18d0 : ffffd9895f6f4060 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandlerCore+0xef
fffff8025e247c00 fffff8025a0c1b21 : 000000000000000c 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
fffff8025e247c40 fffff8025a0c0d8b : 0000000000000000 0000000000000000 fffff8025e247ed0 0000000000000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff8025e247c70 fffff8025a0c35d5 : ffffd9895f6f4060 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0x5f
fffff8025e247ca0 fffff8025a118d59 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
fffff8025e247cd0 fffff80259fecbba : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
fffff8025e247d00 fffff80259fec877 : fffff80200000000 fffff80259fec7ac 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x7a
fffff8025e247e40 fffff8027303138f : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
fffff8025e21c5e8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : intelppm!MWaitIdle+0x1f


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BANK0_MSCOD0008_MCACOD0005_PCC_UC_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {420afa50-bcf9-29b3-b2fd-21a20a397f2b}


Followup: MachineOwner
 

Colif

Win 10 Master
Moderator
WHEA = Windows Hardware Error Architecture
It is an error called by CPU but not necessarily caused by it.
Can be caused by Overclocks so remove any you may have.
Can be caused by overclocking software such as MSI Afterburner, Phantom Gaming Tuning (which is on the motherboard website)
Can be caused by drivers though rarely.
Can be caused by heat, unlikely on new PC.
Do you have latest BIOS for motherboard as that can help.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows
Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

motherboard link for later - https://www.asrock.com/MB/Intel/Z390 Phantom Gaming 6/index.asp#Download
 

Colif

Win 10 Master
Moderator
WHEA = Windows Hardware Error Architecture
It is an error called by CPU but not necessarily caused by it.
Can be caused by Overclocks so remove any you may have.
Can be caused by overclocking software such as MSI Afterburner, Phantom Gaming Tuning (which is on the motherboard website)
Can be caused by drivers though rarely.
Can be caused by heat, unlikely on new PC.
Do you have latest BIOS for motherboard as that can help.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows
Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

motherboard link for later - https://www.asrock.com/MB/Intel/Z390 Phantom Gaming 6/index.asp#Download
 

ASK THE COMMUNITY