I am so tired of the game constantly kicking me out to the desktop every time I enter a new map, especially since I also have the problem of my graphics being reset to default settings every time I relaunch the game! I have crashed to desktop from:
ESD (ground/space)
Qo'noS (ground/space)
Drozana (ground/space)
Dyson Sphere (all zones)
Nukara
New Romulus (ground/space)
various other zones and sector blocks.
PLEASE try to fix this! It's been a problem since the start of Season 9, and since I haven't seen it on any "known issues" list, I have to assume it's either only happening to me or it just hasn't gotten enough attention yet.
Nitpicking is a time-honored tradition of science fiction. Asking your readers not to worry about the "little things" is like asking a dog not to sniff at people's crotches. If there's something that appears to violate natural laws, then you can expect someone's going to point it out. That's just the way things are.
That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.
I get no specific message, only one saying the game has crashed. I get kicked out of the game, back to the desktop, with no warning, and I get a crash report. It only happens during a loading screen, when I'm transferring to a new map. When I start the game back up, the launcher begins a process that takes about 20 minutes saying "Verifying Files". It doesn't seem to fix anything, because I keep crashing over and over again.
My KDF character is currently stuck in the space zone of Qo'noS because the game either crashes during the loading screen when I load the character or I manage to get into the game for long enough to hit a transfer to ground or sector space, both of which crash during their loading screens. So, I'm effectively trapped. Thankfully, I've managed to avoid this on my Fed and Rom characters.
I don't think it's a problem with my computer, because the game ran perfectly before the release of Season 9. It happened on Tribble as well, I would constantly crash from various maps, and the Holodeck server would be running fine. I thought it was just problems with the test server, but then it started happening on Holodeck on release.
It *could* be possible that you might have problems with certain software packages which STO is dependant on (f.e. directx, graph drivers, chipset drivers, etc). Have you tried opening eventviewer (run => eventvwr) and search for any information concerning STO crashing?
You might get a 0x0001234 code which could point you to the culprit.
That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.
Comments
Joined January 2009
I call it, the Stoutes paradox.
My KDF character is currently stuck in the space zone of Qo'noS because the game either crashes during the loading screen when I load the character or I manage to get into the game for long enough to hit a transfer to ground or sector space, both of which crash during their loading screens. So, I'm effectively trapped. Thankfully, I've managed to avoid this on my Fed and Rom characters.
I don't think it's a problem with my computer, because the game ran perfectly before the release of Season 9. It happened on Tribble as well, I would constantly crash from various maps, and the Holodeck server would be running fine. I thought it was just problems with the test server, but then it started happening on Holodeck on release.
You might get a 0x0001234 code which could point you to the culprit.
I call it, the Stoutes paradox.