as of a couple patches ago, i am unable to play the game for more than a minute or two with out crashing. there is no specific error message that appears when the game crashes. i assume this is because the crash is being caught by the cryptic crash uploader -"crypticError.exe" I am letting it upload the crash reports/dumps despite how long it takes. now that the 5 year anniversary has come around, i am unable to stay ingame long enough to accomplish anything. I cant even comlete typing a sentence after logging in before the dam game crashes again. I really want to get that anniversary ship.....
since there are no error messages aside from the cryptic error reporter, i have provided a link to my skydrive where i have copied the files from the logs directory, hopefully they contain something useful.
link:
http://1drv.ms/1A5PJ9B
Win7 Ultimate x64 SP1
Intel i7 720QM 1.5 - 2.8 GHZ
8Gb DDR3
nVidia GTX-330M 1Gb GDDR3 (344.11 Driver)
Star Treking, across the universe. Only going forward because we can't find reverse...
Comments
Win7 Pro 64-Bit
Intel i7 3770K 3.50 GHz
16 GB RAM
EVGA GTX 660 2 GB (344.75 Driver)
The crashes occur when running the game on DirectX 9 and 11. Support ticket has been created.
on every crash i get this error code 36294169
anybody know what error 36294169 is or what it means?
heres another error code, from now on i will just make a list and add the codes as they appear
36294169
36518286
36316536
36695960
36389406
36358761
list updated 2/9/15
AMD R9 290x
Intel I7 2700K
16gb of ram
Nothing is overclocked. It's not giving me any errors either, just says the gameclient crashed and kicks me to desktop.
It may be a coincidence, but usually when it crashes, I've just finished the first omega scan, and I am going to the second (crashes while on a map, any map). I've had it crash on ground, space, sector space, and during map transition (before loading screen). If it matters, I make the Omega scan my primary mission.
Cryptic devs:
Here's a crash dump (which is normally sent with the cryptic reporter): https://www.dropbox.com/s/1fi25sws1ei4pjk/GameClient.dmp?dl=0
Since it uses so much RAM, the first one is a small minidump. It might not be useful to you though, so here's a large minidump just in case (200MB): https://www.dropbox.com/s/832airzcjozfxd2/GameClient-heap.7z?dl=0
The above crash dumps where taken right after I triggered a 'Turn in Contraband' doff mission on DS9 (Omega mission was already turned in). I walked away, and when I came back it broke in Visual Studio (I had it attached).
EDIT: If I stay away from social zones, it seems stable. I played 'Dust to Dust' without any problems last night.
This morning though, it crashed WHILE scanning at Wolf 259. I guess the Borg are back.
EDIT2: Scratch that, it crashed DURING Dust to Dust. This is not good.
much of the crash issues atm seem to be related to anything that is affected by the anniversary event. this includes sector space (where Q has some 'witty' dialogue, system space where omega traces are present, ground maps where omega traces are present, and the anniversary episode "Dust to dust".
I wish I could get more info about the error ticket id's I am getting, and have even asked for their meaning from pwe support, but those requests have gone ignored.
I have updated the list of error ticket id's that I made in an earlier post.
"Unfortunately, we have provided all the necessary troubleshooting steps on how to resolve the issue. We have exhausted all possible resources and we still couldn't fix the crash issue. We would like to ask you to kindly wait for the next patch and try to check if that would fix the issue."
Same here. 1-3 crashes per hour since aniversary patch.
Looking for a fun PvE fleet? Join us at Omega Combat Division today.