SWTOR exitting itself

Ok, I just had 3 CTDs in 10 minutes. WTF is happening? I CAN'T PLAY LIKE THIS!

Most of the time a crash to desktop will be do to graphic drivers since this just started after the big graphic patch and repair of the game and a scan of the hard drive showed nothing. I would look at your graphic drivers are up to date i know nvidia just released a graphic driver. The optimization that was down was on the graphic side of swtor They changed alot of the files that were text files to binary so this is were i think your issue is.

@Cuiwe

What are the temps for CPU GPU doing ? use initially http://www.hwinfo.com/

Oh please please, please make it something juicy like a P8400 oc'd to 3.4ghz running a Ti on 300watts

Yeah, I figured that it had something to do with them editting the game code. I completely forgot that they changed from text to binary lol. This is a change I'd NEVER aprove-but then again I am risk averse.

Drivers updated-I'll try installing the latest ATi beta driver-that's as much as I can do. Oh and I can try to reinstall swtor, if that will even accomplish anything is up to anyone's guess.

Here's a full write up of my system:

win7 64bit ultimate

Intel i5 3470 3,2GHz(I think it's set at that frequency, no OC)

8GB RAM

16GB VRAM

ATi HD 7850 2GB, 1,2GHz clock

1680*1050*60Hz resolution

...for some reason I don't think it's on my end. Especially because it crashes at RANDOM locations / times. Hell, yesterday I had it crash during the quick travel lol(I heard it hiccup on my earphones)! The only warning I could find is that virtual storage support(StorLib bus) has "failure using the VxD loader", but I don't think it has anything to do with this. As I said, I didn't have any problems(except crippling lag after 3,0, but that was a common issue) up to this point.

@Cuiwe

Can you post a dxdiag

I found a lot of the newer drivers for that generation of card were less stable then say.. amd_catalyst_13.4_legacy_beta_vista_win7_win8.

To the point that even to this day on Windows 10 with that machine I still use those drivers for my HD7770, granted its nothing flash but it still spits out a pretty dot for swtor.

https://community.amd.com/thread/185041

This may give you some food for thought.

Right, I did two things:

Firstly, I installed the beta driver as I said I would.

Secondly, I changed the AA from "medium" to "high"(I guess from fxaa to msaa).

Result: I had no drop out today. Ok, I had an unfortunate lag spike, but that has absolutely nothing to do with this. Will continue to monitor over the weekend and post accordingly.

---

@Cuiwe wrote:

The only warning I could find is that virtual storage support(StorLib bus) has "failure using the VxD loader"

---

@Cuiwe

1. Go into the Device Manager,

2. click on view, check off "show hidden devices"

3. Scroll down to the item "Virtual File System"

4. Expand this list 

5. Right click on and either disable or uninstall the driver for "StorLib bus (virtual storages support)

@Cuiwe

Can you post a dxdiag ?

Here's a dxdiag link:

http://hastebin.com/ixohuvekop.tex

I am more and more concerned that the signal is breaking up somewhere between me and the actual server. Kinda reminds me of how much I hate "always online" scam. tracert and ping will be next I think.

@Cuiwe

only thing that is an anomaly in the dxdiag is the 2nd monitor what monitor model is this ?

Current Mode: 2560 x 1600 (32 bit) (60Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: SyncMaster
         Monitor Id: SAM03F2
        Native Mode: 1680 x 1050(p) (59.954Hz)

try dropping back to single monitor with the monitor connected by DVI, any change ?

Have you tried searching for dump file to see if any indication ?

Try using http://www.resplendence.com/whocrashed

Meh, WhoCrashed is useless as a free tool. Almost to the "SWTOR free" level useless. I didn't see any dump files created. Because it doesn't really crash. It merely exits itself at its own will. Something is clashing with something elseand its causing instability, I just know it.

The virtual monitor is there because of an HDMI, it won't work the other way-I tried. I've some errors if I don't enable dual monitor. Forgot which because I haven't thought about this for quite some time.

---

@proxos666 wrote:

@Cuiwe

only thing that is an anomaly in the dxdiag is the 2nd monitor what monitor model is this ?

Current Mode: 2560 x 1600 (32 bit) (60Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: SyncMaster
         Monitor Id: SAM03F2
        Native Mode: 1680 x 1050(p) (59.954Hz)

try dropping back to single monitor with the monitor connected by DVI, any change ?

Have you tried searching for dump file to see if any indication ?

Try using http://www.resplendence.com/whocrashed

---

I've finally caught what's happening. Luckily for me, my computer blue screened and I was able to read what was going on:

MEMORY WAS BEING DUMPED

in other words:

MEMORY LEAK.

This is now officialy Bioware problem. When they tried fiddling with the code, they caused my game to have severe problems with memory leaks it seems. Hence it auto exiting itself every time the RAM tried to clear itself(I guess). Very well, it seems that my opponent has showed its face-a very unwise move :D .

@Cuiwe

memory being dumped is what occurs on a blue screen , this is what bluescreen view and what crashed me read to try and ascertain a cause.

If it was a memory leak on the game it would affect every person running the game 

---

@proxos666 wrote:

@Cuiwe

memory being dumped is what occurs on a blue screen , this is what bluescreen view and what crashed me read to try and ascertain a cause.

If it was a memory leak on the game it would affect every person running the game 

---

I wanted to view the dump file, but I don't know how. I got the Windows debugging tools, but I really don't know what to do with them.

Further, here's a .dmp file read out for you to analyze:

DUMP FILE: 101515 - 19765 - 01.dmp
CRASH TIME: 15.10.2015 23:32:34
BUG CHECK STRING: MEMORY_MANAGEMENT
BUG CHECK CODE: 0 x 00000001a
PARAMETER 1: 00000000`00041284
PARAMETER 2: 00000000`f4a2b001
PARAMETER 3: 00000000`0000d2c4
PARAMETER 4: fffff700`01080000
CAUSED BY DRIVER: ntoskrnl.exe
CAUSED BY ADDRESS: ntoskrnl.exe + 74200
FILE DESCRIPTION: NT Kernel and System
PRODUCT NAME: Microsoft(registered) Windows(registered) Operating System
COMPANY: Microsoft Corporation
FILE VERSION: 6.1.7601.19018(win7sp1_gdr.150928-1507)
PROCESSOR: x64
CRASH ADDRESS: ntoskrnl.exe + 74200
STACK ADDRESS 1:
STACK ADDRESS 2:
STACK ADDRESS 3:
COMPUTER NAME:
PROCESSORS COUNT: 4
MAJOR VERSION: 15
MINOR VERSION: 7601
DUMP FILE SIZE: 275.368
DUMP FILE TIME: 15.10.2015 23:33:45

---

@proxos666 wrote:

@Cuiwe

Best thing to do initially is test the memory i'm afraid

normally 5 to 6 test passes is what is recommended

use either www.memtest86.com or www.memtest.org

Edit - have linked one similar thread at Microsoft for you

---

I already did that and got errors. The differing number of errors based upon a scan(first like 400 in 3 hours then 75 in 8,5 hours)-but all were clustered around the 6th Gigabyte(6-6,15 range to be exact).

I even dusted the computer, but I know what I need to do. Eh...if it keeps auto exitting itself even AFTER I install the new memory...EA will hear from me.

---

---

I already did that and got errors. The differing number of errors based upon a scan(first like 400 in 3 hours then 75 in 8,5 hours)-but all were clustered around the 6th Gigabyte(6-6,15 range to be exact).

I even dusted the computer, but I know what I need to do. Eh...if it keeps auto exitting itself even AFTER I install the new memory...EA will hear from me.

---

@Cuiwe

If errors are appearing your memory sticks are faulty hence memory errors

looks like you proved the cause

---

@proxos666 wrote:

---

---

I already did that and got errors. The differing number of errors based upon a scan(first like 400 in 3 hours then 75 in 8,5 hours)-but all were clustered around the 6th Gigabyte(6-6,15 range to be exact).

I even dusted the computer, but I know what I need to do. Eh...if it keeps auto exitting itself even AFTER I install the new memory...EA will hear from me.

---

@Cuiwe

If errors are appearing your memory sticks are faulty hence memory errors

looks like you proved the cause

---

Idk, it can still be a MoBo socket failure or something online(like...TeliaSonera-the gamer's nightmare :D).  We'll see after I get my new RAM aftter KoTFE for sure...

For now, it is RAM failure.