BSOD playing SWTOR: Error 0x5

[drkknight32]

Hey guys,

I recently made my first computer build and it was working fine for a few days, but now I'm beginning to see some lovely Blue Screens. I've got a long log of the blue screens and I've tried the typical checks for problems, but I just can't figure anything out. The computers new and I don't have much installed on it, but I've never experienced a crash outside of a game.


If anyone could help me out I'd really appreciate it, here are my system specs.:

Processor: Intel i7 3960x
Motherboard: ASRock Extreme 9 X79 chipset
RAM: Corsair Vengeance 1600 Mhz
Graphics: 2 x Radeon 7970's
OS: Windows 7 Ultimate - 64 Bit



I apologize if I didn't put something I needed to put. Any help would be appreciated.

 

[writhziden]

Holy blue screen Batman.

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\drkknight32\011912-25615-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`0309d670
Debug session time: Thu Jan 19 18:36:13.897 2012 (UTC - 7:00)
System Uptime: 0 days 1:06:13.756
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0107c059c, 1, fffff8800d0483f7, 0}

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

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+3b33f7 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0107c059c, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800d0483f7, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003107100
 fffff8a0107c059c 

FAULTING_IP: 
atikmdag+3b33f7
fffff880`0d0483f7 87422c          xchg    eax,dword ptr [rdx+2Ch]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ed4b1a0 -- (.trap 0xfffff8800ed4b1a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8a010801b38
rdx=fffff8a0107c0570 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800d0483f7 rsp=fffff8800ed4b330 rbp=fffff8a0108019e8
 r8=0000000000000003  r9=fffffffffbd11060 r10=fffffa800d449740
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
atikmdag+0x3b33f7:
fffff880`0d0483f7 87422c          xchg    eax,dword ptr [rdx+2Ch] ds:2350:fffff8a0`107c059c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e809fc to fffff80002ed4c40

STACK_TEXT:  
fffff880`0ed4b038 fffff800`02e809fc : 00000000`00000050 fffff8a0`107c059c 00000000`00000001 fffff880`0ed4b1a0 : nt!KeBugCheckEx
fffff880`0ed4b040 fffff800`02ed2d6e : 00000000`00000001 fffff8a0`107c059c 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0ed4b1a0 fffff880`0d0483f7 : fffff8a0`10801a28 ffffffff`fbd11060 fffff8a0`10801a18 00000000`71690000 : nt!KiPageFault+0x16e
fffff880`0ed4b330 fffff8a0`10801a28 : ffffffff`fbd11060 fffff8a0`10801a18 00000000`71690000 fffff880`6d4d6901 : atikmdag+0x3b33f7
fffff880`0ed4b338 ffffffff`fbd11060 : fffff8a0`10801a18 00000000`71690000 fffff880`6d4d6901 00000000`00000000 : 0xfffff8a0`10801a28
fffff880`0ed4b340 fffff8a0`10801a18 : 00000000`71690000 fffff880`6d4d6901 00000000`00000000 fffff8a0`1073c600 : 0xffffffff`fbd11060
fffff880`0ed4b348 00000000`71690000 : fffff880`6d4d6901 00000000`00000000 fffff8a0`1073c600 fffff880`0cc37a00 : 0xfffff8a0`10801a18
fffff880`0ed4b350 fffff880`6d4d6901 : 00000000`00000000 fffff8a0`1073c600 fffff880`0cc37a00 ffffffff`fbd11060 : 0x71690000
fffff880`0ed4b358 00000000`00000000 : fffff8a0`1073c600 fffff880`0cc37a00 ffffffff`fbd11060 00000000`00000000 : 0xfffff880`6d4d6901


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+3b33f7
fffff880`0d0483f7 87422c          xchg    eax,dword ptr [rdx+2Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+3b33f7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f05127f

FAILURE_BUCKET_ID:  X64_0x50_atikmdag+3b33f7

BUCKET_ID:  X64_0x50_atikmdag+3b33f7

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

If you are overclocking anything, please stop.

All point toward your graphics driver(s). It appears the driver(s) is/are up to date. Are you running Catalyst Control Center/AMD Vision Engine Control Center (CCC.exe)? If so, uninstall all AMD software and drivers (Start Menu -> Control Panel -> Uninstall a program -> Uninstall AMD Install Manager) and then install just the latest drivers for your display card (do not install CCC).

If you do not have CCC.exe installed, re-install your display card drivers as follows.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

If you continue to have problems, post back and we will proceed with further steps.

 

[drkknight32]

Sorry it took so long for me to respond back. Just finished unpacking things at a new apartment. Anyways, I've got the BSOD fixed for the most part. I think the problem ended up being with my second card and/or crossfire support from AMD.

Basically, I can run the computer just fine if I disable crossfire and have done so for at least a week. I'm going to try and run the second card by itself to see if I get the same problem, but I'm probably just going to end up returning it.

 

[writhziden]

Good troubleshooting. Crossfire and SLI bridges have caused issues for a few users resulting in crashes. Too many parts that can go wrong, I imagine. Probably a good idea to determine one card at a time and then return if you cannot get them working jointly. Best of luck!

 

[flirno]

Sorry it took so long for me to respond back. Just finished unpacking things at a new apartment. Anyways, I've got the BSOD fixed for the most part. I think the problem ended up being with my second card and/or crossfire support from AMD.

Basically, I can run the computer just fine if I disable crossfire and have done so for at least a week. I'm going to try and run the second card by itself to see if I get the same problem, but I'm probably just going to end up returning it.

I had similar issues on a new system and the problem turned out to be the overlocking used to get to 1600 on the RAM. I notice you are using 1600 RAM also which if you are using XMP settings it is technically an Overclock which is not going to work well with SWTOR when the load spikes up.