Strange BSODs, Unable to Determine Cause Alone

Occasionally, my entire system will just hang and either be forced to restart, or, very rarely, it will be able to regain control and continue working. I've ran memtest and memtestx86 to determine if the cause is my ram, but both tests showed the ram is working fine. The cause could be my GPU, an ASUS R9 290, but I have already done two RMA's to have the card repaired.

To get a bit of insight on these BSOD's, my system is very unstable for most games. When running Rust, my system seems to be extremely stable and can run the game for eternity. Whilst watching videos on youtube, the system is somewhat stable, the potential of a crash is still there, but I am free to do as I please for hours. Now, when playing other games, such as: League of Legends, Garry's Mod, Fallout: New Vegas, Bordelands 2, the system is extremely unstable. The most I can get is a few hours and crashing is extremely frequent.

I have been told that doing a bios update fixes most problems of an unstable system, but my motherboard rejected the latest bios that I tried to use in the update. I am afraid I have nothing left up my sleeve, and thus, must turn to these forums.

I have used the DM Log Collector program, so the ZIP is attached below. I am hoping to have this problem resolved soon as I must escape this elo hell in League of Legends and reach my true potential: Challenjour.

You will do yourself a world of favours by installing a genuine copy of Windows 7, you have an HP PID on a retail Gigabyte motherboard which means your install is counterfeit.

Code:

Host Name:                 TURTLE-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Levande
Registered Organization:   
Product ID:                00426-OEM-8992662-00010 ---> HP PID
Original Install Date:     6/1/2015, 5:31:39 PM
System Boot Time:          6/15/2015, 9:31:10 PM
System Manufacturer:       Gigabyte Technology Co., Ltd.
System Model:              GA-78LMT-USB3
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.

Counterfeit installations such as yours can contain heavily modified code that can cause the installation to behave it unexpected ways. Analysing BSODs and determining their causes on these sorts of installations is completely unreliable, and for this reason most analysts won't attempt it.

My recommendation is to install a genuine copy of Windows 7. This will minimise the problems you are experiencing and make subsequent diagnosis of BSODs far more reliable. Once you are running a genuine Windows 7 installation and are still experiencing BSODs, upload your new logs we will be happy to help you solve them.

Good move on going genuine. The single dump is a 0x124 which denotes a hardware error but doesn't show which piece of hardware is faulty.

Code:

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: 0000000000000000, Machine Check Exception
Arg2: fffffa8007faa038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

3: kd> !errrec fffffa8007faa038
===============================================================================
Common Platform Error Record @ fffffa8007faa038
-------------------------------------------------------------------------------
Record Id     : 01d0ade7f1c5a188
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/23/2015 19:08:18 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007faa0b8
Section       @ fffffa8007faa190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007faa100
Section       @ fffffa8007faa250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007faa250

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007faa148
Section       @ fffffa8007faa2d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000fdefc024
  Misc.       : 0xc00a0fff01000000

Run all rounds of Windows Updates prior to carrying out the stress and diagnostic tests outlined below.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

   Warning

If you're overclocking your system, revert back to stock clocks now.

   Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

 CPU TEST

Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

 RAM TEST

Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

THREE

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check

FOUR

 GPU TEST

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.