Continual crashes - any response from FDEV?

Status
Thread Closed: Not open for further replies.
Just on a hunch, I backed my CPU down a bit and viola, no more crashing.

Feels like a critical timing issue that isn't giving the options file mentioned above enough time to write properly if you're overclocked.

No other problems were evident on my PC @ 40.0 CCX but I backed it down to 38.0 on my 5900X just to see if it would help. Stable for about an hour now, so call it a win.

Still got a CTD on exit. Might see if 37 which is no OC might eliminate the close CTD.

Handing in missions = CTD

Dropping to CPU default clock
 
After I reset the files using the launcher (and, switched to Horizons and back), I had to confirm and accept the recommended default graphic values. Any possibility there is a graphic setting getting turned back up and triggering it? Just a thought. Good luck all

p.s. I also continue having some "adjudication" and "transaction" I think disconnects during the game, distinct from the game crashing during loading.
 
Last edited:
Some findings - deleting the file in %appdata%/roaming/Frontier Developments/Elite Dangerous/Options works for some for others it just makes it crash during planetary generation.
Launching the Launcher as Administrator will likely get you into the game and let you load in but the issue with turning in missions still persists, my guess it's something with the transactions not getting acknowledged properly and not something you can tinker your way into fixing.

This is after wiping the game (deleted all steam files, files in %appdata&, files in my documents) and updating GPU drivers.

So yeah, this update is a massive dumpster fire and the reason why you don't push stuff into production on a Friday.
 
Last edited:
No joy handing in missions. Causes CTD after prolonged standby.

Fortunately the mission does get counted, but restarting after every hand in is getting old quick.

I'm at stock CPU settings and deleted modifications to the graphics overide xml.

No fun

I guess nothing will be forthcoming until Monday at the earliest.

I'm out till it gets fixed.

Have a great weekend
 
Last edited:
Same thing here, I go to hand in a mission, select the reward type, get a spinning orange star for 20 seconds and then kicked back to the desktop with the Frontier error reporting window. I'm running the none Steam version using the ED Launcher on Windows 10 with the latest updates. I tried verifying file integrity, rebooting my machine and making sure my anti-virus skips and doesn't monitor all Frontier folders and game files. Last crash I had was at 8:30PM EST.

Windows 10 64bit
Aorus Z690 Master MB
i9 13900K
EVGA 3090 Ti FTW 3 24 GB
64 GB G.Skill Trident DDR5 7200
EVGA 1500W Supernova PSU
2X Samsung 980 Pro 2TB M.2
4X Samsung 870 Evo 2TB SSD
 
It's not your overclocked CPU/GPUs. It's not on your end. This is affecting a vast number of CMDRs, undoubtedly running in a myriad of configurations.
For many of us, the game runs fine until you try to turn-in missions. I have been running for hours without issue, doing CZs, just not turning-in my missions.
Reinstalling the game is a waste of your time.

The discons I have had have been Blue Cobras (adjudication server problems).
 
I'm getting a CTD every time I hand in a mission. I can't tell if the missions are being counted because they don't show up in my logs and the BGS Talley app doesn't see them. I guess I could try checking the credits, but I haven't been paying attention to them.
 
im sorry but do you expect them to say something like "hey ho we figured it out in the first 10 minutes, it will be fixed on august 20th 18:34"?
no. it was a joke. and sarcasm. so chill. what I expect: I expect that they will continue to live up to their reputation. and it's been over 2 days, not 10 minutes, since they created this self-inflicted problem; they messed things up in less than a week, so they should be able to unf fix it in less than a week. Have a great day.
 
I have two laptops. Both had a pile of Windows updates last night which were run to completion. They both also had nVidia driver updates to 536.99. One is an i7-4710HQ and GTX980M and crashes every time. The other is a Ryzen 9 5900HX and RTX3080 and has not crashed once, although I did get a "Blue Cobra" on one occasion.
 
I'm getting a CTD every time I hand in a mission. I can't tell if the missions are being counted because they don't show up in my logs and the BGS Talley app doesn't see them. I guess I could try checking the credits, but I haven't been paying attention to them.
They are, I did see my credit balance go up after turning a bunch of them in (and yeah CTD on every single one). My guess is that something screws up on whatever calls the transition into the reward screen or something related like logging because it obviously gets reported to the server, then it spins for 20 seconds, and then it crashes. Can't exactly hook up a debugger to it.
I have two laptops. Both had a pile of Windows updates last night which were run to completion. They both also had nVidia driver updates to 536.99. One is an i7-4710HQ and GTX980M and crashes every time. The other is a Ryzen 9 5900HX and RTX3080 and has not crashed once, although I did get a "Blue Cobra" on one occasion.
How's turning in missions for you? For me things look stable aside for that, so if you're out mining or exploring you're probably fine, if you're stacking massacres you'll be pulling your hair out.
 
Glad this thread is here. Also encountering crash to desktop when completing missions. Started tonight for me. At first I assumed it was something on my end because the game is usually extremely stable for me. Steam here so I validated all game files and re-started. Game crashed again on mission completion / hand in for reward.

I guess I'll just play something else and keep checking on on this thread and the issue tracker (https://issues.frontierstore.net/issue-detail/61281).
 
I wish i could try to complete missions :) is just straight CTD before i even get to the title menu.... gets through the planetary surface generation then blam.

No overclocking or anything.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom