I save religiously, and do not need autosave. On top of that, autosave is causing CTDs in my game. Most games have a menu option that allows you to disable it (TW1 did, via the .ini), strangely TW2 does not seem to allow that option. I looked in the ini files in the config folder and found nothing. Anyone?

Its mostly been overlooked, but does the autosave cause CTD in your system or by some other factors!.

Whatever causes the CTDs, it's the autosave that triggers it. About one out of every 7 or 8 autosaves crashes my game. This is not the only game where I've experienced some issues with autosave (happened a couple of times in FO3, running a ton of mods), but unlike most games, TW2 does not allow you to toggle autosave in the menus. Horrible design decision.

Disable power saving for your Hard Disk and check if it eliminates the issue!. (there can be many reasons, just try the above and see if it helps!)

Thanks for the suggestion, but HD power saving was never on to begin with (system standby is also set to 'never'....I know, I am not very energy friendly with this machine, but then it's never on unless I am actively using it).

(/me scratches his head)

Did you check up the support page/FAQ for Witcher 2 and see if it helps

http://www.gog.com/en/support/the_witcher_2
http://en.thewitcher.com/forum/index.php?/topic/22348-technical-faq/

- - - -

If its not present over there, then something else outside the game is causing the crashes. Just triggered by the saving session.. could be related to RAM or Page File or something overheating during this process.

Try a clean boot and run the game to see if it still crashes.

If it does, check Event Viewer.

I usually turn off the unnecessary background processes before I launch a resource taxing game like this (including my virus scanner's 'realtime protection'). It might be the mods I've installed, although I am only using 5 or so mods downloaded from the Nexus and the readme from all of the authors indicates the mods are updated for at least 1.3 (but not necessarily 1.35--although I had already experienced this issue starting with 1.3).

Turning them off manually doesn't usually kill everything.

And is you suspect it's mods, then remove them and see.