CTD on startup - mod number

[Mjonir]

Hi,

 

 

I just finished modding a freshly installed Fallout 3 with a lot of mods and after playing a bit with the load order I launched it for a first test round. There were some major problems, but that's not what brought me here. After this first test, I tried to re-launch Fallout 3 with the same configuration, only to encounter CTD on startup (the program freezes while loading mods). Since it worked perfectly with no ESP checked, I started checking some and unchecking others in order to isolate the problem/conflict.

 

What's very weird is that actually, my game crashes when I simply have too many mods checked regardless of those that are checked, and this happens around 162 checked ESPs, which still should be under the limit. For example, the game starts normally with 161 mods, and then crashes if I activate another one (whatever it is), and works if I uncheck one of the previously checked mods and replace it with another. Sure I could play with less mods, but that would be a bit annoying and I'd prefer to fix this if I can.

 

 

Would anybody have an idea on how to fix this?

 

Thanks in advance.

[mechine]

Yeah sure

 

 

you have FOMM?

 

 

If you do, right click the load list, then copy load order to clip board an paste it here.

 

 

 

 

Also it wouldn't hurt to put more information in

 

like which patch you use, retail disc or download, DLC's or No DLC's, Computer system, XP or Vista, install location

FOMM? FOSE?

 

 

 

I mean from what you said you could have just saved time

 

and put the title of this post as CTD at startup

 

then just wrote "I crash if I use more than 167 mods"

 

 

eh

 

 

It doesn't really matter how many mods you load, but the order in which you load them is rather important

 

Along with how clean the install was, which patch it was, are there DLC's, Are there compatiblity patches after some of the esp's

if there are conflicts, ect.

 

There's pinned topics that go into more detail, really long though.