BSOD while playing various games.

Yoggitron23 · 29 Dec 2014

I'm an avid gamer and play League of Legends, TF2, Hearthstone, and many other games.
Recently I've been having (seemingly) random BSODs after playing these games for more than an hour at a time, except for Hearthstone, suprisingly.

I am generally unable to see what error codes come through due to my pc restarting almost instantly after the BSOD comes up, which I apologize for not having.

If any more information is required, I am willing to supply it as needed.

Attachment 344661

Attached is the debug file that is asked for in BSOD threads.

Many thanks in advance! :)

koolkat77 · 04 Jan 2015

Code:


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


Loading Dump File [C:\Users\USER\Downloads\Compressed\TREVOR-PC-Mon_12_29_2014_171528_30\122914-25437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e50890
Debug session time: Tue Dec 30 05:49:19.187 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:13.281
Loading Kernel 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, {0, fffffa80032388f8, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80032388f8, 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.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031876f0 fffff800`02ecdcb9 : fffffa80`032388d0 fffffa80`018ed660 fffff8a0`00000014 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03187c10 fffff800`02daeea7 : fffffa80`032388d0 fffff800`02e282d8 fffffa80`018ed660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03187c40 fffff800`02d16275 : fffff800`02e89d00 00000000`00000001 fffffa80`02869830 fffffa80`018ed660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03187c80 fffff800`02c8c261 : fffff880`01157e00 fffff800`02d16250 fffffa80`018ed600 0002c007`ba050080 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03187cb0 fffff800`02f1e73a : 0002a007`d6440080 fffffa80`018ed660 00000000`00000080 fffffa80`018db040 : nt!ExpWorkerThread+0x111
fffff880`03187d40 fffff800`02c738e6 : fffff880`02f63180 fffffa80`018ed660 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03187d80 00000000`00000000 : fffff880`03188000 fffff880`03182000 fffff880`03764730 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try