Help regarding Frequent CTD

[Condedarkworld]

Hello, as it is stated in the title of thi topic, i need help in regards to frequent (and seeminly random) CTD's. they usually happen when a new cell loads (entering main world, inn, dungeon, etc etc)
This happens in every new (and old) save i have, this is a new install with mods that are to my liking, if anyone can help me figure this out, i will be glad

https://pastebin.com/cMwhp9XG

[plutocene]

Just a guess, try disabling steam overlay renderer. Both Nvidia drivers and the overlay renderer pop up in the crash log, which leads me to believe that this is involved.

[traison]

That crash log is unreliable, because the wrong thread context was dumped. See section 6.1 in my paper on reading crash logs in my signature if you want to know more.

 

Best guess I can come up with is that this crash was either directly or indirectly caused by "IED". That is probably Immersive Equipment Display.

[Condedarkworld]

Okay, so, after some moments of thinking and re-assessing my mods, i discovered that it was caused by the ENB i downloaded having been tailored for another weather mod (catedral weathers and not obsidian), after fixing this foolish mistake, the game ceased to crash, i thank you all for your time and help.

[Condedarkworld]

im going crazy with this one, i tought my crashes were due to the wrong weather mod for my ENB preset, so installed the correct one, then it kept crashing "must be the ENB" i tought, disabled it, played for a good while and it crashed again, and once again, lots of mentions about my NVIDIA drivers, so i booted windows in safe mode, used DDU to remove them, installed new ones (latest NVIDIA) and once again... crashed... with mentions of the fricking driver... I really dont know what to do besides doing all that safe mode and DDU shenanigan to install one of my old drivers i have backed up...

Latest crash log: https://pastebin.com/Qv9E1ACb

I really dont know what to do now, besides trying to see if the game still crashes even without mods, but i really dont want to endure the... carriage cutscene...

I gladly accept any help

[traison]

48 minutes ago, Condedarkworld said:

...so i booted windows in safe mode, used DDU to remove them, installed new ones (latest NVIDIA) and once again... crashed...

 

Considering the bad reputation nVidia's drivers have had the past few years I'd say you would have had better luck installing an old driver, as newer equals better almost certainly does not apply to nVidia. They're no doubt vibe coding their drivers trying to prove their point to crypto-bros.

 

48 minutes ago, Condedarkworld said:

...with mentions of the fricking driver...

 

Not seeing that in your crash log.

 

48 minutes ago, Condedarkworld said:

I really dont know what to do...

 

Depends on whether this crash occured during save file serialization or deserialization. The problem was in the save file named Autosave2_30C02D6B_0_5A61727961_HighHrothgar_001057_20260428165658_27_1, or it's SKSE co-save.

 

If this is a save file you tried to load when the crash occured, then open it in ReSaver to see what it has to say about it. If the save file is fine then delete (i.e. move or rename) the SKSE co-save and test again. If the game is now working you have a mod that's causing a serialization or deserialization error in SKSE. Finding that might get quite annoying.

 

If this crash happened while you were saving, then the issue is in serializing a mesh with a BSEffectShaderMaterial node with a "Type" value set to kEffect. A debugger might be required to find out where that came from.

Edited April 28 by traison

[Condedarkworld]

So, firstly i thank you for the reply.
I belive the driver is " nvwgf2umx.dll" mentioned in the log, I used an auto-analyzer to help me figure out, i may be modding this game for years, but back then i barelly got any crashes like this... usually with the good amazing "outdated/abandoned" sexlab mod that we know and love (or not), so it was quite easy to either, avoid the functionality that cause  the crash or just disable it, but since i did the big mistake of installing everything before playing the game itself, im quite stuck to figure out what is causing it as easily as before

and yes, the crash (seems) to happen on autosaves, i did not experience it once while manually saving, and honestly, it is EXTREMELLY random when it actually crashes the game, wich makes figuring out what is the problem much harder (at least with my limited experience on this regard)

Also, were could i find a debugger to pinpoint what mesh is the issue? would it be a simple mod or a program to hook on to skyrim executable? (or another service, im quite unaquainted with skse or the development/debugging of mods or plugings)

Oh and lastly (if im not bothering much) if the issue is caused by saving, would analyze the save wield any response? the crashes happen even on new saves if that gives any clue

[traison]

2 hours ago, Condedarkworld said:

I belive the driver is " nvwgf2umx.dll"...

 

That is not a driver, but I can see where the confusion is coming from as it's most likely bundled with the driver. Drivers use the sys extension, usually at least. You're quite unlikely to ever see a crash log from a usermode application reference an actual driver - it may not even be technically possible.

 

2 hours ago, Condedarkworld said:

it is EXTREMELLY random when it actually crashes...

 

Learn to break it, instead of trying to fix it. It'll get you to the answer quicker. In other words, make it not random, find a place where it's very likely (or guaranteed) to happen.

 

2 hours ago, Condedarkworld said:

...would analyze the save wield any response?

 

If one is created despite the crash then yeah throw that into ReSaver. It's quite likely it's just going to tell you its corrupt, but who knows.

 

2 hours ago, Condedarkworld said:

Also, were could i find a debugger to pinpoint what mesh is the issue? would it be a simple mod or a program to hook on to skyrim executable?

 

Simple? No. You need to know the x86-64 assembly language, how a compiler works and how to bypass debugger traps and DRM. Only then can you see about getting one into Skyrim.

 

Your best bet might be to remove mods until the problem goes away. If you want to try limiting the search a bit, start by disabling CBPC followed a by mods containing a dll. The "dispatched message." is in the crash log and this is from an internal communication system between SKSE and SKSE plugins if I'm not mistaken.

Edited April 28 by traison

[Condedarkworld]

4 hours ago, traison said:

If this crash happened while you were saving, then the issue is in serializing a mesh with a BSEffectShaderMaterial node with a "Type" value set to kEffect. A debugger might be required to find out where that came from.

okay, so with this information, the problem is in a mesh, correct? so if i can somehow scan all meshes, to find wich one has this error (from my research this kEffect in a mesh can lead to crashes on save, correct if im wrong) i can simply... remove the type? or replace it with something else? ofc it will change its visual or what not, but honestly, wouldnt be the first time i have to edit something so it works, the main diff is that this time i dont know exactly what mesh is.

Edit: would nifskope file checker do the trick? it does seem to have the capability to check for a value name and its... well... value

Edited April 28 by Condedarkworld
more info/question

[traison]

53 minutes ago, Condedarkworld said:

...the problem is in a mesh, correct?

 

Seems so.

 

53 minutes ago, Condedarkworld said:

...from my research this kEffect in a mesh can lead to crashes on save, correct if im wrong...

 

That seems unlikely, but sure, if kEffect is some leftover from Oblivion or Fallout 4 which is absolutely not supported in Skyrim SE then why not.

 

53 minutes ago, Condedarkworld said:

...would nifskope file checker do the trick?

 

Using NifSkope would still have you open each mesh (of potentially thousands) one by one. I would not do it like this. If I was to go by the BSEffectShaderMaterial and mesh hint, I'd search through all nifs in all mods, including those hidden in BSA archives for "BSEffectShaderMaterial". With any luck you don't have thousands or even hundereds of these in your mod files. Notepad++ can do most of it, but it won't search within packed BSAs. I've made a utility that can do it. It's available upon request.

Edited April 28 by traison

[Condedarkworld]

9 minutes ago, traison said:

 I've made a utility that can do it. It's available upon request.

Would love to give it a shot, honestly just anything to get this dead horse of a install going, too much hassle to really reinstall all of this (hours and hours of downloading stuff, and the end result is something i liked... even if a bit broken by this crash issue)

[traison]

Link sent.

[Condedarkworld]

Okay, so, after trying to find the mesh (wich i wasnt able to) I did the following...
I was playing normally with autosave turned off (via mod) to test out if manual saving was free from the issue... it was not, but, one thing that standed out that it crashed in a place with a "fireplace" model (the mesh with a bundle of wood alone by itself), that made me think that it was a possible issue with ENB light (since it changes the meshes, and nifskope got a bit pissy with one of them... tho i dont think it was the fireplace one), so i disabled it and tested again, ran fine for a while until it crashed again, future logs didnt mention any keffect or similar, soooo I figured it might be the driver all along, so I repeated the DDU safemode stuff and installed the earliest driver I have backuped in my hard drives, and who would have guessed, the problem seems to be gone? honestly I cannot be 100% sure, but I turned auto save on and Im constantly saving in areas that seem likelly to cause a crash and they dont!

Since Im on an RTX 3050 i cannot say if others using different gpu's might have the same issue I had (or i might still have it! will edit this if it does not crash during this week, and will make a new post if it does crash again, with a new log), but if anyone is interested, the version Im currently using is 532.03, I have other version backed up that prolly wont crash (if the issue was the driver in the first place) but since Im tired of this, i will just keep using this oldass version until i encounter another crash with similar log

I deeply thank you glorious traison for helping me out, time is life, and for you to have spent time, even if just mere minutes helping me on this forum, I feel gratitude.

Wish you a nice and lovelly day : )

[Condedarkworld]

Okay... the crashes still persis on saving... but their seemingly "random" behaviour really makes me have no fucking idea of what can be, like, its happens ONLY on saving, all other crashes i had that werent on saving are things im well aware and could fix by myself (execpt one regarding obody and it trying to apply morphs on a non-existant npc near falkreath, wich I cant solve due to the fricking MCM option to disable performance mode just ignoring all inputs... annoying but it isnt like I really go there or plan to at the moment)

To be fair, it is highly likelly caused by a mod, tho I yet to test out if it crashes on vanilla, wich could mean windows is at fault or some other software outside the game (wich would be odd considering this windows 11 install is very clean, installed it like a month ago)

and the logs now show nothing related to shader or effect, at least that i was able to see (did ctrl + f and searched for keffect and shader, nothing found), could try and disable the DLL mods that appear on the logs, since they are consistent, might do that.

For now i just play the game without autosave and pray that it doesnt crash, tho it is funny to see my save numbers go so high

[Condedarkworld]

Okay, so, I figured out the cause of this, There is a mod named "Modex" wich is basically additemmenu but much better and AE compatible, problem is that its feature "show in-game results" does something something you crash when saving after a while, I tested using the fuction and saving and moving repeatedly and it triggered a CTD, and the log shows only SKSE.dll, SkyrimSE.exe, HDTSMP64.dll and other DLL's that run non-stop (or something else, dont know alot to say for certain), so if ANYONE else stumbles upon this post, and has the same issue as I do, it is modex show in-game feature, just dont use it i guess... 

https://www.nexusmods.com/skyrimspecialedition/mods/137877?tab=bugs

https://www.nexusmods.com/skyrimspecialedition/mods/17230?tab=posts

[traison]

31 minutes ago, Condedarkworld said:

Okay, so, I figured out the cause of this...

 

Well done. This is the problem with dll mods. They have great potential; this has 2 opposite meanings.

 

Edit: Here's a replacer mod:

https://www.nexusmods.com/skyrimspecialedition/mods/65343

Edited May 13 by traison

[Condedarkworld]

Honestly, my biggest mistake was getting too confided that I could just install everything and play without any issues... sometimes I forget the basics even after near 9 years of modding this game! overconfidence is trully a slow and incidious killer, but finally deciding to search out the mods I first installed and reading through their requirements, posts, bugs, etc etc lead me to the discussions and posts linked above.

I also gotta thank you for spending our time here on this topic, thankies (●'◡'●)