Constant CTDs after migrating to new PC, need advice with enblocal

[RaulCuevas]

Recently I migrated all my data, included Skyrim, to a new system. My specs are as follow:

 

Intel i5 3.2 ghz 65000

Nvidia GTX 970 4 gb

16 GB Ram

SSD 256 GB for Skyrim

Windows 7 64 bits

 

Anyway, I used my same mods and my FPS went Sky high even on Ultra, and my sluttering disapeared. Problem is, I'm now getting totally random CTDs in normal gameplay, when I used to have them like, once a week or something.

 

I'm using all the official plugins properly cleaned, the USLEEP and in general all guidelines for a stable game (yes, I checked my load order is the same, I copied the files in the Skyrim folder in the Appdata directory).

 

Now, I'm guessing it may be a problem with my settings in my enblocal.ini file. I use enboost but not enb, and in my past system, I remember sometime I was crashing like crazy in my old system due to bad setting in the ini. I'm hoping somebody could help me, telling me the recommended numbers and settings according to my specs. I got the VideoMemorySizeMb value using the calculator (the one where you have to sustract certain number from the result).

 

Any help would be appreciated.

 

My ini:

 

[PROXY]
EnableProxyLibrary=false
InitProxyFunctions=true
ProxyLibrary=d3d9B.dll

[GLOBAL]
UsePatchSpeedhackWithoutGraphics=true
UseDefferedRendering=false
IgnoreCreationKit=true

[PERFORMANCE]
SpeedHack=true
EnableOcclusionCulling=true

[MEMORY]
ExpandSystemMemoryX64=false
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=128
=11734
EnableCompression=false
AutodetectVideoMemorySize=false

[THREADS]
DataSyncMode=0
PriorityMode=0

[MULTIHEAD]
ForceVideoAdapterIndex=false
VideoAdapterIndex=0

[WINDOW]
ForceBorderless=false
ForceBorderlessFullscreen=false

[ENGINE]
ForceAnisotropicFiltering=true
MaxAnisotropy=16
ForceLodBias=false
LodBias=0.0
AddDisplaySuperSamplingResolutions=false
EnableVSync=true
VSyncSkipNumFrames=0

[LIMITER]
WaitBusyRenderer=false
EnableFPSLimit=false
FPSLimit=60.0

[iNPUT]
//shift
KeyCombination=16
//f12
KeyUseEffect=123
//home
KeyFPSLimit=36
//num / 106
KeyShowFPS=106
//print screen
KeyScreenshot=44
//enter
KeyEditor=13
//f4
KeyFreeVRAM=115
//B
KeyBruteForce=66

[ADAPTIVEQUALITY]
Enable=false
Quality=1
DesiredFPS=20.0

[ANTIALIASING]
EnableEdgeAA=false
EnableTemporalAA=false
EnableSubPixelAA=false

[FIX]
FixGameBugs=true
FixParallaxBugs=true
FixParallaxTerrain=false
FixAliasedTextures=true
IgnoreInventory=true
FixTintGamma=true
RemoveBlur=true
FixSubSurfaceScattering=true
FixSkyReflection=true
FixCursorVisibility=true
FixLag=false

[LONGEXPOSURE]
EnableLongExposureMode=false
Time=1.0
BlendMax=0.0

[Hexxagone]

Open Skyrim.ini (My Documents/My Games/Skyrim) and add the following to it:

 

[Papyrus]

fPostLoadUpdateTimeMS=500.0

bEnableLogging=1

bEnableTrace=1

bLoadDebugInformation=1

 

Afterward, in that same folder you will see a new folder called Logs. Inside that: Script. Inside Script you will (eventually) find 4 logs. Double click and they should open with notepad or any text editor.

 

Papyrus.0.log is the most recent. At the end of it you will see the last process to happen before the crash. Use it to find out why it is crashing.

[RaulCuevas]

The papyrus log isn't mean to be used as a crash log, actually. That practice tend to send gamers in goose chases looking for faulty mods when the reason might be far from the script activity in the log.

 

Also, not all crashes are script related. As I say, I'm almost sure the issue is memory related.

[Hexxagone]

Its good to test if the crash is scrupt related or not. It also shows what process happened before the crash like awarding an achievement. I found out my crash was the achievement 48 crash bug using this.

[RaulCuevas]

Many mod authors advice against using it as a crash log. Also, certain scripts repeat themselves hundred of times and it doesn't mean anything particular. I've found the test made by disabling plugins 5 or 10 at a time MUCH more useful and accurate.

 

Anyway, as I said, the issue did arise with the change of PC, and so, the specs.

 

I'd appreciate advice on configuring the enblocal ini file.

[RaulCuevas]

Bump, I guess.