BSOD when loading SWTOR 0x50

FIXED!!!!! Turns out it was the displaylink driver. Supposedly version 6.3-7.0 don't work with SWTOR. Removed the driver and loaded version 6.0 and it worked.


Hey guys, I recently installed a new SSD into my rig (Crucial M4 120GB). Reinstalled windows 7 Ultimate 64bit and updated all the drivers. Everything seems to run great except for when I click the play button on my SWTOR screen, the computer crashes a couple seconds after I click the button and goes to a blue screen. A split second before it crashes, the screen gets distorted, then the blue screen appears. I have rolled back my display driver and it didnt solve the problem, I then updated it to the latest driver and it also didnt help. I have uninstalled and reinstalled the game about 5 times but again, that didnt help. I can play BF3 on Ultra settings with no problem at all and the computer only crashes right after I try to play SWTOR. Any ideas on how I can fix this problem? Im leaning towards a bad driver but im not sure on how to figure out which one is bad.

Here are the specs of my rig:

CPU: Intel i7 950 (stock clock 3.1ghz)
Motherboard: Asus Rampage 3 Extreme
Graphics: Sapphire HD6970 (stock clock)
RAM: Corsair Dominator 2000mhz 8GB (4 sticks @ 2GB each)
HD: Crucial M4 SSD 120GB
OS: Windows 7 Ultimate 64bit

I will upload the zip file from the diagnostic I got from this site and if there is any other info needed please let me know and I will provide it.

Any help would be greatly appreciated. Thanks in advance.

Welcome to SevenForums.

* Is the firmware for your SSD up-to-date

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8008be2010, fffff88008e86fb8, 0, 2}

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

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008be2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88008e86fb8, 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: 
atikmpag+6fb8
fffff880`08e86fb8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`027569c8 fffff880`0633b000 : 00000000`00000116 fffffa80`08be2010 fffff880`08e86fb8 00000000`00000000 : nt!KeBugCheckEx
fffff880`027569d0 fffff880`0633ad0a : fffff880`08e86fb8 fffffa80`08be2010 fffffa80`06ebc010 fffffa80`076dc410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02756a10 fffff880`04bb4f07 : fffffa80`08be2010 00000000`00000000 fffffa80`06ebc010 fffffa80`076dc410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02756a40 fffff880`04bdeb75 : 00000000`ffffffff 00000000`000103eb 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02756b20 fffff880`04bdd2bb : 00000000`00000102 00000000`00000000 00000000`000103eb 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02756b50 fffff880`04bb02c6 : ffffffff`ff676980 fffffa80`076dc410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02756bf0 fffff880`04bdce7a : 00000000`00000000 fffffa80`06ebc010 00000000`00000080 fffffa80`076dc410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02756d00 fffff800`03170e5a : fffffa80`07586c60 fffffa80`0738db50 fffffa80`06caab30 fffffa80`0c3ff900 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02756d40 fffff800`02ecad26 : fffff880`03164180 fffffa80`0738db50 fffff880`0316f0c0 fffff880`021884a0 : nt!PspSystemThreadStartup+0x5a
fffff880`02756d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6fb8
fffff880`08e86fb8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6fb8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce4f72e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

0: kd> lmvm atikmpag
start             end                 module name
fffff880`08e80000 fffff880`08ecb000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu Nov 18 15:51:42 2010 (4CE4F72E)
    CheckSum:         00050806
    ImageSize:        0004B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get the latest drivers for your video card.

METHOD:

Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATI and reboot the system. Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper

Link: AMD Driver Autodetect

* More information on: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

You're also having a BCC 124. Go through this thread step by step: Stop 0x124 - what it means and what to try

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008160028, fa000000, 400405}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008160028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0338eb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner

Reinstall this driver: dlkmd.sys (Same way you did for the video drivers)

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffdb814c, 0, fffff80002f00b38, 0}

*** WARNING: Unable to verify timestamp for dlkmd.sys
*** ERROR: Module load completed but symbols could not be loaded for dlkmd.sys

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

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: ffffffffffdb814c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002f00b38, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003114100
GetUlongFromAddress: unable to read from fffff800031141c0
 ffffffffffdb814c 

FAULTING_IP: 
nt!MmProbeAndLockPages+118
fffff800`02f00b38 410fb601        movzx   eax,byte ptr [r9]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  1

TRAP_FRAME:  fffff8800b8b5550 -- (.trap 0xfffff8800b8b5550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000009 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f00b38 rsp=fffff8800b8b56e0 rbp=fffff880062f1110
 r8=fffffa8007909ea0  r9=ffffffffffdb814c r10=0000000000000008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po nc
nt!MmProbeAndLockPages+0x118:
fffff800`02f00b38 410fb601        movzx   eax,byte ptr [r9] ds:ffffffff`ffdb814c=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8ceec to fffff80002ee4fc0

STACK_TEXT:  
fffff880`0b8b53e8 fffff800`02e8ceec : 00000000`00000050 ffffffff`ffdb814c 00000000`00000000 fffff880`0b8b5550 : nt!KeBugCheckEx
fffff880`0b8b53f0 fffff800`02ee30ee : 00000000`00000000 ffffffff`ffdb814c 00000000`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4514f
fffff880`0b8b5550 fffff800`02f00b38 : fffffa80`0c0be2e0 fffff800`02ef5d5c 00000000`00000000 fffff800`02efb08f : nt!KiPageFault+0x16e
fffff880`0b8b56e0 fffff880`062d620d : fffffa80`07909e70 00000000`00000200 00000000`00000002 ffffffff`ffdb814c : nt!MmProbeAndLockPages+0x118
fffff880`0b8b57f0 fffffa80`07909e70 : 00000000`00000200 00000000`00000002 ffffffff`ffdb814c 00000000`00000000 : dlkmd+0x3c20d
fffff880`0b8b57f8 00000000`00000200 : 00000000`00000002 ffffffff`ffdb814c 00000000`00000000 00000000`00000000 : 0xfffffa80`07909e70
fffff880`0b8b5800 00000000`00000002 : ffffffff`ffdb814c 00000000`00000000 00000000`00000000 fffffa80`08d22790 : 0x200
fffff880`0b8b5808 ffffffff`ffdb814c : 00000000`00000000 00000000`00000000 fffffa80`08d22790 fffff880`062d2306 : 0x2
fffff880`0b8b5810 00000000`00000000 : 00000000`00000000 fffffa80`08d22790 fffff880`062d2306 fffff880`062f3810 : 0xffffffff`ffdb814c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dlkmd+3c20d
fffff880`062d620d ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dlkmd+3c20d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dlkmd

IMAGE_NAME:  dlkmd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50ab3e70

FAILURE_BUCKET_ID:  X64_0x50_dlkmd+3c20d

BUCKET_ID:  X64_0x50_dlkmd+3c20d

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

4: kd> lmvm dlkmd
start             end                 module name
fffff880`0629a000 fffff880`0631e000   dlkmd    T (no symbols)           
    Loaded symbol image file: dlkmd.sys
    Image path: dlkmd.sys
    Image name: dlkmd.sys
    Timestamp:        Tue Nov 20 14:25:20 2012 (50AB3E70)
    CheckSum:         0006BA7F
    ImageSize:        00084000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Perform a System File Check:

• Click on the start
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

Reduce items at start-up. Nothing except anti-virus is required:

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Post back your results.

Hmm & you're welcome :)

Have you gone through the 116 & 124 troubleshooting links?

Okay :)

Enjoy your game, take your time & go through those threads later.

Post if there are any BSOD-s.

Good luck :)

How are things going?
Were you able to resolve the crashes?

What about the game?

:)

You're welcome & glad to help. :)

   Tip

• If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner