Modded CK3 - C Drive filling up rapidly

[Dirty Jack]

Hello,
I'm running a modded version of the game and experienced in the past the issue of the crash/log thing filling up.

This is not the case now. The game's been running for about 5-10 minutes and it's already close to 10 GB full.

I also noticed that it's using 21gb of memory in Task Manager.

If I close the game, the space is cleared-up but this essentially makes it unplayable the way I want to.

Any ideas on what I can do? I can't even figure out where it's being filled up.

[Nightingaleze]

you're talking about RAM?

use RAMmap to clear your memory, I installed mod Game of throne it usually used 12-15 GB memory that's normal

set the Visual memory to help your RAM but it'll cost your drive some space.

IF your drive filled up rapidly it's probably because of Visual memory setting that's normal when RAM is almost full, the Visual memory will help RAM by get some GB Ram that the game required to Harddisk instead that maybe why your drive C filled up rapidly


your task manager RAM is up to 21 gb, I guess you never Cleanup your RAM right? when Install the mod the mod creator always tells you what is the requirement before install

sorry for bad english

[Half-lidded Bruiser]

You're using dumpster-fire mods. If logs are getting flooded, it's because you're using mods with persistent errors.
You'll have to either read the logs to identity the source(s) of the errors, or disable all of your mods, then try playing for a bit with one (1) more mod enabled each session until you figure out which one is jumping the shark.

[Dirty Jack]

It's not the error log that's increasing.
It's something else. I have it set to Read-Only and it doesn't increase.

[jpcerutti]

Again, something in one of the mods is poorly written/coded and is creating your issue. You have to figure out which one of the mods is giving you a problem and either fix the issue (mod the mod) or quit using it. They probably failed to close something out or delete old data and a file or dataset is doubling in size every time it is referenced.

[Phero]

Download something like "Windirstat" a small free tool that will tell you what is using up your storage space.

[Dirty Jack]

Originally posted by Phero:

Download something like "Windirstat" a small free tool that will tell you what is using up your storage space.

Apparently it's a c:\pagefile.sys that keeps increasing.

Any ideas? It's not even showing up when I go to location so I'm thinking this is a system file.

[Cinemax]

Originally posted by Nightingaleze:

you're talking about RAM?

use RAMmap to clear your memory, I installed mod Game of throne it usually used 12-15 GB memory that's normal

set the Visual memory to help your RAM but it'll cost your drive some space.

IF your drive filled up rapidly it's probably because of Visual memory setting that's normal when RAM is almost full, the Visual memory will help RAM by get some GB Ram that the game required to Harddisk instead that maybe why your drive C filled up rapidly


your task manager RAM is up to 21 gb, I guess you never Cleanup your RAM right? when Install the mod the mod creator always tells you what is the requirement before install

sorry for bad english

This guy is kind of correct but he's using wrong terminology. You probably have dynamically expanding virtual memory (which he called visual memory). When a mod runs like ass and burns a ton of RAM the OS will offset to a file on C:\ called pagefile.sys (hidden, system file). By default it sizes dynamically but has a min|max value.

Search > Advanced System Settings
Advanced > Virtual Memory > Change
Custom Size:
Initial Size (MB):
Maximum Size (MB):
Set

Set them to a fixed value (same min/maxed) for a consistent allocation. I like to set to the same value as my physical memory (RAM). If you don't provide enough paging space for your ♥♥♥♥ mod to ♥♥♥♥ up your ♥♥♥♥♥♥♥♥♥, your game will run VERY bad. Memory paging also shortens the lifespan of SSDs it uses, so enjoy that.

But yeah, to clarify, your problem stems from the mod sucking ass, as others have said.


Edit: I wrote this as you were typing the post that confirmed all of the above. Damn I'm good.

[Dirty Jack]

Originally posted by Cinemax:

Originally posted by Nightingaleze:

you're talking about RAM?

use RAMmap to clear your memory, I installed mod Game of throne it usually used 12-15 GB memory that's normal

set the Visual memory to help your RAM but it'll cost your drive some space.

IF your drive filled up rapidly it's probably because of Visual memory setting that's normal when RAM is almost full, the Visual memory will help RAM by get some GB Ram that the game required to Harddisk instead that maybe why your drive C filled up rapidly


your task manager RAM is up to 21 gb, I guess you never Cleanup your RAM right? when Install the mod the mod creator always tells you what is the requirement before install

sorry for bad english

This guy is kind of correct but he's using wrong terminology. You probably have dynamically expanding virtual memory (which he called visual memory). When a mod runs like ass and burns a ton of RAM the OS will offset to a file on C:\ called pagefile.sys (hidden, system file). By default it sizes dynamically but has a min|max value.

Search > Advanced System Settings
Advanced > Virtual Memory > Change
Custom Size:
Initial Size (MB):
Maximum Size (MB):
Set

Set them to a fixed value (same min/maxed) for a consistent allocation. I like to set to the same value as my physical memory (RAM). If you don't provide enough paging space for your ♥♥♥♥ mod to ♥♥♥♥ up your ♥♥♥♥♥♥♥♥♥, your game will run VERY bad. Memory paging also shortens the lifespan of SSDs it uses, so enjoy that.

But yeah, to clarify, your problem stems from the mod sucking ass, as others have said.
:adulterer:

Edit: I wrote this as you were typing the post that confirmed all of the above. Damn I'm good.

In that case, I'd rather not damage my SSD.
Is there some method I can find which mod is causing this problem?

I run a AGOT and Shogunate modpacks and those don't have this problem but when I want to play a more vanilla game, the modpacks I've tried using (Taken from Highly-Rated public collections posted by others) I seem to be encountering this issue.
Also I haven't seen anyone mention this issue in the collection discussions.

Thanks regardless for clarifications.


Alternatively, if you have a collection that does the job without causing this issue that could also work. I can then maybe cross-reference with the other collections and find what the trouble mods are.

[Cinemax]

Originally posted by Dirty Jack:

Originally posted by Cinemax:

This guy is kind of correct but he's using wrong terminology. You probably have dynamically expanding virtual memory (which he called visual memory). When a mod runs like ass and burns a ton of RAM the OS will offset to a file on C:\ called pagefile.sys (hidden, system file). By default it sizes dynamically but has a min|max value.

Search > Advanced System Settings
Advanced > Virtual Memory > Change
Custom Size:
Initial Size (MB):
Maximum Size (MB):
Set

Set them to a fixed value (same min/maxed) for a consistent allocation. I like to set to the same value as my physical memory (RAM). If you don't provide enough paging space for your ♥♥♥♥ mod to ♥♥♥♥ up your ♥♥♥♥♥♥♥♥♥, your game will run VERY bad. Memory paging also shortens the lifespan of SSDs it uses, so enjoy that.

But yeah, to clarify, your problem stems from the mod sucking ass, as others have said.


Edit: I wrote this as you were typing the post that confirmed all of the above. Damn I'm good.

In that case, I'd rather not damage my SSD.
Is there some method I can find which mod is causing this problem?

I run a AGOT and Shogunate modpacks and those don't have this problem but when I want to play a more vanilla game, the modpacks I've tried using (Taken from Highly-Rated public collections posted by others) I seem to be encountering this issue.
Also I haven't seen anyone mention this issue in the collection discussions.

Thanks regardless for clarifications.


Alternatively, if you have a collection that does the job without causing this issue that could also work. I can then maybe cross-reference with the other collections and find what the trouble mods are.

To clarify that point, it's not the mods doing it, it is simply the way SSDs work. NAND flash has a finite number of writes until the logic gate gets 'stuck' open. This happens to every SSD ever, ever on a long enough timescale. Memory has a lot of R/W and FTL operations, so when your computer is doing memory operations on an SSD, it increases the wear on the drive faster. To compensate for this, vendors include significantly more NAND than advertised, activating 'spare' NAND to replace failed NAND and keep the capacity as advertised. Regardless, the more you write to an SSD, the closer to death it creeps, but the process happens very slowly.

In other words, if you replace the computer every 7 years, which is average, you won't cause enough wear on the SSD to ever notice this problem. It happens silently in the background.

Just set your memory paging to a fixed value (same min and max). If you have 16GB of RAM, set it to 16384MB. You'll stop seeing your disk usage changing. The 16GB will stay reserved at all times, however.