game keeps crashing with mods install.

[greg100]

i have no idea why it keeps crashing

[jfraser]

that usually means one of your mods is missing a dependency or your load order is wrong. are you using a mod manager?

[plutocene]

4 hours ago, greg100 said:

i have no idea why it keeps crashing

 

That is not addressable based on this statement. What mod organizer are you using, what game version, when does it crash, does it crash consistently or randomly, provide the crash log, etc.     

[deff.]

4 hours ago, greg100 said:

i have no idea why it keeps crashing

 

• load order maybe be messed up;
• missing mods requirements/dependencies;
• some mods are obsolete and can cause crash as well;
• some mods can be for another game version as well (as we know there are 2 versions - 1.10.163 (before next-gen update) and game version with next-gen update.

 

You described your problem pretty lazy - crashlog form Buffout 4 can tell you more about your crashing. With CM Toolkit you can check your F4SE plugins - it will analyze if all plugins are correct for your game...

[greg100]

14 hours ago, Skylar Gray said:

 

• load order maybe be messed up;
• missing mods requirements/dependencies;
• some mods are obsolete and can cause crash as well;
• some mods can be for another game version as well (as we know there are 2 versions - 1.10.163 (before next-gen update) and game version with next-gen update.

 

You described your problem pretty lazy - crashlog form Buffout 4 can tell you more about your crashing. With CM Toolkit you can check your F4SE plugins - it will analyze if all plugins are correct for your game...

crash-2025-07-27-10-00-24.log 

 

14 hours ago, plutocene said:

 

That is not addressable based on this statement. What mod organizer are you using, what game version, when does it crash, does it crash consistently or randomly, provide the crash log, etc.     

crash-2025-07-27-10-00-24.log

[greg100]

cm toolkit

 

cm-toolkit.log

[plutocene]

The crashlog has been modified it seems, there is no mod list. Classic suggests MCM error, verify the .dlls with CM-Toolkit under F4SE. I would reinstall MCM and any that are marked yellow, red ones are the wrong version and need to be replaced. Since you still have not provided any further information, this is pretty much all that I can deduce. 

[deff.]

19 minutes ago, greg100 said:

cm toolkit

 

cm-toolkit.log 7.31 kB · 1 download

 

Have you checked plugin status in CM Toolkit under F4SE? There are no errors should be...

 

And provide full modlist - you have NG game, so double check mods, because some of them working only with 1.10.163...it's  pretty easy to mess up everything

[greg100]

1 hour ago, Skylar Gray said:

 

Have you checked plugin status in CM Toolkit under F4SE? There are no errors should be...

 

And provide full modlist - you have NG game, so double check mods, because some of them working only with 1.10.163...it's  pretty easy to mess up everything

howe do i post a full modlist

 

 

Edited July 28, 2025 by greg100

[greg100]

it said no og mods detected

 

also im using vortex

[subaverage]

Even when the crash log does not point to it you could check whether you have "Weapon Debris" enabled. If so, you could try to turn it off. Next you could check your LOD settings and turn them all to the lowest. Same with shadows, lighting and decal quantity. When this helps you could rise these settings step by step again with a lot of testing. These are only some general options to look at. Your modlist might bring more information.

 

PS.: Do you use a main menu replacer?

Edited July 28, 2025 by subaverage

[deff.]

@greg100 I don't know how to export modlist from Vortex, but if you want some help/advice then I believe you can find answer in google about modlist export...And my subjective opinion is that Vortex is a little bit tricky mod manager. At least for me. MO2 is more comfortable and more transparent. But as I said, it's subjective

 

Whats  the status under CM Toolkit F4SE? All F4SE dll plugins must be green without errors...(like in pic) 

 

 

And there are two main errors in your crashlog:

 

# Checking for Scaleform Gfx Crash........... SUSPECT FOUND! > Severity : 5 # 
-----
# Checking for MCM Crash..................... SUSPECT FOUND! > Severity : 3 #

 

 

As @plutocene said, check MCM install, your version is this one. 

 

 

 

And provide modlist, if you want to solve problem...

Edited July 28, 2025 by Skylar Gray

[greg100]

7 hours ago, subaverage said:

Even when the crash log does not point to it you could check whether you have "Weapon Debris" enabled. If so, you could try to turn it off. Next you could check your LOD settings and turn them all to the lowest. Same with shadows, lighting and decal quantity. When this helps you could rise these settings step by step again with a lot of testing. These are only some general options to look at. Your modlist might bring more information.

 

PS.: Do you use a main menu replacer?

these are my game settings

 

[subaverage]

These settings are already low and "Weapon Debris" is no option for you. Did you try out the suggestion from above and reinstalled MCM? And what about a main menu replacer? In addition can you describe when the crashes happen? During game play or even at the start? If during gameplay is there a pattern or can the crashes happen everywhere and in every situation? You should have a file called "plugins.txt" in C:\Users\<your username>\AppData\Local\Fallout4. It's a simple text file and contains your modlist.

Do you perhaps use high-res texture mods like bodyskins? (or even lod mods)?

Edited July 28, 2025 by subaverage

[greg100]

11 hours ago, subaverage said:

These settings are already low and "Weapon Debris" is no option for you. Did you try out the suggestion from above and reinstalled MCM? And what about a main menu replacer? In addition can you describe when the crashes happen? During game play or even at the start? If during gameplay is there a pattern or can the crashes happen everywhere and in every situation? You should have a file called "plugins.txt" in C:\Users\<your username>\AppData\Local\Fallout4. It's a simple text file and contains your modlist.

Do you perhaps use high-res texture mods like bodyskins? (or even lod mods)?

it lkoads up for a second  then crashes

crash-2025-07-29-02-02-09.logplugins.txt

Edited July 29, 2025 by greg100

[subaverage]

What I can see is that your plugins.txt contains alone more than 400 esps. Plus there are some esms from mods and the base game. As long as they are all enabled and still use a full mod slot you exceed the mod limit of 254 (might be 255, but I means it's 254) mods that use a full slot. So either at least about 160 esps need to be flagged as esl or you would need to disable a lot of them. Some mods don't even have plugin files, so coming back to the main menu replacer I believe that next-gen FO4 can't handle them and will not work. As always I would highly recommend to start a new playthrough without any mods enabled and play until leaving Vault 111 the first time. After making a save one could beging to install and activate mods step by step and with a lot of testing.

[greg100]

4 hours ago, subaverage said:

What I can see is that your plugins.txt contains alone more than 400 esps. Plus there are some esms from mods and the base game. As long as they are all enabled and still use a full mod slot you exceed the mod limit of 254 (might be 255, but I means it's 254) mods that use a full slot. So either at least about 160 esps need to be flagged as esl or you would need to disable a lot of them. Some mods don't even have plugin files, so coming back to the main menu replacer I believe that next-gen FO4 can't handle them and will not work. As always I would highly recommend to start a new playthrough without any mods enabled and play until leaving Vault 111 the first time. After making a save one could beging to install and activate mods step by step and with a lot of testing.

plugins.txtcrash-2025-07-29-12-13-35.log 

[deff.]

2 hours ago, greg100 said:

plugins.txt 5.96 kB · 2 downloads crash-2025-07-29-12-13-35.log 63.57 kB · 2 downloads  

 

Try without AAF Autonomy mod - disable it and try without it.

[greg100]

12 hours ago, Skylar Gray said:

 

Try without AAF Autonomy mod - disable it and try without it.

loads up then crashes after cc

 

[greg100]

Plugins.txt

[deff.]

1 hour ago, greg100 said:

Plugins.txt 5.93 kB · 0 downloads

 

I 'd say that load order is messed up and/or incompatibility in mod area.. Disable all mods and start new game. Then add them back one by one. Add 2-3 mods - check! Add another  3 - CHECK! Your problem is might be in that you added ton with mods without checking them in game...And I have no clue how to sort load order of mods in Vortex. 

 

 

[subaverage]

1 hour ago, Skylar Gray said:

 

I 'd say that load order is messed up and/or incompatibility in mod area.. Disable all mods and start new game. Then add them back one by one. Add 2-3 mods - check! Add another  3 - CHECK! Your problem is might be in that you added ton with mods without checking them in game...And I have no clue how to sort load order of mods in Vortex. 

 

 

This might be the best way. And play until leaving Vault 111 the first time without - any!! - mods enabled. After a save begin with modding step by step. But one last question. You speak of cc. Is your game perhaps downgraded and you have the CC content still in your load order?

[greg100]

18 minutes ago, subaverage said:

This might be the best way. And play until leaving Vault 111 the first time without - any!! - mods enabled. After a save begin with modding step by step. But one last question. You speak of cc. Is your game perhaps downgraded and you have the CC content still in your load order?

ok but what does this mean?

 

[Miauzi]

Vor 48 Minuten sagte greg100:

ok, aber was bedeutet das?

 

 

Do you use Vortex as your mod manager?

 

For example, Vortex analyzes the mod list after installation, including "plugins" -> "Deploy Mods."

But it can't do this if a program is running at the time that accesses the installed mods -> for example, an open "Bodyslide" program.

 

Then this error message may appear.

[deff.]

6 hours ago, subaverage said:

This might be the best way. And play until leaving Vault 111 the first time without - any!! - mods enabled. After a save begin with modding step by step. But one last question. You speak of cc. Is your game perhaps downgraded and you have the CC content still in your load order?

 

He's/her crashlog says that game version is NG.

 

And @greg100 - remove this one from modlist [07]     DLCUltraHighResolution.esm. You can easily download texture pack like this one - https://www.nexusmods.com/fallout4/mods/65720. Default HighRes pack is not very friendly with lot of mods and it's too heavy. 

 

And about mod manager - I highly recommend switch to Mod Manager 2. I think that it's easier and more transparent. You will have two panes - left side your mods (which can/must/need to be organised in logical load order) and right pane will be plugins (.esm, .esp and esl.). Don't  take it personal but it looks like that you are very beginner in modding and I would like to say than MO2 manager will make your life easier. In the early beginning I tried Vortex and I throw it out after 1 hour. 

 

As I said - change your mod manager and then start to download mods. Exit the Vault and download base (F4SE plugins like Buffout, Fallout patch, Address library etc), then download texture pack/-s for game...Add block by block and don't forget to check mods in game. I'm not talking about F4SE plugins - I'm talking about mods which changing the game, like quests, personal character looks (skin, hair, eyes etc), AAF mods/animations/, gamplay changing mods...Don't hurry! Take your time and mod with patience...In another case you wil get the same shit with crashes/errors/flickering textures/etc...

Edited July 30, 2025 by Skylar Gray