Call of chernobyl ошибка unhandled exception occurred see log for details

Обновлено: 03.07.2024

25 Jul, 2017 @ 11:40am Call of Chernobyl: unhandled exception occurred see log for details

Has anyone else encountered this before? I tried to get CoC to work but it crashes 10 mins into the game every time. I'm currently running DocX dynamic faction, DocX quest, STCoP weapons pack, Dynamic HUD.

I also checked log, but I couldn't make anything out of it.

25 Jul, 2017 @ 11:45am post the last few lines of the log. We can't tell you what happened, or even really spitfall possibilities with the amount of info you've given. For that matter, what were you doing in-game when it happened? 25 Jul, 2017 @ 11:50am post the last few lines of the log. We can't tell you what happened, or even really spitfall possibilities with the amount of info you've given. For that matter, what were you doing in-game when it happened?

It crashes most of the time when I get killed, and have to reload quick save.

Thank you for helping btw.

Logs are posted below.
*** RESET [0 ms]
Config-file [appdata\user.ltx] saved successfully
* MEMORY USAGE: 686003 K
* End of synchronization A[1] R[1]
refCount:pBaseZB 1
refCount:pBaseRT 1
* DVB created: 1536K
* DIB created: 512K
- r__tf_aniso 4
- r2_tf_mipbias 0.
* RM_Dump: textures : 2252
* RM_Dump: rtargets : 15
* RM_Dump: vs : 89
* RM_Dump: ps : 82
* RM_Dump: dcl : 20
* RM_Dump: states : 68
* RM_Dump: tex_list : 1427
* RM_Dump: matrices : 0
* RM_Dump: lst_constants: 0
* RM_Dump: v_passes : 2106
* RM_Dump: v_elements: 2107
* RM_Dump: v_shaders : 1188
* GPU shading: vs(0/4.0/40), ps(0/4.0/40)
* GPU vertex cache: unrecognized, 24
* NVidia MGPU: Logical(1), Physical(1)
* Starting rendering as 2-GPU.
*** RESET [783 ms]
* MEMORY USAGE: 686395 K
* End of synchronization A[1] R[1]
* [win32]: free[1582404 K], reserved[181088 K], committed[2430748 K]
* []: textures[1302749 K]
* [x-ray]: process heap[691737 K], game lua[25089 K], render[7062 K]
* [x-ray]: economy: strings[23929 K], smem[643250 K]
* Saving spawns.
* Saving objects.
* 21110 objects are successfully saved
* Game foxhound220 - quicksave3.scop is successfully saved to file 'appdata\savedgames\foxhound220 - quicksave3.scop'
! ERROR on rejecting: entity not found. parent_id = [0], entity_id = [27139], frame = [134682].
! ERROR on rejecting: entity not found. parent_id = [0], entity_id = [25858], frame = [134913].
! ERROR on rejecting: entity not found. parent_id = [0], entity_id = [28680], frame = [135498].
! ERROR on rejecting: entity not found. parent_id = [0], entity_id = [29187], frame = [135498].
! ERROR on rejecting: entity not found. parent_id = [0], entity_id = [29953], frame = [135498].
incorrect action [8]->[8]
* [win32]: free[1590340 K], reserved[170988 K], committed[2432912 K]
* []: textures[1303773 K]
* [x-ray]: process heap[694185 K], game lua[26995 K], render[7221 K]
* [x-ray]: economy: strings[23894 K], smem[643833 K]
Call of Chernobyl version 1.4.22
using marshal library
alife_storage_manager.on_game_start()
ammo_aggregation.on_game_start()
artefact_degradation.on_game_start()
axr_companions.on_game_start()
axr_keybind.on_game_start()
axr_task_manager.on_game_start()
axr_trade_manager.on_game_start()
axr_turn_on_campfire.on_game_start()
azazel_mode.on_game_start()
coc_treasure_manager.on_game_start()
dxr_encyclopedia.on_game_start()
dxr_scopes.on_game_start()
* sound : cache: 65537 kb, 4856 lines, 13820 bpl
dynamic_news_manager.on_game_start()
enhanced_animations.on_game_start()
fast_travel.on_game_start()
game_relations.on_game_start()
info_portions.on_game_start()
item_animations.on_game_start()
itms_manager.on_game_start()
m_mines.on_game_start()
mask_hud.on_game_start()
mob_trade.on_game_start()
modules.on_game_start()
pda.on_game_start()
phantom_manager.on_game_start()
release_item_manager.on_game_start()
safe_release_manager.on_game_start()
sleep_dep.on_game_start()
slot_hud.on_game_start()
surge_manager.on_game_start()
survival_mode.on_game_start()
ui_enemy_health.on_game_start()
ui_mm_faction_select.on_game_start()
weapon_heat.on_game_start()
wpn_effects.on_game_start()
xr_combat_ignore.on_game_start()
xr_corpse_detection.on_game_start()
xr_danger.on_game_start()
xr_eat_medkit.on_game_start()
xr_gather_items.on_game_start()
xr_statistic.on_game_start()
xrs_debug_tools.on_game_start()
xrs_dyn_music.on_game_start()
xrs_facer.on_game_start()
xrs_kill_wounded.on_game_start()
* phase time: 275 ms
* phase cmem: 682111 K
* phase time: 46 ms
* phase cmem: 681986 K
* Loading spawn registry.
* 17936 spawn points are successfully loaded
* Loading objects.
* 21110 objects are successfully loaded
* Game foxhound220 - quicksave3 is successfully loaded from file 'appdata\savedgames\foxhound220 - quicksave3.scop' (0.738s)
* phase time: 738 ms
* phase cmem: 694065 K
* phase time: 48 ms
* phase cmem: 694030 K
* phase time: 46 ms
* phase cmem: 694017 K
* [win32]: free[1591064 K], reserved[163988 K], committed[2439188 K]
* []: textures[1294926 K]
* [x-ray]: process heap[693828 K], game lua[30939 K], render[7221 K]
* [x-ray]: economy: strings[23277 K], smem[488842 K]
stack trace:

25 Jul, 2017 @ 11:59am post the last few lines of the log. We can't tell you what happened, or even really spitfall possibilities with the amount of info you've given. For that matter, what were you doing in-game when it happened?

It crashes most of the time when I get killed, and have to reload quick save.

Thank you for helping btw.

0023:0C0A01F5 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1CB052 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1CB869 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C231663 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C125836 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C162446 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C162917 xrGame.dll, CDialogHolder::IgnorePause() Okay, only really needed the stack trace.
According ot that, you are having an error of some sort related to dialog. Was the game stable prior to adding mods?
Simplest thing you can do, is reinstall the game, then the weapon pack. Then, pay close attention ot the install order and compatibility patches, and install your other mods, one at a time, until you find which one triggers the crashes.

EDIT: Most likely culprits are the docx mods (potentially installed in the wrong order, causing issues).

25 Jul, 2017 @ 12:52pm

Okay, only really needed the stack trace.
According ot that, you are having an error of some sort related to dialog. Was the game stable prior to adding mods?
Simplest thing you can do, is reinstall the game, then the weapon pack. Then, pay close attention ot the install order and compatibility patches, and install your other mods, one at a time, until you find which one triggers the crashes.

EDIT: Most likely culprits are the docx mods (potentially installed in the wrong order, causing issues).

Welp, turns out it even crashes in fresh reinstall without any mods on.

Log as follow:
stack trace:

0023:0C0901F5 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1BB052 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1BB869 xrGame.dll, CDialogHolder::IgnorePause()

[error][] : Parameter error

25 Jul, 2017 @ 1:38pm

EDIT: Most likely culprits are the docx mods (potentially installed in the wrong order, causing issues).

Welp, turns out it even crashes in fresh reinstall without any mods on.

Log as follow:
stack trace:

0023:0C0901F5 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1BB052 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1BB869 xrGame.dll, CDialogHolder::IgnorePause()

[error][] : Parameter error Just checking, but are you making the mistake of installing it over call of pripyat? CoC is supposed to be a standalone install.

25 Jul, 2017 @ 1:54pm

Welp, turns out it even crashes in fresh reinstall without any mods on.

Log as follow:
stack trace:

0023:0C0901F5 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1BB052 xrGame.dll, CDialogHolder::IgnorePause()
0023:0C1BB869 xrGame.dll, CDialogHolder::IgnorePause()

[error][] : Parameter error

Just checking, but are you making the mistake of installing it over call of pripyat? CoC is supposed to be a standalone install.
No, but I think I know where went wrong. I might have over written my rar file with mods.
And you're right, I think it's DocX's Dynamic faction that's causing the problem. I haven't have any problems after I stopped using the Dynamic Faction.

Что делать поначалу не выдетает а потом вышел из игры и уже сохранения не грузятся вылетает!

Как найти лог игры:
В Win хр лог находится:

C:\Documents and Settings\All Users\Документы\S.T.A.L.K.E.R. - \logs

В Win7 и Win8 лог находится:

C:\Users\Public\Documents\S.T.A.L.K.E.R. - \logs
(C:\Пользователи\Общие\Документы\S.T.A.L.K.E.R. - \logs)
Или в поиске файлов на компьютере задать искать файл *.LOG
Файл лога имеет название вида "xray_имя пользователя. log", открывается текстовым редактором Блокнот.
Запись об ошибке находится внизу, обычно, после строки FATAL ERROR
Дальше: набираешь в поиске "сталкер справочник вылетов" и ищешь подходящее лечение.

долго думал но так и не дошло что из этого ошибка?
* Detected CPU: Intel(R) Pentium(R) CPU G3260 @ 3.30GHz [GenuineIntel], F6/M12/S3, 3300.00 mhz, 25-clk 'rdtsc'
* CPU features: RDTSC, MMX, SSE, SSE2, SSE3, MONITOR/MWAIT, SSSE3, SSE4.1, SSE4.2
* CPU threads: 2

Initializing File System.
using fs-ltx fsgame.ltx
FS: 41617 files cached 28 archives, 7483Kb memory used.
Init FileSystem 14.016207 sec
'xrCore' build 3967, Dec 14 2009

-----loading c:\games\s.t.a.l.k.e.r. - call of pripyat\gamedata\configs\system.ltx
-----loading c:\games\s.t.a.l.k.e.r. - call of pripyat\gamedata\configs\system.ltx
Initializing Engine.
Starting INPUT device.
Loading DLL: xrRender_R2.dll
Loading DLL: xrRender_R3.dll
refCount:m_pAdapter 1
Loading DLL: xrRender_R4.dll
* D3D

Душман4ик Оракул (63285) Последние 25 строк скопируй.

CScriptEffector() called
- Destroying level
DestroySingleton::RefCounter: 0
DestroySingleton::RefCounter: 0
DestroySingleton::RefCounter: 0
Input: 1
Config-file saved successfully
Destroying Direct3D.
* RM_Dump: textures : 0
* RM_Dump: rtargets : 0
* RM_Dump: rtargetsc : 0
* RM_Dump: vs : 0
* RM_Dump: ps : 0
* RM_Dump: dcl : 0
* RM_Dump: states : 0
* RM_Dump: tex_list : 0
* RM_Dump: matrices : 0
* RM_Dump: lst_constants: 0
* RM_Dump: v_passes : 0
* RM_Dump: v_elements: 0
* RM_Dump: v_shaders : 0
refCount:pBaseZB 1
refCount:pBaseRT 1
DeviceREF: 1
вот последние 25 строк

Душман4ик Оракул (63285) Это лог завершения игры в штатном режиме. Нужен именно после вылета. Да пипец не фига не работает! У нет не какой фатальной ошибки, у меня тока запускается сталкер и сразу вылетает ошибка. Душман4ик Оракул (63285) Сразу после вылета игры создай на рабочем столе простой текстовый блокнотовский документ. Открываешь его, кликаешь в нем правой кнопкой мыши и нажимаешь "вставить". Если ничего не вставляется, тогда причину не определить. Пробуй следующее: Запускай игру от имени Администратора. Если стоит мод и в папке с игрой есть папка gamedata, переименуй её например в gamedata1 и запусти игру без нее. Если игра установлена в C:\Program Files переустанови ее в другой раздел диска. Так же пробуй сначала запустить чистую игру и уже потом устанавливай мод. DestroySingleton::RefCounter: 0
DestroySingleton::RefCounter: 0
DestroySingleton::RefCounter: 0
Input: 1
Config-file saved successfully
Destroying Direct3D.
* RM_Dump: textures : 1
* : 1: ui\ui_load
* RM_Dump: rtargets : 0
* RM_Dump: rtargetsc : 0
* RM_Dump: vs : 1
* : 1: null
* RM_Dump: ps : 1
* : 1: null
* RM_Dump: dcl : 0
* RM_Dump: states : 1
* RM_Dump: tex_list : 1
* RM_Dump: matrices : 0
* RM_Dump: lst_constants: 0
* RM_Dump: v_passes : 1
* RM_Dump: v_elements: 1
* RM_Dump: v_shaders : 1
refCount:pBaseZB 1
refCount:pBaseRT 1
DeviceREF: 3
Вот последние 25 строк, а FATAL ERROR нету ( Душман4ик Оракул (63285) FATAL ERROR здесь и не будет. Это лог штатного выключения игры. Лог ошибки можно получить только после вылета игры. И то иногда бывают пустые логи, тогда причину вылета определить вообще не реально. Душман4ик Оракул (63285) Иногда бывают пустые логи, тогда причину вылета определить вообще не реально. Душман4ик Оракул (63285) Сразу после вылета игры создай на рабочем столе простой текстовый блокнотовский документ. Открываешь его, кликаешь в нем правой кнопкой мыши и нажимаешь "вставить". Если ничего не вставляется, тогда причину не определить.

* Detected CPU: Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz [GenuineIntel], F6/M5/S1, 1695.00 mhz, 25-clk 'rdtsc'
* CPU features: RDTSC, MMX, 3DNowExt!, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, HTT
* CPU cores/threads: 2/4

Initializing File System.
using fs-ltx fsgame.ltx
FS: 56477 files cached 28 archives, 7482Kb memory used.
Init FileSystem 2.085442 sec
'xrCore' build 7090, Jul 5 2018
У меня еще ошибки не уместились

Актуальная версия сборки v6.03+fix_291118
============================================
В данной теме рассматриваются ошибки, проблемы, связанные с загрузкой и функционированием сборки. Актуальная версия 6.03. Ошибки рассматриваются: в приложенном вами, xray_имя.log - журнальном файле, используемый движком X-Ray для журналирования возникших в игре ошибок, позволяющий определить тип ошибки, а также причину её возникновения. Приложите, JSGME.ini - генерируется ММодов в качестве файлов настроек, которые содержат активные модификации в сборке.

S.T.A.L.K.E.R.: Call of Pripyat

10 окт. 2019 в 14:34 I just installed this mod (no addons) and keep getting this error everytime I try to start a new game. How can I fix this? 10 окт. 2019 в 14:58 10 окт. 2019 в 15:15 I just installed this mod (no addons) and keep getting this error everytime I try to start a new game. How can I fix this?

Good luck with it.

I just remembered why I never played it mutch.
Crashes in every 5 minutes. Funny is my system is different but it crashes with this one to.
Sad.

Hmmm. Yesterday 0 crashes with dx11, today like 6 in 2 hours.
Someone. Make STALKER game with modern engine! 15 окт. 2019 в 6:17

i know anecdotal evidence isn't worth all that much, but i've played like 250 hours of anomaly with only two crashes not related to the (most likely already fixed) wild territory izlom bug

difference is that i'm using dx9 enhanced instead
dx10 and 11 were always ♥♥♥♥♥♥ with STALKER games

i know anecdotal evidence isn't worth all that much, but i've played like 250 hours of anomaly with only two crashes not related to the (most likely already fixed) wild territory izlom bug

difference is that i'm using dx9 enhanced instead
dx10 and 11 were always ♥♥♥♥♥♥ with STALKER games

Yeah. I recal lthe same. Just thought it would finally work.
For some reason skyboxes dont work in dx9. Damn

Few of my crashes seem to be UI related.

17 окт. 2019 в 3:51 Hmmm. Yesterday 0 crashes with dx11, today like 6 in 2 hours.
Someone. Make STALKER game with modern engine! It's all the LUA stuff that makes the game unplayable, the mod pack has dozens of LUA programs/scripts interfacing with one program(the game) without awareness of each other or way of testing if something will break in game without manually testing. (LUA errors are the ones i get the most often, actual engine crashes are rarer ime and it's sometimes easy to pinpoint what caused the crash)
Yeah, 100% not a recipe for disaster.
ps: You can know if it's a LUA crash if the error in the log.txt file has an error number and says something generic such as "The specified module could not be found") Hmmm. Yesterday 0 crashes with dx11, today like 6 in 2 hours.
Someone. Make STALKER game with modern engine!

It's all the LUA stuff that makes the game unplayable, the mod pack has dozens of LUA programs/scripts interfacing with one program(the game) without awareness of each other or way of testing if something will break in game without manually testing. (LUA errors are the ones i get the most often, actual engine crashes are rarer ime and it's sometimes easy to pinpoint what caused the crash)
Yeah, 100% not a recipe for disaster.
ps: You can know if it's a LUA crash if the error in the log.txt file has an error number and says something generic such as "The specified module could not be found")
Something like that.

Actually I will uninstall it.
Works better now but it seems thousands of hours stalker have done its deed. :D
I just need totally new game of same genre.

Читайте также: