Sudden crashes Thread - MISERY mod for S.T.A.L.K.E.R.: Call of Pripyat

So basically i've been playing misery so far without any issues but today i started getting Not enough storage and Out of memory crashes. I didn't tinker with anything and have been running misery stable for several months. Tried lowering settings, alife and clean install of both misery and CoP. I checked both my HDD and RAM but there are no issues there. Specs are: GTX 1080, i7-6700K, 16GB RAM. Please help.

These can happen if you play a long time without saving or reloading. When you take a break, try exiting the game and see if you have less of those.

I'll try thanks for advice. The weirdest thing is that the crashes came out of nowhere and without any reason.

That's x-ray engine. Your rig is plenty strong. I assume you are running no add-ons since you didn't mention them. If it continues, post the last ten or so lines of your log usually following the phrase FATAL ERROR.

My bad sorry i forgot to say that im using TAZ, Vancer2's All Weapons upgrades (TAZ version) and the Scope replacement mod. Unfortunately the game still crashes, here's the log entry:

FATAL ERROR

[error]Expression : data
[error]Function : CVirtualFileReader::CVirtualFileReader
[error]File : D:\prog_repository\sources\trunk\xrCore\FS.cpp
[error]Line : 545
[error]Description : c:\steam\steamapps\common\stalker call of pripyat\gamedata\textures\wpn\ammo\shell_bump.dds
[error]Arguments : Not enough storage is available to process this command.

stack trace:

another example:

FATAL ERROR

[error]Expression : data
[error]Function : CVirtualFileReader::CVirtualFileReader
[error]File : D:\prog_repository\sources\trunk\xrCore\FS.cpp
[error]Line : 545
[error]Description : c:\steam\steamapps\common\stalker call of pripyat\gamedata\sounds\music\_menu_misery_angelsanddemons_stereo.ogg
[error]Arguments : Not enough storage is available to process this command.

stack trace:

Edited by: darken070

I'm not sure which of those add-ons uses that shell_bump.dds which is an icon file. TAZ uses higher quality textures and they will use up a pool of memory set aside for the purpose in the game more quickly. Basically the game engine uses allocated pools of memory to store graphics, the next movement for all NPC's/Mutants, etc. Those pools of memory are finite and are not increased with having plenty of DDR in your GPU and/or Motherboard. The game is already fixed to use all the memory it can and uses around 2.5GB of RAM by itself. As long as you have enough RAM for Windows and your open programs (Anything at/above 8GB is plenty) the game has all the memory it needs.

On a side note, I highly recommend against using more than one add-on at a time. Things get exponentially more complicated to troubleshoot and also more likely you will have odd problems. IIRC Vancer is in school and I can't recall if his add-on is 100% compatible with 2.1.1. I believe he plans on updating it when 2.2 is released.

TAZ is 100% compatible if all the patches are applied, but it does have a higher overhead file quality/size wise.

When you do use an add-on, I highly recommend starting a new game unless it specifically states otherwise. The tiniest change can require a new game, it's not us, it's xray LOL.

Thanks i'll try to re-install without Vancer's addon.

Happy Hunting Stalker!

Ok its not the addon's fault, just got another crash:

FATAL ERROR

[error]Expression : fatal error
[error]Function : out_of_memory_handler
[error]File : D:\prog_repository\sources\trunk\xrCore\xrDebugNew.cpp
[error]Line : 336
[error]Description : <no expression>
[error]Arguments : Out of memory. Memory request: 4096 K

stack trace:

Those happen, as I said, without any add-ons. The previous log you posted was add-on related. This game, on this engine, will never be completely crash free. We have fixed a ton of bugs, but play long enough in one session without exiting and you will eventually get some of those.

Well after re-installing the game a couple of times and finishing almost all quest in zaton, i found out that the game crashes only in jupiter or while traveling there regardless of how long i play without saving/reloading. Also the out of memory crashes stopped and now its only Not enough storage is available to process this command.

All I can say is that I only tried TAZ once, because I am pretty happy with the existing weapons. I never have trouble traveling between maps causing CTD's or get that error. Jupiter has almost twice the quantity of life in it and is the largest AI load in CoP. It tends to have more crashes. Often, lowering your switch_distance for alife by 50 meters on that map will reduce the number of crashes.

TAZ is 100% compatible with MISERY, I don't think that is the problem, but more it may aggravate the issue because it is more demanding.

Well i'll be damned. I lovered alife by 50 meters and some graphics settings a little and the crashes actually stopped. Thanks a lot.

We are squeezing so much more out of this tired old engine sometimes just backing off a tiny bit keeps things more stable. We have roughly Four Times as much life in the zone at 300m than at the original 100 or 150m in the vanilla game. If you use higher than 300m, it gets even worse. If your drives and CPU can't shuffle things fast enough, weird stuff happens. When I am optimizing a new system, I run across the front of the Jupiter plant between the Burer tunnel and Checkpoint. If I can play smooth at a certain switch_distance and group of video settings there, I know everywhere else will work fine. It is the busiest couple hundred meters on the 3 maps.

I'm glad you've gotten things more stable - Happy Hunting!