Still getting 25316319 on holodeck, but good to see that others with this number is getting into tribble.
A new Nvidia driver came out today for geforce.
Gforce 331.82 Game ready driver, version 331.65
Update: I installed the new driver from Nvidia, restarted computer and tried to start the game. I made it to the same screen and it still crashed, but it gave me a "Unknown" for an error code. The most interesting part is the debug log. that I reset before I tried to load into the game.
It is as follows: [1120/075429:ERROR:backend_impl.cc(2083)] Corrupt Index file
[1120/075429:ERROR:cache_util_win.cc(43)] Unable to move the cache: 0
[1120/075429:ERROR:backend_impl.cc(134)] Unable to move cache folder C:\Program Files\Perfect World Entertainment\Star Trek Online_en\cef_cache to C:\Program Files\Perfect World Entertainment\Star Trek Online_en\old_cef_cache_000
[1120/075429:ERROR:backend_impl.cc(221)] Unable to create cache
[1120/075435:INFO:CONSOLE(0)] "Select shard: 0," source: http://launcher.startrekonline.com/static/all/js/api.js(96)
Thinking about deleting my ".patch, piggs and prepatch files and doing a new patch upload. What ya think?
My original code was: 25316319
Hope they see this.
everyone shouldn't have much of a problem the next patch that was put on tribble fixed log in issues I was able to log in as for others not sure just know they've come up a fix that's going to work on alot of people who've been having issues so far i've been able to get on tribble just not holodeck the patch should be up and done by tommorow since that's what bran said since it was done yesterday it'd be patched by tursday.
WOW!!!! Over an hour to patch, and still does not work and crashes just before LoR screen......This time the error code I got was *Unknown*......Way to go guys. Still no resolution. :mad::mad::mad::mad:
everyone shouldn't have much of a problem the next patch that was put on tribble fixed log in issues I was able to log in as for others not sure just know they've come up a fix that's going to work on alot of people who've been having issues so far i've been able to get on tribble just not holodeck the patch should be up and done by tommorow since that's what bran said since it was done yesterday it'd be patched by tursday.
There is still at least one or two outstanding error tickets but it looks like 18897741 might have been the major source issue (and still the one I am getting).
EDIT: Hoping Branflakes comes in to let us know how that ticket is progressing in being worked on. After that, I hope The Stahl gives the Team that worked on this issue the rest of the week off.
Funny. Trying to log in and get the "unknown" error code instead of the 18897741. :blink:
Oh, and the error window now closes by itself without any possibility to type anything in there.
Happened as well on Tribble as on Holodeck.
Didn't have any update to load since my last 18897741 error, though.
"I came from a time long gone, saw many other times...
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. Pop-Up Window: "You Have Been Banned For Submitting Too Many Crash Report Support Tickets"
7. Thank You For Playing STO
8. STO Crashes
9. Submit Crash Report
possibilitiesare a thing of hope,sometimes it drives us toward something better
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. Pop-Up Window: "You Have Been Banned For Submitting Too Many Crash Report Support Tickets"
7. Thank You For Playing STO
8. STO Crashes
9. Submit Crash Report
Well, I think they put a lock on that by creating the self-terminating "unknown"-error code...
"I came from a time long gone, saw many other times...
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. Pop-Up Window: "You Have Been Banned For Submitting Too Many Crash Report Support Tickets"
7. Thank You For Playing STO
8. STO Crashes
9. Submit Crash Report
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. Pop-Up Window: "You Have Been Banned For Submitting Too Many Crash Report Support Tickets"
7. Thank You For Playing STO
8. STO Crashes
9. Submit Crash Report
lmfao i know right.. but they still havent found a fix to two other tickets. hopefully they will by tomorrow.
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. Pop-Up Window: "You Have Been Banned For Submitting Too Many Crash Report Support Tickets"
7. Thank You For Playing STO
8. STO Crashes
9. Submit Crash Report
It could also go like this:
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. At the time any captain reaches his ship, THIS appears on the whole screen.
7. STO Crashes
8. Instead of an ID number, THIS LINK is generated.
9. A final message pops up: "Thank you for waiting for Star Trek Online!"
I sure as hell hope I don't get left alone in here. I seem to be the only one with this ticket number!
26531885
If you guys do get your issue fixed before I do, would you all kindly leave some reading materials and some snacks for me? Perhaps a sleeping bag? Empty threads can get mighty cold in winter.
I sure as hell hope I don't get left alone in here. I seem to be the only one with this ticket number!
26531885
If you guys do get your issue fixed before I do, would you all kindly leave some reading materials and some snacks for me? Perhaps a sleeping bag? Empty threads can get mighty cold in winter.
Got a care package for u. Ill even include a space heater! Just do the same for me.
What nobody realizes is that these glitches could all be interlinked. This Launcher crash could just open the field up to another crash loader. Remember: these all come in 3's. LOLS
possibilitiesare a thing of hope,sometimes it drives us toward something better
What nobody realizes is that these glitches could all be interlinked. This Launcher crash could just open the field up to another crash loader. Remember: these all come in 3's. LOLS
Radeon X1250...and not finding much support at all....any help?
Unfortunately there is nothing you (we) can do from our end. Only Cryptic's programmers can fix our crashes. The next patch is coming tomorrow. So fingers crossed. This is Branflakes latest update about our situation.
A "Timed Out" error AFTER crash? That is just awesome. SMH
yeah I feel special I googled the ticket number apparently my ticket was a problem in neverwinter....back in may. however there didn't seem to be a fix and even if there was its the wrong game.
Comments
Update: I installed the new driver from Nvidia, restarted computer and tried to start the game. I made it to the same screen and it still crashed, but it gave me a "Unknown" for an error code. The most interesting part is the debug log. that I reset before I tried to load into the game.
It is as follows:
[1120/075429:ERROR:backend_impl.cc(2083)] Corrupt Index file
[1120/075429:ERROR:cache_util_win.cc(43)] Unable to move the cache: 0
[1120/075429:ERROR:backend_impl.cc(134)] Unable to move cache folder C:\Program Files\Perfect World Entertainment\Star Trek Online_en\cef_cache to C:\Program Files\Perfect World Entertainment\Star Trek Online_en\old_cef_cache_000
[1120/075429:ERROR:backend_impl.cc(221)] Unable to create cache
[1120/075435:INFO:CONSOLE(0)] "Select shard: 0," source: http://launcher.startrekonline.com/static/all/js/api.js(96)
A link to my bug report with my specs, when this first started.
http://techsupport.perfectworld.com/showthread.php?t=38981
Thinking about deleting my ".patch, piggs and prepatch files and doing a new patch upload. What ya think?
My original code was: 25316319
Hope they see this.
For all who wanna see & here the resolution: Jump!
Two related compositions: Kara Remembers & All Along The Watchtower
But I think I was pretty close with my second, well hidden guess...
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
SPACE, THE PRISON OF INFINITY, THE LOST FRONTIER
There is still at least one or two outstanding error tickets but it looks like 18897741 might have been the major source issue (and still the one I am getting).
EDIT: Hoping Branflakes comes in to let us know how that ticket is progressing in being worked on. After that, I hope The Stahl gives the Team that worked on this issue the rest of the week off.
Oh, and the error window now closes by itself without any possibility to type anything in there.
Happened as well on Tribble as on Holodeck.
Didn't have any update to load since my last 18897741 error, though.
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. Pop-Up Window: "You Have Been Banned For Submitting Too Many Crash Report Support Tickets"
7. Thank You For Playing STO
8. STO Crashes
9. Submit Crash Report
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
Don't give'em any ideas.
SPACE, THE PRISON OF INFINITY, THE LOST FRONTIER
Have you even considered that Cryptic has already thought of what I posted? LOLS
(insert witty remark here)
SPACE, THE PRISON OF INFINITY, THE LOST FRONTIER
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
But that would be too simple.
lmfao i know right.. but they still havent found a fix to two other tickets. hopefully they will by tomorrow.
But I'm still a mere human."
Vice Admiral Chris Curtiss, Temporal Ambassador
Yeah I suppose it would lol. even more bizarre would be getting a nanunanu error code.
It could also go like this:
1. Load STO Launcher
2. Cryptic's Patch is applied
3. Hit "Engage"
4. STO loads
5. Reaches Character Screen
6. At the time any captain reaches his ship, THIS appears on the whole screen.
7. STO Crashes
8. Instead of an ID number, THIS LINK is generated.
9. A final message pops up: "Thank you for waiting for Star Trek Online!"
26531885
If you guys do get your issue fixed before I do, would you all kindly leave some reading materials and some snacks for me? Perhaps a sleeping bag? Empty threads can get mighty cold in winter.
Got a care package for u. Ill even include a space heater! Just do the same for me.
Radeon X1250...and not finding much support at all....any help?
It said Fatal Error: Unable to initialize on demand patching and connect to patch server the connection ws idle for too long
I get that after it crashes at the cryptic screen...ticket 14178516
A "Timed Out" error AFTER crash? That is just awesome. SMH
Unfortunately there is nothing you (we) can do from our end. Only Cryptic's programmers can fix our crashes. The next patch is coming tomorrow. So fingers crossed. This is Branflakes latest update about our situation.
yeah I feel special I googled the ticket number apparently my ticket was a problem in neverwinter....back in may. however there didn't seem to be a fix and even if there was its the wrong game.