1.0 crashing constantly

[ROGOT]

Been playing the 1.0 release for about 80 hours now co-op with gf without any issues at all, completely blown away by the performance until the hotfix came out, now we can't play anymore... both in single player mode and with her joined, the game crashes to the below error after just 1 or 2 minutes.

I've tried all the recommended fixes:
- Verified game files
- Redownloaded the game
- Cleared cache
- Updated GPU drivers
- Installed studio GPU drivers
- Tried DX11 and vulcan
- Made sure windows is updated
- Set graphics to low with anything that could remotely impact performance off


The error I get is this:

Version: 367101, IsEditor: No, IsPerforceBuild: No, BuildConfiguration: Shipping, Launcher: Steam, NetMode: Listen Server, IsUsingMods: No, IsSaveGameEdited: No

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008

FactoryGameSteam_FactoryGame_Win64_Shipping!AFGConveyorChainActor::GetAvailableSpace() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\FactoryGame\Source\FactoryGame\Private\FGConveyorChainActor.cpp:1615]
FactoryGameSteam_FactoryGame_Win64_Shipping!AFGConveyorChainActor::Factory_Tick() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\FactoryGame\Source\FactoryGame\Private\FGConveyorChainActor.cpp:267]
FactoryGameSteam_FactoryGame_Win64_Shipping!`AFGBuildableSubsystem::TickFactoryActors'::`67'::<lambda_7>::operator()() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\FactoryGame\Source\FactoryGame\Private\FGBuildableSubsystem.cpp:816]
FactoryGameSteam_FactoryGame_Win64_Shipping!`ParallelForImpl::ParallelForInternal<TFunctionRef<void __cdecl(int)>,`ParallelFor'::`2'::<lambda_1>,std::nullptr_t>'::`2'::FParallelExecutor::operator()() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Public\Async\ParallelFor.h:116]
FactoryGameSteam_FactoryGame_Win64_Shipping!LowLevelTasks::TTaskDelegate<LowLevelTasks::FTask * __cdecl(bool),48>::TTaskDelegateImpl<`LowLevelTasks::FTask::Init<`ParallelForImpl::ParallelForInternal<TFunctionRef<void __cdecl(int)>,`ParallelFor'::`2'::<lambda() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Public\Async\Fundamental\TaskDelegate.h:171]
FactoryGameSteam_Core_Win64_Shipping!LowLevelTasks::FTask::ExecuteTask() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Public\Async\Fundamental\Task.h:627]
FactoryGameSteam_Core_Win64_Shipping!LowLevelTasks::FScheduler::TryExecuteTaskFrom<LowLevelTasks::TLocalQueueRegistry<1024>::TLocalQueue,&LowLevelTasks::TLocalQueueRegistry<1024>::TLocalQueue::DequeueGlobal,0>() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Private\Async\Fundamental\Scheduler.cpp:349]
FactoryGameSteam_Core_Win64_Shipping!LowLevelTasks::FScheduler::WorkerMain() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Private\Async\Fundamental\Scheduler.cpp:378]
FactoryGameSteam_Core_Win64_Shipping!UE::Core::Private::Function::TFunctionRefCaller<`LowLevelTasks::FScheduler::CreateWorker'::`2'::<lambda_1>,void __cdecl(void)>::Call() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Public\Templates\Function.h:480]
FactoryGameSteam_Core_Win64_Shipping!FThreadImpl::Run() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Private\HAL\Thread.cpp:68]
FactoryGameSteam_Core_Win64_Shipping!FRunnableThreadWin::Run() [C:\BuildAgent2\work\b731a33f2a691e17\UE4\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:149]

We're playing on laptops, windows 11 and GPUs are 3050.

Hopefully it will work better when I host the game back home on my desktop, I'll post the result tomorrow, until then any advise is very welcome!

Thanks :)

[ROGOT]

Edit: Just tried installing the DirectX End-User Runtime Web Installer, still no resolve...

[MuttMutt's GameRoom]

I believe this is an issue with the conveyor system. There was a hotfix released that was supposed to help but the crash was still there.

I had good luck with forcing all the conveyor settings to the lowest available but I believe now that is messed up as well, probably due to another hotfix that they thought would help but made things worse.

Some people are using the argument of -DX11 to force the Direct X 11 API's to be used and that may work but since DX11 is going to likely be removed at some point we should avoid it if at all possible.

https://satisfactory.wiki.gg/wiki/Launch_arguments is a good place to look on how to handle the argument.

If you read through the error logs you can see a reference to "Shipping" as well as the "Conveyor Chain" so I have to assume this is still the conveyor system causing issues. The error report will hopefully help the Dev's figure out and fix the problem and get it fixed. On my system I don't even get the error reports but that is a different issue likely related to using Linux.

[ROGOT]

You're right about the conveyor system, as mentioned it worked flawlessly on medium tier laptops in co-op for up to 11 hours straight at times without any issue other than the deafening cooling fans of course.
I just tried on my desktop I7-9700K/3060 and while it took a bit longer, the issue persists... same error report. I also tried forcing dx11 and lowered anything related to view distance and conveyers to off/lowest but that didn't help.
It seemed to work all the way until yesterday afternoon, not sure if the latest hotfixes came out just about then and screwed us over.

I really hope they attend to this issue as the game is practically unplayable for us now and we miss our great factory :/

[Valiant Maverick]

Originally posted by ROGOT:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008

The heck? That's a segfault. It might be a null pointer dereference since the address is really close to zero. That's a common programming error and will probably require another patch to fix.

I don't think your graphics settings are going to have any impact as that message is thrown by the factory mechanics and doesn't look like it has anything to do with rendering. I'm totally shooting in the dark here, but freeing up some more RAM might delay this and allow you to play for longer at a time. That's IF the bug is triggered by an edge case that happens when you run low on RAM, and that might not be what's going on at all.

[Paragon]

Originally posted by ROGOT:

Been playing the 1.0 release for about 80 hours now co-op with gf without any issues at all, completely blown away by the performance until the hotfix came out, now we can't play anymore... both in single player mode and with her joined, the game crashes to the below error after just 1 or 2 minutes.

I've tried all the recommended fixes:
- Verified game files
- Redownloaded the game
- Cleared cache
- Updated GPU drivers
- Installed studio GPU drivers
- Tried DX11 and vulcan
- Made sure windows is updated
- Set graphics to low with anything that could remotely impact performance off

ROGOT Try this...several people have had this same EAV error with some Nvidia cards and its due to a issue with FXAA.

OP Blasty: The crash is due to the Anti-Aliasing methods "None" and "FXAA" not being supported on DX12.

The fix is as follows:

1) Right click on the game in your steam library, go to Properties, then under "Launch Options" (in the General tab) put in -d3d11

2) Launch the game, it should now run, but now you're using the legacy DX version which is not recommended. stop game and proceed to main menu.

3) Go to Options -> Video -> Anti Aliasing Method (under "Advanced" category), switch it to Temporal AA (TAA). Also change Upscaling Method - set to None. And save.

4)Exit Game.

5) Remove the -d3d11 launch option in library.

6) Launch the game again, go into Options -> Video again and switch Graphics API (under Display at the top) to DirectX 12, save, then restart the game.

Maybe this will work for you.

[ROGOT]

Originally posted by Paragon:

Originally posted by ROGOT:

Been playing the 1.0 release for about 80 hours now co-op with gf without any issues at all, completely blown away by the performance until the hotfix came out, now we can't play anymore... both in single player mode and with her joined, the game crashes to the below error after just 1 or 2 minutes.

I've tried all the recommended fixes:
- Verified game files
- Redownloaded the game
- Cleared cache
- Updated GPU drivers
- Installed studio GPU drivers
- Tried DX11 and vulcan
- Made sure windows is updated
- Set graphics to low with anything that could remotely impact performance off

ROGOT Try this...several people have had this same EAV error with some Nvidia cards and its due to a issue with FXAA.

OP Blasty: The crash is due to the Anti-Aliasing methods "None" and "FXAA" not being supported on DX12.

The fix is as follows:

1) Right click on the game in your steam library, go to Properties, then under "Launch Options" (in the General tab) put in -d3d11

2) Launch the game, it should now run, but now you're using the legacy DX version which is not recommended. stop game and proceed to main menu.

3) Go to Options -> Video -> Anti Aliasing Method (under "Advanced" category), switch it to Temporal AA (TAA). Also change Upscaling Method - set to None. And save.

4)Exit Game.

5) Remove the -d3d11 launch option in library.

6) Launch the game again, go into Options -> Video again and switch Graphics API (under Display at the top) to DirectX 12, save, then restart the game.

Maybe this will work for you.

I tried this but it didn't seem to help, thanks a lot for suggesting it though :)

What seemed to help though is that I changed the belt update frequency to unlimited rather than the 30 we limited it to due to trying to maximize performance. It's been running for at least 20 minutes now without an issue. Now we're trying in multiplayer with identical settings, I'll report back if this is solved in case others run their heads against this issue.

Also the 3rd hotfix didn't affect the issue at all.

[ROGOT]

Unfortunately there was no resolve still... it seems that we are able to play for something like 10 minutes at most now before I (the host) crashes with the same error message as initially.
I'm beginning to suspect that this has nothing to do with graphics and that we've in some way built a conveyor belt that is not allowed to exist... Perhaps when a certain machine uses it occasionally it crashes?

[MuttMutt's GameRoom]

Originally posted by ROGOT:

Unfortunately there was no resolve still... it seems that we are able to play for something like 10 minutes at most now before I (the host) crashes with the same error message as initially.
I'm beginning to suspect that this has nothing to do with graphics and that we've in some way built a conveyor belt that is not allowed to exist... Perhaps when a certain machine uses it occasionally it crashes?

To test this once you log into the game head out of your factory area and explore. If the game doesn't crash while no conveyors are visible it may give some more weight to where the issue lies. If it lasts a lot longer or until you move back into the area of your factory then crashes keep a note of the times. If it does crash outside of the area where conveyors are visible see if the error is the same as that may show that it's not the graphics but the actual function of the conveyors themselves.

Maybe start a new game just for testing and don't build anything and see if a crash happens or not. I know it's a pain but the more data the dev's have the better they can solve the issues.

[Paragon]

Originally posted by ROGOT:

Unfortunately there was no resolve still... it seems that we are able to play for something like 10 minutes at most now before I (the host) crashes with the same error message as initially.
I'm beginning to suspect that this has nothing to do with graphics and that we've in some way built a conveyor belt that is not allowed to exist... Perhaps when a certain machine uses it occasionally it crashes?

Does setting your FPS Cap to 60 or 30 help at all?

[michbret123]

Me too, the game is now crashing every hours and that didn't occur before the last patch.

[ROGOT]

I seemingly got it working, it's a bit hard to tell what actually made the real difference. What is different from the initial state is:

- Turned off XMP in bios
- Deleted some unused conveyor belts in the factory
- Turned on DLSS with performance mode

I got the idea to disable XMP from the official website Q/A where someone mentioned it related to gen 13 and 14 intel processors and issues there so I thought why not try that... In retrospect my PC did also feel stressed with it enabled, so generally a good move I suppose, I'm not that much of a performance hunter so any impact there doesn't matter to me, stability and less noise is preferable, even at the cost of visuals.

Now It still crashes, but the interval now is more than an hour, and the error code is not exactly the same, I'll post from next crash if anyone's interested.

I kind of get the feeling from this that it was more the complexity of the game that overwhelmed my laptop as the factory grew, and my PC which is now in a more stable state can handle it... until it can't of course ;)

[ROGOT]

Solved:
After I recently built a blueprint, which in hindsight, I created just before the trouble really started, I had the same horrible crashing experience as just when it started... 1-5 minutes between crashes...

I had built up a suspicion about an elevator in this blueprint that had extended outside of the blueprint machine, but was still accepted and the blueprint could be saved...

So I tried deleting this blueprint at first, then crash, consistently each time without it being deleted. Then I tried deleting the elevator in question, also crash.

The solution that made everything work now is that I took my save to this map editor website, deleted the elevator and started it up again... no crash for hours at end...

So to anyone who reads this, still without resolve, watch those elevators... it's probably not very helpful considering how hard it could be to narrow down in bigger factories, but at least it's something to try out.

[stephanpeck]

Originally posted by ROGOT:

Solved:
After I recently built a blueprint, which in hindsight, I created just before the trouble really started, I had the same horrible crashing experience as just when it started... 1-5 minutes between crashes...

I had built up a suspicion about an elevator in this blueprint that had extended outside of the blueprint machine, but was still accepted and the blueprint could be saved...

So I tried deleting this blueprint at first, then crash, consistently each time without it being deleted. Then I tried deleting the elevator in question, also crash.

The solution that made everything work now is that I took my save to this map editor website, deleted the elevator and started it up again... no crash for hours at end...

So to anyone who reads this, still without resolve, watch those elevators... it's probably not very helpful considering how hard it could be to narrow down in bigger factories, but at least it's something to try out.

Glad you ended up figuring it out. I had a very similar experience with a buggy blueprint. I had some splitters at the edge of my blueprint and elevators on the outside of the blueprint and whenever I deleted either, my game would instantly crash. (As well as crashing when I'd exit to desktop.)

Took your advice and used a map editor to delete the affected splitters and elevators in the built instances of the blueprint, and those parts in the blueprint designer so that I could save the fixed blueprint. No crashes since!

[Kage Goomba]

Seems the reoccurring theme is to keep everything inside the cube or risk major issues. (not the first time I've heard about this)

[Ozgamer]

the game crashes if i drive, run or fly. i've posted on their discord etc, but they all said #usererror. buch of idiots. has anyone else had this problem. it's not a system problem. i'm completely lost on how to fix this.