Been getting repetitive BSODS lately Battlefield 3

I have had 8 BSODs this past week all while playing Battlefield 3. I am using OEM Windows 7 Home Premium 64bit freshly installed a few weeks ago, after getting a second 6950 for crossfire. All of my drivers are up to date as far as I know. I have attached the necessary files, as well as a BlueScreenView report.

Um, no they arent.

Related to RTCore64.sys MSI Afterburner from Micro-Star Int'l Co. Ltd. A huge cause of BSOD's. Yours is from 2005. If you dont need it remove it, if you do update it.

Thanks, I updated to MSI Afterburner Beta and it has an updated RTCore64.sys. I have however had a few more BSODs since. Any idea what these are from? On the most recent one, right after the bsod, windows got stuck at the welcome screen, so I had to manually reboot. Then the bios info showed my primary boot drive with (s.m.a.r.t. ERROR), when normally it is (s.m.a.r.t. OK). It failed to find the boot device so I powered down again and powered of the PSU for a few seconds and then it booted up fine. I should also mentioned that I am now using three dell u2412m monitors. I had to swap my two 6950s in their slots to use the FleX edition as the primary one (to use three monitors all connected by dvi).

Attached the files including a BlueScreenView report in the zip this time.

Problem Devices:

Code:

AODDriver4.1	ROOT\LEGACY_AODDRIVER4.1\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Security Software (this is just to check that it is installed and working properly; nothing needs to be done with this information at this time):

Code:

mbamservice.exe	c:\program files (x86)\malwarebytes' anti-malware\mbamservice.exe	4888	8	200	1380	12/04/2012 15:23	Not Available	Not Available	Not Available
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	828	8	200	1380	12/04/2012 15:20	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 17:21
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2496	8	200	1380	12/04/2012 15:21	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 17:21
msseces.exe	c:\program files\microsoft security client\msseces.exe	2380	8	200	1380	12/04/2012 15:21	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 14:35

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\alduin\Windows_NT6_BSOD_jcgriff2\041212-8533-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`0309c650
Debug session time: Thu Apr 12 13:05:46.987 2012 (UTC - 6:00)
System Uptime: 0 days 17:15:43.205
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {a4e6, 2, 1, fffff80002edfde2}

Probably caused by : hardware ( win32k!NtUserGetThreadState+1e )

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

5: 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: 000000000000a4e6, 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: fffff80002edfde2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003106100
 000000000000a4e6 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+122
fffff800`02edfde2 00418b          add     byte ptr [rcx-75h],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Steam.exe

TRAP_FRAME:  fffff8800e9eb7c0 -- (.trap 0xfffff8800e9eb7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800308bca8 rbx=0000000000000000 rcx=000000000000a55b
rdx=fffffa800edc0890 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002edfde2 rsp=fffff8800e9eb950 rbp=fffffa800edc0890
 r8=fffffa800dad6390  r9=00000000000000b9 r10=fffff88003088180
r11=fffff88003088100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         ov up ei pl nz na pe cy
nt!KiInsertTimerTable+0x122:
fffff800`02edfde2 00418b          add     byte ptr [rcx-75h],al ds:0001:00000000`0000a4e6=??
Resetting default scope

MISALIGNED_IP: 
nt!KiInsertTimerTable+122
fffff800`02edfde2 00418b          add     byte ptr [rcx-75h],al

LAST_CONTROL_TRANSFER:  from fffff80002ed4229 to fffff80002ed4c80

STACK_TEXT:  
fffff880`0e9eb678 fffff800`02ed4229 : 00000000`0000000a 00000000`0000a4e6 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0e9eb680 fffff800`02ed2ea0 : 00000000`00000000 fffffa80`0dad62b0 fffffa80`0ae5ca90 fffffa80`0dad6370 : nt!KiBugCheckDispatch+0x69
fffff880`0e9eb7c0 fffff800`02edfde2 : 00000000`00000000 00000000`00000000 fffffa80`0c513570 fffff800`02ed7b7a : nt!KiPageFault+0x260
fffff880`0e9eb950 fffff800`02eca822 : fffffa80`0dad62b0 00000000`00000000 00000000`00000000 00000000`00000005 : nt!KiInsertTimerTable+0x122
fffff880`0e9eb9b0 fffff800`02edba9f : fffff900`c0953330 fffff960`001a6c63 fffff800`000000b9 00000000`00000000 : nt!KiCommitThreadWait+0x332
fffff880`0e9eba40 fffff800`02eb4c3e : fffffa80`0a924400 00000000`0000001b 00000000`0309dc00 fffff880`03088100 : nt!KeWaitForSingleObject+0x19f
fffff880`0e9ebae0 fffff800`02edae61 : ffffffff`ffb3b4c0 fffffa80`0af2c820 fffffa80`0a924440 00000000`7efdb000 : nt!ExpWaitForResource+0xae
fffff880`0e9ebb50 fffff800`02eddc13 : 00000000`0008fd20 fffffa80`0dad62b0 fffff880`0e9ebca0 00000000`00000000 : nt!ExAcquireResourceSharedLite+0x2c6
fffff880`0e9ebbc0 fffff960`0013698e : 00000000`00000000 fffff900`c0800b90 fffff900`c26bd010 00000000`00000000 : nt!ExEnterPriorityRegionAndAcquireResourceShared+0x23
fffff880`0e9ebbf0 fffff800`02ed3f13 : fffffa80`0dad62b0 fffff880`0e9ebca0 fffffa80`0dad62b0 00000000`00001398 : win32k!NtUserGetThreadState+0x1e
fffff880`0e9ebc20 00000000`73222e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73222e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!NtUserGetThreadState+1e
fffff960`0013698e 33db            xor     ebx,ebx

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  win32k!NtUserGetThreadState+1e

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
---------

Points to hardware. Since MSI Afterburner interfaces with hardware, this could be a result of the software installed. Is MSI Afterburner necessary for your system to run?


Since you are running off an SSD, a few questions (I had an answer to one and provided the answer in red):

• Is the firmware for the drive up to date?
  
  
• Is your BIOS up to date? No ASUS - Motherboards- ASUS M4A89GTD PRO/USB3
  
  
• Do you have your Chipset drivers up to date?
  
  
• Are your hard disk controller drivers up to date?

SSDs are new technology, so a negative answer to any of the above questions can mean the hardware will not coexist in your system in a stable manner.

Controller drivers are generally in the Motherboard Support site: ASUS - Motherboards- ASUS M4A89GTD PRO/USB3 -> Download -> OS: Windows 7 64bit -> SATA

Unfortunately, it appears yours are not included... To determine which you have, post a screenshot of your device manager under IDE ATA/ATAPI Controllers by expanding this set of devices.

To reach device manager: Start Menu -> Right click Computer -> Manage -> Device Manager from the list on the left
Alternatively: Start Menu -> Control Panel -> Hardware and Sound -> Device Manager