Jump to content

Game CTD every ten minutes after installing mods. advice?


trueandsmooth

Recommended Posts

Was up until 6 am last night figuring out how to install mods, how to use archive invalidater and mod manager, only to find the game now ctd every ten minutes after modding success (the new mod content is now present in the game, which makes me very happy). Aparently I'm ment to use FO3edit to detect conflicts, so I've just downloaded it and read Information, chucked its esp in the data folder and put it at the bottom of my load order. Problem is the FO3edit app just goes way over my head in context to its use discription / information. Is there any type of simplistic FO3edit user guide lying around or is it going to be another 6 am learning journey again? or is my current set of mods or load order causing the extremely annoying CTD's?

 

The CTDs are also seemingly random, at times I'll play for around 20 mins then ctd, other times its every 5 mins a ctd occures. Dosnt seem to be linked to game content loading in game either. Just plain random from as far as I can tell.

 

my current load order:

 

1)fallout3.sem

2)CALIBR.esm

3)FOOK.esm

4)Fellout-SOTD.esp

5)WeaponModKits.esp

6)Marts Mutant Mod - Increased Spawns.esp

7)FOOK.esp

 

(and now after final crash fallout2.hardcoded.esp has been included) - (havnt played the game yet with the new esp either incase your intrested ?)

 

8)Fallout2.Hardcoded.esp

 

 

Oh and on a final note, after each ctd, I get that bane of games message, 'graphics display driver has stopped working and has fully recovered.' Which by the way I hardly ever get, well, until I installed these amazing mods.

 

(edit) And one last detail I forgot to mention, when it came to placing various mod folders into the data folder, some of the mods which aparently work together(like mmm, calibr and fook), had folders of the same name that needed to go into the data folder, example: there were two of 3 different mods which had 'texture' folders, so since you clearly cant have multiple of the same named folder, I just placed everything in one texture folder.

 

...basically I repeated this process with folders with the same name, then say, if in a textures folder there was a weapons folder, one for calibr and one for fook, I would go into each of the mods weapons folders pull out their files, and chuck them all in one weapons folder, which was in the f3 data folder. (hope that makes sense :sweat:)

 

I was up until the wee early hours trying to get it all working, so if theres a proper way to handle this little conundrum please do tell.

Link to comment
Share on other sites

Btw its not just, 'display driver has stopped working and has recovered' errors, I also get the plain ol 'fallout 3 has stopped working' error box aswell.

 

And noticed some people say ctds are linked to corrupt save files, which isnt the case with me, ever since I started the game afresh with the mods installed, these crashes have been very common, I got crashes just before I took the goat, and crashes pretty much every 10 mins after that, but once I got into the wasteland, the crashes became less often, then more often then just plain random and annoying and often. Im currently attempting to kill 7 molerats in some sewer, and its just crashing all over the shop, but its just so enjoyable to play I will probably continue even with ctd in my face every 5-10 minutes...

Link to comment
Share on other sites

You did well with the data folders, that is the actual way you're supposed to do it.

In your load order, you're missing:

 

<other esms go here>

 

Mart's Mutant Mod.esm

 

<misc mods go here>

 

<fook goes here>

<WMK goes here>

 

Weapon Mod Kits - Fook.esp <-- take this one from FOIP

 

Mart's Mutant Mod.esp

 

<mmm - increased spawns go here, use the one that comes with mart's mutant mod beta 4.

 

Mart's Mutant Mod - FOOK.esp <-- use the one that comes with fook

Link to comment
Share on other sites

Btw its not just, 'display driver has stopped working and has recovered' errors, I also get the plain ol 'fallout 3 has stopped working' error box aswell.

 

And noticed some people say ctds are linked to corrupt save files, which isnt the case with me, ever since I started the game afresh with the mods installed, these crashes have been very common, I got crashes just before I took the goat, and crashes pretty much every 10 mins after that, but once I got into the wasteland, the crashes became less often, then more often then just plain random and annoying and often. Im currently attempting to kill 7 molerats in some sewer, and its just crashing all over the shop, but its just so enjoyable to play I will probably continue even with ctd in my face every 5-10 minutes...

Hey. I like the way you think. I have CTD's sometimes too but Not "That" often, it usually happens when loading, thats about it.

Still, Playing even through bugginess. I like you dude. Most people scream a game sucks because of Bugs.

 

I'm not sure if this would help, but try lowering some of the graphics down there. It helped when I lowered the distances for the actors and things. I was able to start handling the game and it crashed less often.

Link to comment
Share on other sites

Cheers for the support guys, seariously. I've been looking for load order advice like that for a while but no one seemed to deliver. And nel I had those distances set to max thinking my lil 8800 gs could handle it haha! Never realised that could be the problem, cheers man.

 

Ok so far, what I've done is rearranged the load order like tg said, but its still crashing. Ive also changed the graphics to medium, and made shure all the view distances are very low. I also have the latest drivers. But its still crashing at the same frequency as before. o_O

 

Theres also a new problem, when I updated the files in the data folder, somehow I forgot to also update the textures and mesh files! :dry: Now raiders are pink, and some creatures are even invisible! I also cant seem to figure out which files were the origionals so I can look through them, and compaire the new ones and replace them through the process of elimination. I feel I've made aright mess of it, and really dont want to reinstall the game, reinstall all the mod apps aswell as the mods them selves but at this point I think its my only option. Anyways I can only go forward from here so I'm not to worried, especially with a community like this behind you.

Link to comment
Share on other sites

You forgot archiveinvalidation it seems -_-

Vanilla files are safelly packed inside the bsas, no way of screwing them. Tho if you installed a mod that adds new things with new textures, you're bond to see funky stuff unless you install the relevant textures.

Link to comment
Share on other sites

Ok - this is what I'm about to do; first, organizing all the mods into a neat collection of folders (re unzipping base dl zips into new folders), organized them into their nessicary load order ready to be placed back in the f3 folder and data folder. Simply, getting organized so I dont make a mistake like this again.

 

Then I'm going to atempt to purge the f3 and data folder of all the mod content currently placed there, texture files, .esp files, everything mod related basically, leaving all mod apps alone as I cant see how they could effect anything at this stage.

 

I will also (painfully) restart the game afresh, (sweet, vault 101 again.. huff.. ¬_¬) also in low graphic settings once purging and re placing of mods has been completed and see how it goes. Rinse & repeat. Looks like another 6 am session to me, time for some redbull & pringles. Good times..

Link to comment
Share on other sites

Archive invalidation is what is used to let the mods work, check and make sure its active, that might fix your problem. If not, Try this. Unload "ALL" Mods, and only load the fallout 3 ESM and the DLCs.

 

Test it, if it works, Load each mod one at a time, load one, check it...if it works, load another.

 

Keep going until you get to the errors again. That would mean that you could have a mod thats messing things up.

 

Thats what I did when my thing started acting all funky.

 

If that doesn't work, then hell. I dunno.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...