After modding Skyrim for 4 years, I am at a loss [NLA+180 mods+New Game/Save]

[edesart]

I'm having a similar problem. Research is sketchy. People are blogging all over the place about it and offering differing and often opposite opinions as to the fixes. I have seen several people post that it was a problem that was supposed to be fixed but then other's are posting that it's been so long since ms/amd/nvidia has known about it that they aren't hopeful.

I've been tweaking my memory configs in the ini's. Seems that enblocal is getting hosed by either win 10 or the video driver. I use nvidia and they update often. I've noticed diffent types of crashes depending upon which drivers are running. I opted into the nvidia experience beta drivers recently and it crashed Skyrim immediately. I reverted.

I've been playing around with this and I still am getting random ctd's.

[MEMORY]

ExpandSystemMemoryX64=true

ReduceSystemMemoryUsage=true

DisableDriverMemoryManager=true ;

DisablePreloadToVRAM=false

EnableUnsafeMemoryHacks=false ;

ReservedMemorySizeMb=512

VideoMemorySizeMb=4064 ;

; VideoMemorySizeMb=7810

EnableCompression=true

AutodetectVideoMemorySize=false

The nvidia memory manager was definitely the cause of earlier crashes so on advice I turned it off and that seemed to work well. ENB is supposed to cash to my ssd when vram allocation rises over my 4gb. It would appear windows 10 is stopping this from happening. My log shows me running at nearly 4 at load but I can't see any correlation between vram load and the crashing. Driving me nuts as well. :tongue:

Edited July 6, 2016 by edesart

[Darkstyler35]

<I've noticed diffent types of crashes depending upon which drivers are running. I opted into the nvidia experience beta drivers recently and it crashed Skyrim immediately. I reverted>

 

A guy recently resolved this kind of problem by reverting to older drivers, perhaps more compatible.

[HalloweenWeed]

I had a random CTD too when using Realistic Water Two. Then it was repeatable 100% of the time at a point in NE Solstheim (NW of the Skaal village) so I figured it out.

 

Also, take this word of advice from a former troubleshooter of >10yrs.: don't assume 100% that just because you did those things that caused the problem. Sometimes it is just coincidence and there is another problem developing. Does it happen in other games? And yes, could be some mods and/or drivers don't play well with Win10 DirectX, sound, etc.

 

 

When you know probable cause (the previous actions before the problem) it is all well and good to use troubleshooting shortcuts to save time, but when they don't work you should go back to the basics and start troubleshooting from the beginning without assuming anything.

Edited July 6, 2016 by HalloweenWeed