I thermal crash constantly but the log says it tried to edit a file that was protected

Spacecat8229 shared this bug 8 months ago
Solved

2023-09-01 12:12:09.655 - Thread: 29 -> Exception occurred: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

at SharpDX.Direct3D11.DeviceContext.ExecuteCommandList(CommandList commandListRef, RawBool restoreContextState)

at VRage.Render11.RenderContext.MyRenderContext.ExecuteCommandList(CommandList commandListRef, RawBool restoreContextState)

at VRage.Render11.RenderContext.MyRenderContext.ExecuteContext(MyFinishedContext& fc, String caller, Int32 callerLine, String callerPath)

at VRageRender.MyTransparentRendering.ConsumeWork()

at VRage.Render11.Render.MyRenderScheduler.Done()

at VRageRender.MyRender11.DrawGameScene(IRtvBindable renderTarget, IBorrowedRtvTexture& debugAmbientOcclusion)

at VRageRender.MyRender11.DrawScene()

at VRageRender.MyRender11.FullDraw(Boolean draw)

at VRageRender.MyRender11.Draw(Boolean draw)

at VRageRender.MyDX11Render.Draw(Boolean draw)

at VRageRender.ExternalApp.MyRenderThread.Draw()

at VRageRender.ExternalApp.MyRenderThread.RenderFrame(Boolean async)

at VRageRender.ExternalApp.MyRenderThread.RenderCallback(Boolean async)

at VRageRender.ExternalApp.MyRenderThread.RenderThreadStart(Object param)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart(Object obj)

Replies (2)

photo
0

Hello!

Thank you for contacting us. Since this is a bug report, I'm moving your ticket to our support page, where our QA team will take care of you.

Kind Regards

Keen Software House

photo
1

Hello, hugo,

thank you for reaching us with your issue. We are sorry that you are experiencing it.

Can you please provide me more information about the crash that you are experiencing?

Does it happen in the game when you are doing something specific? Does it require any steps to reproduce?

I can see from log that you are using lot of mods and scripts. Are you experiencing this same crash when you try to play in vanilla game, or only in the modded?

Does this issue happen to you when playing single player, in Lobby online mode or on any server?

Please try to recreate this crash on world/server without mods. It is mod creator/owner responsibility to make sure the mod is working with the current game version.

You can try these workarounds if you are experiencing this crash in vanilla (no mods) game:

  • Verify your game files in Steam – right-click on Space Engineers in Steam Library → Properties → Installed Files → Verify Integrity of Game Files
  • Delete SpaceEngineers.cfg file (it means your game configuration will be deleted) – you can access your SpaceEngineers.cfg by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers.
  • Delete ShaderCache folder – same access as above
  • Back up your whole Space Engineers Roaming folder and delete it
  • Restart Steam
  • Reinstall VC Redist 2017
  • Update graphic drivers
  • Reinstall the game
  • Make sure your operating system is fully updated

If nothing from these would work for you and the crash will continue to occur, please send me new log file from the game without mods.

Thank you in advance.

Kind Regards

Keen Software House: QA Department

photo
1

it happens on unmodded worlds of any type and just at random times.

photo
1

i beleive that the cache reset workd as i am playing on a modded multiplayer worlds and it has not chrashed

photo
1

Hello, Spacecat8229,

thank you for reaching us back with the update!

Happy to hear that you are no longer experiencing this issue and are now able to play the game flawlessly.

Since there is nothing more I can currently help you with regarding this issue, I will close it as solved.

If you happen to experience/observe any other issue in the game, please do not hesitate to contact us again.

Happy Engineering!


Kind Regards

Keen Software House: QA Department

photo
Leave a Comment
 
Attach a file