Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD possibly associated with gaming

05 Jan 2015   #1
ubersyd

Windows 7 Home Premium 64bit
 
 
BSOD possibly associated with gaming

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.


My System SpecsSystem Spec
.
05 Jan 2015   #2
ubersyd

Windows 7 Home Premium 64bit
 
 

Bump, any help would be appreciated!
My System SpecsSystem Spec
07 Jan 2015   #3
ubersyd

Windows 7 Home Premium 64bit
 
 

Bump
My System SpecsSystem Spec
.

07 Jan 2015   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Code:
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
---------
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
My System SpecsSystem Spec
Reply

 BSOD possibly associated with gaming




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD with Gigabyte G1 Gaming GTX970 in SLI while gaming
Hi guys, This is my first post in this forum since I have not received any help from elswhere. You guys are my only hope. Okay, so I recently bought two G1 Gaming GTX970 graphics cards. The first driver install went bad by windows using its own drivers, so I got the Display Driver...
BSOD Help and Support
BSOD (possibly Chrome and IE)
My client is having a problem with BSOD running WIN7 Home Premium - BSOD appears to happen when they access Chrome and IE - I have run the SF Diag tool and included the zip file :) Thanks in advance for your help !
BSOD Help and Support
BSOD - possibly from overheating
Hello all, My desktop has recently been throwing out BSOD. Once it happens, any attempt to reboot or restart will end up with another BSOD, all of which have different messages (DRIVER IRQ NOT EQUAL, PAGE FAULT, etc). I suspect it may be due to overheating but I can't be sure - the desktop...
BSOD Help and Support
BSOD Occurring Randomly while gaming and when i am not gaming???
I dont know why. I recently bought a new computer and it has been doing this since i first got it. I dont know why but hopefully you can help me. :D My Computer Stats: -Intel® Core™ i7-3770K -GIGABYTE GA-Z77X-UD3H Z77 - NVIDIA GeForce GTX 660 Ti 2GB -Corsair Vengeance 8GB -2TB Hard Drive...
BSOD Help and Support
BSOD Possibly because of SLI / OpenGL
System Specs: Cpu: i7 970 Motherboard: Rampage III Extreme Ram: OCZ Flex Extreme 12 GB Tripple Channel kit @ 2133 Video: 2x Nvidia HD superclocked 570s in SLI Hard Drive(s): 3x Ocz vertex 2 in raid 0, (superfetch, prefetch, indexing, defragmentation disabled) Western Digital Caviar Black 2tb...
BSOD Help and Support
BSOD, possibly memory?
Long story short, i've been getting BSOD's for a while and originally thought it was down to a dodgy stick of ram (Ballistix PC2-5300 BL2KIT12864AA663.8FE4) which didn't like running at the correct timings (3-3-3-12 @ 2.1/2.2v). Pulled this and the system seemed to be ok. But recently i've been...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 00:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App