This may or may not be related to the long talked about gameclient crashes, but I've just about reached the end of my tether with it so thought it was time to write up a bug report (especially as I've just managed to get a Cryptic Error Tracker number from it). Hopefully there's some information that's usable in here to track down the issue as its becoming a major annoyance.
If the mod's feel there's already an existing thread this sits better in please feel to merge the thread.
Issue: Game is periodically causing my graphics to lock and crash, often causing a hard crash to desktop (although this isn't always the cash). At any rate graphics become unresponsive for an extended period which in time gated missions make the game very difficult to actually play.
System Setup: Nvidia GTX 560 Ti, Windows 7, Current Nvidia Driver (347.52 - although I've been having issues since the winter event patch which was several driver iterations ago), assuming the rest of the system details are essential since it seems to be graphics based.
Crash Details: Crash that I've just had gave me a Cryptic Error tracker number eventually Error No. 36261725, haven't had one of any of the others that I can recall.
Crashes usually start after the game has been running for a little while (hour or so - doesn't appear driven by what I'm doing as it goes in normal sector space or on a mission - later seems more common but that might be perception as its more annoying), but difficult to put a definitive timeframe on it. Then all of a sudden the graphics lock up and the screen goes blank. If I try to do anything at this point I usually get a Gameclient not responding message and the client hard crashes to desktop with no Cryptic Error Tracker. Recently tried switching to DirectX 9EX mode to see if it made any difference (which it hasn't). Last crash I got with the error details above crashed the graphics, although audio could be heard to continue in the background (Voth phase of the Undine Battlezone), eventually tried alt-tabbing out of the game when the phase ended and the client crashed to desktop with the above error number. Previous early alt-tab's haven't generated an error tracker just crashed the client hard.
When the graphics crashes happen Windows Event Viewer is recording the following Errors (summarised for not making this post too long).
Display driver nvlddmkm stopped responding and successfully recovered.
The following repeat a number of times over a minutes:
- \Device\Video5
- Graphics Exception: ESR 0x4058040=0xa0061a0c (some or the reported errors vary the second address)
- Graphics Exception: Shader Program Header Error (various numbers 18, 17, 12, 11, 9, 3, 2)
Error List starts with the following:
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video5
Variable String to Large
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video5
NVRM: Graphics TEX Exception on (GPC 1, TPC 3): TEX FORMAT
For the graphics crash previous to the above one the display driver error details are essentially the same, however also get the following error data.
Windows Error:
Faulting application name: GameClient.exe, version: 0.0.0.0, time stamp: 0x54ee72b3
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7
Exception code: 0xc0000374
Fault offset: 0x000ce753
Faulting process id: 0x1530
Faulting application start time: 0x01d0534c1480673a
Faulting application path: C:\Program Files (x86)\Cryptic Studios\Star Trek Online\Live\GameClient.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: a08d5a80-bf44-11e4-ba5e-f46d04966f69
Windows Information:
Fault bucket 201282860, type 22
Event Name: FaultTolerantHeap
Response: Not available
Cab Id: 0
Problem signature:
P1: GameClient.exe
P2: 0.0.0.0
P3: 54EE72B3
P4: ffffbaad
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp\FTH4BA2.tmp\fthempty.txt
These files may be available here:
Analysis symbol:
Rechecking for solution: 0
Report Id: a08eba15-bf44-11e4-ba5e-f46d04966f69
Report Status: 0
And:
Fault bucket 886949377, type 17
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: GameClient.exe
P2: 0.0.0.0
P3: 54ee72b3
P4: StackHash_3cac
P5: 6.1.7601.18247
P6: 521ea8e7
P7: c0000374
P8: 000ce753
P9:
P10:
Attached files:
C:\Users\Matt\AppData\Local\Temp\WER4BE0.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Matt\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_GameClient.exe_ceeadf4ceed26c42454bb149217c6ee4e962122_085f6412
Analysis symbol:
Rechecking for solution: 0
Report Id: a08d5a80-bf44-11e4-ba5e-f46d04966f69
Report Status: 0
Comments
A workaround I have been testing (been working so far) is to switch from Fullscreen mode to windowed mode (hit Apply) then back to Fullscreen (hit apply again)
I used to have a problem with the game always wanting to start in windowed mode, and when I would switch to Fulllscreen, it would hang up whenever I opened ANY window using the onscreen UI. After the Anniversary , this seemed to go away...but the crashes started. My workaround worked for fixing the window problem, so I tried it for the crashes....and it seems to be working. SO maybe they have something to do with one another.
The crash happens pretty much anywhere, but seems more prone to happen in mission. For each crash I have pretty much the same crash report from windows. Here are a copy of the windows application log when one of the crash happened, all appcrash logs are pretty much the same.
And the second event related to the crash recorded by windows
This is getting where I don't feel like playing much with game crashing usually at the wrong time. Please fix
E'Mc2 : Science Reman torp T'Varo, deadly annoyance :P
Kunmal: Tactical fed Klingon, ground specialist, USS Kanewaga
Ka -tet Tier 5 fleet fully completed Starbase and fleet property
Maybe I will return to it in a year when these insane crashes have been (hopefully) fixed.
After the anniversary updates and subsequent patches, it crashes all the time. I'm lucky if I get 30 minutes of play.
It doesn't just crash to desktop, but just to a constant black screen, where the only option is to click the restart button on the computer.
Graphics drivers are updated to the newest, GFX card is Radeon 290X. Win7 64bit.
I cannot get any crash report or anything, because of this POS update.
No other game presents any problem at all.
Well, see you in a few years.
Edit: Before any of you "recommend" to check cooling, the temperature of everything is perfectly low and Watercooled.
But of course a real fix from Star Trek Online or Nvidia would be great.
Been playing for 2 hours 4 crashes going back to the other stable mmo's like World of War craft.
cant even get through one mission. Glad I did not waste the mony on a lifetime subscrption...
If it's works, it could mean the problem came from the newer version of the Nvidia driver, and so the problem isn't from Star Trek Online (because before the new patch from Nvidia side the game hasn't this bug).
Well I've been running 344.11 drivers for a long while now without issue. I had updated back in October and then rolled back to this version because the newer version kept crashing (graphics driver crash, not game crashing) when I was playing any game for more than 15 minutes. 344.11 has been fine save for during the first two weeks of Winter event and now again since Thursday's patch where I'm experiencing CTDs continuously.
The really annoying thing is that the Devs never confirm there is an issue when this happens. Yet it only shows up after a patch, even when I've changed no drivers or settings, and then it disappears after another patch a week or two later usually. So they are clearly doing something to fix it but never confirm it or mention it in patch notes.
Edit: For the sake of testing, I cleared out my drivers and then went to version 347.09 as you suggested. I've just had another CTD.
You can try to uninstall all your software from Nvidia too (except the 347.09 of course) then restart your computer and check if your driver crash again when STO is active.
Btw, I try to find a solution to your problem, but I realise it'll not replace a real fix from STO/Nvidia.
The game is unplayable and the Devs really need to fix this now.
The final thing I can suggest is to put the Bloom Quality (in Graphics settings) to Low or Off... Don't ask me why... But it prevented some friends and myself from repetitive graphical crashes in the past.
If it still doesn't works, you can try to install more older Drivers from the last year, but it'll be a pretty long process and the result is highly uncertain...
I don't get a message. I only ever got messages when I was running newer driver versions, but with this CTD it literally just closes the game and windows pops up a warning to say the game stopped working.
Event logs show the problem is with GameClient.exe causing a problem in ntdll.dll. The most common problem with a game causing this crash is a memory leak they've introduced.
For reference, my holodeck settings had bloom turned off completely until last night. But the crashes started up again on Thursday.
I also can't install any drivers older than the 344.11 because those are the earliest drivers which support the GTX 970.
Thanks for your advice, but the problem here isn't with drivers, it's with the game and most of us are just screwed until they fix it.
I have the same problem and I have an ATI card.
Look:
Faulting application name: GameClient.exe, version: 0.0.0.0, time stamp: 0x54ee72b3
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7
Exception code: 0xc0000374
I am afraid that it's definitely a STO problem.
Googled "ntdll.dll star trek online" just gave me this : http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htm
I don't know if it can help you guys as a temporary fix or not...
In an other -and desperate- hand, I just found a guy who fixed the problem with a run of Malwarebyte (anti-malware software), but he more look like a lucky guy or voodoo sorcery to me.
I looked at that exact page the last time I had this problem (during Winter event) and it was no use. The error code windows provides points to a heap error which is something Cryptic needs to fix. Nothing we can do on our end to fix their bad code.
I've crashed five times in the last two hours now. Most recently I was literally just sitting doing nothing in Sol system. I had logged in to this character and just started typing in chat then bam...
So fed up of this.
Nvidia have a habit of breaking things in driver releases, but in this instance its not just Nvidia. As already stated some users of ATI cards also have the same issue.
Before the aniversay event I'd regularly get device hung errors then when the Aniversary event went live I started to get the "Gamclient.exe has stopped working" messages. They have now mutated into just plain CTD's with no errors (other than in the system event logs).
It makes me remember there is a "Reduced file streaming" in the "Advanced" settings, maybe switching this option can reduce the frequency of your crashes...
Did you guys already tried to reinstall the whole game ? Or at least tried to delete some files ? Like the shaders from localdata etc then forced the verification with the launcher to download new ones ?
With the new stuff on Tribble I suppose they're pretty busy at the moment, but it's also possible to see a fix in the next patch...
A good thing would be to have a message about the status of an eventual fix. Like a kind of "we're on it", or even a "we're not able to reproduce the problem".
Yeah, it's getting to be a real pain in the a*se like.
You know, I haven't tried that because I have 16GB of RAM and see no need to disable storing data in RAM. I will turn it off just now just to rule it out, though I'm already 99.9% sure it will make no difference.
Though talking about that option, the tooltip on that makes zero sense. "Turning this option off on systems with low RAM could cause crashes"....... yet turning it on is actually what will use more RAM lol.
I haven't this time round. During the Winter event when it was having the same issue, I completely deleted my install and re-downloaded it, all to no avail.
Yeah, I know they are probably busy with Tribble (though I've not seen any confirmation for the numerous Tribble bugs I've reported either), and that's normal with a big update coming. But I would like at least an acknowledgement that this is happening and we're not all just imagining it.
Sorry to haven't been able to help you and just wasted your time.
No worries man, I appreciate you trying.
150304 02:44:44 34 Client[0 P[5255@661830 Kern@Khamseen]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
Thought I'd post it just in case. Really need this fixed, so infuriating.
The devs are aware of it thought, and there's a thread on Reddit outlining the problems as well.
And yet for over a month here on their bug report forum they refuse to acknowledge this problem, quality customer support.
The ticket number at the bottom was 37267120.
Hope you fix it next patch or I'll find something else to play, no sense in playing when you can't do any missions.....
E'Mc2 : Science Reman torp T'Varo, deadly annoyance :P
Kunmal: Tactical fed Klingon, ground specialist, USS Kanewaga
Ka -tet Tier 5 fleet fully completed Starbase and fleet property
The answer to the question in my sig is most definitely, no.
It only seems to happen the first time I've logged in on every character.
Not to mention whenever I log in for the first time I have extreme lag where I can do nothing but wait 2 or 3 minutes until it normalizes.
Fatal Error: Direct3D driver returned error code
(D3DERR_DEVICEHUNG) while checking sync query.
Technical Details: Sync query 13 0x13e6e20 GetData = =
0x88760874 0 F 0
Is my GPU the problem or the game?
Thats the error I used to regularly get before it started just crashing with the "gameclient.exe has stopped working" dialog box.
And no. Its not your GPU. If it were I would guess Cryptic would be quick to acknowledge the error but all we've got on this particular issue is silence.
So...Cryptic...how about at least a nod to the issue? Please? I'm asking nicely....