I've tried everything in STO, Arc, Windows, DirectX except for registry edits and the only things that may have at least slowed down the crashes (I have a folder w 100's) or were just coincidental, were (1) shutting off the Image Softening feature in my Nvidia control panel/Manage 3d settings which now makes my text harder to read, (2) changing the STO advanced setting to limit my frame rate from 120 to 60, and (3) per Support added the line "ArcOverlayEnable 0" in the launcher options command line. Support was very responsive and nice, but it played out like this -- send us your dxdiags, you have out of date graphics drivers even though they were from 6/8/2021 and installed 6/10/2021, no response about the drivers, then closed the ticket when I told them shutting off Image Softening may have helped but I still get crashes. edit: btw, remove as much of the Xbox Live TRIBBLE that MS will allow to remove, unless of course you need it.
I'm force-verifying the latest patch and hoping the patch notes didn't bother to mention server fixes. These fixes could be internal to STO or Arc or the handoffs with Akamie Tech & we may never know. After going through all my Event Viewer logs, it looks like my "permissions" issue went away but my nvidia driver nvlddmkm.sys times out and fails then resets ok. The driver has been replaced many times & is current so I'm now stuck. To protect my sanity I've reconciled that my Lifetime Sub in STO did pay for itself and I've reactivated all my old WOW characters.
I've tried everything in STO, Arc, Windows, DirectX except for registry edits and the only things that may have at least slowed down the crashes (I have a folder w 100's) or were just coincidental, were (1) shutting off the Image Softening feature in my Nvidia control panel/Manage 3d settings which now makes my text harder to read, (2) changing the STO advanced setting to limit my frame rate from 120 to 60, and (3) per Support added the line "ArcOverlayEnable 0" in the launcher options command line. Support was very responsive and nice, but it played out like this -- send us your dxdiags, you have out of date graphics drivers even though they were from 6/8/2021 and installed 6/10/2021, no response about the drivers, then closed the ticket when I told them shutting off Image Softening may have helped but I still get crashes. edit: btw, remove as much of the Xbox Live TRIBBLE that MS will allow to remove, unless of course you need it.
I'm force-verifying the latest patch and hoping the patch notes didn't bother to mention server fixes. These fixes could be internal to STO or Arc or the handoffs with Akamie Tech & we may never know. After going through all my Event Viewer logs, it looks like my "permissions" issue went away but my nvidia driver nvlddmkm.sys times out and fails then resets ok. The driver has been replaced many times & is current so I'm now stuck. To protect my sanity I've reconciled that my Lifetime Sub in STO did pay for itself and I've reactivated all my old WOW characters.
That is probably what they want, for us to stop talking about it/dealing with it. So cryptic can sweep it under the rug. Now they have new worries, cryptic is stealing character slots, lol.
"Nuke the entire site from orbit--it's the only way to be sure"
Cause there's at least 1-2 threads still being created, all I can do is advise you log a Arc Support Ticket as shown in the thread above, and also follow the instructions for uploading a Dxdiag (Report) from Direct X tool in Text format showing all your Graphic Drivers, Direct X details, and others that help Arc to forward info to Q&A or DEVs. Hopefully they also escalate to Tier 2.
If they do not escalate to Tier 2, perhaps try and request they do so, especially if you've included the Dxdiag report to them in Text format!
First time ever that I've gotten two Crashes in one day, Incident Crash ID 3779dc. Earlier I posted the other above.
I know it's typical many get 2-4x or more Crashes each day. Usually I've only gotten one, yet still again I wasn't doing anything intensive just walking or standing somewhere when it occurred.
@LEMMINGER83 I would stop it with your flooding of this thread with crash after crash after crash as it might starting aggravating the mods.
Hmm... interesting point. I was just trying to help on that matter.
Since "Post it at the forum" is usually the first advice you get when filing a ticket. So you think submitting a ticket for each crash is less aggravating?
Or is this just your kind way to tell me to shut up, since the case is hopless and I can post as many crash IDs as I want, they'll not fixin' anything anyways?
Thinking about it, you might be right though... I guess keep posting those IDs might indeed just be a waste of time.
I have uninstalled STO around 20 times since I started playing, on 3 systems. I build my own PC's and work directly with people that know what is and is not compatible when it comes to building PC's, as it was my living for 20 years. I have been playing STO for the last 5+ years and its the only game which crashes for no reason at all.
We know games really only work on Dual core CPU's so that could be an issue we really haven't explored as technically this is an old game. I do not need to go through my specs as they are way over the Maximum specs required for this game.
There are a select number of Task Force Omega's "TFO" Which crash. One being Hive Onslaught another is Assault on Terok Nor as well as Transdimension Tactics, which as you know only allows a set time to get out of the starting area. Also as there is a 30 min penalty for not scoring or doing damage you are locked out for 30 mins, which is pointless even trying. Then there are other loading screen errors like, "Cannot transfer to Map" which again makes you have to go to ground or open up your character screen.
And Finally they still haven't fixed Stranded in space which has been broken for nearly 3 years. If they were paid on fixing things then they would have fired everybody except the spotty kid who works for lollypops. 3 years shows the LACK of interest in actually doing anything, so players crashing because of simple clashes with OS and hardware is not their concern.
When I started out you had to look at compatibility lists and figure out which hardware worked together so your customer was happy, unlike today anybody that produces any game will say, Compatible with Windows, when there are differences between all platforms.
Fix the bugs please and not just sit on them ignoring lifetime subscribers
Is there any way to tell what the code mean? I just got a crash again and I wasn't even doing anything. Just standing next to the exchange without interacting with anything. Didn't even have the exchange open.
I'm getting game crashes on map transfers. Been parked at the Dil mine to turn in vp vouchers and leaving airlock or returning has game crash to desktop. Crashed more in the last week than it has the past 10 years I've played
@LEMMINGER83 I would stop it with your flooding of this thread with crash after crash after crash as it might starting aggravating the mods.
Hmm... interesting point. I was just trying to help on that matter.
Since "Post it at the forum" is usually the first advice you get when filing a ticket. So you think submitting a ticket for each crash is less aggravating?
Or is this just your kind way to tell me to shut up, since the case is hopless and I can post as many crash IDs as I want, they'll not fixin' anything anyways?
Thinking about it, you might be right though... I guess keep posting those IDs might indeed just be a waste of time.
Just edit a previous post. Go to the first post you made and top far right of your post will bring up a cog to edit. That way you won't be flooding (or seen to be flooding the thread then. Could help you in the long run.
If you log all your crash I.D's when they come to read it. They have them there all in one place instead of one being on page 1 on a thread another on page another again on page 2 and then maybe another on page 3
Another crash well 3 of them in the past 2 hours. 2021-07-01 17:49:41: Executable GameClient.exe crashed. Crash ID: 37de30. The only pattern I noticed is the crashes and map load bug happen more often when the server is under heavier load likewise less often when the population levels are low. I am more convinced then ever this is a server problem that's kicking us out of game.
The only pattern I noticed is the crashes and map load bug happen more often when the server is under heavier load likewise less often when the population levels are low. I am more convinced then ever this is a server problem that's kicking us out of game.
Interesting observation. I first noticed the map/zone transfer crashes right around the time covid lock-downs started (+/- March 2020). Perhaps people staying home more have loaded up the servers, and have caused some kind of issue with data packet transfers? If so, perhaps that is also related to patch data? What kinds of data loading/transferring issues could a heavily loaded server potentially cause?
Question - are the crash reports not uploaded to Cryptic automatically, when the crash dialog comes up?
They used to upload to them after a crash yet it also used to upload a lot of other data cause sometimes it take 10-30 minutes to send. Now I think they stopped that, but you'd at least hope they'd report or upload the Crash Incident ID, but now there's no indication that's even done. Hense why some are still posting when they happen, trying to help.
While others have just mostly given up!
I haven't seen a crash in a week after downloading the latest Nvidia drivers 471.11, yet again today saw one Incident ID 38513d.
And like usually it's mostly when I'm doing very little, often on a social map, like standing still or just going to go to Inventory, exchange, or something else. 80% of others I know that's when it occurs for them as well, only the very odd time has 1 in 5 does it occur doing a TFO or something.
Is there any way to tell what the code mean? I just got a crash again and I wasn't even doing anything. Just standing next to the exchange without interacting with anything. Didn't even have the exchange open.
Only the game devs know & they're apparently not telling. What you CAN do though is right after a crash (note the time) call up windows Event Viewer app (type in event viewer in the search box), then go to Windows Logs then System. You should see information hits, warning hits, and any error (crash) hits. A lot of the info is white noise but some errors can tell you whether or not you are crashing due to a video driver for example.
@LEMMINGER83 I would stop it with your flooding of this thread with crash after crash after crash as it might starting aggravating the mods.
Hmm... interesting point. I was just trying to help on that matter.
Since "Post it at the forum" is usually the first advice you get when filing a ticket. So you think submitting a ticket for each crash is less aggravating?
Or is this just your kind way to tell me to shut up, since the case is hopless and I can post as many crash IDs as I want, they'll not fixin' anything anyways?
Thinking about it, you might be right though... I guess keep posting those IDs might indeed just be a waste of time.
I think your not the one with the issue here, as it's good to report each Incident ID, otherwise you're not being Informative! Though I'd support edit of posts made the same day where possible. I've been on the Volunteer Bug Hunter Team for several years, and worked with DEVs many times to fix several issues.
Yet making a new POSTs with new INFO, is not going to aggravate mods by any means...
PS: Mod's don't get aggravated making a new posts, when it provides new, or different INFO describing where/when it occurs, especially if your trying to help. Sometimes two short messages, is nicer and easier to read, than one long one. What they don't like is people being mean, or trying to intentionally upset people.
Yes, this two today... every single day there is a CTD, once at least.. to make sue i have no lag or crashs, i change instances to a less populated ones..
I have had more crashes since they re launched the Dominon Recruitment drive, since they launched the original Dominion recruitment drive, coincidence, i think not, there are issues associated with the recruitment systems they have running and maybe once that passes and two to 5 patchs down the line things might get back to stable. But I just log in now do the minimum Risa, run a couple of toons reputation fillers, I klink recruit, 1 Dom recruit and, just now on my Dom recruit im doing the heavy task of looking at fleet donations of dilithium, doffs etc standing in ESD and the game dies goes into cryptic crash mode and then says unable to run cryptic crash handler ( win 10 pro 19043) so its task manager close and go to something else I have a good list of crashes from 26/5 and most are doubles where if I relog in and continue to play and hour on usually in social areas DS9 ESD the game dies again. I dont know if someone ran some textures boosting to the game or tried to squeeze in some code to improve element apperances or compress jpgs of console images icons for the ship equipment and toon gear slots, or for the inventory but something has been done within the dominion recruitment content which I feel is the culprit to this sudden instability.
Laddy, don't you think you should... rephrase that??
Mostly when standing around on Risa often not moving or walking (not running) which is like many (reports) above at ESD or a few other locations getting ready to check Exchange or something else.
& no one has commented if this helps...
Still I think it's increased, for some especially after they've installed the Windows 10 21H1 update; which came out at about the same time or just before 5/25. And windows has the most recent update as today, same with my driver.
Someone else (a friend) stated turning off Lighting 2.0 also seems to reduces the # of crashes. I found the NVidia GeForce GTX 1650 Ti Drivers issued June 22nd (most recent) have helped reduce it for me too, as well as perhaps turning OFF Dynamic Lighting, I don't like turning off Lighting 2.0 and it may also help! Still the CORE of the issue is in the STO code itself, that they hopefully are working to identify the real cause!
Not complaining, I know it takes a lot of hard work and investigation to resolve, so we can only be patient...
Comments
I'm force-verifying the latest patch and hoping the patch notes didn't bother to mention server fixes. These fixes could be internal to STO or Arc or the handoffs with Akamie Tech & we may never know. After going through all my Event Viewer logs, it looks like my "permissions" issue went away but my nvidia driver nvlddmkm.sys times out and fails then resets ok. The driver has been replaced many times & is current so I'm now stuck. To protect my sanity I've reconciled that my Lifetime Sub in STO did pay for itself and I've reactivated all my old WOW characters.
That is probably what they want, for us to stop talking about it/dealing with it. So cryptic can sweep it under the rug. Now they have new worries, cryptic is stealing character slots, lol.
https://www.arcgames.com/en/forums/startrekonline#/discussion/1261957/load-game-since-5-25-update-just-black-screen-or-crashes/p1
Cause there's at least 1-2 threads still being created, all I can do is advise you log a Arc Support Ticket as shown in the thread above, and also follow the instructions for uploading a Dxdiag (Report) from Direct X tool in Text format showing all your Graphic Drivers, Direct X details, and others that help Arc to forward info to Q&A or DEVs. Hopefully they also escalate to Tier 2.
If they do not escalate to Tier 2, perhaps try and request they do so, especially if you've included the Dxdiag report to them in Text format!
Perhaps I'd just been playing less though, perhaps like some.
Many tire or reporting them continously since 5/25, so hopefully they FIX it soon.
I know it's typical many get 2-4x or more Crashes each day. Usually I've only gotten one, yet still again I wasn't doing anything intensive just walking or standing somewhere when it occurred.
Hmm... interesting point. I was just trying to help on that matter.
Since "Post it at the forum" is usually the first advice you get when filing a ticket. So you think submitting a ticket for each crash is less aggravating?
Or is this just your kind way to tell me to shut up, since the case is hopless and I can post as many crash IDs as I want, they'll not fixin' anything anyways?
Thinking about it, you might be right though... I guess keep posting those IDs might indeed just be a waste of time.
I have uninstalled STO around 20 times since I started playing, on 3 systems. I build my own PC's and work directly with people that know what is and is not compatible when it comes to building PC's, as it was my living for 20 years. I have been playing STO for the last 5+ years and its the only game which crashes for no reason at all.
We know games really only work on Dual core CPU's so that could be an issue we really haven't explored as technically this is an old game. I do not need to go through my specs as they are way over the Maximum specs required for this game.
There are a select number of Task Force Omega's "TFO" Which crash. One being Hive Onslaught another is Assault on Terok Nor as well as Transdimension Tactics, which as you know only allows a set time to get out of the starting area. Also as there is a 30 min penalty for not scoring or doing damage you are locked out for 30 mins, which is pointless even trying. Then there are other loading screen errors like, "Cannot transfer to Map" which again makes you have to go to ground or open up your character screen.
And Finally they still haven't fixed Stranded in space which has been broken for nearly 3 years. If they were paid on fixing things then they would have fired everybody except the spotty kid who works for lollypops. 3 years shows the LACK of interest in actually doing anything, so players crashing because of simple clashes with OS and hardware is not their concern.
When I started out you had to look at compatibility lists and figure out which hardware worked together so your customer was happy, unlike today anybody that produces any game will say, Compatible with Windows, when there are differences between all platforms.
Fix the bugs please and not just sit on them ignoring lifetime subscribers
2021-05-02 10:51:31: Executable GameClient.exe crashed. Crash ID: 33fc8a
2021-05-02 10:54:24: Executable GameClient.exe crashed. Crash ID: 33fc94
2021-05-16 11:25:50: Executable GameClient.exe crashed. Crash ID: 34c4f2
2021-06-01 15:29:42: Executable GameClient.exe crashed. Crash ID: 35c195
2021-06-07 06:29:10: Executable GameClient.exe crashed. Crash ID: 362ff0
2021-06-17 15:31:08: Executable GameClient.exe crashed. Crash ID: 36e3fa
2021-06-29 18:42:40: Executable GameClient.exe crashed. Crash ID: 37bc82
Just edit a previous post. Go to the first post you made and top far right of your post will bring up a cog to edit. That way you won't be flooding (or seen to be flooding the thread then. Could help you in the long run.
If you log all your crash I.D's when they come to read it. They have them there all in one place instead of one being on page 1 on a thread another on page another again on page 2 and then maybe another on page 3
Interesting observation. I first noticed the map/zone transfer crashes right around the time covid lock-downs started (+/- March 2020). Perhaps people staying home more have loaded up the servers, and have caused some kind of issue with data packet transfers? If so, perhaps that is also related to patch data? What kinds of data loading/transferring issues could a heavily loaded server potentially cause?
They used to upload to them after a crash yet it also used to upload a lot of other data cause sometimes it take 10-30 minutes to send. Now I think they stopped that, but you'd at least hope they'd report or upload the Crash Incident ID, but now there's no indication that's even done. Hense why some are still posting when they happen, trying to help.
While others have just mostly given up!
I haven't seen a crash in a week after downloading the latest Nvidia drivers 471.11, yet again today saw one Incident ID 38513d.
And like usually it's mostly when I'm doing very little, often on a social map, like standing still or just going to go to Inventory, exchange, or something else. 80% of others I know that's when it occurs for them as well, only the very odd time has 1 in 5 does it occur doing a TFO or something.
@lemminger83
I think your not the one with the issue here, as it's good to report each Incident ID, otherwise you're not being Informative! Though I'd support edit of posts made the same day where possible. I've been on the Volunteer Bug Hunter Team for several years, and worked with DEVs many times to fix several issues.
Yet making a new POSTs with new INFO, is not going to aggravate mods by any means...
PS: Mod's don't get aggravated making a new posts, when it provides new, or different INFO describing where/when it occurs, especially if your trying to help. Sometimes two short messages, is nicer and easier to read, than one long one. What they don't like is people being mean, or trying to intentionally upset people.
Last crash code is 386b74.
2021-07-09 15:31:12: Executable GameClient.exe crashed. Crash ID: 38af29
2021-07-09 18:37:01: Executable GameClient.exe crashed. Crash ID: 38b2f9
38d2ca Incident Crash Id
35d59d
Mostly when standing around on Risa often not moving or walking (not running) which is like many (reports) above at ESD or a few other locations getting ready to check Exchange or something else.
& no one has commented if this helps...
Still I think it's increased, for some especially after they've installed the Windows 10 21H1 update; which came out at about the same time or just before 5/25. And windows has the most recent update as today, same with my driver.
Someone else (a friend) stated turning off Lighting 2.0 also seems to reduces the # of crashes. I found the NVidia GeForce GTX 1650 Ti Drivers issued June 22nd (most recent) have helped reduce it for me too, as well as perhaps turning OFF Dynamic Lighting, I don't like turning off Lighting 2.0 and it may also help! Still the CORE of the issue is in the STO code itself, that they hopefully are working to identify the real cause!
Not complaining, I know it takes a lot of hard work and investigation to resolve, so we can only be patient...