Man, I am tired of reinstalling Oblivion every single time an inexplicable CTD occurs... I better follow this guide now onwards...I almost did this except the pyffi'ng part, which I never really understood (some modders do it for us, eg. Arthmoor), so just did not bother.
But now I am [censored] sick and tired of these [censored] CTDs now *Samuel Jackson mode*
You know what? Reinstalling the whole game is almost never a good answer for CTD and other mod problems. Also, this guide is very much overkill, and many of the steps are more akin to personal superstition than to technical understanding or good sensible practice.
I have not Pyffied any meshes. I have only cleaned some of the mods in my load order. I do not follow the advice about turning on ESMs and ESPs one at a time.
I use BAIN to install as much as I can, OBMM for the few remaning. That way, uninstalling is a breeze when I do run into a problem. I begin with FCOM and COBL and the UOP. I make sure that setup is working. If not, I work on that and only that until I get it working. Usually - almost always - a problem at this point indicates a mistake in installing. Then, I add small groups of mods slowly, reading the readmes and asking questions on the forum if I don't understand something. I playtest in between to make sure things are showing up like I understand they should.
Also, I rebuild the bashed patch every time I add or subtract a mod from my load order. And I always keep up with the Wrye Bash and BOSS threads, because I learn a ton by reading them.
And, you know the result? I seldom get CTDs. Maybe every fourth playthrough, if that. I'm just careful. There's no magic method. There's just learning and being careful and making mistakes and asking questions and more learning.
I suspect that most gamestopping problems are the result of
- a mistake in installation
- missing a key piece of information in a readme
- rushing the process
- installing a problem mod
- expecting to play for over four hours at a time without a CTD
gothemasticator