BSOD when launching Star Wars: The Old Republic

When I go to press the play button on the splash screen of the game, I get a blue screen that reads:

PAGEFAULT_IN_NONPAGED_AREA

I've tried reinstalling, but that didn't work. When I re-installed, I didn't remove everything. I ran the system file checker as suggested by someone over at Yahoo! Answers, that didn't work either. So now I'm turning to you guys. I don't want to completely re-install without at least trying to troubleshoot first. The game takes awhile to re-download.

here's the zip folder:
Attachment 248992

Not the best security software. Please uninstall for troubleshooting purpose:

Code:

Start Menu\Programs\Avira    Public:Start Menu\Programs\Avira    Public
Start Menu\Programs\Avira\Avira Desktop    Public:Start Menu\Programs\Avira\Avira Desktop    Public
Start Menu\Programs\Spybot - Search & Destroy    Public:Start Menu\Programs\Spybot - Search & Destroy    Public

Removal Tools:

Avira AntiVir Removal Tool - Download
Removing Spybot - Safer-Networking Forums

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    
    • Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

System Optimisers

Please remove the following software:

Code:

Advanced SystemCare 5    "c:\program files (x86)\iobit\advanced systemcare 5\asctray.exe" /autostart    user-PC\user    HKU\S-1-5-21-1524752268-1942279602-8085283-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner - PC Optimization and Cleaning - Free Download but make sure you back up the registry before making letting ccleaner delete anything.


Perform a System File Check:

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

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

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

Install all updates including Service Pack 1:

Code:

Version    6.1.7600 Build 7600

• Learn how to install Windows 7 Service Pack 1 (SP1)

Update your NVIDIA drivers:

Code:

Driver    c:\windows\system32\drivers\nvlddmkm.sys (8.17.12.6724, 12.36 MB (12,962,792 bytes), 2/23/2011 7:28 AM)

METHOD:

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

Drivers - Clean Left over Files after Uninstalling

Link for download: NVIDIA Driver Downloads - Automatically Detect NVIDIA Products

Go to this link: Intel® Driver Update Utility. Check the system for latest updates. Download and install them one by one.

Coming to what caused the BSOD:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 50, {ffffffffffd9e08c, 0, fffff80003095db0, 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+3a9ed )
 
Followup: MachineOwner
---------
 
2: 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: ffffffffffd9e08c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003095db0, 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 fffff800032ad0e0
GetUlongFromAddress: unable to read from fffff800032ad198
ffffffffffd9e08c 
 
FAULTING_IP: 
nt!MmProbeAndLockPages+130
fffff800`03095db0 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:  fffff88008e48510 -- (.trap 0xfffff88008e48510)
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=fffff80003095db0 rsp=fffff88008e486a0 rbp=fffff88010912110
r8=fffffa800931de10  r9=ffffffffffd9e08c r10=0000000000000008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po nc
nt!MmProbeAndLockPages+0x130:
fffff800`03095db0 410fb601        movzx   eax,byte ptr [r9] ds:ffffffff`ffd9e08c=??
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff800030f5a74 to fffff80003076040
 
STACK_TEXT:  
fffff880`08e483a8 fffff800`030f5a74 : 00000000`00000050 ffffffff`ffd9e08c 00000000`00000000 fffff880`08e48510 : nt!KeBugCheckEx
fffff880`08e483b0 fffff800`0307412e : 00000000`00000000 ffffffff`ffffffff fffff8a0`112e3000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x422b7
fffff880`08e48510 fffff800`03095db0 : 00000000`00000000 00000000`00000000 fffffa80`07b7ce60 fffff800`030853ec : nt!KiPageFault+0x16e
fffff880`08e486a0 fffff880`109039ed : fffffa80`0931dde0 00000000`00000200 00000000`00000002 ffffffff`ffd9e08c : nt!MmProbeAndLockPages+0x130
fffff880`08e487b0 fffffa80`0931dde0 : 00000000`00000200 00000000`00000002 ffffffff`ffd9e08c 00000000`00000000 : dlkmd+0x3a9ed
fffff880`08e487b8 00000000`00000200 : 00000000`00000002 ffffffff`ffd9e08c 00000000`00000000 00000000`00000000 : 0xfffffa80`0931dde0
fffff880`08e487c0 00000000`00000002 : ffffffff`ffd9e08c 00000000`00000000 00000000`00000000 fffffa80`07ff0660 : 0x200
fffff880`08e487c8 ffffffff`ffd9e08c : 00000000`00000000 00000000`00000000 fffffa80`07ff0660 fffff880`108ffa56 : 0x2
fffff880`08e487d0 00000000`00000000 : 00000000`00000000 fffffa80`07ff0660 fffff880`108ffa56 fffff880`10912470 : 0xffffffff`ffd9e08c
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
dlkmd+3a9ed
fffff880`109039ed ??              ???
 
SYMBOL_STACK_INDEX:  4
 
SYMBOL_NAME:  dlkmd+3a9ed
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: dlkmd
 
IMAGE_NAME:  dlkmd.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5016f5c8
 
FAILURE_BUCKET_ID:  X64_0x50_dlkmd+3a9ed
 
BUCKET_ID:  X64_0x50_dlkmd+3a9ed
 
Followup: MachineOwner
---------
 
2: kd> lmvm dlkmd
start             end                 module name
fffff880`108c9000 fffff880`10931000   dlkmd    T (no symbols)           
   Loaded symbol image file: dlkmd.sys
   Image path: \SystemRoot\system32\drivers\dlkmd.sys
   Image name: dlkmd.sys
   Timestamp:        Tue Jul 31 02:59:52 2012 (5016F5C8)
   CheckSum:         0005D6B5
   ImageSize:        00068000
   Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You may refer to this post: https://www.sevenforums.com/crashes-d...ml#post2228188 and follow what's mentioned by the user.

Hope this helps.

Well

Any recent crashes?

Do you mean blue screen?

Does your PC crash on other games?

Intel driver update shouldn't take long.

Upload new dumps.

Nothing new.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffd9e08c, 0, fffff800030f0db0, 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+3a9ed )
Followup: MachineOwner
---------
2: 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: ffffffffffd9e08c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030f0db0, 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 fffff800033080e0
GetUlongFromAddress: unable to read from fffff80003308198
 ffffffffffd9e08c 
FAULTING_IP: 
nt!MmProbeAndLockPages+130
fffff800`030f0db0 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:  fffff8800b5e3510 -- (.trap 0xfffff8800b5e3510)
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=fffff800030f0db0 rsp=fffff8800b5e36a0 rbp=fffff88005322110
 r8=fffffa8006c155f0  r9=ffffffffffd9e08c r10=0000000000000008
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po nc
nt!MmProbeAndLockPages+0x130:
fffff800`030f0db0 410fb601        movzx   eax,byte ptr [r9] ds:ffffffff`ffd9e08c=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80003150a74 to fffff800030d1040
STACK_TEXT:  
fffff880`0b5e33a8 fffff800`03150a74 : 00000000`00000050 ffffffff`ffd9e08c 00000000`00000000 fffff880`0b5e3510 : nt!KeBugCheckEx
fffff880`0b5e33b0 fffff800`030cf12e : 00000000`00000000 ffffffff`ffffffff fffff8a0`1a246000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x422b7
fffff880`0b5e3510 fffff800`030f0db0 : 00000000`00000000 00000000`00000000 fffffa80`08d35090 fffff800`030e03ec : nt!KiPageFault+0x16e
fffff880`0b5e36a0 fffff880`053139ed : fffffa80`06c155c0 00000000`00000200 00000000`00000002 ffffffff`ffd9e08c : nt!MmProbeAndLockPages+0x130
fffff880`0b5e37b0 fffffa80`06c155c0 : 00000000`00000200 00000000`00000002 ffffffff`ffd9e08c 00000000`00000000 : dlkmd+0x3a9ed
fffff880`0b5e37b8 00000000`00000200 : 00000000`00000002 ffffffff`ffd9e08c 00000000`00000000 00000000`00000000 : 0xfffffa80`06c155c0
fffff880`0b5e37c0 00000000`00000002 : ffffffff`ffd9e08c 00000000`00000000 00000000`00000000 fffffa80`08028880 : 0x200
fffff880`0b5e37c8 ffffffff`ffd9e08c : 00000000`00000000 00000000`00000000 fffffa80`08028880 fffff880`0530fa56 : 0x2
fffff880`0b5e37d0 00000000`00000000 : 00000000`00000000 fffffa80`08028880 fffff880`0530fa56 fffff880`05322470 : 0xffffffff`ffd9e08c

STACK_COMMAND:  kb
FOLLOWUP_IP: 
dlkmd+3a9ed
fffff880`053139ed ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  dlkmd+3a9ed
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dlkmd
IMAGE_NAME:  dlkmd.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5016f5c8
FAILURE_BUCKET_ID:  X64_0x50_dlkmd+3a9ed
BUCKET_ID:  X64_0x50_dlkmd+3a9ed
Followup: MachineOwner
---------
2: kd> lmvm dlkmd
start             end                 module name
fffff880`052d9000 fffff880`05341000   dlkmd    T (no symbols)           
    Loaded symbol image file: dlkmd.sys
    Image path: \SystemRoot\system32\drivers\dlkmd.sys
    Image name: dlkmd.sys
    Timestamp:        Tue Jul 31 02:59:52 2012 (5016F5C8)
    CheckSum:         0005D6B5
    ImageSize:        00068000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Anyway, update the thread once you've completed all the steps from my first post.