BSOD mostly in games

Welcome!

Try updating your video card drivers first. Go to Device Manager, right-click on your card, and select Update Driver Software.

You can also try a memory test yourself. Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\030310-15584-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`03052e50
Debug session time: Wed Mar  3 05:11:57.583 2010 (GMT-5)
System Uptime: 0 days 2:38:56.300
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f8c3a8 -- (.exr 0xfffff88002f8c3a8)
ExceptionAddress: fffff80002e92389 (nt!KiProcessExpiredTimerList+0x0000000000000129)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f8c450 -- (.trap 0xfffff88002f8c450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80092bf6a8 rbx=0000000000000000 rcx=f7fffa80092bf6a8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e92389 rsp=fffff88002f8c5e0 rbp=fffffa80071c0168
 r8=fffff88002f66301  r9=0000000000000002 r10=00000000000000e1
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`02e92389 48894108        mov     qword ptr [rcx+8],rax ds:f7fffa80`092bf6b0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7ec2e to fffff80002e86ed0

STACK_TEXT:  
fffff880`02f8b488 fffff800`02e7ec2e : 00000000`0000000b fffff800`02e95494 fffff880`02f8bc00 fffff800`02eb3e28 : nt!KeBugCheck
fffff880`02f8b490 fffff800`02eacbed : fffff800`03093c24 fffff800`02fcca3c fffff800`02e15000 fffff880`02f8c3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8b4c0 fffff800`02eb4250 : fffff800`02fd4b5c fffff880`02f8b538 fffff880`02f8c3a8 fffff800`02e15000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8b4f0 fffff800`02ec11b5 : fffff880`02f8c3a8 fffff880`02f8bc00 fffff880`00000000 fffffa80`092bf6a0 : nt!RtlDispatchException+0x410
fffff880`02f8bbd0 fffff800`02e86542 : fffff880`02f8c3a8 fffffa80`071c0168 fffff880`02f8c450 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02f8c270 fffff800`02e84e4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f8c450 fffff800`02e92389 : fffffa80`071c0120 fffffa80`096b5168 fffffa80`096b5168 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8c5e0 fffff800`02e92e7e : 00000016`3413f251 fffff880`02f8cc58 00000000`000953e1 fffff880`02f681a8 : nt!KiProcessExpiredTimerList+0x129
fffff880`02f8cc30 fffff800`02e92697 : 00000006`f8701fc1 00000006`000953e1 00000006`f8701f61 00000000`000000e1 : nt!KiTimerExpiration+0x1be
fffff880`02f8ccd0 fffff800`02e8f6fa : fffff880`02f64180 fffff880`02f6efc0 00000000`00000000 fffff880`04032588 : nt!KiRetireDpcList+0x277
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e7ec2e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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