Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Hey Crashy, what ya doin


NickelNine's Avatar


NickelNine
10.26.2012 , 11:20 AM | #11
Quote: Originally Posted by Foobert View Post
You're running the game on a 32bit OS and you either don't have enough ram or you aren't giving 3gb of user memory to applications. (http://dwf.blogs.com/beyond_the_pape...ows-vista.html)
I dont think thats the problem at all, because this is the only game that this happens to me on. I've run COH, WoW, Dc Universe all without any problems, not to mention all the singleplayer games that i run without any of the crashes i experience in SWTOR

Foobert's Avatar


Foobert
10.28.2012 , 09:42 PM | #12
Quote: Originally Posted by NickelNine View Post
I dont think thats the problem at all, because this is the only game that this happens to me on. I've run COH, WoW, Dc Universe all without any problems, not to mention all the singleplayer games that i run without any of the crashes i experience in SWTOR
Show me another game you play where its memory usage exceeds 1.7GB after a couple of hours...

LetoAtreidesII's Avatar


LetoAtreidesII
10.31.2012 , 02:41 PM | #13
USEFUL Cut and Paste Advice:

If you're getting the memory leak crashes that many/most of us have, the advice Bioware Customer Service gives may very well be of no use to you and you'd be well advised to ignore it. Instead, do the following:

1. If you have 32-bit Windows, either upgrade to 64-bit or use this method to remove the RAM cap:
http://www.evga.com/forums/tm.aspx?m=960087&mpage=1
This will allow your system to use more than 3.5 gigs of RAM, which is the hard-coded limit in 32 bit Windows.

2. If you already have 64-bit Windows, install more RAM in your system.

3. The following did not help me, but it may help you:
Increase your GDI object cap; for Windows 7 users only (adapted from Slaxinexx's original post here http://www.swtor.com/community/showthread.php?t=547744)

a. Start up your registry editor (Start -> Run -> regedit)
b. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
c. Optional: click on the key (windows) and export it to any new file name to create a backup
d. Click on GDIProcessHandleQuota
e. Click on Decimal under base
f. The value should be 10,000 (default). Change this to 20,000.
g. Exit registry editor and reboot

More RAM available to the system will allow you to play for a much longer period of time before the memory leak causes the client to crash. It seems that for most people, this is so effective that they don't crash at all, or at least not very often.

This issue has been reported and discussed in the following threads without any official acknowledgement:
http://www.swtor.com/community/showthread.php?t=542551
http://www.swtor.com/community/showt...=538577&page=6
http://www.swtor.com/community/showthread.php?t=544501
http://www.swtor.com/community/showthread.php?t=545715
http://www.swtor.com/community/showthread.php?t=545382
http://www.swtor.com/community/showthread.php?t=541996
http://www.swtor.com/community/showthread.php?t=544474
http://www.swtor.com/community/showthread.php?t=544832
http://www.swtor.com/community/showthread.php?t=542298
http://www.swtor.com/community/showthread.php?t=539461
http://www.swtor.com/community/showthread.php?t=545666
http://www.swtor.com/community/showthread.php?t=543716
http://www.swtor.com/community/showthread.php?t=548620
http://www.swtor.com/community/showthread.php?t=549553

In each case where Bioware CS has responded to these threads, they have treated it like a new and unknown issue and thus applied their ineffective standard troubleshooting protocol. In the meantime, much of the community has correctly identified the problem. As such, it stands reason to assume that Bioware is unaware of the problem and is not working on a fix. If they were aware of the issue, Bioware CS should respond with "this issue will be fixed in an upcoming patch" instead of useless troubleshooting advice. Since a fix by Bioware is not forthcoming, users would be well advised to use the three suggested fixes above and ignore Customer Service's troubleshooting tips.

If my three suggested tips are not possible for or useful to you, there is still some hope. It is possible that Bioware will eventually acknowledge and fix this issue, since they have done so before. The memory leak crash was acknowledged and largely fixed sometime back in 1.2, unfortunately, only to reemerge in 1.4. As bad as this may seem, this is a much better track record than Trion had with Rift, which had a similar issue which was never acknowledged or fixed, at least at the time when I quit that game back in January.