Crashing on force verify and in game.

couch222 · January 2019

I haven't been able to get on since the last pre patch came out. I let that run and close on completion. Now, whenever i log in i crash (usually get 60s in game). Whenever i try and force verify the launcher crashes. I have on demand patching off and still nothing. Is this a known issue? Any ideas?

alesstorm · January 2019

2 days traying to log in to game. It crashes on starting. 64 bit eror something. Win10 here. Reinstall it 3 times already. Install...patch ... engage.. crash. Cryptic errorX64

ekypyros · January 2019

Try in Launcher Options Safemode for first run !

alesstorm · January 2019

ekypyros wrote: »

Try in Launcher Options Safemode for first run !

I try anything already. And many times.
Crashes on start up.

alesstorm · January 2019

I am 40 years old. And I have a computer technical education. 2 days I tried to start this game. Tried everything. This game has no support. And it does not work. I wanted to play it after six years of a break. But now I give up. On the fact that it simply is not possible.

defianttron · January 2019

> @alesstorm said:
> I am 40 years old. And I have a computer technical education. 2 days I tried to start this game. Tried everything. This game has no support. And it does not work. I wanted to play it after six years of a break. But now I give up. On the fact that it simply is not possible.

I tried to come back after years to today too, I have the same issue as this, I installed arc and began install of STO and it hard crashes my PC...

wtf.

alesstorm · January 2019

190123 16:29:08 2843 [1]: ERROR: HTTP patching problem (BadHttpResponse):

190123 15:40:42 1 [1]: Using HTTP patching: server level3.stohttppatch.crypticstudios.com port 80 prefix Startrek
190123 15:40:47 2 [1]: Syncing required files
190123 15:40:47 3 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/bins3.hogg
190123 15:40:47 4 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/bins2.hogg
190123 15:40:47 5 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/bins.hogg
190123 15:40:47 6 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/character.hogg
190123 15:40:47 7 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/object.hogg
190123 15:40:47 8 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/sound.hogg
190123 15:40:47 9 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/texture3.hogg
190123 15:40:47 10 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/texture2.hogg
190123 15:40:47 11 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/texture.hogg
190123 15:40:47 12 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/data.hogg
190123 15:40:47 13 [1]: Scanning hogg C:/Games/Star Trek/Star Trek Online_en/Star Trek Online/Live/piggs/exes.hogg
190123 15:40:48 14 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62098)
190123 15:40:48 15 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62101)
190123 15:40:48 16 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62097)
190123 15:40:48 17 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62099)
190123 15:40:48 18 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62100)
190123 15:40:48 19 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62102)
190123 15:40:58 20 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 12 completed responses (localport=62101): socket was shutdown:linkQueueRemove(0:No error)
190123 15:40:58 21 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62104)
190123 15:40:59 22 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 2 completed responses (localport=62104): socket was shutdown:linkQueueRemove(0:No error)
190123 15:40:59 23 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62105)
190123 15:41:00 24 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 14 completed responses (localport=62099): socket was shutdown:linkQueueRemove(0:No error)
190123 15:41:02 25 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62106)
190123 15:41:43 26 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 84 completed responses (localport=62100): socket was shutdown:linkQueueRemove(0:No error)
190123 15:41:43 27 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62108)
190123 15:42:25 28 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 131 completed responses (localport=62108): socket was shutdown:linkQueueRemove(0:No error)
190123 15:42:25 29 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62121)
190123 15:42:25 30 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 5 completed responses (localport=62121): socket was shutdown:linkQueueRemove(0:No error)
190123 15:42:25 31 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62122)
190123 15:42:25 32 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 2 completed responses (localport=62122): socket was shutdown:linkQueueRemove(0:No error)
190123 15:42:26 33 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62123)
190123 15:42:26 34 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 4 completed responses (localport=62123): socket was shutdown:linkQueueRemove(0:No error)
190123 15:42:26 35 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62124)
190123 15:42:27 36 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 6 completed responses (localport=62124): socket was shutdown:linkQueueRemove(10054:Connection reset by remote host)
190123 15:42:27 37 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62152)
190123 15:42:27 38 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 2 completed responses (localport=62152): socket was shutdown:linkQueueRemove(10054:Connection reset by remote host)
190123 15:42:27 39 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62153)
190123 15:42:27 40 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 2 completed responses (localport=62153): socket was shutdown:linkQueueRemove(0:No error)
190123 15:42:27 41 [1]: HTTP patching connected to level3.stohttppatch.crypticstudios.com:80 (localport=62154)
190123 15:42:27 42 [1]: HTTP patching disconnected from level3.stohttppatch.crypticstudios.com:80 after 1 completed responses (localport=62154): socket was shutdown:linkQueueRemove(0:No error)
190123 15:42:27 43 [1]: HTTP patching failed for data/texture_library/Space/Sector/Sector_Gridlines_10_Circle_D.wtex: too many retries on HTTP xfer

alesstorm · January 2019

ayrsayle · January 2019

This is funny, this morning it worked like anyday, until last update, then, started to crash.

eladamd · January 2019

ticket submitted cryptic loader keeps failing since TODAY's update, verified all files, running through steam. HELP....
SOS... Aye captn thar be a wee bit of a problem.

eladamd · January 2019

ayrsayle#7924 wrote: »

This is funny, this morning it worked like anyday, until last update, then, started to crash.

same here...

eladamd · January 2019

eladamd#2673 wrote: »

ticket submitted cryptic loader keeps failing since TODAY's update, verified all files, running through steam. HELP....
SOS... Aye captn thar be a wee bit of a problem.

Update background cryptic reporting tool :
Initializing...
Attaching to crashed process...
Harvesting data from crashed process...
Mode: Customer
Communicating with Cryptic Error Tracker...
Terminating crashed process...
Sending Diagnostic Information...
Cleaning up...
Cleanup Complete!
Waiting for description...
Sending Description...
Description Sent.
All Error Reporting Complete!

eladamd · January 2019

ticket 136591927 again... used -safemode...

eladamd · January 2019

[0109/200805:ERROR:backend_impl.cc(134)] Unable to move cache folder E:\Program Files (x86)\Steam\SteamApps\common\Star Trek Online\cef_cache to E:\Program Files (x86)\Steam\SteamApps\common\Star Trek Online\old_cef_cache_000
[0109/200805:ERROR:backend_impl.cc(221)] Unable to create cache
[0109/200823:INFO:CONSOLE(0)] "Select shard: 3," source: http://launcher.startrekonline.com/static/all/js/api.js(157)
[0110/221129:INFO:CONSOLE(0)] "Uncaught ReferenceError: LauncherAPI is not defined," source: about:blank(1)
[0110/221129:ERROR:backend_impl.cc(2083)] Corrupt Index file
[0110/221129:ERROR:cache_util_win.cc(43)] Unable to move the cache: 0
[0110/221129:ERROR:backend_impl.cc(134)] Unable to move cache folder E:\Program Files (x86)\Steam\SteamApps\common\Star Trek Online\cef_cache to E:\Program Files (x86)\Steam\SteamApps\common\Star Tre

eladamd · January 2019

ok manually went in and renamed not lets see...

centaurianalpha · January 2019

Force verify, SafeMode, proxy, restart PC...nothing is working! Game got to character selection screen the firat time, and proptly crashed to desktop. So much for spending any more $$ on in-game items....

spellblind · January 2019

This is always the same. I had this issue now over a month EVERYTIME they did an update.
When will they learn NOT to ruin the whole gamestartup again and again ?
Guess everybody would be ok with some temporary graphics issues or something like that.
But don't even let the complete game startup is the wrong verification method.

jimduval · January 2019

When all else fails it can mean that it is an windows related problem. Maybe some patch that turned certain files to read only where the game needs them to be fully accessible for example. Or maybe some of the windows registry files that got messed up just too much for the game to make sense out of it.

The first problem can be solved by some tool, not sure how it is called but is allows you to take back control over the machine and files.

The second is not as easy to fix but still is something an reinstall of windows will fix.

I must say tho, this no support from cryptic is worrying to me, in the past month or so i have seen many people reporting the same problems over and over again and none received support from cryptic not even a notice of them being aware and working on a possible fix nothing

I do hope you guys do manage to get back into game with these tips tho, to all of you good luck trying to get it back to work and who knows we might meet some time in game

Friendly regards from,
Jim

defianttron · January 2019

> @"jimduval#7537" said:
> When all else fails it can mean that it is an windows related problem. Maybe some patch that turned certain files to read only where the game needs them to be fully accessible for example. Or maybe some of the windows registry files that got messed up just too much for the game to make sense out of it.
>
> The first problem can be solved by some tool, not sure how it is called but is allows you to take back control over the machine and files.
>
> The second is not as easy to fix but still is something an reinstall of windows will fix.
>
> I must say tho, this no support from cryptic is worrying to me, in the past month or so i have seen many people reporting the same problems over and over again and none received support from cryptic not even a notice of them being aware and working on a possible fix nothing :(
>
> I do hope you guys do manage to get back into game with these tips tho, to all of you good luck trying to get it back to work and who knows we might meet some time in game :) Friendly regards from,
> Jim

Not worth the effort anymore, I am done with this game, disgusted by lack of reply from any dev whatsoever. Loads of players can not play, install the game or even patch the client without locking out freezing their whole PC or having nothing but client / patcher crashes.

Not worth the effort anymore, so done.

centaurianalpha · January 2019

Any bugfix that requires re-installing the OS is unacceptable. It just points out how poorly the patch was planned & executed. Over 1000 tickets this month so far, and counting, no response on mine yet...

jimduval · January 2019

centaurianalpha wrote: »

Any bugfix that requires re-installing the OS is unacceptable. It just points out how poorly the patch was planned & executed. Over 1000 tickets this month so far, and counting, no response on mine yet...

I agree in full with it being poorly made but as cryptic show no sign of fixing this or even acknowledge the problem so the only way to get back into game is by the suggestions i offered, it is fine you wont make use of them but then it also means you will not get back into the game for any time soon

spellblind · January 2019

Hey guys i found a"quick" fix.
Go to your StarTrekOnline_en folder right click, properties and unckeck that writeprotection box (may have different name as i dont have english OS). Make sure it is completely clear. You may have to click 2 time sinto the box. Then apply. Now open the folder and do that too to all 5 folders inside. Last but not least enter the Star Trek Online folder and do it to all the remaining folders in it. Now go back to the Star Trek Online_en folder and right click to Star Trek Online.exe (teh executable file with a color icon), properties, compatibility, bottom button settings for all users, Compatibility Mode Windows 7 and bottum box run as administrator.
Let the Launcher do the full check again and enjoy the game opening without crash.

Sorry i forget to tell: start Star Trek Online.exe from the folder with right click run as administrator. Dont use the Arc Prelauncher

alesstorm · January 2019

Problem solved.
1) Run Star Trek online under Administrator.
2) Turn Patch on demend OFF.
3) Turn proxi server form EU to No proxi.
4) Turn Rive tuner statistik server and Afterberner OFF. Game will not start with MSI Afterburner on.
5) Set safe mode On on the first start up.
6) Under any surcumstances DO NOT set Full Screen ON on first start up.

spellblind · January 2019

> @alesstorm said:
> Problem solved.
> 1) Run Star Trek online under Administrator.
> 2) Turn Patch on demend OFF.
> 3) Turn proxi server form EU to No proxi.
> 4) Turn Rive tuner statistik server and Afterberner OFF. Game will not start with MSI Afterburner on.
> 5) Set safe mode On on the first start up.
> 6) Under any surcumstances DO NOT set Full Screen ON on first start up.

indeed. Looks like the MSI Afterburner somehow causes a problem.

centaurianalpha · January 2019

Tried running STO as Admin. - no result
Tried reinstalling Win 7 Pro 64-bit OS - no result
Tried running STO in Win 7 compatibility mode - no result
Submitted error code (142777685) info to Support, no answer yet

Result - no STO, no more purchase of ZEN (I'm a LTS with literally $1000's spent in-game); STO quit me, not the other way 'round...

ekypyros · January 2019

centaurianalpha wrote: »

Tried running STO as Admin. - no result
Tried reinstalling Win 7 Pro 64-bit OS - no result
Tried running STO in Win 7 compatibility mode - no result
Submitted error code (142777685) info to Support, no answer yet

Result - no STO, no more purchase of ZEN (I'm a LTS with literally $1000's spent in-game); STO quit me, not the other way 'round...

PPL when the launcher Crash !

1.) Browse with file Explorer to STO Folder 
2.) Make right click on Folder
3.) Choose Preference 
4.) Remove Write protection from All Folders and sub-folders "checkbox"  (that's times a little.....)
5.) Say Yes to all Ask !
6.) Run the Launcher Again !

killerdragon79 · January 2019

This crashing is doing my nut in, seriously guys guys, it's happening constantly and now I can't get into the game, Please sort this!

joreliadon · January 2019

Just to recap: since last week right before the Anniversary event update, Launcher crashes the pc after login.
PS: Windows 7 Sp1 on I7-5820K 12 cores 32 Gb ram SSD - never issues before
- Tried running STO as Admin. - crashes during patching or just after launch after login.
- Tried reload of files - crashes during patching or just after launch after login.
- Tried reinstalling with Steam client - Same effect
- Tried reinstalling with Arc client - Same effect
- Tried reinstalling Win 7 Pro 64-bit OS - Sp1 - No change, crashing
- Tried running STO in Win 7 sp1 vmware - Downloader launches and crashes before even i type login.
- Tried running STO in Win X on wife's PC (monster PC with AMD Ryzen 12 cores) with windows 10. Same exact thing.

Bottom line: the new installer/downloader executable (rather then the patch) is bugged broken. I cannot get in game using my computers and I cannot get older donwloaders to run without updating to the bugged one.

I am missing the anniversary event and I already missed the freebies. Will probably miss the ship as well this year too.

What the -beep- ARC? CRYPTIC? WHOEVER? FIX THIS !!!! FIX THIS NOW !!! COMPENSATE FOR THIS DAMAGE !!!

ekypyros · January 2019

[/quote]

joreliadon wrote: »

Just to recap: since last week right before the Anniversary event update, Launcher crashes the pc after login.
PS: Windows 7 Sp1 on I7-5820K 12 cores 32 Gb ram SSD - never issues before
- Tried running STO as Admin. - crashes during patching or just after launch after login.
- Tried reload of files - crashes during patching or just after launch after login.
- Tried reinstalling with Steam client - Same effect
- Tried reinstalling with Arc client - Same effect
- Tried reinstalling Win 7 Pro 64-bit OS - Sp1 - No change, crashing
- Tried running STO in Win 7 sp1 vmware - Downloader launches and crashes before even i type login.
- Tried running STO in Win X on wife's PC (monster PC with AMD Ryzen 12 cores) with windows 10. Same exact thing.

Bottom line: the new installer/downloader executable (rather then the patch) is bugged broken. I cannot get in game using my computers and I cannot get older donwloaders to run without updating to the bugged one.

I am missing the anniversary event and I already missed the freebies. Will probably miss the ship as well this year too.

What the -beep- ARC? CRYPTIC? WHOEVER? FIX THIS !!!! FIX THIS NOW !!! COMPENSATE FOR THIS DAMAGE !!!

ekypyros wrote: »
centaurianalpha wrote: »

Tried running STO as Admin. - no result
Tried reinstalling Win 7 Pro 64-bit OS - no result
Tried running STO in Win 7 compatibility mode - no result
Submitted error code (142777685) info to Support, no answer yet

Result - no STO, no more purchase of ZEN (I'm a LTS with literally $1000's spent in-game); STO quit me, not the other way 'round...
PPL when the launcher Crash !

1.) Browse with file Explorer to STO Folder 
2.) Make right click on Folder
3.) Choose Preference 
4.) Remove Write protection from All Folders and sub-folders "checkbox"  (that's times a little.....)
5.) Say Yes to all Ask !
6.) Run the Launcher Again !

centaurianalpha · January 2019

PPL when the launcher Crash !

1.) Browse with file Explorer to STO Folder 
2.) Make right click on Folder
3.) Choose Preference 
4.) Remove Write protection from All Folders and sub-folders "checkbox"  (that's times a little.....)
5.) Say Yes to all Ask !
6.) Run the Launcher Again !

After I reinstalled Win 7 Pro 64-bit, for some reason the system will not allow me Admin permissions for some functions, despite the fact that my one account is listed as an Admin account. So, when I try to uncheck the "Read Only" boxes, they immediately revert back, and I also cannot run CHKDSK.

So, I went back to a ticket response from last summer, and it turns out that by deleting the /Star Trek Online/Live/pigs/bins.hogg file, then letting the launcher force-verify and patch, the file was fixed, and I'm back online. In fact, it turns out that apart from running CHKDSK or doing a computer restart, this is the best way to fix the "ERROR: DV: cannot find patchxfer" file problem. I'm just glad I didn't clear out my ticket history before now!

centaurianalpha · January 2019

(sorry, double-post)

Crashing on force verify and in game.

Comments