test content
Logo
What is the Arc Client?
Install Arc
Options
Launcher/ Patcher CTD Problem
qordaq
Member Posts: 129 Arc User
Greetings,
Item: Cryptic Launcher Crash to Desktop. Progressively deteriorating issue since Pre-patching started for 5th Year anniversary event.
Initially, during pre-patch, after logging out of the game the launcher would pop up and attempt to pre-patch. It would get to 11% or so and freeze up.
After the 5th Anniversay Patch. I was unable to log into the game at all. Launcher starts to load, then the patcher begins and freezes for several minutes
before simply crashing to the desk top and displaying a Error Handler ticket like below.
Date: 03 Feb 2015
Error handler Ticket # 13762118
(This is like the 6th or 7th ticket number for this problem, I did not record the previous #'s)
Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [IP Address]
2 7 ms 6 ms 8 ms 10.14.200.1
3 35 ms 9 ms 7 ms ip72-214-194-81.ga.at.cox.net [72.214.194.81]
4 41 ms 50 ms 49 ms dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 33 ms 31 ms 31 ms 68.105.30.22
6 35 ms 34 ms 33 ms ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
7 41 ms 41 ms 41 ms ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62]
8 52 ms 53 ms 54 ms ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53]
9 67 ms 63 ms 63 ms ae0.mpr4.bos2.us.zip.zayo.com [64.125.20.29]
10 63 ms 63 ms 61 ms ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
11 70 ms 64 ms 63 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
12 64 ms 66 ms 75 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 74 ms 71 ms 72 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 * * * Request timed out.
15 60 ms 60 ms 61 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Trace complete.
Net Test:
Contacting nettest server..time out
hit return to exit
Pathping:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 [PC Name]
1 [IP Address]
2 10.14.200.1
3 ip72-214-194-81.ga.at.cox.net [72.214.194.81]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 68.105.30.22
6 ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
7 ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62]
8 ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53]
9 ae0.mpr4.bos2.us.zip.zayo.com [64.125.20.29]
10 ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
11 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
12 border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [IP Address]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% [IP Address]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.14.200.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% ip72-214-194-81.ga.at.cox.net [72.214.194.81]
0/ 100 = 0% |
4 47ms 0/ 100 = 0% 0/ 100 = 0% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 32ms 0/ 100 = 0% 0/ 100 = 0% 68.105.30.22
0/ 100 = 0% |
6 34ms 0/ 100 = 0% 0/ 100 = 0% ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
0/ 100 = 0% |
7 44ms 0/ 100 = 0% 0/ 100 = 0% ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62]
0/ 100 = 0% |
8 50ms 0/ 100 = 0% 0/ 100 = 0% ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53]
0/ 100 = 0% |
9 59ms 0/ 100 = 0% 0/ 100 = 0% ae0.mpr4.bos2.us.zip.zayo.com [64.125.20.29]
0/ 100 = 0% |
10 61ms 0/ 100 = 0% 0/ 100 = 0% ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
0/ 100 = 0% |
11 60ms 0/ 100 = 0% 0/ 100 = 0% 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
0/ 100 = 0% |
12 68ms 0/ 100 = 0% 0/ 100 = 0% border11.te7-1-bbnet1.bsn.pnap.net[63.251.128.41]
0/ 100 = 0% |
13 62ms 0/ 100 = 0% 0/ 100 = 0% perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
Trace complete.
Now I'll admit that I have no idea what any of this really means. I have seen where others have the same time out problem with Net Test,
but otherwise the only thing that looks "Funky" to me is the 14th line of the Tracert where there are no values followed by a timeout message.
Prior to the issues I have mentioned during the pre-patch, I was able to log in normally and play the game. I'd like to add that I was also able to patch and play on Tribble during testing without any issues as well.
Again, I don't really understand the nuances of these testing metrics, but I am guessing that the Pathping info is saying that I have no packet loss? Is that correct? Or am I miss reading and it's saying I am getting nothing?
Anyway, not really sure what else to do. I have been playing the game since open Beta and have had few real issues beyond the normal occasional disconnects and server timeouts others have mentioned--usually right around major updates and the like.
Thanks in advance for any suggestions/ help. I love STO and have really missed not being able to log in and play for the past week.
Item: Cryptic Launcher Crash to Desktop. Progressively deteriorating issue since Pre-patching started for 5th Year anniversary event.
Initially, during pre-patch, after logging out of the game the launcher would pop up and attempt to pre-patch. It would get to 11% or so and freeze up.
After the 5th Anniversay Patch. I was unable to log into the game at all. Launcher starts to load, then the patcher begins and freezes for several minutes
before simply crashing to the desk top and displaying a Error Handler ticket like below.
Date: 03 Feb 2015
Error handler Ticket # 13762118
(This is like the 6th or 7th ticket number for this problem, I did not record the previous #'s)
Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [IP Address]
2 7 ms 6 ms 8 ms 10.14.200.1
3 35 ms 9 ms 7 ms ip72-214-194-81.ga.at.cox.net [72.214.194.81]
4 41 ms 50 ms 49 ms dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 33 ms 31 ms 31 ms 68.105.30.22
6 35 ms 34 ms 33 ms ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
7 41 ms 41 ms 41 ms ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62]
8 52 ms 53 ms 54 ms ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53]
9 67 ms 63 ms 63 ms ae0.mpr4.bos2.us.zip.zayo.com [64.125.20.29]
10 63 ms 63 ms 61 ms ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
11 70 ms 64 ms 63 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
12 64 ms 66 ms 75 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 74 ms 71 ms 72 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 * * * Request timed out.
15 60 ms 60 ms 61 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Trace complete.
Net Test:
Contacting nettest server..time out
hit return to exit
Pathping:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 [PC Name]
1 [IP Address]
2 10.14.200.1
3 ip72-214-194-81.ga.at.cox.net [72.214.194.81]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 68.105.30.22
6 ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
7 ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62]
8 ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53]
9 ae0.mpr4.bos2.us.zip.zayo.com [64.125.20.29]
10 ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
11 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
12 border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [IP Address]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% [IP Address]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.14.200.1
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% ip72-214-194-81.ga.at.cox.net [72.214.194.81]
0/ 100 = 0% |
4 47ms 0/ 100 = 0% 0/ 100 = 0% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 32ms 0/ 100 = 0% 0/ 100 = 0% 68.105.30.22
0/ 100 = 0% |
6 34ms 0/ 100 = 0% 0/ 100 = 0% ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233]
0/ 100 = 0% |
7 44ms 0/ 100 = 0% 0/ 100 = 0% ae2.cr2.iah1.us.zip.zayo.com [64.125.21.62]
0/ 100 = 0% |
8 50ms 0/ 100 = 0% 0/ 100 = 0% ae14.cr2.dca2.us.zip.zayo.com [64.125.21.53]
0/ 100 = 0% |
9 59ms 0/ 100 = 0% 0/ 100 = 0% ae0.mpr4.bos2.us.zip.zayo.com [64.125.20.29]
0/ 100 = 0% |
10 61ms 0/ 100 = 0% 0/ 100 = 0% ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
0/ 100 = 0% |
11 60ms 0/ 100 = 0% 0/ 100 = 0% 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
0/ 100 = 0% |
12 68ms 0/ 100 = 0% 0/ 100 = 0% border11.te7-1-bbnet1.bsn.pnap.net[63.251.128.41]
0/ 100 = 0% |
13 62ms 0/ 100 = 0% 0/ 100 = 0% perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
Trace complete.
Now I'll admit that I have no idea what any of this really means. I have seen where others have the same time out problem with Net Test,
but otherwise the only thing that looks "Funky" to me is the 14th line of the Tracert where there are no values followed by a timeout message.
Prior to the issues I have mentioned during the pre-patch, I was able to log in normally and play the game. I'd like to add that I was also able to patch and play on Tribble during testing without any issues as well.
Again, I don't really understand the nuances of these testing metrics, but I am guessing that the Pathping info is saying that I have no packet loss? Is that correct? Or am I miss reading and it's saying I am getting nothing?
Anyway, not really sure what else to do. I have been playing the game since open Beta and have had few real issues beyond the normal occasional disconnects and server timeouts others have mentioned--usually right around major updates and the like.
Thanks in advance for any suggestions/ help. I love STO and have really missed not being able to log in and play for the past week.
Post edited by qordaq on
0
Comments
A 60 MS ping to the server is not bad at all. You seem to be fine there.
What is more likely is an incompatible graphics card/driver or some other similar hardware problem and the game. There seems to be at least one, if not a couple, of PC setups that get crashed to desktop since the 5yr patch. AFAIK the cause is not yet known and there is not yet a fix for it. Other machines work fine all day long.
Not sure what to tell you... keep an eye on the player threads about these issues, maybe someone will have a soon.
Not so sure about this....
The 'Net Test' diagnostics talks to a simple diagnostic server located on the same local network as the STO Servers. If 'Net Test' can't establish a connection to a simple diagnostic server, (so the STO Servers are out of the picture here...) its unlikely the STO Client can establish a connection to the STO Patch Servers...
Now what could be causing this? Its not a Graphics issue since 'Net Test' is a Command Line Text only application that doesn't use advance graphics...
'Net Test' is attempting to make the connection, so your Computer's DNS service was able to resolve the hard-coded diagnostic server name into a IP Address....
Now the 'Path Ping' isn't showing any dropped packets, so that's not blocking the connections...
So its looking more and more as if the problem is something systemic with your system...
hings that can block the 'Net Test' (and the STO Client) connection could be...
One thing you could try is to boot your system into 'Safe' mode with networking, and see if STO runs properly. This would check if your system is running a conflicting application/utility...
So the first thing I tried was updating the driver for my graphics card, guess what; it worked Doh!
...*Shakes head in embarrassment*...
I guess something in the updated launcher must have been relying on that.
So, I'll still need to play for a bit to confirm stability and all, but I was able to patch, load, and select a Character... Then actually log into the game. I'll update if there are any additional issues.
Again, thanks for taking the time to assist.
maj! {Klingon word for "Good"}
Operations Team, 12th Fleet