Bsod

ClassyKM · 30 Aug 2018

My friend's computer keeps crashing while playing games.

Specs:
GPU: GTX 760
Processor: FX-6300
RAM: Ballistix Sport 8GB
Motherboard: GA-78LMT-USB3 (rev. 6.0)
SSD: 500GB Samsung that just replaced an older 500GB HDD.
Windows 10 64bit

Here is the DMP File: 083018-5734-01.dmp - Google Drive

I will add that I had him disable fast startup to rule out that possibility.

mrjimphelps · 30 Aug 2018

Put the old drive back in the computer, to see if the problem stops. If so, then put the new drive back in the computer, to see if the problem returns. This will confirm whether or not the drive is the cause of the problem.

If it is confirmed that the drive is the cause of the problem...

Did you say that you now have an HDD in the computer? If so, then make sure that the HDD is installed in the computer, and run CHKDSK /F. This will check the drive for errors, and fix them if it finds any.

ClassyKM · 30 Aug 2018

My bad, the HDD was replaced by the SSD, fixed the typo. He will go into the boot menu you start from the other hard drive. (He had it running as storage but never deleted Windows off of it)

EDIT: He went back to his SSD because there's a problem with the HDD's installation of Windows 10.

Here is a report from WhoCrashed:

On Thu 8/30/2018 1:29:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\083018-5734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC4A7)
Bugcheck code: 0x124 (0x0, 0xFFFFCB884F9648F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

ClassyKM · 11 Sep 2018

Fixed, the problem was my friend had his SSD as a slave drive instead of the master so he set it as the Master and reformatted the Hard Drives, one of which had his old OS.