Gaming BSOD

[Impulse Fire911]

Win 7 info:
- 64 bit
- Windows 7 ultimate
- Retail
- about 2 years
- About 1.5 years, no reinstallation
Ok so here is the problem, my computer bluescreens when playing a game such as crysis or even counterstrike source for no reason. This doesnt happed during normal everyday use can someone point me out in the right direction?
File is included

 

[zigzag3143]

Win 7 info:
- 64 bit
- Windows 7 ultimate
- Retail
- about 2 years
- About 1.5 years, no reinstallation
Ok so here is the problem, my computer bluescreens when playing a game such as crysis or even counterstrike source for no reason. This doesnt happed during normal everyday use can someone point me out in the right direction?
File is included

You have about 8 different causes all pointing to hardware. Read here what it means and what to try.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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 - http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html




Also you have some ancient driver that in themselves can cause crashes. Obviously from way before win 7

lirsgt.sys    3/6/2004 03:53:01 PM    fffff880`06cde000    fffff880`06ceb000    0x0000d000    0x404a2c1d                            
RTCore64.sys    5/25/2005 02:39:12 AM    fffff880`0718d000    fffff880`07193000    0x00006000    0x42941d90                                                   
pcouffin.sys    12/5/2006 10:39:30 AM    fffff880`043ca000    fffff880`043de380    0x00014380    0x457584a2                            
atksgt.sys    10/20/2008 03:50:38 AM    fffff880`06c7d000    fffff880`06ccc000    0x0004f000    0x48fc384e

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\032611-36296-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0340a000 PsLoadedModuleList = 0xfffff800`03647e50
Debug session time: Sat Mar 26 21:50:06.151 2011 (GMT-4)
System Uptime: 0 days 1:50:25.557
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffff85, 2, 1, fffff80003480967}

Probably caused by : hardware ( nt!KiDeferredReadyThread+287 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffff85, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003480967, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b20e0
 ffffffffffffff85 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeferredReadyThread+287
fffff800`03480967 004885          add     byte ptr [rax-7Bh],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Crysis2.exe

TRAP_FRAME:  fffff88002f22600 -- (.trap 0xfffff88002f22600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000004
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003480967 rsp=fffff88002f22790 rbp=0000000000000002
 r8=0000000000000004  r9=0000000000000002 r10=fffff8000340a000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiDeferredReadyThread+0x287:
fffff800`03480967 004885          add     byte ptr [rax-7Bh],cl ds:4480:ffffffff`ffffff85=??
Resetting default scope

MISALIGNED_IP: 
nt!KiDeferredReadyThread+287
fffff800`03480967 004885          add     byte ptr [rax-7Bh],cl

LAST_CONTROL_TRANSFER:  from fffff8000347b469 to fffff8000347bf00

STACK_TEXT:  
fffff880`02f224b8 fffff800`0347b469 : 00000000`0000000a ffffffff`ffffff85 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f224c0 fffff800`0347a0e0 : 00000000`00000000 fffff880`02f63180 fffffa80`07f9f190 fffff800`035ae4d3 : nt!KiBugCheckDispatch+0x69
fffff880`02f22600 fffff800`03480967 : fffff880`02f63180 fffffa80`06208ac0 00000000`00000000 fffffa80`05210060 : nt!KiPageFault+0x260
fffff880`02f22790 fffff800`034873b7 : fffffa80`06eb4c20 fffffa80`06eb4c68 fffffa80`06eb4c68 00000000`00000000 : nt!KiDeferredReadyThread+0x287
fffff880`02f22810 fffff800`03487e7e : 0000000f`6d23dc6b fffff880`02f22e88 00000000`00067863 fffff880`009ed1e8 : nt!KiProcessExpiredTimerList+0x157
fffff880`02f22e60 fffff800`03487697 : fffffa80`056359c1 fffffa80`00067863 00000000`00000000 00000000`00000063 : nt!KiTimerExpiration+0x1be
fffff880`02f22f00 fffff800`03482065 : 00000000`0000a000 fffffa80`04e21520 00000000`00000000 fffff880`01661c50 : nt!KiRetireDpcList+0x277
fffff880`02f22fb0 fffff800`03481e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`091edbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDeferredReadyThread+287
fffff800`03480967 004885          add     byte ptr [rax-7Bh],cl

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiDeferredReadyThread+287

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

 

[DeanP]

lirsgt.sys & atksgt.sys,
Please remove Tages Software as they are a known cause of BSOD on some Windows 7 Systems.

RTCore64.sys,
Remove RivaTuner/EVGA Precision/MSI Afterburner as they are a known cause of BSOD with Windows 7

Pcouffin.sys,
Update ALL CD/DVD Programs

 

[Impulse Fire911]

thanks a lot for the help guyse i will try these