Hello there
Starting from yesterday i cant bypass the ue4 fatal error when launching the game
I cant seem to fix so i reached out to u guys
Things i did:verify files - unsubscribing all the mods - changing the number for full screen mod on game user settings [would fix game usually but it wont anymore] - changed windows from 10 to 11
(Sorry if my english is not good enough) :]
Is there any other error code/words that show up? D3d? Renderthread? Anything?
Nop nothing at all only got :
the ue4-conan sandbox game has crashed and willā¦
Fatal error!
Greetings Exile,
Thank you for your report. Can you please share your log file with us?
You can find it by following:
Steam\steamapps\common\Conan Exiles\ConanSandbox\Saved\Logs
Feel free to reach out in private via direct message if you prefer.
Thank you in advance.
I did delete game completly and download it again but didnt help at all
ConanSandbox-backup-2023.01.28-02.05.23.log (15.8 KB)
You have close to 40 mods. Have you tried without them? It could be an outdated mod or a corrupted mod pak.
i tried even without mods still same error
Are you hitting continue after you remove the modlist? Continue can carry stuff in you dont want when trying to get to the bottom of the error.
Sameish problem, but with different error log. No matter what I press (modded, unmodded, continue/launch/new game), the game just throws the error message, and done. COMPLETELY uninstalled, even deleted the remaining files, because Steam is a castrated useless piece of bloatware, it canāt even delete completely stuff.
And nothing.
Updated drivers and Windows, even used a month old (when the game worked) version from a restore point, nothing.
Unsubbed from all the mods, still error. (Yeah, there are some mods that arenāt crispy new updated, but worked with pre 3.0 and even after the 3.0).
But freshly installed, naked, modless game, and noooo, immediately corrupts itself somehow.
Funny is, there were no update, the game just corrupted itself.
I have been playing the game for 18.5 hours on steam and i dont have a single mod but im getting the same error code
Looking thru the logsā¦ this seems to be a major part of the issue - LogStreaming:Error: Couldnāt find file for package /Engine/EditorMaterials/GizmoMaterial requested by async loading code. NameToLoad: /Engine/EditorMaterials/GizmoMaterial
[2020.12.13-03.51.45:699][ 0]LogStreaming:Error: Found 0 dependent packagesā¦
[2020.12.13-03.51.45:699][ 0]LogEngine: ERROR: Failed to load special material ā/Engine/EditorMaterials/GizmoMaterial.GizmoMaterialā. This will probably have bad consequences (depending on its use)
got this also - LogPakFile: New pak file ā¦/ā¦/ā¦/ConanSandbox/Content/Paks/DLC_EXT_DLC_Siptah.pak added to pak precacher.
[2020.12.13-03.51.47:572][ 0]LogAsyncObjectFinder:Error: FAsyncObjectFinder: Asset ā/Game/UI/UIModuleTable.UIModuleTableā (used by ā/Engine/Transient.GUIModuleController_0ā) should have been loaded at this point! Please fix! Note: Will try to syncload the asset to continue execution. i have done the verify filesā¦ I did a full reloadā¦ i back out the latest graphic driver updateā¦ all of that and cannot get the UA4 to stop on the launch or continueā¦ and removed all the modsā¦ nothing is getting this to run
I would appreciate it if the devs where more active in helping us to fix what they created becoz a lot of people love this game but it has way to many bug
To @Xpkx
Another way to get more info about the crash (Used it a lot on another game āwarframeā in the first beta version)
- Go to this link to download ProcDump and extract all its content to a new folder named ProcDump on your desktop
- Launch āConanā launcher
- Wait until the downloading process is finished but DO NOT click PLAY yet.
- Press the Windows Start menu and type cmd, and then hit Enter
- Type cd desktop\procdump in the new command window, and hit Enter
- Type procdump -e -t -w ConanSandbox.exe and hit Enter!
- Click PLAY to launch the game and reproduce the problem in the game
- Wait until the game is closed, locate the ProcDump folder on your desktop and attach the DMP file to support ticket or upload and share the dmp file.
.
.
.
.
.
.
This will give you something like this (tested with a ābugā) :
Microsoft Windows [version 10.0.19044.2486]
(c) Microsoft Corporation. Tous droits rƩservƩs.
C:\Users\fredd>procdump -e -t -w conanSandbox.exe
āprocdumpā nāest pas reconnu en tant que commande interne
ou externe, un programme exƩcutable ou un fichier de commandes.
C:\Users\fredd>cd desktop\procdump
C:\Users\fredd\Desktop\ProcDump>procdump -e -t -w conanSandbox.exe
ProcDump v10.1 - Sysinternals process dump utility
Copyright (C) 2009-2021 Mark Russinovich and Andrew Richards
Sysinternals - www.sysinternals.com
Waiting for process named conanSandbox.exeā¦
Process: ConanSandbox.exe (31032)
Process image: C:\Program Files (x86)\Steam\steamapps\common\Conan Exiles\ConanSandbox\Binaries\Win64\ConanSandbox.exe
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: n/a
Hung window check: Disabled
Log debug strings: Disabled
Exception monitor: Unhandled
Exception filter: [Includes] * [Excludes]
Terminate monitor: Enabled
Cloning type: Disabled
Concurrent limit: n/a
Avoid outage: n/a
Number of dumps: 1
*Dump folder: C:\Users\fredd\Desktop\ProcDump*
Dump filename/mask: PROCESSNAME_YYMMDD_HHMMSS
Queue to WER: Disabled
Kill after dump: Disabled
Press Ctrl-C to end monitoring without terminating the process.
[11:47:49] Exception: 406D1388
[11:52:05] Exception: 406D1388
[11:52:05] Exception: 406D1388
[11:52:05] Exception: 406D1388
^C <= So here I do a Ctrl-C to end the monitoring as the game freeze on loading (I tried to connect to a server on the same machine.
[11:52:17] Dump count not reached.
//-------------------------------------------
This will end with and Exception number like 0x406D1388 which in my case mean āNative code setting thread name causes process shutdown with managed debuggerā basically ConanSandbox try to create a thread that is already present on my machine therefore the crashā¦
This will state you ALL the exception not the last one that is log on the crash which can be important.
To @Xpkx : Can you retry an see if there is another exception that is present ?
//-------------------------------------------
Usually your āEXCEPTION_ACCESS_VIOLATIONā is often linked to multiple memory access and/or unauthorised released of them.
For some itās the used of MSI Afterburner or ā¦
- Baidu IME
- GeDoSaTo
- Raptr overlay
- Lucid VirtuWatt software
- Razer Synapse Program
- Razer Chroma SDK
- Rivatuner Statistics Server
- MSI Afterburner OSD
Anything that can use or manage the same video (stream) or audio of the game (twitch overlay or any overlay) could cause thisā¦
Ok but how do i fix my game i just want to play conan is that too mich to ask for
To @Gl1tch3d_22 ,
The main problem is there is too much bugS, and despite you are not using any mods the game itself interact with too much things.
Case 1 : The Update went bad (Update mean download then reorganise your files). Event steam verification is not a sure, in some others games it cause more crash than it solved.
Case 2 : The Update is ok but somethings in your system is in conflict with ConanSandbox.exe (Any VideoCard manager, accelerator.
Case 3 : The updated game optimisation try something your system does not have (IE you need new videocard update or a system update or redo it if failed.)
Using the ProcDump can only give us a hint of what create the crash. And this can help others players like me give you a advice that could save your play ^^ ā¦
//-------------------------------------------------------------------
If I cannot have any info, I will go for the usual advice :
0. Copy-Paste you game.db or dlc_siptah.db* on desktop (Safeguard you play)
- Suppress the game from Steam
- Reboot
- Manual suppress any Conan leftover trace in registry (regedit) and steam folders
- Reboot
- Update windows, Update your video Card
- Reinstall and reboot
- Disable any others application (streaming, twitch, Videocard manager, game Mananger)
- Lauch steam only and Conan exiles only
*1 : usually in "C:\Program Files (x86)\Steam\steamapps\common\Conan Exiles\ConanSandbox\Saved"
I donāt know if it helps, or is it still relevant, but mine had a prose reason to crash:
Updated my bios (because one setting was missing from the previous version), and it made the RAM clocks unstable. Before I could reach 3600mhz at CL14 (with a 3200mhz CL14 kit), but with the current version, I was only able to run the ram at 3400CL14.
But Conan is a pretty sensitive entity, all my other games and system ran perfectly, expect this game. So I reinstalled, resubbed the mods, nothing. I changed the ram to its original XMP profile, to 3200 mhz. And it works now.
So the lesson is: it could be ANYTHING that this game does not like. Even if you put your blue shirt on, it wonāt start if it does not like blue.
I am having the same error. Playing single player with no mods on PC Xbox app. It happens randomly during load screen or shortly after game loads, but not every time.
Itās like the players using MSI afterburner, some memories optimisations are not well supported by how UnrealEngine4 is implemented (UE4 error).
Same as the UE4ās TDR (Timeout Detection and Recovery) which checks if your graphics card and your computer are working properly, and resets your graphics card and your GPU if not. (thus conflict between MSI afterburner and Conan exiles).
This option can be shutdown in registry (Fix 7 of https://www.drivereasy.com/knowledge/how-to-fix-unreal-engine-crash-quickly-and-easily/)
There are similar cases in other games with same error that was solved by disabling " Full screen Optimizations", force Nvidia parameter to not used the integrated video cardā¦
Some player was able to bypass with uninstall the game, suppress conan exiles directory then reinstall it.
But try disabling " Full screen Optimizations" firstā¦ it may be a video management conflict.
Thanks for the answer!
I have AMD card, but as I can see, it is a registry edit, so does not matter. But I did some research quick, and the TDR is a mechanism that restarts the driver when it hangs or freezes. I wonder If I turn this off, will the game just slow down, or freeze for a period of time instead of the instant crash?
I will tinker with it.