When loading saves ingame...

[Guest KillMeTwice]

Ok I have a problem... Im pretty sure that its because of that I have like 80 mods or something but when I install few mods (like 10) the game crashes nearly every time I try to load a saved game ingame. And now when I have nearly every mod (not the badly conflicting ones) loaded it crashes every time I try to load a game when playing. Its nt very bad thing because I normally dont die in Oblivion and dont normally do something I could need to load save. But its still very annoying.

[nosisab]

Ok I have a problem... Im pretty sure that its because of that I have like 80 mods or something but when I install few mods (like 10) the game crashes nearly every time I try to load a saved game ingame. And now when I have nearly every mod (not the badly conflicting ones) loaded it crashes every time I try to load a game when playing. Its nt very bad thing because I normally dont die in Oblivion and dont normally do something I could need to load save. But its still very annoying.

This is a known and annoying issue, related to the crash on exit. It goes most of times when reloading ingame from different cell (you can test to see if loading while in the same cell works fine). It seems related to memory deadlocks more than in memory lack. I think some mods creates situations where something that need to be unloaded or loaded can't be done for being need for another yet in memory, other times may be caused for the dynamic ordering retrieving the wrong of two similar objects the savegame relies on one of then.

 

While annoying this isn't a thing that can be solved with a few hints, you seems right suspecting a direct conflict, indeed the load order is able to resolve that conflicting issue most of times just overwriting (in memory) the former one and so, the last "wins", but this fails when unloading and or reloading.

 

Edit: Once I had a problem where I couldn't even load (not reloading) saved games because I changed the load order. The load bar goes unto some point and just freeze, sometimes with the HD spinning madly without performing any read or writing while the processor tried to solve the deadlock.