LOOT not reporting ITMs

[Amuscaria]

I've been suing LOOT for a long time, and it usually tells me if there are ITMs in a mod I'm using and tells me to clean it. I'm pretty familiar with cleaning and making compatibility patches. After my recent troubles of getting a stable game with even a few mods, I decided to go and check every one of my mods for ITMs (I was told they cause CTDs) and clean all of them. I've found that I had a handful of the mods used had at least 1 (sometimes up to 40) ITMs that LOOT didn't tell me about when I sorted the mods.

My 1st question is: does LOOT automatically check of ITMs like TES5Edit, or does it only know that a mod has ITMs if someone reports it to a database? I'm not familiar with the inner workings of LOOT.

 

My second question: is it safe for me to clean all ITMs and UDRs from my mods? I've seen mixed answers on Reddit and the Nexus. Thought I'd ask some experts at S.T.E.P.

 

Thank you for the clarification.

[Kelmych]

LOOT only knows about ITMs and UDRs if they are reported to their database.

 

It is usually safe to eliminate ITMs and UDRs. The mod page on Nexus and/or STEP will typically indicate if this should not be done.

[Amuscaria]

Does ITMs cause CTDs, though? Or are they generally harmless? I've read that UDRs should be removed because they do cause CTDs.

[IsharaMeradin]

ITMs should not cause CTDs.  At the worst, they'll prevent another mod which changes the same record and is loaded earlier from having its changes used.

 

Some ITMs are intended as the author wants to ensure that the items have specific values for their mod to function properly.  Other ITMs are from changes that were reversed rather than simply removing the record from the plugin.

[Amuscaria]

Then I'm at a lost at what's causing my CTDs. I suppose It's possible I set my ini files to use too much memory, although I am using the STEP guide to the letter. I have ENBoost, and my rig should be more than enough for the "Performance" ENB from Vivid weathers with a gtx 1070, an i7-6700k overclocked 4.2 ghz CPU and 16 gigs of DDR4 RAM.

 

I've tried Crash Fixes, which didn't help. Chaning my ENBoost Threads settings based in the anti-CTD fixes didn't help.

 

I thought about checking the memory, but something seems to be not working with the MemoryBlockLog. It will only record 2 entries then stop. I have no idea what happened. It worked the first time, then just stopped. I've reinstalled it, but still only records 2 entries (85,85 for the first block, and 2,2 for the second). This is while running around the Windhelm docks WITH Better Docks enabled.

 

I've been using only vanilla skyrim, official DLCs, and then just texture packs. Still CTDs on start up half of the time.

 

Any ideas what else I can do, or does my GTX 1070 simply not work with END correctly?

Edited September 12, 2016 by Amuscaria

[Kelmych]

Did you use BethIni to setup the game INI configuration to make sure they were correct; there are some INI settings that will cause CTDs. When you installed the texture mods, what resolution did you use? You mentioned Better Docks which is more than a texture mod; what other mods are you using that aren't texture or mesh only mods? Have you tried running without the ENB active, and if so were there also regular CTDs? It would be helpful if you posted your enblocal.ini (using spoiler tags so it doesn't take up as much room.

[Amuscaria]

Here are my inis.

 

Skyrim.ini: https://pastebin.com/hvAwbXyw

 

Skyrimprefs.ini: https://pastebin.com/UrU98Tj9

 

ENBlocal: https://pastebin.com/gxj31ems

 

SKSE.ini: https://pastebin.com/4t2MfBwy

 

 I made them from the default ULTRA inis from bethesda after the game detects my settings. I copied them from my "/documents/games/skyrim" folder, into my MO profiles folders and edited them there based on Gamerpoet's Youtube video, as well the STEP wiki.

My Textures are SKyrim HD LITE, and AmidianBorn Book of Silence + Landscapes + Mines and caves, The Rustic HD textures, and a couple of other ones. None of them are higher than 2k. And the Official HD pack, but left those unchecked.
 

I wasn't testing the game with a single profile. I have 1 profile where I used only high-res texture mods, another where I have mods that expands on the towns (ETAC), Skyrim immersive creatures, Skytest, Immersive Armors, and another Vanilla with just the UI addons like SKY UI, expanded UI, MoreHud, a matter time, etc.

 

None of these make a more stable game. The ENB even crashes with just vanilla Skyrim half of the time on the main menu. My drivers, maybe?

I've tried expanding my SKSE memory patch to 1024 (1280), and it doesn't seem to help.

Edited September 12, 2016 by Amuscaria

[Greg]

If you set UseOSAllocators=1 in CrashFixPlugin.ini, Memory Blocks Log will not report correct values and the [Memory] section of skse.ini will be ignored. This is because the Crash Fixes plugin disables the memory management section of SKSE to use its own memory management strategy.

 

I usually leave UseOSAllocators=0 and use the SKSE memory settings.

[Amuscaria]

Does the crash fixes work when UseAllocators=0?

So is my 1024mb first block not actually 1024, and I was running out of memory this whole time?

 

Thanks for the heads up, though. I will try with UseAllocators=0.

Edited September 12, 2016 by Amuscaria

[Amuscaria]

I think I finally found the cause of my constant CTDs: It was either Geforce Experience or the Steam Overlay. I've disabled them both and my game hasn't crashed. Fingers crossed. :P

 

[Kelmych]

Multiple posts have mentioned problems with the game overlay programs from both Nvidia and AMD. I haven't heard of any problems caused by the Steam overlay.

[Greg]

Does the crash fixes work when UseAllocators=0?

 

So is my 1024mb first block not actually 1024, and I was running out of memory this whole time?

 

Thanks for the heads up, though. I will try with UseAllocators=0.

Yes, Crash Fixes works when UseOSAllocators=0.

 

Well, no. You have two choices in regards to memory allocation strategies. If UseOSAllocators=0, the game uses the SKSE memory management strategy so you have to adjust the memory settings in skse.ini and you can monitor the first and second block usage in Memory Blocks Log. If UseOSAllocators=1, the game uses the Crash Fixes alternative memory allocation strategy so Memory Blocks Log no longer accurately reports the usage of the first two blocks. In other words, Memory Blocks Log is effectively useless if you have UseOSAllocators=1.

 

The general recommendation is to install Crash Fixes with the default INI settings (which has UseOSAllocators=0) and to use the SKSE memory allocation strategy and this is how I have Crash Fixes configured.

[Amuscaria]

Yes, Crash Fixes works when UseOSAllocators=0.

 

Well, no. You have two choices in regards to memory allocation strategies. If UseOSAllocators=0, the game uses the SKSE memory management strategy so you have to adjust the memory settings in skse.ini and you can monitor the first and second block usage in Memory Blocks Log. If UseOSAllocators=1, the game uses the Crash Fixes alternative memory allocation strategy so Memory Blocks Log no longer accurately reports the usage of the first two blocks. In other words, Memory Blocks Log is effectively useless if you have UseOSAllocators=1.

 

The general recommendation is to install Crash Fixes with the default INI settings (which has UseOSAllocators=0) and to use the SKSE memory allocation strategy and this is how I have Crash Fixes configured.

Awesome! Thanks for the help. :)

[remlnx]

Actually I have had 0 CDT since when I have set "UseAllocators=1" AND "CustomMemoryBlock=1". Before that I had 1 CDT every two hours or so, now it is 3 days (about 20 hours playtime) without any CDT. So yes..I really warmly suggest to set both values to 1

 

Sent from my SM-G925F using Tapatalk