Brigadier

Likewise, thanks.

Well, as far as the re-entry heating is concerned, since I understand the heating algorithms have been significantly changed with the 1.0.x releases, try using a heat shield on the re-entry vehicle. The parachute is now burning up if you release it too soon (this happened to me until I understood the more realistic physics being applied to re-entry), so wait until the heating effects are gone before deploying. Right click on the parachute before deploying and look for the recommendation on chute deployment in the part window (I've seen Unsafe, Risky and Ok flags so far). I've also noticed that the SAS modes are much more sensitive. I tend to leave SAS ON and manually adjust the vehicle orientation on descent or use RETROGRADE but sometimes my capsule flips, even with a nose cone chute. It also means watching your battery power carefully.

I had the same error and, according to the error.log file, it appears you have a 4GB system. Try reducing the window resolution in Settings before running the game. This solved the problem for me.

I think I may have resolved this. I decreased the window screen resolution from 1360x1024 to 1280x1024 and turned anti-aliasing from 2x to off. Ran for 8 uninterrupted hours. Next, I'll increase each of these one at a time to see what my limitation is. I guess I might need a new gfx card.

KSP: 1.0.4 (Steam) Windows 7 SP 1 32-bit Problem: KSP crashes frequently, often when recovering a mission but just as often after a period of playing time (not consistent). Mods Installed: KER v1.0.17.0, Active Texture Management - X86 - Aggressive v5-0, via CKAN v1.8.4 (beta) Extract from error.log Unity Player [version: Unity 4.6.4f1_99f88340878d] mono.dll caused an Access Violation (0xc0000005) in module mono.dll at 001b:10107259. Error occurred at 2015-06-27_231248. D:\Program Files\Games\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by xxxx. 77% memory in use. 3580 MB physical memory [792 MB free]. 0 MB paging file [2645 MB free]. 2048 MB user address space [133 MB free]. Write to location 00000000 caused an access violation. I can upload the output_log if it's required and someone tells me how best to do it. I've seen discussions of access violations related to the frequency of reversions to the Space Center but this error can occur, for me, without any reversions. It appears that I'm running out of memory but I reduce the running software to reasonable minimums (no browser running, no email client, unnecessary TSRs stopped, etc.). The error occurs regardless. The game has been removed and reinstalled and I've tried playing without and with ATM Aggressive and Basic in attempts to reduce the memory load. They don't seem to help at all but I'm not sure I'd see a difference. This is a fascinating game and I really enjoy it but the crashes are annoying and will prevent me from trying longer missions in fear of losing valuable progress (I don't have that much free time!). I recently played it on another computer (Windows 7 64-bit, 16GB RAM) and it never crashed after 30 hours of gameplay over several days. I'd upgrade to 64-bit and add memory (not just for this game ) but I've seen posts that suggest 64-bit KSP isn't stable. Do I run 32-bit KSP on a Win 7 64-bit? I was hoping that 1.0.x versions were going to solve this. I keep hoping.