I'm having a CTD issue, and I can't identify the problem.

[Tandwan]

I know there are people out there with more mods in their Skyrim then me, so I won't say I have a s*** ton but I do. I have about 30+ mods running on my game and recently my game just randomly started crashing to desktop for no reason at all. I don't get an error message and i've looked through the Skyrim folder for a crash log and I can't find one. Is there a way to find out which mod it is that is causing this issue or if it's my game itself OTHER THEN going through and disabling every single mod I have, loading the game, seeing if it crashes and rinse/repeat? Is there a crash log and i'm just not seeing it?

[AnkhAscendant]

You have to turn on the Papyrus error logging to get your crash log. I grabbed the instructions from an old thread on here:

 

Copy these in your skyrim.ini in Documents > My Games > Skyrim >[skyrim.ini]:

[Papyrus]

bEnableLogging=1

bEnableTrace=1

bLoadDebugInformation=1

 

Then your logs will be in your My Games folder. Papyrus.0.log will always be the newest one, if what I've read is correct. I always save it as a text file and go look at in in a better word processor so I can actually read it with some formatting... See if you have any scripts running that give you tons of errors, they're probably eating your RAM and that's probably your problem mod.

 

Alternatively, your computer may just not be able to handle to load... My game kept committing suicide with Warzones running just because my computer isn't good enough (*sadness* :( )

 

Thirdly, (and which probably should have been firstly), if you can recreate the CTDs in the same spots consistently, you probably have a mod conflict or a broken mod that edits that area. In that case deactivating and testing is the best bet

[Tandwan]

You have to turn on the Papyrus error logging to get your crash log. I grabbed the instructions from an old thread on here:

 

Copy these in your skyrim.ini in Documents > My Games > Skyrim >[skyrim.ini]:

[Papyrus]

bEnableLogging=1

bEnableTrace=1

bLoadDebugInformation=1

 

Then your logs will be in your My Games folder. Papyrus.0.log will always be the newest one, if what I've read is correct. I always save it as a text file and go look at in in a better word processor so I can actually read it with some formatting... See if you have any scripts running that give you tons of errors, they're probably eating your RAM and that's probably your problem mod.

 

Alternatively, your computer may just not be able to handle to load... My game kept committing suicide with Warzones running just because my computer isn't good enough (*sadness* :( )

 

Thirdly, (and which probably should have been firstly), if you can recreate the CTDs in the same spots consistently, you probably have a mod conflict or a broken mod that edits that area. In that case deactivating and testing is the best bet

 

 

Thanks for the reply, and my apologies for not coming back as I went to sleep. (Had been up all night prior to). If what I am reading is correct it looks like i'm getting errors from the Natalie companion mod and her looking for someone to heal and not finding them. That's what I see a lot of in there, so with that said is it best to re-download this mod and see if I can fix it that way or simply to ditch the mod?

[AnkhAscendant]

It would be best to test if she's the problem before going too drastic. The best way would be to go back to a save before you installed the mod and keep that one deactivated, and activate all of the others. If it still crashes it's probably not that mod, at least not alone. If it seems to be working, you can see if there's an update and try to fix it, and if there isn't one inform the mod author about the problem (they may not like to hear it, but they should know) and ditch it.

 

If you don't have an earlier save, deactivating it on the problem one is somewhat less reliable a test and not quite as good practice, but if you keep error logging on it will at least show you if you have any orphaned scripts still trying to run in your savegame to see if it's safe to keep playing without it. Once again, if you're still crashing without signs of that mod in the log, it's probably a different one. (If you have to do this method, I'd deactivate it, make a new save, then exit and reload that save so that you don't have the "cannot find this mod script!" errors that you'd get from having deactivate it and it will be easier to read.)