What to do when you can't save?

[Rockatanskiy]

Lately, I've been getting CTDs whenever I try to save my game. I try unchecking various mods in FOMM, but to no avail. Sometimes I will actually be able to save, but then I won't be able to during my next play session, even if I didn't change load order/mods/anything.

 

I can play through the game just fine, but any type of saving, quick save, auto save, manual save.... they all cause the game to crash after a 2-3 second delay after attempting to overwrite a save or make a new one. I guess the crash happens before the save is complete, because all the data that I would have been saving would now be lost.

 

I am honestly stumped as to what to do, and any help would be much appreciated.

[Cipscis]

I've seen this bug mentioned before, although I don't think anyone knows what causes it. If I remember correctly, killing yourself (for example, using "player.KillActor" in the console) then loading a game should allow you to save again normally.

 

Cipscis

[TheOutlander]

I've seen this bug mentioned before, although I don't think anyone knows what causes it. If I remember correctly, killing yourself (for example, using "player.KillActor" in the console) then loading a game should allow you to save again normally.

 

Cipscis

Really?

 

Jeese I get the bug from time to time, usually when I add a new mod or mess with one significantly and a certain amount of time passes.

[Rockatanskiy]

I've seen this bug mentioned before, although I don't think anyone knows what causes it. If I remember correctly, killing yourself (for example, using "player.KillActor" in the console) then loading a game should allow you to save again normally.

 

Cipscis

 

I know EXACTLY what you are talking about, but that is a slightly different scenario. That works when your current save file CTDs on load (not save), but an old file still loads properly. I discovered that on my own a while back. Unfortunately, the same technique doesn't work for the error I'm getting...

[TheOutlander]

I've seen this bug mentioned before, although I don't think anyone knows what causes it. If I remember correctly, killing yourself (for example, using "player.KillActor" in the console) then loading a game should allow you to save again normally.

 

Cipscis

 

I know EXACTLY what you are talking about, but that is a slightly different scenario. That works when your current save file CTDs on load (not save), but an old file still loads properly. I discovered that on my own a while back. Unfortunately, the same technique doesn't work for the error I'm getting...

Yeah I'm stuck with the problem at the moment too, I can fast travel once and then anytime I do anything that results in a save bam ctd. Last time I had this problem it was a mod being a pest (flickone's v1 of his power helmet - well turning it off stop the problem).

[Deleted1084753User]

Interesting, I had this same problem a few days back while I was working on a mod. I thought it was my mod that was causing the problem somehow (damned if I knew how though, I wasn't doing anything remotely connected to saving). Guess this explains it then, it's a known bug and probably wasn't my fault heh. Can't remember what fixed it now..... probably just removed the mod I think. Anyway, had the exact same problem, entering any location that triggered a quicksave = CTD, manually saving or quicksaving also = CTD. Got quite frustrating.

I love this game, it's great fun to play and easy to mod mostly, but seriously..... the bugs really kill it sometimes :(

[TheOutlander]

It's frustrating that I have to kill myself at the start of every gaming session (everytime I load Fallout 3), just to be able to save (if I don't kill myself now, it crashes on save).

 

:sigh:

[Rockatanskiy]

Whenever I used to get CTDs, I would find the mod that caused it rather easily, and then stop using it. Simple.

 

However, this time I either can't find the mod that is causing the problems, or it is much deeper than that. I've turned off the handful of mods I've acquired since it started to happen, but that just doesn't seem to work at all. Sometimes, I can get lucky and turn a mod off and then be able to save, but the next time I load up FO3, the problem comes back. Sometimes to ability to save will come back randomly, even though I haven't changed anything in FOMM.

 

On another note, I tried starting a new game, and I was able to save just fine in that new file.

And lastly, I heard about something called "save game bloating." I have no idea what that is, but could that be the reason why a new file will work, but my regular ones do not?

[Yossarian22]

Whenever I used to get CTDs, I would find the mod that caused it rather easily, and then stop using it. Simple.

 

However, this time I either can't find the mod that is causing the problems, or it is much deeper than that. I've turned off the handful of mods I've acquired since it started to happen, but that just doesn't seem to work at all. Sometimes, I can get lucky and turn a mod off and then be able to save, but the next time I load up FO3, the problem comes back. Sometimes to ability to save will come back randomly, even though I haven't changed anything in FOMM.

 

On another note, I tried starting a new game, and I was able to save just fine in that new file.

And lastly, I heard about something called "save game bloating." I have no idea what that is, but could that be the reason why a new file will work, but my regular ones do not?

 

Save Game Bloating normaly happens, when a Mod creates lots of objects with PlaceatMe and dont mark them for Delete after using. You could check your savegame. I have heard, that the Engine gets problems, if the savegame is a lot above 10 mb, but not sure about the concrete number. You should get more Info about this in the Oblivion Forum Section.

 

What you descripted sounds for me more like some kind of Mod Conflict. I had this once, when I activated my first GTS Map Marker ESP and the second Map Marker ESP together. I dont know why, but after I deleted the old File the Problem was gone, so maybe its because you have 2 Mods, that changes the same Cells or same Objects or something like that.

 

I definitly would try to disable some Mods, that change a lot in many spaces. Potential candidats I could think of: Mammoths, my Map Marker ESP, MMM, Winter Mod etc.

 

Also I have read about, that sometimes savegames have problems, if a Mod deletes Objects in a Cell/Worldspace, that you did already visited before.

 

Well, hope it helped, good luck.

[Rockatanskiy]

Whenever I used to get CTDs, I would find the mod that caused it rather easily, and then stop using it. Simple.

 

However, this time I either can't find the mod that is causing the problems, or it is much deeper than that. I've turned off the handful of mods I've acquired since it started to happen, but that just doesn't seem to work at all. Sometimes, I can get lucky and turn a mod off and then be able to save, but the next time I load up FO3, the problem comes back. Sometimes to ability to save will come back randomly, even though I haven't changed anything in FOMM.

 

On another note, I tried starting a new game, and I was able to save just fine in that new file.

And lastly, I heard about something called "save game bloating." I have no idea what that is, but could that be the reason why a new file will work, but my regular ones do not?

 

Save Game Bloating normaly happens, when a Mod creates lots of objects with PlaceatMe and dont mark them for Delete after using. You could check your savegame. I have heard, that the Engine gets problems, if the savegame is a lot above 10 mb, but not sure about the concrete number. You should get more Info about this in the Oblivion Forum Section.

 

What you descripted sounds for me more like some kind of Mod Conflict. I had this once, when I activated my first GTS Map Marker ESP and the second Map Marker ESP together. I dont know why, but after I deleted the old File the Problem was gone, so maybe its because you have 2 Mods, that changes the same Cells or same Objects or something like that.

 

I definitly would try to disable some Mods, that change a lot in many spaces. Potential candidats I could think of: Mammoths, my Map Marker ESP, MMM, Winter Mod etc.

 

Also I have read about, that sometimes savegames have problems, if a Mod deletes Objects in a Cell/Worldspace, that you did already visited before.

 

Well, hope it helped, good luck.

 

 

Well... I do have your map markers and MMM, but I've had those for plenty of time before this started happening. But come to think of it, the problems did start occuring around the same time as I tried mammoths (or "mommoths" as they were called.) I noticed this before, and I deleted the .esp, and the problem seemed to go away, but like I said, the next time I started up FO3, the CTDs on save started happening again.

 

I do have another mod similar to Mammoths, which is called the Big, Bad, and the Ugly. It adds floaters and wanamingos to creature lists. Perhaps this is conflicting with MMM? I'll go check it out, but I'm pretty sure I've tried the game without that before too...

 

EDIT: turned Big bad and ugly off to no avail. I even waited 4 days in an isolated cell before attempting to save. I also checked out the save files, which are about 5.5 mb, so they're fine.