Persistent crashing Thread - S.T.A.L.K.E.R.: Call of Chernobyl mod for S.T.A.L.K.E.R.: Call of Pripyat

I do not know what causes this but as of 1.4.11 this mod feels essentially unplayable as I cannot go 5 minutes without the program dying. It doesn't CTD with an error log like the normal game did, for reasons unknown to me, instead it feels like the game just terminates itself. Kills its own process or whatever. I've tried fiddling around with the rendering as I usually just played in DirectX 9 Enhanced mode but I cranked it up to DX11 thinking perhaps this was my OS not liking older programs. What's the deal with this? Is there any way to fix this? This mod would be perfect without the around-the-clock random crashes without warning or explanation.

Operating system is Windows 10 Home 64-bit, the version used is from GOG. My graphics card is an MSI GTX 970, my CPU is an FX-6100 hex-core processor, and I have 8GB DDR3. If anyone can advise on this I'd really appreciate it - I was looking forward to playing this badly. Please and thank you.

I don't know either. I have the same issue. Odd how very few people seem to be reporting this.

I am having same issue. Are you running any addons? Because I wonder if they may be causing problems, but planning to try call of chernobyl barebones to see if can find out.

I have the current addons (including relevent compatability patches) :

- STCOP weapon pack

- Dynamic Hud mod

- Dynamic Fatcions

- Outfit Addon

- W.A.R.F.I.G.H.T.E.R

I dont know if one of these addons or a combination of these addons is causing some problems but will test and try things more when I can and keep updated because I want this issue fixed also so I can play this wonderful mod in all its Glory.

One more thing. Could it be potentially the 32 bit program memory limitations issue like with SOC or does COP not have this problem when comes to mods?

Many Thanks,

J

After little digging and testing it seems that the problem for me was the EAX in the sound options. If it is on then switch it off and you may have some luck.

Regards

J

Kind of an old post, but I've been getting these too for a while now (at least since 1.4.22). At first I thought it was mods, but even playing vanilla it happens (although it seems less frequently). I can't narrow it down to anything specific, I've tried playing on lowest/disabled options in both video and game settings, disabled EAX, etc. and every once in a while it pops up.

I've even tried messing with the core affinity, overclock, and just about everything else except new hardware.

I just get a CTD and an empty Stack Trace: error when I post to notepad, it's driving me nuts! Maybe an issue with AMD/chipset?

FX 8320, GTX 970, 16gb ram, Samsung 850 SSD, temps all good.

I am having the same issue as Pepe_Silvia. The game crashes and directs me to the log and all i can find is a Empty stack trace and only occasionally the stack trace is followed by a bit of data. I made a thread with a copy of my log result here: Moddb.com

Id really love to figure this out; I love playing this mod, but it would be nice if i didn't kills itself at random.

Update: The crashes now happen consistently as soon as the loading screen would prompt me to select any key to start.

Edited by: domdl

Hmm, I haven't had a Crash at load, maybe a corrupt save?

However, I just had another one after ~30min of playing, scavenging in Army Warehouses; playing strictly Vanilla. I've noticed that it tends to crash when I'm in my inventory. Sometimes after a few seconds, sometimes after several minutes while I'm transferring loot.

Empty stack trace:

Edited by: Pepe_Silvia

If it was a corrupted save my log would have this at the end:

stack trace:

xrGame.dll
xrGame.dll

or "Can't open section" error (See also "Corrupt installation errors", below.)

That's why I am so confused. Ive been using this resource Metacognix.com

It is incredibly helpful for trying to diagnose issues.

Hmm, I have the -exact- same setup as Pepe_Silva:

8320 at 4ghz, 16GB, gtx970 (365.10), 850 EVO SSD, I don't know if mobo is the same, I'm on 970 chipset I think (ASUS M5A97 r2). Game version 1.4.22.

I'm having the -exact- same problem as Pepe_Silva and I believe comraderichard too. The crash happens with or without addons, either DX 10 or 11, "Unhandled Exception...check log" beep at desktop, leading to a blank Stack Trace:

and no arguments or errors at the bottom of longform log. I also notice crashes often when accessing inventory, though I've also seen it after sprinting for a long time. I don't know if this is normal, but the ONLY oddity I've found anywhere is this bit nearing the bottom of the xray_r log:

* GPU shading: vs(fffe0300/3.0/30), ps(ffff0300/3.0/30)
* GPU vertex cache: unrecognized, 16
* NVidia MGPU: Logical(1), Physical(1)
* Starting rendering as 2-GPU.
*** RESET [211 ms]

I'm not using SLI, and isn't MGPU a laptop designation? Everything is set for single GPU in my control panel too. Is this a normal part of starting the renderer, or does Xray think I have two GPUs installed? I hope some/any of this might help to track down this strange event.

Thanks to the mod creators and all the dedicated tinkerers!

This is getting fucking ridiculous. Everything was normal until the game decided to fuck itself over and now both of my saves end up in fatal errors. The devs need to fucking fix this shit. I will rate this crap with a 1/10 until they do something

This is getting fucking ridiculous. Everything was normal until the game decided to fuck itself over and now both of my saves end up in fatal errors. The devs need to fucking fix this shit. I will rate this crap with a 1/10 until they do something.

This doesn't help at all, looks like you just rage trough the threads and blame the Devs for everything. I'm running CoM (which is 10x more unstable) + about 13 Addons. I have about 1 or 2 crashes per day. That's it.

People "could" try to help you, but for that you need to add the log.

If you want to try for good this time, use the Repack or use a finished Assembly like this one -> Stalker-Mods.Clan

This is getting fucking ridiculous. Everything was normal until the game decided to fuck itself over and now both of my saves end up in fatal errors. The devs need to fucking fix this shit. I will rate this crap with a 1/10 until they do something

Now calm the fuck down kiddo, you're not even raging about the same issue we were trying to figure out. And the dev's don't really owe you shit, since it's a free mod and they're doing this on their own time.

Get a grip

Edited by: Pepe_Silvia

Happens to me also sometimes the screen will turn completely Grey or 1 color and CTD.

I'm having a very odd problem, which always results in a CTD. It begun with the game crashing when I tried to kill a bloodsucker in outskirts, the game crashed the moment he died. It continued in Jupiter Underground with crashes every once in a while after killing a snork. Now the problem is consistent and every time I try to kill a pseudogiant in the Red Forest my game crashes. (The crash just started, and I hadn't fought any other beasties besides Monolith soldiers and zombies since I started the game, which was as a loner in the outskirts vine anomaly building spawn)

Any help would be greatly appreciated!

Current Addons:

• Autumnal Winds
• Better Torchlight
• Dynamic Factions
• Dynamic Hud
• Dynamic Questlines
• Increased Weapon Damage
• Outfits
• STCoP

No idea what exactly i'm supposed to paste from the logs, but here are the last lines in my logs:

FATAL ERROR
 
[error]Expression    : SG
[error]Function      : CRender::model_CreateParticles
[error]File          : r4.cpp
[error]Line          : 581
[error]Description   : Particle effect or group doesn't exist
[error]Arguments     : industrial_particles\weapon_smoke
 

stack trace:

0023:00B83813 xrCore.dll, xrDebug::fail()
0023:01FAA46F luabind.beta7-devel.rc4.dll, luabind::detail::class_rep::constructor_dispatcher()
0023:66C7266D lua51.dll
0023:66C77246 lua51.dll, lua_pcall()
0023:058D20F3 xrGame.dll, CDialogHolder::OnFrame()
0023:0578B84A xrGame.dll, CDialogHolder::IgnorePause()
0023:00453BCB xrEngine.exe, CInput::OnFrame()
0023:0040F17A xrEngine.exe, CRenderDevice::message_loop()
0023:0040F23D xrEngine.exe, CRenderDevice::Run()
0023:0045EBDD xrEngine.exe, InitSound2()
0023:0045F363 xrEngine.exe, InitSound2()
0023:0045F466 xrEngine.exe, InitSound2()
0023:0046B1A3 xrEngine.exe, CApplication::load_draw_internal()
0023:74C462C4 KERNEL32.DLL, BaseThreadInitThunk()
0023:77E10FD9 ntdll.dll, RtlSubscribeWnfStateChangeNotification()
0023:77E10FA4 ntdll.dll, RtlSubscribeWnfStateChangeNotification()

Edited by: Zevros

So I've been running in to an issue when going to the NPP, and it seems to be only when going to the NPP.

Couldn't find any help for this issue online, thought I might be able to grab some help here.

Mods im using;

-CoC

-Dynamic HUD

-Warfare

-Arsenal OVerhaul

-Outfit Addon

- Increased Weapon Damage

FATAL ERROR
 
[error]Expression    : m_available_count
[error]Function      : CID_Generator<unsigned int,unsigned char,unsigned short,unsigned char,unsigned short,0,65534,256,65535,0>::tfGetID
[error]File          : e:\stalker\x-ray source\x-ray_callofchernobyl\src\xrgame\id_generator.h
[error]Line          : 92
[error]Description   : Not enough IDs
 

stack trace:

0023:00B937E1 xrCore.dll, xrDebug::fail()
0023:0B8F7C54 xrGame.dll, CDialogHolder::IgnorePause()
0023:0B90A20C xrGame.dll, CDialogHolder::IgnorePause()
0023:00B989C9 xrCore.dll, CInifile::remove_line()
0023:00B957C7 xrCore.dll, str_container::dock()
0023:61E1E65D MSVCR120.dll, strtol()
0023:00B98F4B xrCore.dll, _GetItem()
0023:0B90155F xrGame.dll, CDialogHolder::IgnorePause()
0023:0B7886A8 xrGame.dll, CDialogHolder::IgnorePause()
0023:0B7500BF xrGame.dll, CxIOFile::Scanf()
0023:0B7B65FF xrGame.dll, CDialogHolder::IgnorePause()
0023:06ECC314 luabind.beta7-devel.rc4.dll, luabind::detail::implicit_cast()

can somebody help me pls

Afro_Pick wrote:

I am having same issue. Are you running any addons? Because I wonder if they may be causing problems, but planning to try call of chernobyl barebones to see if can find out.

I have the current addons (including relevent compatability patches) :

- STCOP weapon pack

- Dynamic Hud mod

- Dynamic Fatcions

- Outfit Addon

- W.A.R.F.I.G.H.T.E.R

Pretty sure the problem is that warfighter and dynamic factions aren't compatible with each other. From what I heard.

can somebody help me pls Did you have any addons installed? It keeps mentioning XrEngine and Xr_ini along side RenderDevice. I think you might want to try changing your render setting.

Poohammad wrote:

Hmm, I have the -exact- same setup as Pepe_Silva:

8320 at 4ghz, 16GB, gtx970 (365.10), 850 EVO SSD, I don't know if mobo is the same, I'm on 970 chipset I think (ASUS M5A97 r2). Game version 1.4.22.

I'm having the -exact- same problem as Pepe_Silva and I believe comraderichard too. The crash happens with or without addons, either DX 10 or 11, "Unhandled Exception...check log" beep at desktop, leading to a blank Stack Trace:

and no arguments or errors at the bottom of longform log. I also notice crashes often when accessing inventory, though I've also seen it after sprinting for a long time. I don't know if this is normal, but the ONLY oddity I've found anywhere is this bit nearing the bottom of the xray_r log:

* GPU shading: vs(fffe0300/3.0/30), ps(ffff0300/3.0/30)
* GPU vertex cache: unrecognized, 16
* NVidia MGPU: Logical(1), Physical(1)
* Starting rendering as 2-GPU.
*** RESET [211 ms]

I'm not using SLI, and isn't MGPU a laptop designation? Everything is set for single GPU in my control panel too. Is this a normal part of starting the renderer, or does Xray think I have two GPUs installed? I hope some/any of this might help to track down this strange event.

if it's only happening on DX 10 - 11 then your GPU might not support it or it might not be installed.

Hope this is a still active thread, and that there arn't any rules I don't know about that I'm breaking, but I'd like some kinda fix for the constant crashes. I'm seriously getting pissed off with this shit, I can barely do anything before the game decides it wants to crash. Get in a gun fight with every bandit in the entire world? Crash. Loot corpses? Crash. Just launched the game after the last crash and had to sell some shit to the fat guy again, cause you didn't save after doing business with him, and are getting around to the part where you finish the deal? You bet it's gonna crash.

If I read like I'm blaming anyone like I'm blaming the Dev's or anything, i'm not tryin' too, in fact, I might have an older version cause for all I know they've probably updated it by now. I'm also using some mods as well, I don't remember what they're called, but I remember what they do. 1 adds to the arsenal, another adds more armor and clothes; 1 I believe gives you better deals with merchants, 1 adds faction ratings, 1 I believe makes side jobs pay better (cause if I remember correct, originally side jobs barely pay enough to by bread), and 1 makes it so merchants will buy weapons and clothes off you regardless of the state they're in (cause seriously, how am I to make a prophet if I gotta' fix all this shit first? Fixin' shit costs rubels).

I can't remember that many more, but I hope they sound familiar enough. It's been a long time since I played the game too, started a new game, and honestly I remember back then it didn't crash this often with the mods I've been using. Didn't add any new mods or anything either. I don't know if there's anything I gotta turn off anywhere, like I remember something about turning something off in sound to help keep crashes from happening at least consistantly within' a few minutes.

So I encountered a weird, persistent crashing issue in Zaton. The top half of Zaton is blocked by like a invisible wall of crash. If i try to go north in zaton, the game just closes. I have the Arsenal overhaul addon and the Outfit addon, but I don't think that would be an issue. Has anyone else had this issue?

Playing 1.5 and it has random crashes everywhere.

Not sure what I should do to fix it. Have OA, AO, Lost to the Zone, lootmoney added on.

Same here... Sometimes it crashes after 2 minutes, sometimes after 2-3 hours. And it is almost always when i'm in inventory. I'm playing 1.4.22 with bunch of mods, no issues with them, same in vanilla.

I'm playing 1.4.22 without addons, and still crash after 5 minutes.

Hey guys. For those who have those strange CTDs without any error whatsoever, you could still try this fix here:

It's initially for Stalker CoP, but for me it did the trick! - No crashes since then. For record: I play the game on Win 10, 64bit on full details flawlessly now.

I want to point out though, it's not by me - Credit goes to stevo8891 From the PC Perpective Forums. I just found it on the web and wanted to share it:

==================================

You have to edit windows memory registrys. For these registry files to exist, you must have WindowsXP Service Pack 2, SP1 does not have these and it is rumored that STALKER will run on SP1 without crashing due to that specific reason

Anyway go into run and type: regedit.exe Then open the following folders: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control Session Manager\Memory Management

make sure you clicked the folder that is labeled "Memory Management" and not the folder it contains, once you clicked that folder then you work on the window to the right which shows all the files. In there, a file will exist called "PagedPoolSize" Right-click and click "Modify" and change the value to "ffffffff" that is eight letter 'f's and no quotations.

After that You have to create a new file Right-click anywhere in the blank space and hover over New and click "DWORD Value" Name the file "PoolUsageMaximum" exactly as i typed only without the quotations. And modify this file too and enter the value "00000028" that is six zeros a two and an eight and no quotations.

After that you are done and stalker should work due to the fix in windows' memory management. Enjoy STALKER! ==================================================

This worked for me and it hasnt crashed once now thanks to this. Im not taking any responsibility if anything goes wrong. (even tho I dont know if anything could even go wrong but i dont know) So anyways: Hopefully this helps a few people run the game a bit smoother that are experiencing problems Goodluck.

bapho1531848231 wrote:

Hey guys. For those who have those strange CTDs without any error whatsoever, you could still try this fix here:

It's initially for Stalker CoP, but for me it did the trick! - No crashes since then. For record: I play the game on Win 10, 64bit on full details flawlessly now.

I want to point out though, it's not by me - Credit goes to stevo8891 From the PC Perpective Forums. I just found it on the web and wanted to share it:

==================================

You have to edit windows memory registrys. For these registry files to exist, you must have WindowsXP Service Pack 2, SP1 does not have these and it is rumored that STALKER will run on SP1 without crashing due to that specific reason

Anyway go into run and type: regedit.exe Then open the following folders: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control Session Manager\Memory Management

make sure you clicked the folder that is labeled "Memory Management" and not the folder it contains, once you clicked that folder then you work on the window to the right which shows all the files. In there, a file will exist called "PagedPoolSize" Right-click and click "Modify" and change the value to "ffffffff" that is eight letter 'f's and no quotations.

After that You have to create a new file Right-click anywhere in the blank space and hover over New and click "DWORD Value" Name the file "PoolUsageMaximum" exactly as i typed only without the quotations. And modify this file too and enter the value "00000028" that is six zeros a two and an eight and no quotations.

After that you are done and stalker should work due to the fix in windows' memory management. Enjoy STALKER! ==================================================

This worked for me and it hasnt crashed once now thanks to this. Im not taking any responsibility if anything goes wrong. (even tho I dont know if anything could even go wrong but i dont know) So anyways: Hopefully this helps a few people run the game a bit smoother that are experiencing problems Goodluck.

Just so you know, there's no reason to registry edit here. All you're doing is creating a page file of a minimum ~4.2GB, which can be accomplished in Windows with Control Panel > Advanced System Settings > Performance > Virtual Memory and change the size of your page files there. Not sure how having the game on a drive without a page file will affect it, but doing it this way (as far as i know) gives the same result while being far easier and less risky compared to poking around in your registry.

My game starts to crash a lot when I installed the 1.4.22 patch for Call of Chernobyl. I was playing it on 1.4.12(I think) before installing the patch. And now when I want to start a new game it just crashes. I tried it without any mods but then it keeps on crashing. I thought(this is just me being an idiot) that by installing a mod it could help alleviate the problem but it just keeps on crashing anyway. I am not clueless as what to do. I might just have to wait the official release of 1.5 of Call of Chernobyl.

Oops I'm noob and this is question is stupid but how does this signature thing work. I'm not so sure what I am supposed to do with it.

Edited by: bgcmanzaressacisd

Hey there I'm new to posting in here but this thread seemed like the right place to post this, I too am also having persistent crashes, in both 1.4.22 and 1.5 R6, the stack trace is the same, possible due to the mods I'm unsure but I want to make sense of the stack trace if anyone can help

In 1.5 my mods are

Structures Redux

Autumn Winds

Original Weapons Renewal

In 1.4.22 My Mods are

Structures Redux

Autumn Winds

Arsenal Overhaul

Increased Weapon Damage

I am using the correct version of mods to the version of the game but several times I get this stack trace, I also use dx10 this might be part of the issue.

intro_delete ::update_game_loaded
* [win32]: free[979228 K], reserved[82792 K], committed[3132220 K]
* [ D3D ]: textures[2287482 K]
* [x-ray]: process heap[612580 K], game lua[19939 K], render[3488 K]
* [x-ray]: economy: strings[21219 K], smem[447862 K]
* [win32]: free[979100 K], reserved[82648 K], committed[3132492 K]
* [ D3D ]: textures[2287482 K]
* [x-ray]: process heap[613097 K], game lua[20300 K], render[3489 K]
* [x-ray]: economy: strings[21219 K], smem[447862 K]
stack trace:

0023:60DC4F28 d3d11.dll, D3D11CreateDeviceAndSwapChain()
0023:60DC74F0 d3d11.dll, D3D11CreateDeviceAndSwapChain()
0023:60D73E5A d3d11.dll, D3D11CreateDeviceAndSwapChain()
0023:0522DE17 xrRender_R3.dll
0023:0040F17A xrEngine.exe, CRenderDevice::message_loop()
0023:0040F23D xrEngine.exe, CRenderDevice::Run()
0023:0045EBDD xrEngine.exe, InitSound2()
0023:0045F363 xrEngine.exe, InitSound2()
0023:0045F466 xrEngine.exe, InitSound2()
0023:0046B1A3 xrEngine.exe, CApplication::load_draw_internal()
0023:7586336A kernel32.dll, BaseThreadInitThunk()
0023:77C498F2 ntdll.dll, RtlInitializeExceptionChain()
0023:77C498C5 ntdll.dll, RtlInitializeExceptionChain()