Crashing 75% through launch

[OM3GA]

After uninstalling all of my mods, I am still stricken with an issue that not even reinstalling could fix, which causes the game to crash at 75% loading with the following crash report:

https://pastebin.com/ThdXV98E

Time-sensitive request, but any help is appreciated, as I'm sure my recruits are scared, considering I left them on a direct collision course with Sol.

[linuxgurugamer]

Assuming this is Steam, you need to open the steam directory and manually delete the GameData folder, then veify files.  Most likely there are leftover files from mods which get left behind.

[OM3GA]

Already manually deleted GameData, still got issues. I believe I may have used a mod that has corrupted or changed part of the base games launch and patch loading code, and then the broken patch loader has been updated to the Steam cloud. I still have no idea why this is happening though, as I am sure that the Steam cloud VERIFIES all files that get sent to it to make sure they are only creating a backup of base-game files, hence why I keep my saves over my three separate computers.

[VoidSquid]

I'd need the crash.dmp file for running an analysis with Windbg.

[Superfluous J]

1. Back up your saves, like in an entirely different directory.
2. Note the Steam install directory.
3. Uninstall from Steam
4. Delete that Steam install directory you noted earlier. Yes, it will still be there. Because Steam. ¯\_(ツ)_/¯
5. Install from Steam
6. Verify it launches.
7. Put your saves back.
8. Verify it launches.

If that fails... yeah we need some files. I'd personally start with the ksp.log file.

Edited September 5, 2019 by 5thHorseman

[OM3GA]

I've found the culprit! A lonesome save file! The save file was, somehow, causing the initialisation to fail part-way by making the game search for a file that didn't exist. I don't know what the file was, possibly a dependency for a mod that changed the KSC buildings or some other fundamental part of the game. I'll continue to investigate in my own time, but the issue has ultimately been resolved. Thanks for the suggestions, everyone!