BSOD possibly associated with gaming

[ubersyd]

Hi, ive been having this problem for maybe a year now but it seems to have gotten worse, here's my ZIP file...

It seems to happen when only when I'm gaming, and i have a suspicion it may have something to do with either my ram or graphics card, Thanks for any advice/help!


Sorry in advance, I'm a bit of a computer noob.

 

[ubersyd]

Bump, any help would be appreciated!

 

[ubersyd]

Bump

 

[koolkat77]

[FONT="Lucida Console"]Loading Dump File [C:\Users\YUSRA\Downloads\debug-SYDSCOMPUTER-xxxx\SFdebugFiles\010515-22120-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03060000 PsLoadedModuleList = 0xfffff800`032a36d0
Debug session time: Mon Jan  5 12:08:23.620 2015 (UTC + 6:00)
System Uptime: 0 days 0:36:12.619
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
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800892e028, be200000, 21136}

Probably caused by : GenuineIntel

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

4: 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: fffffa800892e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, 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:  javaw.exe

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

STACK_TEXT:  
fffff880`009bbb58 fffff800`03029a3b : 00000000`00000124 00000000`00000000 fffffa80`0892e028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009bbb60 fffff800`031ec463 : 00000000`00000001 fffffa80`07762d30 00000000`00000000 fffffa80`07762d80 : hal!HalBugCheckSystem+0x1e3
fffff880`009bbba0 fffff800`03029700 : 00000000`00000728 fffffa80`07762d30 fffff880`009bbf30 fffff880`009bbf00 : nt!WheaReportHwError+0x263
fffff880`009bbc00 fffff800`03029052 : fffffa80`07762d30 fffff880`009bbf30 fffffa80`07762d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009bbd50 fffff800`03028f0d : 00000000`00000008 00000000`00000001 fffff880`009bbfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009bbd90 fffff800`0301ce88 : 00000000`3e3c5960 00000000`00000204 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009bbdc0 fffff800`030d44ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009bbdf0 fffff800`030d4313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009bbf30 00000000`772925df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`416ceb04 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772925df


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}

Followup: MachineOwner
---------[/FONT]

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