64-bit Crash reports looking the same.

[sharpspoonful]

I'm seeing a lot of "Write to location 03bd0000 caused an access violation." in my crash reports. I'm getting a lot of hangs when going to either the VAB or SPH, and total system freezes only managed by a hard restart. Anyone got a moment to help me pinpoint whats causing the access violation and how to manage it?

Logs:

Crash.dmp

Error.log

Output_log.txt

Report.ini

[BrutalRIP]

im getting the same issue i know this does'nt help but at least you know your not alone

[sharpspoonful]

03bd0000 looks like a memory address. If I had to guess, I'd say that the 64-bit version is still having trouble with being 64-bit and accessing too much memory.

Interesting. I wonder if this is a more unnoticed problem in 32-bit as well.

[NathanKell]

Nope, none of that has anything to do with why you crashed; that's all detritus from the Unity player closing unexpectedly.

To see what *actually* caused the crash, look at the stack trace at the bottom of output_log.txt.

In this case, it's all within the (obfuscated) stock code, and therefore yet another "KSP Windows x64 is just not stable, and doesn't deal with exceptions properly" crash.