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 while playing games


14 Nov 2012   #1

Windows 7 Pro 64
 
 
BSOD while playing games

I usually get BSOD while playing games, but sometimes when I get to my computer after being away for a while I notice that it has rebooted (since it is at the login screen). The only times it reboots on its own is when It BSOD on me other than that i leave it on and only turn it off when i will be gone for days.

My System SpecsSystem Spec
.

14 Nov 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome to SevenForums.

It's a hardware bug check. Go through this guide -> Stop 0x124 - what it means and what to try step by step and let us know your findings.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa801066c8f8, 0, 0}

Probably caused by : AuthenticAMD

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

2: 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: fffffa801066c8f8, 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_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031bd6f0 fffff800`032d1ca9 : fffffa80`1066c8d0 fffffa80`0fadab50 00000000`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`031b2547 : fffffa80`1066c8d0 fffff800`0322c2d8 fffffa80`0fadab50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`03119945 : fffff800`0328dae0 00000000`00000001 fffffa80`10650b10 fffffa80`0fadab50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`03098841 : fffff880`010dee00 fffff800`03119920 fffffa80`0fadab00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`03325e6a : 280a0000`736f0306 fffffa80`0fadab50 00000000`00000080 fffffa80`0fac9040 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`0307fec6 : fffff880`02f64180 fffffa80`0fadab50 fffff880`02f6efc0 00005628`02060000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bcee0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

2: kd> !sysinfo
!sysinfo [ cpuinfo | cpumicrocode | cpuspeed | gbl | machineid | registers | smbios ] [-csv | -noheaders]
2: kd> !sysinfo cpuspeed
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
2: kd> !errrec fffffa801066c8f8
===============================================================================
Common Platform Error Record @ fffffa801066c8f8
-------------------------------------------------------------------------------
Record Id     : 01cd99c5a4d166eb
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/23/2012 19:57:24 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100f52
Processor ID  : 0x0000000000000002

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

Local APIC Id : 0x0000000000000002
CPU Id        : 52 0f 10 00 00 08 04 02 - 09 20 80 00 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  @ fffffa801066cb10

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

Error         : DCACHEL1_DRD_ERR (Proc 2 Bank 0)
  Status      : 0xb669c00000000135
  Address     : 0x00000004b9644c80
  Misc.       : 0x0000000000000000
Uninstall Daemon Tools, it's a known cause of BSOD-s.
My System SpecsSystem Spec
17 Nov 2012   #3

Windows 7 Pro 64
 
 

So far i have updated everything and pointed a fan in my case. Now instead of BSOD the programs just crash. Now i guess i will contiue with the rest of the steps and do the mem tests
My System SpecsSystem Spec
.


18 Nov 2012   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Keep us posted. Good luck.
My System SpecsSystem Spec
18 Nov 2012   #5

Windows 7 Pro 64
 
 

Ok, I remeber i hjad this problem last spring too and i thought i fixed it with a driver update but apparently it didnt work. When i was having the problem before i was told to do all this:

Start with Stop 0x124 - what it means and what to try and use the following to supplement the steps in that link:
  • Monitor temperatures during the following tests.
    Use the following programs to monitor the temperatures.
  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.
When i run Prime95 my comuter BSOD almost right after it starts. I tried seeing what the temp gets to but it crashes to quick for me to get a good reading. I did see that the CPU got to 67c
My System SpecsSystem Spec
19 Nov 2012   #6

Windows 7 Pro 64
 
 

Ok ran all the memory test and all is good. I guess all i can do is reinstall Windows which is what i have been trying to avoid. I still cant get the Prime95 to run without crashing.
My System SpecsSystem Spec
19 Nov 2012   #7

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

I'm afraid no amount of reinstalling Windows is gonna help you here, mate. Koolkat is pretty accurate in that this is a hardware-based BSOD triggered by a hardware fault, and the output she displayed makes it evident we're dealing with a bad CPU. The Prime95 crashing also testifies to this.

Now, I do know that motherboard software loves to cause these errors despite being software and not hardware, so you'll want to uninstall any software that came with your motherboard. Only keep device drivers that come with your motherboard that actually are required to make things function properly, like audio and network drivers. Also, go ahead and update them as well, including your BIOS.

If none of those works, it's time to consider using your warranties if they're available and replace hardware, starting with the CPU, then follow up with the motherboard and then power supply. I personally however think it's a bad CPU. If you don't have the thing overclocked, and you can confirm the temperatures on it are good when running Prime95 or some other heavy operations, then it's time for a replacement.
My System SpecsSystem Spec
20 Nov 2012   #8

Windows 7 Pro 64
 
 

HMMM I took this comp to a shop 2 years ago for a problem like this and they told me that my new BFG 650w power supply was bad and they installed a Thermaltake 430w. I wonder if i have a bad CPU and they just diagnosed it as a power supply? I was also told that a bad CPU wouldnt BSOD or lock up a computer, but with my limited knowledge I have to scream Bull Shit to that.
My System SpecsSystem Spec
26 Nov 2012   #9

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

Happy Thanksgiving, mate! And you're certainly right, because a bad CPU would most certainly cause both those symptoms!
My System SpecsSystem Spec
Reply

 BSOD while playing games




Thread Tools




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 05:20 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33