KSP 1.0.4 Crashing - mono.dll caused an Access Violation

[Brigadier]

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.

[gerishnakov]

I have this exact same problem. Here's a link to my error and output_log files http://1drv.ms/1KorCrF

[Brigadier]

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.

[gerishnakov]

I think the problem on my end might be the number and complexity of the mods I'm running. I know my PC can handle stock KSP with all the graphics settings at max no problem, and it did so happily until just today when I think I overdid the modding.

[sarbian]

Why are you using ATM if you don't have part mods ? The stock game has all its texture converted to DDS already. You may even loose mem from doing that.

[gerishnakov]

Thanks for the tip sarbian, I had just assumed ATM was a good thing to have going all round. I'll restart without it and see if that makes a difference.

[Brigadier]

Likewise, thanks.