CTD, Need help deciphering crash log

[Grey Cloud]

Your SKSE.ini should look similar to this

[Display]
iTintTextureResolution=2048

[General]
ClearInvalidRegistrations=1
EnableDiagnostics=1

[Memory]
DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=256

 

No more, no less. Your DefaultHeap and ScrapHeap figures my be different. If they are let me know what they are.

 

For CrashFixPlugin.ini

UseOSAllocators=1

AlignHeapAllocate=1

All other settings are at default. I would recommend replacing your current CrashFixPlugin.ini with the one from the Crash Fixes archive and then making the these two changes. That way you will know that you have not got any rogue settings in there from previous experiments.

 

If you have SKSE Plugin Preloader correctly installed you will have a d3dx9_42.dll in your Skyrim folder.

 

In your Skyrim folder you should also have

d3d9.dll [Note that this is a different dll than the SKSE Plugin Preloader dll]

enbhost.exe

enblocal.ini

 

For good measure you should also download Bethini which I forgot to mention earlier. You can run that later.

[Ludicrate]

Correct, that's how I have it installed

[Grey Cloud]

34 minutes ago, Ludicrate said:

Correct, that's how I have it installed

And you saying that you still crash?

 

Do you see the ENBoost text on the start up screen as per my screenshot?

[Uncle64]

safety load/ssme Should you not use, since they are abandoned.

 

I can add to this line in skse.ini

 

DefaultHeapInitialAllocMB=768   You can set that value on 1024 if you need it, BUT you can never revert it back down to 768.

[Grey Cloud]

8 minutes ago, Uncle64 said:

You can set that value on 1024 if you need it, BUT you can never revert it back down to 768.

Interesting, why not? Never heard that one.

[Uncle64]

25 minutes ago, Grey Cloud said:

Interesting, why not? Never heard that one.

You dont....But I can inform you that it is old information.
If you check on some of the mayor treads on Steam you will find the information. And you should actually know that.

 

 

Only to be clear. You cant put it on 1025 and play and change it to 768 and play on the same save, It have same issue as Ugridstoload you cant change that one to.

[Grey Cloud]

25 minutes ago, Uncle64 said:

But I can inform you that it is old information.

Just because it is old information does not mean it is reliable information. If it was so important I would have thought that it would have been mentioned on a regular basis rather than be buried on Steam somewhere.

Can you explain why this settings cannot be reverted? Every other setting in every other ini that I am aware of can be altered and then changed back to the original setting. What is different about this one? Could you also explain what happens if you do revert it becuase I'm pretty sure I have done it on this machine and my previous one.

 

meh321 doesn't mention it.

https://www.nexusmods.com/skyrim/mods/72725

Data/SKSE/SKSE.ini (not needed if UseOSAllocators=1 in CrashFixPlugin.ini):

• Set DefaultHeapInitialAllocMB:Memory to 768. If you are using a lot of mods or higher uGrid than 5 then set 1024. Helps with CTD during save load, especially if you can load the save after qasmoke. Max value is 1280. If you are using ENB you may get CTD on startup with higher value than 768 and ExpandSystemMemoryX64 true in enblocal.ini!
• Set ScrapHeapSizeMB:Memory to 256. Game can't use more than 256 of this and setting higher serves no purpose.

GamerPoets don't mention it.

https://gamerpoets.com/text-tutorials/skyrim-text/skse-skyrim-script-extender-start-finish/

 

This Steam guide doesn't mention it

https://steamcommunity.com/app/72850/discussions/0/540740500921363665/

 

I couldn't find anything on S.T.E.P.

[Psalam]

1 hour ago, Ludicrate said:

Correct, that's how I have it installed

ENBoost can be a bit trickier if you have Windows10. This is from my blog:

 

2) ENBoost. This one is more difficult and I hope to do a walkthrough at some point in the future. It is VERY important if you have less than 4GB of VRAM. If you have 8GB or more you probably don't need it. At 4GB it's your call (I have 4GB and I use it). Anyway, you will need to look in more than one place in order to complete this (although it will take you through it). Start here:

 

https://www.nexusmods.com/skyrim/mods/73618

 

As if ENBoost is not difficult enough MicroSoft has chosen to throw some additional glitches in for users of Windows 10. If you have problems getting ENBoost to work and you run Windows 10 take a look at this (I had to):

 

https://forums.nexusmods.com/index.php?/topic/3089504-fix-for-skyrim-crashing-instantly-with-enb-on-windows-10/?p=56131491

 

If you are using Windows10 look at the last link and follow the instructions carefully. I had fits with ENBoost and Windows10 until this was pointed out to me. I have no issues with it now.

[Grey Cloud]

2 minutes ago, Psalam said:

ENBoost can be a bit trickier if you have Windows10.

Perhaps this was once true for one particular version of W10 but is it true for all versions? I've had several versions of W10 on this machine and never had a problem with my ENB, either installing it or updating it.

 

The post you are linking to is 2 years old. How many W10 updates have come and gone since then?

 

There's also this thread here on LL

https://www.loverslab.com/topic/58153-crash-fix-enboost-60-by-boris-vorontsov/

 

15 minutes ago, Psalam said:

As if ENBoost is not difficult enough

You keep posting this but it is 3 fucking files and some basic tweaking of settings in an ini file all of which are explained simply and clearly by the likes of S.T.E.P. and GamerPoets.

[Just Don't]

32 minutes ago, Grey Cloud said:

Perhaps this was once true for one particular version of W10 but is it true for all versions? I've had several versions of W10 on this machine and never had a problem with my ENB, either installing it or updating it.

 

Yep, I've been playing both LE and SE in Windows 10 for years, and the issues with ENB were minor (mostly due to using old presets with the wrong binaries, or not having the enbhelper dll for custom weather support in some presets). The big issue with W10 is the dlls from Reshade, where you must rename or remove some dlls, making certain features from Reshade useless.

[GenioMaestro]

3 hours ago, Uncle64 said:

...

DefaultHeapInitialAllocMB=768   You can set that value on 1024 if you need it, BUT you can never revert it back down to 768.

 

2 hours ago, Uncle64 said:

You dont....But I can inform you that it is old information.
If you check on some of the mayor treads on Steam you will find the information. And you should actually know that.

 

Only to be clear. You cant put it on 1025 and play and change it to 768 and play on the same save, It have same issue as Ugridstoload you cant change that one to.

Please, can you link the post where you read that? Or any other thecnical info about it?

 

As far as I know, DefaultHeapInitialAllocMB only determines the size of the Block1 and did so at the beginning of the game. Increase the value from 768 to 1024 can solve the random CTD caused by Block1 full.

But if you can load your savegame and play the game, the DefaultHeapInitialAllocMB value is totally indifferent. Nothing related to DefaultHeapInitialAllocMB is stored inside the savegame.

[Grey Cloud]

4 minutes ago, GenioMaestro said:

But if you can load your savegame and play the game, the DefaultHeapInitialAllocMB value is totally indifferent. Nothing related to DefaultHeapInitialAllocMB is stored inside the savegame.

Thank you. That was my understanding of things.

 

And while you are here, didn't you post about this a while back?

Crash Fix ENBoost

https://www.nexusmods.com/skyrim/mods/73618

[Ludicrate]

Yeah, I did all that right, not the first time either, and thanks for your help again, but it's not gonna work.  I just delet d Skyrim, I'm done messing with it for a while.  Merry Christmas

[Ludicrate]

I've never needed ENB to run Skyrim with the mods I listed on the OP, played for months without ENB, years before that until i first tried ENB.  Skyrim only ever crashed to do other mod inconsistenties, which I worked out, so I clearly do not need ENB.  Skyrim isn't crashing for me due to memory, I've pretty much checked that off the list, meaning even if I got ENB, the crashes would still likely keep occurring.  I know about not changing Skse.ini from 1024 back down also, and that was not the problem.  I believe a bad mod or something corrupted the savegame.  Doing a clean install next month or something, I'm not wasting any more time on it any time soon.

[Grey Cloud]

I'm not trying to be insulting but your problem is that you have too many preconceptions based on too little understanding of how Skyrim and modding it works.

 

You say that Skyrim is not crashing for you because of memory but how do you now that? If it were true then you would be the only person in 8 years of Skyrim that was exempt from the limitations of Skyrim's poor memory management.

That Skyrim has such limitations is well documented and not just my opinion. Skyrim LE's 32-bit engine can only handle 3.1GB of RAM. Why do you think the stability tools are all memory management tools? My machine has 32GB of RAM but Skyrim doesn't care.

 

What people typically refer to as an ENB consists of two parts - the binaries (ENBoost) and a preset (the pretty graphics part. Rudy, Bleak, Bixie, etc.). You can run ENBoost without a preset, and that is what I have been trying to get you to do, but you cannot run a preset without ENBoost.

 

2 hours ago, Ludicrate said:

Skyrim only ever crashed to do other mod inconsistenties,

That is your interpretation of things. How do you know that the combination of these mods was not pushing your game over the edge due to memory issues?  I run 300 mods and there are many on LL who run similar or greater numbers. Mod 'inconsistencies' what are they?

 

2 hours ago, Ludicrate said:

I know about not changing Skse.ini from 1024

That is nonsense and can safely be ignored.

 

 

It is entirely possible and even probable that your saves not loading is due to memory. Saves grow as your game goes on, all those items in your inventory, all those journal entries etc.

After 1 hour my save was 7.55MB, after 162 hours it is 24.6MB. That is not large by any means but it is still three times larger than it was.

Saves can become corrupted but, in my experience at least, it is very rare.

 

As you are going to do a fresh install, I suggest you make sure that there is nothing left of the old installation before installing the new game. Don't just install over the old.

Then get the base, vanilla game stable before you load it with mods. Install Alternative Start Live Another Life or Skyrim Unbound so you can quickly start new games without the wagon ride (which is notoriously buggy).

[Ludicrate]

The culprit, I feel very confident in saying, is this: I thought I was going off a totally vanilla install of Skyrim when I started back on this save a few months ago, from having uninstalled it a year previously.  In fact, I had already uninstalled and reinstalled Skyrim back then, going so far as setting up basic things like SkyUI, but what I didnt do was totally uninstall Civil War Overhaul the correct way, which I still had the file for, well before it was taken down.  There were still Civil War Overhaul Scripts that had begun conflicting with Open Civil War, the conflicts with which didn't effectively kick in until well into my save with the battle of whiterun (was probably causing some other less frequent crashes until that point too.)

 

Doing a totally clean uninstall of all mods, the game, then reinstalling and making sure no possible CWO stuff remaining on my computer at all lol