Can you share your process for diagnosing CTD?

[SirSnagglepuss]

I have been having problems for about a week trying to get my game running properly. I've been spending the last couple days researching this topic so I can just figure it out myself but the two answers I have come up with are SSEEdit can help you diagnose startup CTD, and the only other option I found is to go through everything and uninstall one by one. I get how that works but my problem is my CTDs are completely random. Usually, I can play for 30 mins just fine (just long enough to let down your guard and not save for a while) before it crashes. The one by one option just isn't realistic, it would take days of troubleshooting. I just want to know what steps you more experienced people would take to figure out the cause of your problem.

[Algabar]

The one by one option just isn't realistic, it would take days of troubleshooting. I just want to know what steps you more experienced people would take to figure out the cause of your problem.

 

You can speed up this process at least a bit: Disable not one file at a time, but 10 (ore even more). Then test.

You can even disable half your mods as a start and test, if the problem persists. If it does, disable the other half. Then disable half of the mods left and so on... OFC you have to pay attention to mod dependencies: If you disable mods needed by other mods, you will run into new problems...

Also, always test with a new game. If a new game is stable, then it's not a mod issue. If you get CTDs with a new game ,too., the problem is probably mod related.

 

Problem with all these methods is, that the results might be misleading, if the actual issue isn't a single mod, but a combination of mods...

 

In fact, "random" CTDs can be very difficult to track down. IMHO the best way of dealing with them is trying to avoid unexpected issues: Build up your load order carefully and "step by step": Install only a few mods at a time, then do some testing. If your setup is stable, you can add further mods - and test again. If you got issues, get them straight before installing anything new. This way, it is far easier to find possible "culprits": Simply check the mods you installed last.

[SirTwist]

The most common CTD is caused by installing a mod, then later on, when you have a few hours in, uninstalling a mod. The second most common is people not carefully reading mod description, and adjusting their load order to what the mod author has posted on their mod page the order which mods go. Third cause of a CTD is typically a combination of things that is happening behind the scenes. Like your A/V wants to update, or windows wants to update, or something else, that keeps you popping in and out of game numerous times.

 

Mod conflicts, and improper load order thanks to Loot, are common. People who are buying, and using computers for the first time, or even not new to pc's, but to modding games, are having problems. Typically, I use Loot to determine what mods are relatively clean, and which are dirty, and clean. I don't use it to organize my load order, at all. I also play Fallout 4, and I have a couple mods that have to be at the bottom of the load order, but Loot wants to put them elsewhere. And when I get to where I can see the mod working, or not, it isn't working, because of Loot. I am digressing. The one thing I do suggest is it's not necessarily a mod conflict that is causing CTD's, rather mod placement. Although it can be a conflict. That is another reason I say read descriptions, and also if there is a bug report, and if your issue is listed there. I know most clothing and armor mods work together, so you shouldn't have a CTD with any of those. Also, most weapons mods play nicely together. It's typically scenery, quest, and other types of mods that can cause CTDS when they don't play nice.

[SirSnagglepuss]

well, I partially solved the problem. I CDT way less than it was before it was random but for the most part was before the half-hour mark. It was ENB, so I'm not sure if it was the mod itself or it just putting too much strain on my system, but it is definitely better now (once or twice all day). also thanks for the advice, I usually just run loot and leave it as is. unfortunately, the only times mod authors mention load order in most cases is when they tell you to put it at the bottom. yes, I am one of the rare breeds that actually read the description.

[Algabar]

I usually just run loot and leave it as is. unfortunately, the only times mod authors mention load order in most cases is when they tell you to put it at the bottom. yes, I am one of the rare breeds that actually read the description.

 

It's perfectly understandable, that a lot of mod authors recommend putting their mod last or very low in your load order. Everyone wants to make sure his mod is working as intended. Besides that, it helps with troubleshooting and telling real bugs from false positives, if you recommend to put your mod last in load order. Whether it is technically really necessary, is another story...

[SirTwist]

There are mods that need to go at the bottom. For example, I'll use Fallout 4, and one mod in particular, Repaired Roofs. This mod does not cause a CTD, at all. Rather, in Sanctuary, after you get out of the vault, if you have this mod anywhere but the absolute bottom of your order, the roofs will look like they do in vanilla Fallout 4. This mod repairs the roofs, and makes them look nice. Weightless mods should be at, or near the bottom, as well. These, also do not cause a CTD, but you can end up carrying a ton of stuff that normally, with mods, be weightless.

 

However, getting back to CTD, reading descriptions, as well as checking posts about the mod, and even some forum hunting, can lead to less CTD's overall. I won't say your game will not crash, but the likely hood of it happening will be less.