Yesterday, with a fresh install of Fallout 3, I installed all the new mods I intended to use, and arranged them in the load order according to what their Readme's said (if they did say), and according to what FOMM and FO3Edit said. When I started up Fallout 3, it loaded the first opening slide but froze there, and the pointer didn't load, though the music was still playing. I had to restart my computer because there was no way to close it no matter what I did. After this happened a few more times, I decided to uninstall Fallout 3 and install it again, then install mods one at a time to see what the problem was.

1. Fallout 3, by itself, was able to get to the main menu fine.
2. Fallout 3 with the Operation Anchorage and The Pitt combo disc installed worked fine as well.
3. Fallout 3 with FOMM and FOSE did too.
4. Fallout 3 with all that as well as FOOK 2 worked.
5. And it worked with FOOK 2, MMM and the Interoperability patch, with the load order arranged correctly.
6. But when I tried to install WMK, it produced the same problem that I described above.

So I uninstalled WMK and continued installing the other mods I had that weren't nearly as large, arranged them correctly in the load order, and started Fallout 3. Starting a new game, everything worked fine until I left the Vault, upon which it crashed to desktop. I loaded the autosave and starting walking from the Vault north, to the Pitt, but after only a few seconds of walking it crashed again. I reloaded it again, and crashed again, a few times until I started fiddling with the graphics settings, but nothing stopped the crashing. I then proceeded to uncheck from my load order everything associated with MMM, Street Lights, DarNified UI and the Automatic Patch I had made. When I started again, the crashing stopped, though DarNified UI was still active somehow. When I tried to turn back on DarNified UI the freezing at the first slide problem happened again, so I left it unchecked (even though it was still working in the game). I then proceeded to The Pitt, and even though it occasionally lagged for a few moments before going back to normal, everything worked fine. I then made it far enough into the quest to get into the Steelyard, but at one point when I attempted to open a medical kit inside one of the buildings, it froze. I assumed this was due to me Alt-Tabbing a few moments before that in order to close a pop-up from a program, but when I tried to load Fallout 3 again the freezing at the slide issue happened again. The only difference this time is I was somehow able to use CTRL+ALT+DELETE to close it. Now I don't want to try again without finding the cause, and I'm hoping someone can help. Here's my load order, with the mods I don't have activated in red:



Help?

Well regenerating the ini is an option (back it up just in case).

As is testing to see if the last loaded save game is a trigger for that (copy past it out or all of them out).

If the crashing happens in the same world space - then it could be a corrupt spawn point (wait out a respawn or go elsewhere to test that).

I recommend a bashed patch over a merged patch any day of the week. Same with BAIN over FOMM.

I've never used FOOK2 though, so that is beyond me.

[edit] oh yeah at one point I had Fallout Stutter Remover causing freezing at the main menu - if using that try removing that FOSE plugin and see. I know Skyranger has put out updates - But I've not kept up or played F3 in a month or more.

I don't use Fook2 but I read, so I'll give it a shot You have some outdated Fook2 plugins in there so head on over to http://www.fookunity.com/forum/showthread.php?t=4212 and make sure your Fook is updated correctly. If that MMM-Fook2 compatability patch was downloaded from the FOIP page at Nexus, it's outdated. I *think* I've seen an updated one but I have no idea where it might be living.

Load order-wise, I would try this:



Outdated FOIP patches can cause the disappearing cursor at the opening slide so make sure you have the current ones for Fook, MMM and WMK.
Regarding your freezing, I think you have a quad-core, don't you? Did you remember to apply the quad-core fix to your ini file?

My new semester of classes is in full swing now so I wont have time to deal with this issue, let alone play the game, for a while. But I just wanted to thank you two for the advice given so far, it'll come in handy once I have time to actually use it.