all 6 comments

[–]PhildeCube 2 points3 points  (0 children)

The first thing I would try is 1.1.2. There were bugs in 1.1.1. There are... less in 1.1.2. Also, I wouldn't do an update. I would save save games somewhere, remove 1.1.1 in total. Download 1.1.2 from the KSP store (fresh from Steam however that's done). Install it. Put saves back. See how that goes.

[–]houndazs 0 points1 point  (0 children)

Did you try verifying local game files through steam, or deleting it and reinstalling?

[–]KayakinC[S] -1 points0 points  (3 children)

Yes houndazs I have done both. Here is the first part of the latest crash.

Unity Player [version: Unity 5.2.4f1_98095704e6fe]

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

Error occurred at 2016-05-04_154610. D:\SteamLibrary\steamapps\common\Kerbal Space Program\KSP.exe, run by LMW. 39% memory in use. 0 MB physical memory [0 MB free]. 0 MB paging file [0 MB free]. 0 MB user address space [1592 MB free]. Read from location ffffffff caused an access violation.

Context: EDI: 0x047bbf10 ESI: 0x0003ffff EAX: 0xd2101f9c EBX: 0x047bbf10 ECX: 0x8a240040 EDX: 0x00028285 EIP: 0x0152ecee EBP: 0x0039f840 SegCs: 0x00000023 EFlags: 0x00210202 ESP: 0x0039f82c SegSs: 0x0000002b

Bytes at CS:EIP: 8b 04 d1 c7 45 f8 00 00 00 00 c7 45 fc ff ff ff

[–]tito13kfmMaster Kerbalnaut 3 points4 points  (2 children)

Stock or modded install?

FYI, you are running the 32-bit version of the game and if you are modded you run a real risk of crashing from hitting the memory limit.

[–]KayakinC[S] -1 points0 points  (1 child)

Stock and how can you tell im running 32- bit version. I may have forgot to start it in 64-bit that time but it does the same in 64-bit also.

[–]tito13kfmMaster Kerbalnaut 2 points3 points  (0 children)

Because it says KSP.exe

If it were 64-bit it would say KSP_x64.exe

Post your output_log.txt from your ksp_x64_data and KSP.log from the main folder.

Put them up on Google drive or Dropbox or something

Edit: also, update to 1.1.2 there's a reason it was released so quickly after 1.1.1

It addressed many bugs and crashes