Platform: Steam
Issue Type: Crash
Game Mode: Single Player
Server Type: PvE
Map: Exiled Lands
Server Name: =SERVER NAME=
Mods: C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3414957155/MildTemperature.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3043356654/FaceIt.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3423068671/Heritage.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3248573436/Attic-Hair.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3073504073/Agonys-Attic.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3326354818/immersivearmor.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3047802602/NexusKitsOnly.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\3036057084/ModAdmin.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\2677532697/TotImmersiveHud.pak C:\Program Files (x86)\Steam\steamapps\workshop\content\440900\2886779102/TotCustom.pak
Bug Description:
Fatal Exception
Bug Reproduction:
This has been happening since 30th Jan update. Tried with no mods. Stripped back mods. Yet still crash either 1 hour in or on start up with no rhyme or reason - Last log [2025.03.14-00.42.52:454][133]LogMemory: Platform Memory Stats for WindowsNoEditor [2025.03.14-00.42.52:454][133]LogMemory: Process Physical Memory: 3545.39 MB used, 4212.66 MB peak [2025.03.14-00.42.52:454][133]LogMemory: Process Virtual Memory: 7792.12 MB used, 8471.60 MB peak [2025.03.14-00.42.52:454][133]LogMemory: Physical Memory: 16035.81 MB used, 49339.22 MB free, 65375.04 MB total [2025.03.14-00.42.52:454][133]LogMemory: Virtual Memory: 14328.09 MB used, 49339.22 MB free, 134217728.00 MB total [2025.03.14-00.42.52:454][133]LogWindows:Error: === Critical error: === [2025.03.14-00.42.52:454][133]LogWindows:Error: [2025.03.14-00.42.52:454][133]LogWindows:Error: Fatal error! [2025.03.14-00.42.52:454][133]LogWindows:Error: [2025.03.14-00.42.52:454][133]LogWindows:Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000001 [2025.03.14-00.42.52:454][133]LogWindows:Error: [2025.03.14-00.42.52:454][133]LogWindows:Error: !0x0000000000000000 [2025.03.14-00.42.52:454][133]LogWindows:Error: [2025.03.14-00.42.52:467][133]LogExit: Executing StaticShutdownAfterError [2025.03.14-00.42.52:473][133]LogPhysics:Error: PHYSX: ( 0) eINVALID_OPERATION : PxScene::lockWrite() detected after a PxScene::lockRead(), lock upgrading is not supported, behaviour will be undefined. [2025.03.14-00.42.52:473][133]LogPhysics:Error: PHYSX: (C:\REPO\Engine\Source\ThirdParty\PhysX\PhysX_3.4\Source\PhysX\src\NpScene.cpp 3020) eINVALID_OPERATION : PxScene::unlockWrite() called without matching call to PxScene::lockWrite(), behaviour will be undefined. [2025.03.14-00.42.52:473][133]LogPhysics:Error: PHYSX: ( 0) eINVALID_OPERATION : PxScene::lockWrite() detected after a PxScene::lockRead(), lock upgrading is not supported, behaviour will be undefined. [2025.03.14-00.42.52:474][133]LogPhysics:Error: PHYSX: (C:\REPO\Engine\Source\ThirdParty\PhysX\PhysX_3.4\Source\PhysX\src\NpScene.cpp 3020) eINVALID_OPERATION : PxScene::unlockWrite() called without matching call to PxScene::lockWrite(), behaviour will be undefined. [2025.03.14-00.42.52:477][133]LogPhysics:Error: PHYSX: (C:\REPO\Engine\Source\ThirdParty\PhysX\PhysX_3.4\Source\PhysX\src\NpScene.cpp 218) eINVALID_OPERATION : PxScene::lockWrite() detected after a PxScene::lockRead(), lock upgrading is not supported, behaviour will be undefined. [2025.03.14-00.42.52:481][133]LogPhysics:Error: PHYSX: (C:\REPO\Engine\Source\ThirdParty\PhysX\PhysX_3.4\Source\PhysX\src\NpScene.cpp 3020) eINVALID_OPERATION : PxScene::unlockWrite() called without matching call to PxScene::lockWrite(), behaviour will be undefined. [2025.03.14-00.42.52:486][133]LogWindows: FPlatformMisc::RequestExit(1) [2025.03.14-00.42.52:486][133]Log file closed, 03/14/25 00:42:52 - System specs: I9-13900KF Processor 64gb DDR5 ram 2x 2TB Samsung SSD 990 Pro GTX 4090 Latest driver. 572.70
I cannot play session without crashing, I was going to write a report about it but then I saw yours. Man, what a heartbreak; just crash after crash, no mods, clean install, verified files, I lowered the graphic settings even tho my rig can more than handle cinematicā¦ crash. I canāt play at ease, waiting for the next crash,
I will spare you the tragic, long, depressing story, but I literally depend on this game so I donāt go ape-shit crazy and start throwing my poop at the walls =[
I would love to know if we are in a niche minority or if everyone is having this major problem. BTW where is that report of a bug stored at, if you please?
I have run several servers, some with over 40 mods, without having crashes.
If this is giving the setup of your computerās virtual memory, that might be the problem. 134217728.00 MB is 128 TB: AFAIK, the largest disk available is 100TB (for about USD$40,000). If your virtual memory is set that high, change it to 1 1/2 - 2 times your 64GB real memory (96-128 GB). That huge value currently set can result in system crashes if the system tries to access virtual memory space on disk that does not exist.
Edit: forgot to give the whole setup. Initial virtual size should be 1 1/2 or 2, the max should be 3x - 194GB
Single player/multi-player/server does not matter. If the computer virtual memory is set up improperly, crashes can occur - that is a computer problem, not a game problem. Check your virtual memory settings.
Too small virtual memory can also lead to crashes.
How exacly does one do that? There are no advanced options where the web is telling me to go in the settings panel, win 10.
Odd that just after the 30th this begun happening. Were it to be a virtual memory issue, what happened in 4600 hours of gameplay where this did not happen
I apologize for not including this link in my first post - I got it on the DSL forum when my server was crashing due to virtual memory, and I am aware it is not something āeverybody knowsā. The OP might well also need this.
Note: I am not allowed to include links in posts so I inserted spaces that need to be removed.
It is not absolutely that virtual memory is your problem. The OP posted his log which suggest a potential a potential for it due to the VM size. After an update, a game might start using more memory due to additions ā¦ or bugs ā¦ in the update. Checking your machine first and posting the log can help locate a problem both ways.
I was just there, they keep directing me to advanced options that do not exist? Thanks for trying to help but this smells FUNCOM like a beached fishing boat.
Who is directing you to what advanced options? The windows central link worked for me for Windows 10.
Donāt recall - you might need to be system admin on PC to change these settings
just followed the instructions at the link. The image on that page is out of date. The āAdvance system settingsā is now on the right side of the page. I had to enter the admin password
Thanks for your help, my system had allocated the memory in the C: partition, 2600 or so , and there were currently over 9k allocated as the game was running. Thanks to your help I allocated the v memory to drive D: from 250k to a max of 500k. Obviously something was very wrong, I hope it stops the crashes, and thank you again.
P.S. I thought you were sending me to the official Microsoft page, where I was. I assumed, my bad. That or my weed has gone stale. Anyways, you got me there.
Glad you got it sorted. Not sure if your your values are typos - did you set 250000 as the initial size/500000 as max? I have a 32Gb main memory system. The values I set were 48000 init/96000 max. A half terabyte max is pretty hefty! With 64Gb, I would double my setting values.
Thanks again for your patience and guidance. I thought higher lvls would be better but evidently, I do not know what I am doing. I havenāt had a single crash since I changed the values; I figured if I had the space, the more v m allocated the better the performance, but I just copied your suggested values, Iām sure they are sensible; besides, like I said, it is evident I do not know what I am doing, heh.
You are welcome. On SSD, wasted space is probably the only issue with excess pagefile size. On HDD, excess can cause some slow down due to head seek time over the unused areas. Some places suggest 4x for max but I have never had a problem at 3x. SSD vs HDD is the way to improve v mem efficiency if you have the option.
Most people never need to deal with v memory and do not even know it exists. People burned by system default not being good enough are those who run programs that require large amounts of memory like this game. Donāt feel bad about not knowing - IMO you shouldnāt have to deal with it.
I waited until near end of the weekend to follow up. kikigirl has done so in your bug report thread.
If your problem is resolved, please mark your bug report as resolved and let others know what fixed it. That will help other players who have the same problem as you and it will help developers by not spending time looking for a bug that does not exist. Thanks!
Yes, I have not crashed a single time since you fixed the problem. I would certainly mark the issue as resolved but unfortunately, this is not my post and I cannot mark anything as āsolutionā.
I flagged my post for moderation and it has been taken down.
This used to be something I did from xp through to win 7 and even turned off for win 10, I tried the same for win 10 and left it at default for some reason I forgot now, but it is great to find resolutions for issues that are not game related but are affected by this particular game, vm being one of them, great find @bowman
Greetings Vanden!
Thank you for reaching out to us and welcome to our forum.
Aside from the valuable tips shared by some players, situations like this may occur due to the usage of Mods in your game. As such, we suggest that you fully uninstall your Mods completely in order to see if your game returns to normal.
Additionally, please verify your files by going to your Conan Exiles on Steam ā right click it and go to āāPropertiesāā ā Installed Files ā and click to āāVerify integrity of game filesāā.
Do let us know if these solutions helped you in fixing your issue please!
, and there were currently over 9k allocated as the game was running. Thanks to your help I allocated the v memory to drive D: from 250k to a max of 500k. Obviously something was very wrong, I hope it stops the crashes, and thank you again.