Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Another Patch - Still CTD

First BioWare Post First BioWare Post

DarkkChaos's Avatar


DarkkChaos
12.05.2012 , 06:54 PM | #21
Sigh....another crash - and still not a single response from C/S. This crash was lucky enough to happen during combat....I rebooted to find me dead and owing credits for repairs!!

Phenomenal....
CTD...every 120 mins...since : 9/26/2012

*** *** ***

star-forge's Avatar


star-forge
12.05.2012 , 07:06 PM | #22
3 times i have CTD tonight think i'm gonna call it a night

MrQuibbles's Avatar


MrQuibbles
12.05.2012 , 07:29 PM | #23
little off topic but, do i need to add a port after the new patch?

morningstation's Avatar


morningstation
12.05.2012 , 07:32 PM | #24
I'm still having it as well and I posted a new thread about the two swtor.exe running in task manager. One of them keeps growing matter what you do in game the amount of memory it takes grows by the second.

DarkkChaos's Avatar


DarkkChaos
12.05.2012 , 07:48 PM | #25
Quote: Originally Posted by morningstation View Post
I'm still having it as well and I posted a new thread about the two swtor.exe running in task manager. One of them keeps growing matter what you do in game the amount of memory it takes grows by the second.
Well THAT'S new.....ill have a peak and see if I have two running...
CTD...every 120 mins...since : 9/26/2012

*** *** ***

morfius's Avatar


morfius
12.06.2012 , 06:55 AM | #26
Quote: Originally Posted by morningstation View Post
I'm still having it as well and I posted a new thread about the two swtor.exe running in task manager. One of them keeps growing matter what you do in game the amount of memory it takes grows by the second.
They are 2 from the beginning, from 1.3 or 1.4 - 1st one grows up to 2.3 second up to 1.2 ... total up to 3.5 GB
I suppose they wanted to be able to go above /3GB per 32 process so they split them...
"The Aing-Tii have a different view of the Force. Not in terms of Jedi or Dark Jedi—of black and white, as it were—but in a way I like to think of as a full-color rainbow."

DarkkChaos's Avatar


DarkkChaos
12.06.2012 , 07:50 AM | #27
Wow....just WOW!

Right as I'm about to start my class end final battle....I crash!!!

Day #3 - still no response's from C/S regarding this issue. I'm happy to see that BW keep nothing but HIGH standards when it comes to their Customer Support....

Crash = 08:47
CTD...every 120 mins...since : 9/26/2012

*** *** ***

DarkkChaos's Avatar


DarkkChaos
12.06.2012 , 05:18 PM | #28
5th crash today : 18:15

Still waiting for any sort of response from Customer Service (I'm actually gonna stop saying "Customer Service" - as this imply's helping your customers.....which are NOT doing).
CTD...every 120 mins...since : 9/26/2012

*** *** ***

OwenBrooks's Avatar


OwenBrooks
12.06.2012 , 06:19 PM | #29
Quote: Originally Posted by DarkkChaos View Post
5th crash today : 18:15

Still waiting for any sort of response from Customer Service (I'm actually gonna stop saying "Customer Service" - as this imply's helping your customers.....which are NOT doing).
First step to any help is post your dxdiag up

MikeTheDuke's Avatar


MikeTheDuke
12.06.2012 , 07:45 PM | #30
Ok, Firstly when you want to look at memory usage, do it while in game, if you are using 16% memory, the game is certainly not running.

There is always 2 processes of swtor.exe one will be the main game the other I am unsure, but this interprocess communication I feel is a reason for some of the lag we see. But this is another side point.

This game is a 32bit game, therefore installing more than 4GB of RAM and running a 64bit OS is not the solution. There is some issues though I have seen with 32bit applications running and needing more RAM that what Windows will allow.

32bit application are allowed to utilise 2GB of RAM in Windows. This can be an issue, especially when games like SWTOR certainly need more. BUT. There is a thing called PAE, which is Physical Address Extensions when enables 36bit addressing when then enables the use of about 3GB of RAM per application. To check to see if PAE is on. It says that it is on by default if the machine support hardware DEP. But this is different for each machine and I have needed to turn it on sometimes.

For Information of PAE and updating.

My suggestion is to try this even if you feel it is already on, give it a try. Another, due to the massive memory contingent required for SWTOR, check the size, location of your swap file. If you open Task Manager and on the processes tab you can view the number of Page Faults (this often needs to be added), if SWTOR.exe is performing a lot of Page Faults, it means it is accessing the Page File a lot. Try increasing the size of the file or
check the disk the page file is on. The page file might have some bad sectors on the disk. So perform a chkdsk If it is happening at regular intervals then it seems that there are issues with your system and it causing it to crash.

Also, try PageDefrage. This is an advanced topic and is only recommended if you know what you are doing. Defrag the drive that the page file is on, this will help create more contiguous spcace. Then run the PageDefrag. Next reboot it will perform this task. NOTE. Read the page carefully and do not assume anything. The Defrag the Page file is OK, but leave the registry hive alone.

I am not sure what else could be offered. Yes upgrading to 64bit OS will remove a lot of memory constraints, evening on a 4GB system this can help give you a little more memory but it will also mean 32 bit applications can access all of the 3GB possible for a 32bit application.

So before you run, check the amount of free memory available on your system as well. Make sure it is enough, stopping processes not needed can help. Stopping services that aren't needed helps more. Other than those thigns I am not sure where else to go, as I am also unsure what else BioWare could do as well, since this is sounding like a specifc problem.

Also if you could post the specs of your machine. Provide information from the eventlog or the reliability history, since the module that it fails in might help with finding the solution.