test content
What is the Arc Client?
Install Arc

STO crashing repeatedly. have command prompt information requested.

STO continues to repeatedly crash while every other game on my computer plays normally, without issues. I've tried force-verifying, proxies, setting to minimum graphics, deleting gameprefs file, as well as uninstalling/reinstalling the game (twice). nothing is working. it doesn't seem like cryptic is aware of the issue, as the problem persists after the last round of server downtime and maintenance.

the game client will run for anywhere between 5 and 30 minutes, before the game freezes, and a crash report window appears.

the following data is the DMP tests requested for these bug reports.


TRACERT results

Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:

1 5 ms 2 ms 2 ms 192.168.2.1
2 46 ms 55 ms 54 ms 10.199.22.1
3 46 ms 45 ms 44 ms gateway-pc10-lehBlocal1.tv13.ptd.net [207.44.120.73]
4 205 ms 64 ms 46 ms gateway2-p1-chi22chi.chi.ptd.net [207.44.112.102]
5 124 ms 96 ms 70 ms 64.125.54.237.available.above.net [64.125.54.237]
6 89 ms 99 ms 94 ms 209.133.7.66.IPYX-143212-002-ZYO.zip.zayo.com [209.133.7.66]
7 171 ms 136 ms 118 ms po110.bs-a.sech-ord.netarch.akamai.com [23.57.98.243]
8 92 ms 119 ms 161 ms a72-52-1-159.deploy.static.akamaitechnologies.com [72.52.1.159]
9 754 ms 406 ms 50 ms ae120.access-a.sech-ord.netarch.akamai.com [23.57.98.249]
10 131 ms 119 ms 178 ms 93.191.173.221
11 127 ms 58 ms 114 ms a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
12 143 ms 169 ms 49 ms 198.49.243.237
13 93 ms 91 ms 97 ms patchserver.crypticstudios.com [208.95.184.200]

Trace complete.

NOTE: lines that show values above 180ms: 4, 9.


NETTEST results

Ping: 46.2 msec
Port: 80: 1029 KB/sec 46 KB/sec 1095 KB/sec 500
Port: 80: 916 KB/sec 52 KB/sec 974 KB/sec 500
Port: 443: 935 KB/sec 42 KB/sec 994 KB/sec 500
Port: 443: 1007 KB/sec 48 KB/sec 1071 KB/sec 500
Port: 7255: 986 KB/sec 45 KB/sec 1047 KB/sec 500
Port: 7255: 962 KB/sec 39 KB/sec 1021 KB/sec 500
Port: 7003: 817 KB/sec 36 KB/sec 867 KB/sec 500
Port: 7003: 945 KB/sec 42 KB/sec 1004 KB/sec 500
Port: 7202: 1078 KB/sec 55 KB/sec 1147 KB/sec 500
Port: 7202: 1059 KB/sec 46 KB/sec 1125 KB/sec 500
Port: 7499: 830 KB/sec 35 KB/sec 880 KB/sec 500
Port: 7499: 1002 KB/sec 42 KB/sec 1064 KB/sec 500
Port: 80: 1002 KB/sec 45 KB/sec 1064 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec

NOTE: all port numbers, all columns report above average results. also i deleted my local ip from these results. i don't feel comfortable posting it here.


PATHPING results

Microsoft Windows [Version 10.0.17134.765]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>pathping patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.184.200]
over a maximum of 30 hops:
0 LAPTOP-9A4C7G9O.Belkin [192.168.2.4]
1 192.168.2.1
2 10.199.22.1
3 gateway-pc10-lehBlocal1.tv13.ptd.net [207.44.120.73]
4 gateway2-p1-chi22chi.chi.ptd.net [207.44.112.102]
5 64.125.54.237.available.above.net [64.125.54.237]
6 209.133.7.66.IPYX-143212-002-ZYO.zip.zayo.com [209.133.7.66]
7 po110.bs-a.sech-ord.netarch.akamai.com [23.57.98.243]
8 a72-52-1-159.deploy.static.akamaitechnologies.com [72.52.1.159]
9 ae120.access-a.sech-ord.netarch.akamai.com [23.57.98.249]
10 93.191.173.221
11 a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
12 198.49.243.237
13 patchserver.crypticstudios.com [208.95.184.200]

Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 LAPTOP-9A4C7G9O.Belkin [192.168.2.4]
0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% 10.199.22.1
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% gateway-pc10-lehBlocal1.tv13.ptd.net [207.44.120.73]
0/ 100 = 0% |
4 43ms 0/ 100 = 0% 0/ 100 = 0% gateway2-p1-chi22chi.chi.ptd.net [207.44.112.102]
0/ 100 = 0% |
5 335ms 0/ 100 = 0% 0/ 100 = 0% 64.125.54.237.available.above.net [64.125.54.237]
0/ 100 = 0% |
6 54ms 0/ 100 = 0% 0/ 100 = 0% 209.133.7.66.IPYX-143212-002-ZYO.zip.zayo.com [209.133.7.66]
0/ 100 = 0% |
7 44ms 0/ 100 = 0% 0/ 100 = 0% po110.bs-a.sech-ord.netarch.akamai.com [23.57.98.243]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% a72-52-1-159.deploy.static.akamaitechnologies.com [72.52.1.159]
0/ 100 = 0% |
9 46ms 0/ 100 = 0% 0/ 100 = 0% ae120.access-a.sech-ord.netarch.akamai.com [23.57.98.249]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% 93.191.173.221
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% a72-52-27-212.deploy.static.akamaitechnologies.com [72.52.27.212]
0/ 100 = 0% |
12 52ms 0/ 100 = 0% 0/ 100 = 0% 198.49.243.237
0/ 100 = 0% |
13 49ms 0/ 100 = 0% 0/ 100 = 0% patchserver.crypticstudios.com [208.95.184.200]

Trace complete.


not sure what to make of some of this data.

Comments

  • kyrutitankyrutitan Member Posts: 2 Arc User
    note- you requested i put this stuff into a txt file. but i saw no function here that allows me to attach files.
  • sthe91sthe91 Member Posts: 5,443 Arc User
    The problem is not necessarily Cryptic's servers but Akamai Technologies. I have the same problem and that is where the packet loss is nowhere else does it exist in that route.
    Where there is a Will, there is a Way.
  • trekpuppytrekpuppy Member Posts: 446 Arc User
    edited May 2019
    sthe91 wrote: »
    The problem is not necessarily Cryptic's servers but Akamai Technologies. I have the same problem and that is where the packet loss is nowhere else does it exist in that route.

    If it's traceroute you're using, remember that it only shows replies from the ingress interface of a router. You can't see if the packet loss happens on the egress interface without doing a traceroute in the opposite direction at the same time. If it's a border gateway, the egress interface may have an IP from Akamai's peering partner and thus be the responsibility of that partner.

    The 100% packet losses reported in the example in the OP is not a sign of an error. Just a router configured not to process the packets that traceroute generates. If it were an error you wouldn't get any replies from routers behind Akamai.

    EDIT: Swapped ingress for egress. Stupid noob mistake :)
    Post edited by trekpuppy on
    ---
    "-Grind is good!" --Gordon Geko
    Accolades checklist: https://bit.ly/FLUFFYS
  • sthe91sthe91 Member Posts: 5,443 Arc User
    edited May 2019
    trekpuppy wrote: »
    sthe91 wrote: »
    The problem is not necessarily Cryptic's servers but Akamai Technologies. I have the same problem and that is where the packet loss is nowhere else does it exist in that route.

    If it's traceroute you're using, remember that it only shows replies from the egress interface of a router. You can't see if the packet loss happens on the ingress interface without doing a traceroute in the opposite direction at the same time. If it's a border gateway, the ingress interface may have an IP from Akamai's peering partner and thus be the responsibility of that partner.

    The 100% packet losses reported in the example in the OP is not a sign of an error. Just a router configured not to process the packets that traceroute generates. If it were an error you wouldn't get any replies from routers behind Akamai.

    When I did my post I did not just use traceroute, I used all of them there is a problem with Akamai Technologies, I am very sure about it. No one every told me to go backwards from Cryptic Studios to my place. I will update the post I made before with the relevant info after doing what you suggested. So much work to find out what the problem is. It is so aggravating! :(

    P.S. I give up. How do you do it? I wish these problems would go away. I used to not have these problems until many patches ago and then everything has gone haywire since then.
    Post edited by sthe91 on
    Where there is a Will, there is a Way.
Sign In or Register to comment.