Vortex Mod Manager

[Sneaksmile]

1 minute ago, Grey Cloud said:

Just because you cannot find the solution to your problems it does not follow that there is not a solution. Thousands of users run LE without constant CTDs.

I did it too, CTDs every 4 or 5 hours with more than 400 mods installed is not bad at all. But now the solution does not work. I tried 'Crash Fixes' instead of SSME and it was even worse. 

[Grey Cloud]

25 minutes ago, Sneaksmile said:

CTDs every 4 or 5 hours with more than 400 mods installed is not bad at all.

Yes it is.

[Sneaksmile]

4 minutes ago, Grey Cloud said:

Yes it is.

Well, CTD every half hour with only 100 mods installed, is much worse. 

 

[Sneaksmile]

11 minutes ago, Grey Cloud said:

Yes it is.

 

And the point is that 5 hours without CTD for me is VERY GOOD compared to what happens now. And if you do not think to help, then better go to another part to show off your game with 2,000 mods and that does not CTD playing 5 days in a row. 

[Guest]

2 hours ago, Sneaksmile said:

But I can't fix the CTDs anymore ... HOW?! ... I did everything the guides with fixes suggest and the CTDs are worse. My only hope is that 64 bits helps something.

I really like LE due to the large number of mods available and with a few mods you can make it look much better than SE (graphically speaking) ... but ... it is very annoying to follow all the guidelines to stabilize it and even then the problems continue or get worse. For example, I managed to stabilize my old game with the Memory Patch, you know SSME and other fixes. But now that doesn't work, the first block fills up too fast and when it reaches 400 MB, the game always CTD. In my old game it took at least 4 hours to reach 400 MB and only CTD when it reached 500 MB. 

I deactivated the 4K Parallax textures and the Dat Grass mod, which are the 'heaviest' Mods that I have installed but the time the game reaches 400 MB does not change at all, it is too fast, it reaches them in less than an hour. 

I no longer know what to do with that CTD problem, due to my prior knowledge of my previous game ... I literally know all the fixes that exist for the game, nothing can surprise me or be new to me in that regard. So I think I have to give up, it has no solution.

What crash exactly and what are you talking about 400/500 MB? I hope it's not RAM because the TESV.exe process should be able to reach ~3.5 GB safely. If your TESV.exe process is running out of 32-bits virtual address space, enable MEMORY:ReduceSystemMemoryUsage within your enblocal.ini as to allow ENB to move certain data to enbhost.exe processes.

 

I get about 1 crash every 1 or 2 months with my setup.

[Sneaksmile]

7 minutes ago, Hawk9969 said:

What crash exactly and what are you talking about 400/500 MB? I hope it's not RAM because the TESV.exe process should be able to reach ~3.5 GB safely. If your TESV.exe process is running out of 32-bits virtual address space, enable MEMORY:ReduceSystemMemoryUsage within your enblocal.ini as to allow ENB to move certain data to enbhost.exe processes.

 

I get about 1 crash every 1 or 2 months or so with my setup.

 

I'm talking about the Memory Patch. Which allows to use more than 256 mb in first block, that the game uses by default. 
 

[Sneaksmile]

10 minutes ago, Hawk9969 said:

What crash exactly and what are you talking about 400/500 MB? I hope it's not RAM because the TESV.exe process should be able to reach ~3.5 GB safely. If your TESV.exe process is running out of 32-bits virtual address space, enable MEMORY:ReduceSystemMemoryUsage within your enblocal.ini as to allow ENB to move certain data to enbhost.exe processes.

 

I get about 1 crash every 1 or 2 months or so with my setup.

 

CTDs are always random, there is no exact reason that causes them. But they happen when the log reaches 400MB or a little less. 

[Sneaksmile]

11 minutes ago, Hawk9969 said:

What crash exactly and what are you talking about 400/500 MB? I hope it's not RAM because the TESV.exe process should be able to reach ~3.5 GB safely. If your TESV.exe process is running out of 32-bits virtual address space, enable MEMORY:ReduceSystemMemoryUsage within your enblocal.ini as to allow ENB to move certain data to enbhost.exe processes.

 

I get about 1 crash every 1 or 2 months with my setup.

'' enable MEMORY:ReduceSystemMemoryUsage '', I already did that, there is no improvement.

[Guest]

Are you talking about Crash Fixes' CustomMemoryBlockTotalSizeMb or SKSE's DefaultHeapInitialAllocMB?

Also, what log is that from the screenshot? I've no idea what I am looking at.

4 minutes ago, Sneaksmile said:

'' enable MEMORY:ReduceSystemMemoryUsage '', I already did that, there is no improvement.

Something is wrong there if you haven't seen any improvements. I can't even load my save game without that option due to TESV.exe running out of virtual address space.

 

[Sneaksmile]

17 minutes ago, Hawk9969 said:

Are you talking about Crash Fixes' CustomMemoryBlockTotalSizeMb or SKSE's DefaultHeapInitialAllocMB?

Also, what log is that from the screenshot? I've no idea what I am looking at.

Something is wrong there if you haven't seen any improvements. I can't even load my save game without that option due to TESV.exe running out of virtual address space.

 

Is this, SSME + Memory Blocks Log 
 

 

[Sneaksmile]

That helped me a lot in my old game, but now it doesn't work. 

[Sneaksmile]

19 minutes ago, Hawk9969 said:

Are you talking about Crash Fixes' CustomMemoryBlockTotalSizeMb or SKSE's DefaultHeapInitialAllocMB?

Also, what log is that from the screenshot? I've no idea what I am looking at.

Something is wrong there if you haven't seen any improvements. I can't even load my save game without that option due to TESV.exe running out of virtual address space.

 

 

'' SKSE's DefaultHeapInitialAllocMB '', I also have that but it doesn't help me. 

[Sneaksmile]

I tried Crash Fixes but it didn't help me. It even causes reboots of my computer ... wtf 

[Sneaksmile]

'' Something is wrong there if you haven't seen any improvements. I can't even load my save game without that option due to TESV.exe running out of virtual address space ''

The only '' improvement '' was a damn stuttering. I was able to fix that by modifying Skyrim.ini and telling the game that uses all the cores (processor) I have and not only 4 cores. But it didn't help with the CTDs at all. 

 

[Sneaksmile]

34 minutes ago, Hawk9969 said:

Are you talking about Crash Fixes' CustomMemoryBlockTotalSizeMb or SKSE's DefaultHeapInitialAllocMB?

Also, what log is that from the screenshot? I've no idea what I am looking at.

Something is wrong there if you haven't seen any improvements. I can't even load my save game without that option due to TESV.exe running out of virtual address space.

 

 

I have not modified anything in the ENB except for what the Modder says to make the ENB work. Except for suggestions to fix CTDs, like that. 

I use this now: 

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

In my old game ''Real Vision ENB ''. 

[Sneaksmile]

38 minutes ago, Hawk9969 said:

Are you talking about Crash Fixes' CustomMemoryBlockTotalSizeMb or SKSE's DefaultHeapInitialAllocMB?

Also, what log is that from the screenshot? I've no idea what I am looking at.

Something is wrong there if you haven't seen any improvements. I can't even load my save game without that option due to TESV.exe running out of virtual address space.

 

 

You see it? What works great for others (for you too), doesn't work for me!! And that's not my fault! I do everything right, damn it. But now I do not know what to do. 

[Guest]

SSME is already included with SKSE, these two settings in SKSE.ini:

[Memory]
DefaultHeapInitialAllocMB=1024
ScrapHeapSizeMB=256

is actually SSME. Don't bother installing it individually since it already comes with SKSE.

 

SKSE caps DefaultHeapInitialAllocMB at 1280 and ScrapHeapSizeMB at 512, don't bother raising them above that.

 

If none of these help, first start by attaching your CrashFixPlugin.ini and enblocal.ini and I'll take a quick look.

 

Reboots as errors is very unlikely to be caused by Skyrim or its SKSE plugins (unless the plugin explicitly tell the OS to reboot). Reboots like that are a sign of an OS glitch, hardware failure or CPU triple faults (unlikely for modern OSes to allow programs to triple fault though).

 

This is bloating a Vortex related thread though, so I recommend you to either start a new thread or send me the info i've requested via PM.

[Sneaksmile]

I am not complaining about Oldrim as a tantrum as the ''gray cloud'' thinks. Only nothing works to fix that. 

[Sneaksmile]

6 minutes ago, Hawk9969 said:

SSME is already included with SKSE, these two settings in SKSE.ini:

[Memory]
DefaultHeapInitialAllocMB=1024
ScrapHeapSizeMB=256

is actually SSME. Don't bother installing it individually since it already comes with SKSE.

 

SKSE caps DefaultHeapInitialAllocMB at 1280 and ScrapHeapSizeMB at 512, don't bother raising them above that.

 

If none of these help, first start by attaching your CrashFixPlugin.ini and enblocal.ini and I'll take a quick look.

 

Reboots as errors is very unlikely to be caused by Skyrim or its SKSE plugins (unless the plugin explicitly tell the OS to reboot). Reboots like that are a sign of an OS glitch, hardware failure or CPU triple faults (unlikely for modern OSes to allow programs to triple fault though).

 

This is bloating a Vortex related thread though, so I recommend you to either start a new thread or send me the info i've requested via PM.

Not in mine. I have to download this:

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

 

[Sneaksmile]

14 minutes ago, Hawk9969 said:

SSME is already included with SKSE, these two settings in SKSE.ini:

[Memory]
DefaultHeapInitialAllocMB=1024
ScrapHeapSizeMB=256

is actually SSME. Don't bother installing it individually since it already comes with SKSE.

 

SKSE caps DefaultHeapInitialAllocMB at 1280 and ScrapHeapSizeMB at 512, don't bother raising them above that.

 

If none of these help, first start by attaching your CrashFixPlugin.ini and enblocal.ini and I'll take a quick look.

 

Reboots as errors is very unlikely to be caused by Skyrim or its SKSE plugins (unless the plugin explicitly tell the OS to reboot). Reboots like that are a sign of an OS glitch, hardware failure or CPU triple faults (unlikely for modern OSes to allow programs to triple fault though).

 

This is bloating a Vortex related thread though, so I recommend you to either start a new thread or send me the info i've requested via PM.

So, like this? 

[Sneaksmile]

I don't know, maybe if it was the OS. I use Windows 10 and it has been almost a year since I updated it to the new version. But no game caused me that, only Skyrim and only with Crash Fixes when I activated the option: '' Custom Memory Block ''. 

[Sneaksmile]

21 minutes ago, Hawk9969 said:

SSME is already included with SKSE, these two settings in SKSE.ini:

[Memory]
DefaultHeapInitialAllocMB=1024
ScrapHeapSizeMB=256

is actually SSME. Don't bother installing it individually since it already comes with SKSE.

 

SKSE caps DefaultHeapInitialAllocMB at 1280 and ScrapHeapSizeMB at 512, don't bother raising them above that.

 

If none of these help, first start by attaching your CrashFixPlugin.ini and enblocal.ini and I'll take a quick look.

 

Reboots as errors is very unlikely to be caused by Skyrim or its SKSE plugins (unless the plugin explicitly tell the OS to reboot). Reboots like that are a sign of an OS glitch, hardware failure or CPU triple faults (unlikely for modern OSes to allow programs to triple fault though).

 

This is bloating a Vortex related thread though, so I recommend you to either start a new thread or send me the info i've requested via PM.

Yep lol ... this is a Vortex topic lol 

I'll send you a personal message, making a new thread is only going to confuse me more and people are only going to suggest things that I've already done. 

[Grey Cloud]

3 hours ago, Sneaksmile said:

And if you do not think to help, then better go to another part to show off your game with 2,000 mods and that does not CTD playing 5 days in a row. 

I have about 300 mods installed. My game crashes once every blue moon (=weeks and weeks) or when I break it (much more often). You obviously don't know as much about modding Skyrim as you think you do. I don't know everything so when things go wrong I point the finger at myself first that way most problems are solved in minutes rather than hours or days.

 

1 hour ago, Sneaksmile said:

CTDs are always random, there is no exact reason that causes them.

There is no such thing as random. CTDs and everything else happen due to a cause. The location or the timing of the crash may be different every time but that does not mean there is not a common underlying cause.

 

1 hour ago, Sneaksmile said:

I tried Crash Fixes but it didn't help me. It even causes reboots of my computer ... wtf 

Wouldn't be anything to do with you, would it?

 

1 hour ago, Sneaksmile said:

Not in mine. I have to download this:

If you had read the instructions for installing SKSE then you would have known that you have to create your own ini file, SKSE does not provide one.

 

53 minutes ago, Sneaksmile said:

Yep lol ... this is a Vortex topic lol 

It doesn't help when you use a new post for every comment.

 

53 minutes ago, Sneaksmile said:

people are only going to suggest things that I've already done.

Done wrong for the most part.

[Sneaksmile]

7 minutes ago, Grey Cloud said:

I have about 300 mods installed. My game crashes once every blue moon (=weeks and weeks) or when I break it (much more often). You obviously don't know as much about modding Skyrim as you think you do. I don't know everything so when things go wrong I point the finger at myself first that way most problems are solved in minutes rather than hours or days.

 

There is no such thing as random. CTDs and everything else happen due to a cause. The location or the timing of the crash may be different every time but that does not mean there is not a common underlying cause.

 

Wouldn't be anything to do with you, would it?

 

If you had read the instructions for installing SKSE then you would have known that you have to create your own ini file, SKSE does not provide one.

 

It doesn't help when you use a new post for every comment.

 

Done wrong for the most part.

Well, it's good that everything works for you, but I'm not you ... duh 

And your pedantic info is not useful at all. End of this. This is a Vortex topic.  

[Grey Cloud]

57 minutes ago, Sneaksmile said:

Well, it's good that everything works for you, but I'm not you ... duh 

And your pedantic info is not useful at all. End of this. This is a Vortex topic.  

Well thank you for the mature and considered response.

Grow up. You have pointed the finger at Skyrim, W10, Crash Fixes and who knows what else. The one thing you haven't looked at is yourself. Modding Skyrim is quite simple once one masters a few basics.

There is no need to be logging memory block usage.

 

You will need these:

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

SKSE Plugin Preloader
https://www.nexusmods.com/skyrim/mods/75795/?

ENBoost (If you are using an ENB preset then you should already have this but it can be used without a preset).
https://wiki.step-project.com/ENBoost

Bethini (This will set your Skyrim.ini and SkyrimPrefs.ini files)
https://www.nexusmods.com/skyrim/mods/69787

Load Game CTD Fix (Stops Infinite Loading Screen (ILS)
https://www.nexusmods.com/skyrim/mods/85443/

The above tools will sort out your memory management and stop 99% of CTDs.

Once you have established a stable game then add mods several at a time. This makes trouble shooting easier.

 

Try following this guide

https://www.loverslab.com/blogs/entry/7521-conglomerate-01-installing-skyrim-stability-fixes-tools/

 

or this one

https://wiki.step-project.com/STEP:2.10.0