KSP keeps crashing (fixed)

[Astronaut]

I try to load my save, and KSP crashes. I went into properties and validated all files. It worked-until now.

[Astronaut]

I would like to get back to my game 😒

[Chibbity]

KSP just crashes, no error message or anything?

Did you add any new mods recently or change anything else that might be related?

Copy paste the crash log here, maybe someone will spot something of importance in it.

[Astronaut]

Sometimes a message will appear, sometimes not. No, I did not add any new mods because adding mods in the middle of a save feels cheaty. And all the crash reports that didn't show up are in fact in my KSP folder. And it's not possible to copy and paste the crash files, since they're files. But they all have one thing in common: KSP will crash when loading my save. This has happened and I went into properties and validated all files, since a few were invalid. This is done before I launch KSP everyday, so that the game will not crash. When that happened the first time, the crash report stated that there was some sort of acess error. I keep validating files before I launch KSP, but I think the Kraken threw a curveball at me.

edit: steam has an 'error' so I can't post (for now), but I can edit.
Well, the crash report was empty, so I selected the error log. This is just the top.
Unity Player [version: Unity 5.4.0p4_b15b5ae035b7]

KSP.exe caused an Access Violation (0xc0000005)
in module KSP.exe at 0023:007c0278.

Error occurred at 2017-10-03_185122.
C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by HP User.
71% memory in use.
0 MB physical memory [2146 MB free].
0 MB paging file [0 MB free].
0 MB user address space [60 MB free].
Write to location 01ffc000 caused an access violation.

Context:
EDI: 0x01ffc000 ESI: 0x5ccb8020 EAX: 0x00000000
EBX: 0x01ffc000 ECX: 0x00000000 EDX: 0x00000080
EIP: 0x007c0278 EBP: 0x016fe82c SegCs: 0x00000023
EFlags: 0x00010212 ESP: 0x016fe820 SegSs: 0x0000002b

Bytes at CS:EIP:
66 0f 7f 07 66 0f 7f 4f 10 66 0f 7f 57 20 66 0f

[Chibbity]

Originally posted by camichint:

And all the crash reports that didn't show up are in fact in my KSP folder. And it's not possible to copy and paste the crash files, since they're files.

They are text files, open them with notepad or something like that, copy the text, and paste it here.

[Knarrwinkel]

Unless you whole machine is corrupted and broken validating the game files will basically not do anything. Files the game will produce like settings or files you put there like mods will not be touched by Steam. You're using the 32 bit version so the first obvious idea would be to try if the 64 bit one works better.

And never post long logfiles into a forum. No forum was build to display megabytes of text. Upload them to a cloud service or to a dedicated site like pastebin.

[Chibbity]

Originally posted by Knarrwinkel:

Unless you whole machine is corrupted and broken validating the game files will basically not do anything. Files the game will produce like settings or files you put there like mods will not be touched by Steam. You're using the 32 bit version so the first obvious idea would be to try if the 64 bit one works better.

And never post long logfiles into a forum. No forum was build to display megabytes of text. Upload them to a cloud service or to a dedicated site like pastebin.

Since this is his thread and it serves no purpose besides troubleshooting his issue I don't see a problem with him posting the whole log here, even if it takes up a dozen pages, who cares? It's his thread. It's not hurting anyone lol.

[Technicalfool]

Aye. If you run with pretty much any kind of modding at all, you're best running KSP_x64.exe and not KSP.exe.

In addition, the official forums are a little better equipped to handle tech support-type posts. Separate sections for modded vs unmodded, plus others from the QA or dev team (and various mod authors) are more likely to read the posts. The relevant section is here: https://forum.kerbalspaceprogram.com/index.php?/forum/7-gameplay-and-technical-support/

And it does look a bit like you're running out of RAM or a mod is causing problems. Copy the whole output_log file to pastebin, dropbox or etc, and ask on the official forums. We might be able to take a deeper look at what's going on there.

[Technicalfool]

Originally posted by Chibbity:

Since this is his thread and it serves no purpose besides troubleshooting his issue I don't see a problem with him posting the whole log here, even if it takes up a dozen pages, who cares? It's his thread. It's not hurting anyone lol.

Given I've seen output logs that exceed 100MB, that may well be enough to trigger anti-spam protection. It's very much advised to upload the log to a cloud provider of some sorts (perhaps zipping excessively large files first) and link it.

[flying diomedea]

@camichint: your error.log shows 0 MB physical memory, 0 MB user address space. It doesn't occur often, but that shows the OS being tricked (no PC runs with 0 physical memory). Another user who had the same, solved the issue updating his GPU drivers. Maybe it's the same in your case, or another driver that changed since the last time KSP run correctly: worth doing a check.

In the meantime, if you suspect your savegame to be corrupted (probably not if the above diagnosis was correct), please know KSP makes regular backup saves (within your game folder is a subfolder named Backup, should hold a number of "persistent(date_time).sfs" files. Just rename your current "persisten.sfs" somehow else, put one of those in the game folder removing the "date_time" suffix and you should have a save that was certainly working with the configuration you had at that time.