DarkOrion4600

Thank you so much! That was so frustrating. You're right, it was indeed Precision X. I don't know if it was advertised to "boost" gaming, but it does unlock the clocking speeds, voltages and fan profiles on my video card, I use it to check how much work my GPU is doing while in game. I don't understand it though, Precision X only uses 53,000K with all of it's components, Chrome right now is using 286,000K and I've used Chrome in the background while playing KSP without it crashing. Actually, the game hasn't crashed AT ALL since I stopped precision X. Maybe it's not running out of memory, that is to say, maybe Precision X isn't using too much memory, maybe Precision X just somehow interferes with KSP's ability to get resources. Whatever the case, it's fixed! Again, thank you.

I'm running the latest Steam release V1.0.4.861 on updated Windows 7 64bit Professional edition I hadn't picked up Space Program in a while and I wanted to try out some of the new re-entry and aero mechanics, little did I know the hurt that was to follow. I've had crashes everywhere, in the loading screen, on the start menu, in VAB, in research, after launch and in the map. 23 crashes since I reinstalled yesterday with different settings each time. I've tried reinstalling, restarting, I've updated my Nvidia Drivers, I've tried changing every graphics setting to the lowest possible, nothing seems to fix or even noticeably prolong the amount of time I play before it crashes. One thing I thought might be causing it might be some sort of error to recognize my windows managed 12gb of pagefile on three separate drives: Unity Player [version: Unity 4.6.4f1_99f88340878d] KSP.exe caused an Access Violation (0xc0000005) in module KSP.exe at 0023:011f9fa0. Error occurred at 2015-08-06_153446. D:\Program Files\steamapps\common\Kerbal Space Program\KSP.exe, run by Chrysaor. 69% memory in use. 4095 MB physical memory [1238 MB free]. 0 MB paging file [0 MB free].<----------------------------- 0 MB user address space [2533 MB free]. Write to location 00000000 caused an access violation. But even after I set a specific amount of pagefile to one of my drives it didn't make any difference to the issue or the log. I'm thinking about reducing the amount pagefile down to a set 4096 on a specific drive and disabling the rest. Any help would be wonderful. EDIT: I tried running with only 4096mb of pagefile on my OS drive, no change Crash Dmp: https://www.dropbox.com/s/bgrsn20bzm8po22/crash.dmp?dl=0 DxDiag: https://www.dropbox.com/s/k2dj38pn5ubxdbf/DxDiag.txt?dl=0 Error Log: https://www.dropbox.com/s/l3zecr0ivywuc1q/error.log?dl=0 Output Log: https://www.dropbox.com/s/ubobobr7s71ju7b/output_log.txt?dl=0 Report Ini: https://www.dropbox.com/s/fhhrlmepj6w9znl/report.ini?dl=0