BSOD when I play computer game

[woarwizzard]

I get a BSOD usually when I play a computer game, and this is the error code windows gives me 0x00000124 (0x0000000000000000, 0xfffffa8007dbf028, 0x00000000b2000040, 0x0000000000000800).

my windows 7 is 64bit
original intalled os, oem version
system is about 1 year old, same with the OS instillation

The BSODs don't occur outside of the game so it leads me to believe it has something to do with the video card? Just speculation. To be more specific, it seems that these bsod's have been occurring ever since I installed an ati radeon 5850, from a 4870 several months ago. My vid drivers are updated and windows says it doesn't have any other hardware drivers to update.

 

[zigzag3143]

I get a BSOD usually when I play a computer game, and this is the error code windows gives me 0x00000124 (0x0000000000000000, 0xfffffa8007dbf028, 0x00000000b2000040, 0x0000000000000800).

my windows 7 is 64bit
original intalled os, oem version
system is about 1 year old, same with the OS instillation

The BSODs don't occur outside of the game so it leads me to believe it has something to do with the video card? Just speculation. To be more specific, it seems that these bsod's have been occurring ever since I installed an ati radeon 5850, from a 4870 several months ago. My vid drivers are updated and windows says it doesn't have any other hardware drivers to update.

Woarwizzard


These crashes were caused by several things but they all point to hardware. Please use these instructions to find out what that means and to figure out what to try.

http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Thanks


Ken

EDIT: I am reading the DMP files now be back soon.

 

[zigzag3143]

As previously indicated all the crashes were caused by hardware with this exception. The one below was caused by your video driver. I would remove all traces of the current driver (there is a mfr removal tool) before downloading and installing the new one.

Ken


Analysis

ALL OF THE CRASHES EXCEPT FOR THIS ONE WERE CAUSED BY HARDWARE.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\123009-46843-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`0309ae50
Debug session time: Wed Dec 30 19:32:40.667 2009 (GMT-4)
System Uptime: 0 days 0:05:53.058
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8008f68010, fffff88007c47150, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+13150 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008f68010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007c47150, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmdag+13150
fffff880`07c47150 48895c2408      mov     qword ptr [rsp+8],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`08a84988 fffff880`04f51ef8 : 00000000`00000116 fffffa80`08f68010 fffff880`07c47150 00000000`00000000 : nt!KeBugCheckEx
fffff880`08a84990 fffff880`04f51c02 : fffff880`07c47150 fffffa80`08f68010 fffffa80`06f55b80 fffffa80`08517410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`08a849d0 fffff880`0480ff07 : fffffa80`08f68010 00000000`00000000 fffffa80`06f55b80 fffffa80`08517410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`08a84a00 fffff880`04839b75 : 00000000`ffffffff 00000000`00005550 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`08a84ae0 fffff880`048382bb : 00000000`00000102 00000000`00000000 00000000`00005550 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`08a84b10 fffff880`0480b2c6 : ffffffff`ff676980 fffffa80`08517410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`08a84bb0 fffff880`04837e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`075b4148 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`08a84cc0 fffff800`03172166 : fffff880`098ccbd0 fffffa80`09939b60 fffffa80`06d07040 fffff800`02ec6d87 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`08a84d00 fffff800`02ead486 : fffff880`02f64180 fffffa80`09939b60 fffff880`02f6efc0 fffff880`01211a90 : nt!PspSystemThreadStartup+0x5a
fffff880`08a84d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmdag+13150
fffff880`07c47150 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_NAME:  atikmdag+13150

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a960a2a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

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

Old drivers needing update

speedfan.sys        fffff880`015e1000    fffff880`015e8000    0x00007000    0x45168798    9/24/2006 09:26:48                        
RivaTuner64.sys        fffff880`06f8f000    fffff880`06f96000    0x00007000    0x469d14e6    7/17/2007 15:13:42                        
Rt64win7.sys        fffff880`0180b000    fffff880`0183d000    0x00032000    0x49a65b0d    2/26/2009 05:04:13                        
cpuz132_x64.sys        fffff880`06bdb000    fffff880`06be3000    0x00008000    0x49cc0d03    3/26/2009 19:17:23                        
spldr.sys        fffff880`0145a000    fffff880`01462000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`03fea000    fffff880`03ff7000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`00fe4000    fffff880`00fef000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

 

[cluberti]

I haven't broken all of these down, but they all have the same (other than the video card error back in December of '09 thrown in) bus error:

2: kd> !errrec fffffa80085178f8
===============================================================================
Common Platform Error Record @ fffffa80085178f8
-------------------------------------------------------------------------------
Record Id     : 01cae36a66f2fa1f
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/24/2010 4:55:56
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008517978
Section       @ fffffa8008517a50
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         : 0
CPU Version   : 0x000000000001067a
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 7a 06 01 00 00 08 04 00 - fd e3 08 0c ff fb eb bf
                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  @ fffffa8008517b10

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

Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

3: kd> !sysinfo smbios
[SMBIOS Data Tables v2.5]
[DMI Version - 0]
[2.0 Calling Convention - No]
[Table Size - 1337 bytes]

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
  Vendor                        American Megatrends Inc.
  BIOS Version                  P1.60
  BIOS Starting Address Segment f000
  BIOS Release Date             03/27/2009
  BIOS ROM Size                 100000

[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]
  Manufacturer                  ASRock
  Product                       P45XE

3: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3113
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 23 Stepping 10
ProcessorNameString = REG_SZ Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
Update Signature = REG_BINARY 0,0,0,0,7,a,0,0
Update Status = REG_DWORD 6
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD a0700000000

  Processor may be overclocked!
  Expected Frequency: 2830
  Actual Frequency:     3113
  Overclock Ratio:      1.10

It's a BUS interconnect error (specifically a cache miss and timeout gathering data from cache), and it's flag is 0x00 meaning it's a local processor originated request (according to the Intel documentation on the MCA architecture in Intel CPUs). So either it happens because there's some problem with the video card (or bus), or you have a failing CPU under load. I honestly couldn't tell you which, and given you built this system yourself it seems (looks like an ASRock P45XE with an overclocked Q9550 running at 3.1GHz), you might just want to try and remove the overclock to see if things get stable again