protonscr

CONCRT140.dll crash/S.T.A.L.K.E.R.: Call of Pripyat (IX-Ray engine) — CONCRT140.dll unimplemented function crash on startup

protonclosed
ValveSoftware/Proton#10168 · opened 2026-09-23 by VictorMolokanov · updated 2026-09-23 · 1 comments · github
VVictorMolokanov 2026-09-23 github

Compatibility Report

Game: S.T.A.L.K.E.R.: Call of Pripyat, running the IX-Ray engine
("Chronicles of Pripyat 4.26" modpack; engine: https://github.com/ixray-team/ixray-1.6-stcop)
Steam AppID: 41700 (please verify)

System

GPU: NVIDIA GeForce GTX 1060, driver 580.178.4
DXVK: v2.7.1-498-ga6764047e587178
Proton: proton-11.0-2c

I confirm:

  • [x] No existing compatibility report found for this game.
  • [x] System is up to date.

Symptoms

xrEngine.exe crashes on startup, right after successful NVAPI/display init,
with a fatal "unimplemented function" abort in CONCRT140.dll:

wine: Call from ... to unimplemented function
concrt140.dll.??0_TaskCollection@details@Concurrency@@QEAA@XZ, aborting

Same crash signature as WineHQ Bugzilla #58583/58584 and
GloriousEggroll/proton-ge-custom#197, but confirmed here on stock Proton,
not just GE-Proton.

Steps to Reproduce

  1. Install S.T.A.L.K.E.R.: Call of Pripyat (AppID 41700) via Steam.
  2. Install the "Chronicles of Pripyat 4.26" IX-Ray modpack over it.
  3. Launch normally via Steam Play/Proton.
  4. Game crashes immediately after NVAPI/display init with the
    CONCRT140.dll error shown above.

Free alternative repro (no purchase needed): install S.T.A.L.K.E.R. Anomaly
(moddb.com/mods/stalker-anomaly) with the AOEngine addon — same crash
signature, same engine family, documented in WineHQ Bugzilla #58583.

What I already tried (no effect)

Installed vcrun2022 via protontricks and confirmed the real native
concrt140.dll (~320KB) is present in the prefix. Forced
WINEDLLOVERRIDES=native,builtin for the whole runtime family
(ucrtbase, vcruntime140, vcruntime140_1, msvcp140, msvcr140, concrt140,
vcomp140, atl140). Despite the override registering correctly and the
native file being present, every one of these DLLs still loads as
"builtin" in the loaddll trace — not "native". Meanwhile a different
native DLL (vcruntime140_cor3.dll, loaded by the game's own .NET launcher
via an absolute path outside system32) loads fine as native in the same
session — so this isn't a general native-loading failure, just this
specific DLL family via the system32 override path.

Logs attached

Full PROTON_LOG=1 WINEDEBUG=+seh,+loaddll logs (default + full override).

Kkisak-valve maintainer 2026-09-23 github

Hello @VictorMolokanov, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/1174#issuecomment-5794865999.

Related threads

Proton versions

Launch options

Upstream links

DLLs