There seems to be some dispute over whether the Oblivion Crash Prevention System is worth using, and whether or not it causes savegame corruption.

So please, enlighten me.

I found this thread from a year ago: http://www.gamesas.com/topic/1111680-reading-weocps-logs/page__hl__weocps__fromsearch__1

I was under the impression that the best practice is to reload from a previous save if weOCPs' "ding" sound is triggered. It prevents crashes, but I don't think it does anything to address the cause of thie instability, which could lead to greater problems down the road.

I don't think it causes save game corruption but can mask what does cause it.

a ctd that is caused by something wrong with the load order (and not system strain - which weOCPs wouldn't prevent anyway) is an indication that something is wrong and should be addressed. Masking this and allowing it to continue is what can lead to all sorts of problems.

Hard to say how serious because to even read the weOCPS log is as arcane a task as it gets for the average user. Plus no support anymore to submit log to the author.

I had a ding like 5 minutes before a CTD and then the save was corrupted. Huh. Got me thinking about the "reload a save" philosophy. I like weOCPS, and it always dings when I go to main menu

I believe that 'ding' is the 'exit bug' that 'http://oblivion.nexusmods.com/mods/22410' fixes. While I used to use weOCPS, once I learned how to track down the errors it was masking I haven't needed it since.

-Dubious-

it will mess up your savegames, avoid it.

OCPS is actually recomended by the author of Fast Exit2.

The "ding" is, so far as I know, the internal windows sound for "oops, gonna crash now". I hear that sound if I crash-exit without OCPS running, otherwise I never hear a "ding".

I don't agree with Gekko64 that is corrupts your savegame either, I don't recall ever hearing that - I have heard it about some "multithreading" OBSE plugin, or whatever it did, which actually did nothing, except cause occasional bugs and crashes.

It's actually reasonably well known, although it isn't talked about much anymore. Given how weOCPS avoids crashes, it isn't that big of a stretch from dodging one to getting a corrupted save.

The game is crashing for a reason. Either due to data errors or some other reason and it's generally bad practice to trust the state of any application once you've done something like that and forced your way around it.

Some people have been lucky. Others had their games fubared after trust it for too long. Unfortunately it looks like the threads where this issue was hotly debated a couple of years ago is gone now.

Interesting information, thanks guys. I think I'll pull it out of my setup. I checked the log and there was a whole mess of stuff right around when I started to experience the issue recounted in Arthmoor's villages thread, so I think it may be the cause.

you have to revert to a save BEFORE you added it

I just liked the reassurance, right now my game only crashes now and then (for some reason twice by fast travelling to Talos Plaza). I am going to remove it and see if I crash. Three weeks ago I was crashing every hour and weOCPS did nothing, but I think it was Streamline fps smoothing conflicting with OSR. I stopped that, no crash. Fairly though I also checked on OSR ini's heaps at the same time