I need help solving an unreal engine crash.

[Celeborn]

A little background of what im running with.

ryzen 7
nividia 3060
32gb ddr5 ram

we are playing on a dedicated server and its important to note that my friends on the same server do not get this error so i have to believe that it is on my end that the problem is happening. It doesn't seem to matter what i'm doing when it crashes. Seems random

This is the error code i'm getting. when it happens i get completely kicked from the game and have to restart everything to get it going again.

Version: 211839, IsEditor: No, IsPerforceBuild: No, BuildConfiguration: Shipping, Launcher: Steam, NetMode: Client, IsUsingMods: No

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x0000000000000000

FactoryGame_FactoryGame_Win64_Shipping!<lambda_ca67515999c2f313172565c8688a503d>::operator()() [D:\BuildAgent\work\78a794e88763017d\UE4\Games\FactoryGame\Source\FactoryGame\Private\FGBuildableSubsystem.cpp:561]
FactoryGame_FactoryGame_Win64_Shipping!ParallelForImpl::TParallelForData<TFunctionRef<void __cdecl(int)> >::Process() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Public\Async\ParallelFor.h:177]
FactoryGame_FactoryGame_Win64_Shipping!TGraphTask<ParallelForImpl::TParallelForTask<TFunctionRef<void __cdecl(int)> > >::ExecuteTask() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:886]
FactoryGame_Core_Win64_Shipping!FTaskThreadAnyThread::ProcessTasksUntilQuit() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:887]
FactoryGame_Core_Win64_Shipping!FTaskThreadBase::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:541]
FactoryGame_Core_Win64_Shipping!FRunnableThreadWin::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:86]


I'm open to any suggestions. Getting to the point that i can play this game anymore

[❤ Sly Succubus ❤]

EXCEPTION_ACCESS_VIOLATION 0x0000000000000000

I'll start here, a 0x0000000000000000 code is actually a very straight forward error, the complete line of zeros is a Null Pointer exception which only happens when something the game is trying to access a location it does not have permission for, despite btw it saying 0x000000000, Unreal's actual error is 0xFFFFFFFF, a known odd display situation but regardless you have a 0xFFFFFFFF Access Error Violation

Now the following code did actually help as those are area that the game should have default access to and its clear it has access to them but I want to ask in advance, when the game is running how much memory is being used up (percentage wise) and the other question, do you have any antivirus on that alters your firewall (such as avast or others?) because this error is a bit of a big one

Not big btw in terms of how large the problem is, but rather of what could be causing it because an Access error violation is a rather massive umbrella term for any program ranging from Java to Unreal and Unreal has several hundred forms of it but I have discarded some because I'm guessing you got the game to run before already, so that ignores driver and windows problems for the moment, so it sounds like a possible firewall block or that your running out of memory as the game loads, it could be something else but its best to start on the basics here.

[Celeborn]

I've got 32gb if ram so doesn't use a high percentage of what I have available. I've run serveral memory diagnostic checks and they have all come up clean. I did have avast but uninstalled it. I only have the basic windows defender running now.

I uninstall and reinstalled the game and this particular error hasn't flagged up again but now I'm getting another one which is the following:

Version: 211839, IsEditor: No, IsPerforceBuild: No, BuildConfiguration: Shipping, Launcher: Steam, NetMode: Client, IsUsingMods: No



Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000001e31a0e88



FactoryGame_FactoryGame_Win64_Shipping!<lambda_ca67515999c2f313172565c8688a503d>::operator()() [D:\BuildAgent\work\78a794e88763017d\UE4\Games\FactoryGame\Source\FactoryGame\Private\FGBuildableSubsystem.cpp:561]

FactoryGame_FactoryGame_Win64_Shipping!ParallelForImpl::TParallelForData<TFunctionRef<void __cdecl(int)> >::Process() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Public\Async\ParallelFor.h:177]

FactoryGame_FactoryGame_Win64_Shipping!TGraphTask<ParallelForImpl::TParallelForTask<TFunctionRef<void __cdecl(int)> > >::ExecuteTask() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:886]

FactoryGame_Core_Win64_Shipping!FTaskThreadAnyThread::ProcessTasksUntilQuit() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:887]

FactoryGame_Core_Win64_Shipping!FTaskThreadBase::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:541]

FactoryGame_Core_Win64_Shipping!FRunnableThreadWin::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:86]


He is the run down of what I have done to try and correct these errors:

I've used a driver update program to update all drivers that it could find

I've updated my graphics card driver

I've tried uninstalling anti virus since i heard that could cause problems

I've run a memory diagnostic with 0 faults

I've verified game files

I've reinstalled the game

I've launched through mod manager with mods turned off

I've tried switching between DX11, DX12 and Vulkan (happens on all setting)

I've turned down graphics setting and capped fps to 60

I'vve turned on VSYNC

['Noracs]

thanks

[Snutt]

Dedicated Servers are still quite experimental and this looks like a game related crash so not much to do but wait until we can get around to looking into this particular crash. It's possible it's been resolved in Update 8.

[Celeborn]

Originally posted by Snutt:

Dedicated Servers are still quite experimental and this looks like a game related crash so not much to do but wait until we can get around to looking into this particular crash. It's possible it's been resolved in Update 8.

Any time line for when update 8 will be out of experimental? We can't apply it to our server to play untill it is 😂