Having the same issue here Time Ranger. Always crashes on any save, tried disabling all mods making a clean actual hard save, then re-enabling all mods an going forward didn't solve the issue. Tried unistalling/re-installing no fix aswell. Googled looking for some insight and found out about the killing yourself work around, though it worked...it seemed like a temp/quick fix the problem would resurface later on. I did as quicksilvera suggested and found that all of my hard/actual saves and autosaves were (.fos , .fos.bak) as they should be, but one of my quicksaves was the dreaded ".tmp", deleted that and reloaded from a hard/actual save fixed the issue for a time. About 30m of game time later and quicksaving every 5m or so I crashed again, looked immediately at my saves and the quicksave had once again shown ".tmp" so the issue seems to be re-occurring intermittently. Just now I ran FO3MasterUpdate (2 mods had errors so they have to remain .esp). From past experience, every time I experience a crash in Fallout I go to my event viewer (win7 64bit OS) and see if I get any insight. Below is what I got. Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x002d37ec Faulting process id: 0xfec Faulting application start time: 0x01cc61aede923492 Faulting application path: C:\Program Files (x86)\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: C:\Program Files (x86)\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 2e140ac4-cda2-11e0-8d96-1c6f65c924ce The exception code tells me its memory related, running memtest after this and my video drivers are up to date (even rolled them back to see if it was the new driver). Thinking our issues are related kinda wondering what if anything your event viewer says. Machine specs: Windows 7 64-bit Home Premium i7 3.4ghz 8gb DDR3 Nvidia GeForce 560 TI edit: Come to think of it, everything was running smooth until I edited the timescale via the console. Googled that and only time folks were running into issues was at the extremes i.e 1. I was running it at 6 so don't think thats the issue but not something to count out just yet.