Aaaaarrrgghh! CTD's when loading a save

[K-61]

Verdammt! Another entire successful patrol lost because of stupid CTD's when reloading the saved patrol. Three separate saved files for the same patrol and every one crashes to desktop upon loading. W7 64 bit, installed outside of program files. I'm beginning to wonder if I have some hardware defect with my new notebook. I have never had such terrible luck with reloading saves on my XP system.

[JokerOfFate]

I got that problem too but it says abandoning mission? what?

[Pisces]

It's probably the situation of the game in which you saved it that is the cause, like being submerged, or other units being within your 3d bubble. The GWX manual has a list of most if not all bugs and quirks that applies to SH3 (not just GWX). And usually explains ways to solve or prevent them. If any savegame position in the list causes a crash then consider it a loss and go back one save. There's no point in wasting time to resurrect it.

Or you have enabled/disabled mods while you were still on patrol, which the savegame relies on to function correctly. Graphical user interface mods are usually no problem, but whatever deals with 3d models and other units and campaigns likely does affect savegames.

If the game runs (or has worked good before) then it probably is not caused by the OS. Temperature issues are unlikely at this point, because the graphics card didn't get to do much work. A memory glitch is possible, but then you would have experienced more spontaneous hangs or crashes of the whole OS. So, focus on how you saved the patrol.

[Weiss Pinguin]

Rule of thumb for save games is never save underwater, and never save within 50 (or maybe 30) kilometers of another unit. Sometimes you may get lucky with a save, but it's best not to take chances.

[Jimbuna]

Try not to delete the default 'Player' name that comes with the game....some of us believe that may have a detrimental effect.

[Gerald]

What then has the opposite effect!