Random crashes during campaign - 64bit

[Blinx7882]

Trying to play through the campaign, all my crashes so far have been on the level Village, not sure if the level is part of the problem, some previous logs in the callstack state a memory access violation, the callstack pointing to CryRenderD3D10.dll

This latest crash, I added some launch commands to run in dx9 and I got the following error after completing the side objective in village for the radar station and the game saved, then crashed: "C1-Launcher Game v6 64-bit Access violation exception (0xC0000005) at 0x0000000030573ECC Write to 0x0000000036768689 failed" The callstack for this one seems to point towards "CryAction.dll"

I have an AMD system, Ryzen 5900x and a RX 6800 GPU - not sure if any of this is contributing

[Blinx7882]

Additional crash now: callstack pointing to CrySoundSystem.dll "C1-Launcher Game v6 64-bit Access violation exception (0xC0000005) at 0x0000000036007B7B Read from 0x0000000000000004 failed"

[ccomrade]

Do you use any mods (better textures and so on)?

Do you load a saved game?

Please always provide full crash details, otherwise there's nothing much to do. You can write it into a collapsed section to keep the text short.

[Choum28]

What exactely do you need ? I'm also having random regular CTD with crysis 64 during game.

Origin version, no mod but I se a custom system.cfg with following var

con_restricted = 0 hud_panoramicHeight = 0 g_ragdollmintime = 10000 e_lods = 0

Game.log

I also have 2 report in event viewer log per crash

Ryzen 7800x3d + RTX3080

Error log

• EventData AppName Crysis.exe AppVersion 6.0.0.0 AppTimeStamp 65cd476e ModuleName CryScriptSystem.dll ModuleVersion 1.1.1.6156 ModuleTimeStamp 47d6e0b9 ExceptionCode c0000005 FaultingOffset 0000000000056020 ProcessId 0x2624 ProcessCreationTime 0x1daeb35bb2e2060 AppPath G:\Jeux\Crysis\Bin64\Crysis.exe ModulePath G:\Jeux\Crysis\Bin64\CryScriptSystem.dll IntegratorReportId eace91d1-a525-4d50-9541-b24dabe67667 PackageFullName
  PackageRelativeAppId

Information log

Bucket 1812091405129689893 BucketType 4 EventName APPCRASH Response Non disponible CabId 0 P1 Crysis.exe P2 6.0.0.0 P3 65cd476e P4 CryScriptSystem.dll P5 1.1.1.6156 P6 47d6e0b9 P7 c0000005 P8 0000000000056020 P9
P10
AttachedFiles \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3f4e79fd-69ec-4525-ba43-3e75a85f26cb.tmp.dmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ed3389d2-704e-4daf-8ee2-451c884b217d.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.41ea9da0-637d-4e1c-9840-3e2ff49ca870.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c7e566cc-8db5-45e0-a59f-8d7cc7af71af.tmp.txt \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.883864ce-6590-4024-951e-9e26d57fd537.tmp.xml StorePath \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Crysis.exe_5e8ce4b9dae3b9bac05f4036aaf5c6c6d3889aab_f631e882_33ad0575-d8b8-4dd7-ae8b-776dcad45dc3 AnalysisSymbol
Rechecking 0 ReportId eace91d1-a525-4d50-9541-b24dabe67667 ReportStatus 268435456 HashedBucket 6c3f93f5b0304e46c925d788374b2b25

[ccomrade]

What exactely do you need ? I'm also having random regular CTD with crysis 64 during game.

Just the log file after the crash occurs is enough. Thanks.

This script system crash above isn't anything common, but it could be a random crash caused by broken memory allocation in 64-bit version. I'm working on a proper fix currently, but it's challenging. There are so many places that need fixing. Preparing all necessary patches manually is not an option in this case. It has to be automated. For the first time.

In the meantime, you can try the CryMP client. I've implemented a workaround for this issue there. It's not a proper fix, but it should work in most cases.

[Choum28]

I try the CryMPclient (development version), no crash for the moment since 2 levels.

[Blinx7882]

Game.log Apologies, here is the log file for the crash. In terms of this latest crash I listed, I have the community Crysis MP installed but I was not running through their executable, as multiplayer crashed when trying to play with a friend all the time upon firing a weapon, so we found the C1 launcher and replaced the exe files and LAN has been amazing through the C1 launcher instead and we only run the game through the C1 64bit exe. No other mods are installed

I loaded a saved game which was a new game which crashed with the CryRenderD3D10.dll in the stacktrace, upon which I added the dx9 launch command. Here is the log file for that one as well: Game Build(6156) Date(04 Aug 2024) Time(16 49 18).log

[ccomrade]

Thanks for the logs.

The first one is definitely due to broken memory allocation. It even crashed inside CrySoundSystem's internal allocator.

About the second one in CryRenderD3D10, no idea what it could be after a quick look.

[Choum28]

Don't know if related, but the Exodus mission is completely buggy, Prophet do not move or fight at the begginning of the mission, he's suppose to rejoin the officer, but instead he move outside the house and then do nothing. After alien encounter, it take very long moment before Nomad move the jeep, and others soldiers do not move on the 2 others jeeps, they just stand here. When he's supposed to move on foot to the crash site (or follow the player not sure), he do nothing or return to the previous base. So the mission never finish as from what I see Prophet is supposed to trigger an event when near the ADAV.

When you tried to restart level (restart level button), you will have no HUD, echap button not working anymure, adsn you cannot tweak weapons.

[ccomrade]

I've just tested it and yes, it's broken in dev version of CryMP. It seems some of our recent changes broke this level. Thanks for the report. Bug created: https://github.com/crymp-net/client-server/issues/179

[Choum28]

Adding log report for Crysis Warhead, which also suffer from regular crashed (vanilla warhead too).

Game.log

[ccomrade]

Ah yes, memory allocation is broken there as well.

[facboy]

any eta for fix for warhead? warhead can't run mpclient :(

[facboy]

alternatively, if it's possible to backport the fixes to this, can you point to the commits/areas of the code in mpclient? not sure if it's beyond me but i could try bodge it into a PR.

[ccomrade]

Unfortunately, the temporary workaround in CryMP has some nasty side effects (https://github.com/crymp-net/client-server/issues/259) as we discovered recently. The clean fix is still not finished. No ETA yet. Too many things going on.

[facboy]

ah, thx. i found that going back to vanilla textures has made it much more stable.