Game Crashes - Only recently in the past 1-2 weeks

[KegZ]

Hello IT experts and fellow factory managers. I need some help with game crashes and possibly a fix for this. It happens every 10 minutes and only started about a week ago.
I don't think my factory is all that big, compared to some of the pictures I see in the community, it feels like I'm no where near any sort of building limit. I run the game on ultra graphics, and my computer should be more than enough to handle it.

Windows 10 Pro
AMD RYZEN 5 7600X 6-Core Processor, 4701 MHZ
Geforce RTX 4080
MOBO - TUF Gaming B650-Plus-WIFI
32GB RAM
powersupply Corsair SF 750W


What I have tried to do...
- Reinstalled the game several times
- Verified Steam files
- Reinstalled windows from a save point 2 weeks prior to this happening.
- Tried different keyboards, mouse, peripherals etc.
- I have sent my hardware in for inspections / diagnostics. CPU, RAM, MOBO, GPU etc.
- Reinstalled windows OS multiple times
- Swapped RAM slots
- Reseated CPU so it sits better
- Uninstalled recent programs (My computer is basically empty only 1 month old. Only has steam installed + Games.

---------------------------------------
THIS IS THE ERROR CODE I GET FROM THE GAME CRASH REPORT SCREEN. If anyone can read this and pick out whats happening that would be amazing.

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

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff

FactoryGame_RHI_Win64_Shipping!FRHICommandListExecutor::ExecuteInner_DoExecute() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\RHI\Private\RHICommandList.cpp:370]
FactoryGame_RHI_Win64_Shipping!TGraphTask<FExecuteRHIThreadTask>::ExecuteTask() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:886]
FactoryGame_Core_Win64_Shipping!FNamedTaskThread::ProcessTasksUntilQuit() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:600]
FactoryGame_RenderCore_Win64_Shipping!FRHIThread::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp:320]
FactoryGame_Core_Win64_Shipping!FRunnableThreadWin::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:86]


-------------------------------
Could be unrelated, but I also get blue screens every few hours. Maybe you can even help me with these crashes too :)
Error codes
-Stop Code: SYSTEM_SERVICE_EXCEPTION
-What Failed: win32kfull.sys

Stop Code: IQL_NOT_LESS_OR_EQUAL
------------------------------

I hope someone out there has a fix or can help me. Much appreciated. Thank you.

[Wolfgang]

Probably an OS issue if you get BSODs. And a quick online search tells that it is likely a driver issue. Try this:
https://answers.microsoft.com/en-us/windows/forum/all/bsod-win32kfullsys/d3c76032-51b2-4b7f-a034-0a5c15be16c3

Make sure your OS is fully-up to date as well as any driver you use.

[kimba-rip]

blue screen of death is a system fault, your pc specs look more than fine to play game..chances are your o/s hard drive is die'in or your have something that needs update'in...try this link for more info.... https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEwjX7qvG7qb9AhUav-0KHUItCDMYABADGgJkZw&ohost=www.google.com&cid=CAASJORoOZX47FMR17iopZBS71qHjQJmvxnhcbvJ1TlyxdygOUHaBQ&sig=AOD64_1cYoCw-NVnLEAPI7nEXcTTIE5wQw&q&adurl&ved=2ahUKEwjj1KbG7qb9AhVqTEEAHeyhAWQQ0Qx6BAgFEAE

[ThunderHawk]

sounds like one of your hard drives is failing do you use more than one and if yes hdd or ssd and what is installed where

also installing windows off a safepoint is never a good idea i would save any data you need to safe and reinstall windows clean that solves most of problems with blue screens

[KegZ]

Hey guys thanks for the help. I'll check out these solutions and report back.
I have a completely new computer, ever single part is less than a month old. I have two SSD, Steam is on a separate drive than the OS. No files or programs kept from my old computer. Should be no viruses/ corrupted programs. It is 100% fresh. I did a fresh OS wipe / install last night so there is nothing on here except steam and satisfactory + drivers I needed. SO hopefully these errors are now gone. But this would be the third time I have reinstalled so I wouldn't be surprised if its hardware.

Ill check my updates and drivers again and run it today to test for any crashes.
Blue screens aside. Did anyone pick up any faults with why the game crashes from the code i posted? It is a separate issue than the BSOD (or is it?)

[KegZ]

C:\Windows\system32>verifier /log

Time Stamp: 02/22/2023 08:13:51.882

Verifier Flags: 0x001209bb

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[X] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Verifier Statistics Summary

Raise IRQLs: 0
Acquire Spin Locks: 0
Synchronize Executions: 0
Trims: 0

Pool Allocations Attempted: 1282287
Pool Allocations Succeeded: 1282287
Pool Allocations Succeeded SpecialPool: 1282287
Pool Allocations With No Tag: 0
Pool Allocations Not Tracked: 958398
Pool Allocations Failed: 0
Pool Allocations Failed Deliberately: 0

Driver Verification List

MODULE: win32kfull.sys (load: 2 / unload: 0)

Pool Allocation Statistics: ( NonPaged / Paged )

Current Pool Allocations: ( 634 / 6 )
Current Pool Bytes: ( 35422 / 864 )
Peak Pool Allocations: ( 648 / 8 )
Peak Pool Bytes: ( 36206 / 1048 )
Contiguous Memory Bytes: 0
Peak Contiguous Memory Bytes: 0

[KegZ]

Different game crash report:

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

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000001ec8cb0ff90

FactoryGame_Renderer_Win64_Shipping!FetchVisibilityForPrimitives_Range<1>() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\SceneVisibility.cpp:940]
FactoryGame_Renderer_Win64_Shipping!FetchVisibilityForPrimitives() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\SceneVisibility.cpp:1548]
FactoryGame_Renderer_Win64_Shipping!OcclusionCull() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\SceneVisibility.cpp:1712]
FactoryGame_Renderer_Win64_Shipping!FSceneRenderer::ComputeViewVisibility() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\SceneVisibility.cpp:3993]
FactoryGame_Renderer_Win64_Shipping!FDeferredShadingSceneRenderer::InitViews() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\SceneVisibility.cpp:4335]
FactoryGame_Renderer_Win64_Shipping!FDeferredShadingSceneRenderer::Render() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\DeferredShadingRenderer.cpp:1654]
FactoryGame_Renderer_Win64_Shipping!RenderViewFamily_RenderThread() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\SceneRendering.cpp:3619]
FactoryGame_Renderer_Win64_Shipping!<lambda_a130dab11d6a2871fd06081edd3ad64f>::operator()() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Renderer\Private\SceneRendering.cpp:3900]
FactoryGame_Renderer_Win64_Shipping!TGraphTask<TEnqueueUniqueRenderCommandType<`FRendererModule::BeginRenderingViewFamily'::`34'::FDrawSceneCommandName,<lambda_a130dab11d6a2871fd06081edd3ad64f> > >::ExecuteTask() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:891]
FactoryGame_Core_Win64_Shipping!FNamedTaskThread::ProcessTasksUntilQuit() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Async\TaskGraph.cpp:600]
FactoryGame_RenderCore_Win64_Shipping!RenderingThreadMain() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp:373]
FactoryGame_RenderCore_Win64_Shipping!FRenderingThread::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp:509]
FactoryGame_Core_Win64_Shipping!FRunnableThreadWin::Run() [D:\BuildAgent\work\78a794e88763017d\UE4\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:86]

[KegZ]

This one happened when I left the game open for 20 or more minutes without touching anything = AFK. Came back, moved the mouse / came back from idling and then crashed seconds later. Would this be a hard drive spinning up and crashing? or some feature going into sleep mode while its idle, and upon waking crashing?

[KegZ]

引用自 Wolfgang：

Probably an OS issue if you get BSODs. And a quick online search tells that it is likely a driver issue. Try this:
https://answers.microsoft.com/en-us/windows/forum/all/bsod-win32kfullsys/d3c76032-51b2-4b7f-a034-0a5c15be16c3

Make sure your OS is fully-up to date as well as any driver you use.

I have done everything on the list going down. No errors reported, and I posted the verified logs above for you to look through.

引用自 kimba-rip：

blue screen of death is a system fault, your pc specs look more than fine to play game..chances are your o/s hard drive is die'in or your have something that needs update'in...try this link for more info.... https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEwjX7qvG7qb9AhUav-0KHUItCDMYABADGgJkZw&ohost=www.google.com&cid=CAASJORoOZX47FMR17iopZBS71qHjQJmvxnhcbvJ1TlyxdygOUHaBQ&sig=AOD64_1cYoCw-NVnLEAPI7nEXcTTIE5wQw&q&adurl&ved=2ahUKEwjj1KbG7qb9AhVqTEEAHeyhAWQQ0Qx6BAgFEAE

Scanned and resolved all issues found, nothing major, just junk files, registry and privacy.
Restarted my computer and scanned again, no issues found, so must be "resolved". I will test tonight and run it for a few hours and see what happens and post my findings.

I appreciate all the help.

[Wolfgang]

I'm not someone who understands these logs (the windows log specifically) but if you continue to have the BSODs maybe reach out to Microsoft with the crash details and the needed files.

[sansee]

New computer, reformatted several times and different error codes? Most likely driver/hardware problem, mostly RAM and mamaboard, and in rare cases it's some Windows update (they don't bother to test everything they push out).

More than often this comes due to faulty drivers (newer isn't always the best) or faulty memory modules. I'm assuming you have two ram modules? Test each one, one and one, in different lanes.

When you reformat you install the exactly the same thing, right? Don't install anything unless you absolutely must, Windows 10 has a pretty good driver base. Next time you reformat don't install ANY extra that comes with the mamaboard, monitor, or mouse f.ex.. And don't update the OS either, just to eliminate that part, unplug it.

And just to be sure run these after the reformat (as Admin);
sfc /scannow (General sys corruption)
DISM.exe /Online /Cleanup-image /Checkhealth
chkdsk /f
mdsched.exe (Memory checker. Choose to restart now. I've caught several faulty memory modules with this one. Run it with one module at a time.)

If everything is fine at this point you know that it's probably the extra/drivers (or the update) you install. Take it one by one and see how far you get.

Process of elimination can be rather long and arduous. Got a faulty mamaboard a few times but it's pretty rare, luckily. CPUs are pretty much clean alround and are usually tested pretty good before they get to you (until they get old then wear have a funny effect on the electron stream.)

[Galimet]

Im getting the same crash, ive tried everyting, my computer is also brand new, evryting updated, and verified, but couldnot find the problem, ive given up, so if you find the problem, hope you can share waht it was,

[KegZ]

引用自 Galimet：

Im getting the same crash, ive tried everyting, my computer is also brand new, evryting updated, and verified, but couldnot find the problem, ive given up, so if you find the problem, hope you can share waht it was,

Hey mate, don't give up yet, I'm close to an answer!

So far I have (apparently) fixed my blue screens, I have not had one for almost 2 days now.
I reinstalled windows again, but repartitioned my drives and only installed the very minimum required. I have fully updated windows and drivers and everything needed. I ran the Restoro program that Kimba linked, and resolved some minor issues... you should try it too.

I also changed my sleep mode from 30 minutes to never and my power usage to performance (not power saving), I cannot say they did anything, but I'm laying it all out there as it may help you... I have looked further into the crashes and what the codes mean and it seems to be RAM / Memory related. My computer parts are currently new generation technology DDR5, new series motherboard etc. If you have new gen parts like me then maybe there are some bugs to be worked out by the tech companies...

I will be ordering new RAM in the next 1-2 weeks and will try that. If my problem is solved I will post back for you. I know its frustrating as hell, so if I can help you too that would just be swell.

Game crashes are less frequent, about 1-2 hours apart instead of every 5 minutes, so i would call that 2 steps forward.

[Galimet]

Yea, that why i gave up, my stuff are almost all new gen, ive got a blue screen only once, for the rest ive only got the game stopping and getting a bug report after 30 -45 min, never past that,

i was using the Epic game store version, bought the Steam one just in case it might have been a launcher probleme, but it was not,

I know it not sleep mode related,.... i dont use it, but,.....the only similarities ive found was it was always at or close to an autosave, might not be related, but nothing to lose at this point,

the only thing that bother me is that this is the only game that happen, all my other game ( other that Forza Horizon 4, who got a Nvidia Driver error atm) are working fine,

Ive been looking for 3 week, at this point im waitng for a fix update from the dev, that might be something they know about and are working on it

[Wolfgang]

引用自 Galimet：

Im getting the same crash, ive tried everyting, my computer is also brand new, evryting updated, and verified, but couldnot find the problem, ive given up, so if you find the problem, hope you can share waht it was,

Do you also have BSODs? Can you please post the error code you see on the blue screen?
Also, when your game is crashing please post the crash log here. Your hardware specs would also be helpfull.

[Wolfgang]

@OP: Good to know that the BSODs are fixed now apparently. Are you getting any new crash log? If you do please post it here.