[1.201.014] EOS "Ghost" Crash

Slushtrap Gamer shared this bug 15 months ago
Won't Fix

A most unsettling crash has been discovered to randomly take place. Where a normal crash often results from an exception being thrown, here no exception or even error message can be observed, with the log ending such as:


2023-01-30 21:11:34.390 - Thread: 23 -> STATISTICS LEGEND,time,ReceivedPerSecond,SentPerSecond,PeakReceivedPerSecond,PeakSentPerSecond,OverallReceived,OverallSent,CPULoadSmooth,ThreadLoadSmooth,GetOnlinePlayerCount,Ping,GCMemoryUsed,ProcessMemory,PCUBuilt,PCU,GridsCount,RenderCPULoadSmooth,RenderGPULoadSmooth,HardwareCPULoad,HardwareAvailableMemory,FrameTime,LowSimQuality,FrameTimeLimit,FrameTimeCPU,FrameTimeGPU,CPULoadLimit,TrackedMemory,GCMemoryAllocated,PersistedEncounters,EncounterEntities

2023-01-30 21:11:34.390 - Thread: 23 -> STATISTICS,32108.9166667,0.07116032,0.2633848,4.437288,2.158751,838.0266,1801.997,34.22557,36.97969,12,0,2252.588,4514.867,332303,-299960,193,0,0,0.07105618,25053,0,0,16.66667,0,0,100,1354166304,2252.588,0,0

2023-01-30 21:11:34.390 - Thread: 23 -> MEMORY LEGEND,Srv,Uav,Read,Debug,Index,Audio,SrvUav,Vertex,Buffers,Physics,Planets,Systems,Textures,Indirect,Constant,RwTextures,Dx11Render,MeshBuffers,FileTextures,DepthStencil,TileTextures,Voxels-Native,CustomTextures,HeightmapFaces,Mesh GPU Buffers,BitStreamBuffers,GeneratedTextures,FileArrayTextures,NativeDictionaries,CubemapDataBuffers,HeightDetailTexture,MyDeviceWriteBuffers,ShadowCascadesStatsBuffers,AI_PathFinding,EpicOnlineServices,EpicOnlineServicesWrapper

2023-01-30 21:11:34.390 - Thread: 23 -> MEMORY VALUES,0,0,0,0,0,0,0,0,0,276,363,1291,0,0,0,0,0,0,0,0,0,0,0,144,0,234,0,0,409,216,3,0,0,0,0,0

This makes it impossible to determine exactly what caused the crash.

Replies (9)

photo
1

Hello, engineer!

Sorry to hear you're experiencing this issue.

Could you share some additional information about the issue?

Is this EOS server a DS or Keen's official one?

Are you experiencing crashes on other servers as well?

Kindly send us the whole log file when experiencing this issue.

We are looking forward to assisting you with this issue.

Kind Regards,

Keen Software House: QA Department

photo
1

This EOS server is a dedicated server run by me, if this happens on other places i dont know since that would only show up in the server logs, which i only have access to on my own server. Heres a log displaying the behavior in full:

photo
1

Hello, engineer!

Could you also send us your (client) log and the log from the Windows Event Viewer when experiencing this issue on your DS?

  • You can access your log files by typing %appdata% into your Windows search bar, and you will get redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers.

To get the Windows Event Viewer log, please open the Event Viewer (from the start menu, type Event Viewer). In the Event Viewer, go to Windows Logs, Application, and send the top “.NET Runtime” error from Application: SpaceEngineers.exe. (please see attached image).

To do this right, please follow these steps:

1) Select the correct file on the left side (Application)

2) Select first the .NET runtime error from the top (using default ordering)

3) Copy the large bottom text and send it to us.

Please Note: make sure that the info is from the Application: SpaceEngineers.exe

Kind Regards,

Keen Software House: QA Department

photo
1

The log from the event viewer is the following:

Application: SpaceEngineersDedicated.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address 00007FFBF61B03C6

Stack:

Sadly, im unable to get the client log files as i wasnt around when this crash occured.

photo
1

Hello, engineer!

Thank you for providing further information.

The exception error in the Windows Event Viewer log seems to be associated with a memory issue or conflict with drivers.

Kindly try the following workarounds that might resolve the issue.

Verify your game files on Steam

  • Right-click on Space Engineers in Steam Library → Properties → Local 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 SpaceEngineers.cfg
  • 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 the issue persists, kindly send us the DS world save you're experiencing this issue with.

  • You can access your saved files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\\SpaceEngineersDedicated\Saves.
  • Please zip the file and attach it here. If you are having difficulty attaching files you can optionally use Google Drive. When sharing a google drive link please make sure it is set to be downloadable by anyone with the link.

Kind Regards,

Keen Software House: QA Department

photo
1

Heres the full world from the server.

photo
1

Still being experienced on the latest version (1.202.124).

photo
1

that event viewer error code indicates an access violation here's a link to microsoft's website for a full explanation

https://learn.microsoft.com/en-us/shows/inside/c0000005

photo
photo
1

Hello engineer!

Thank you for providing additional information.

After reviewing the log, we did not find any errors or exceptions. Furthermore, we were unable to reproduce or experience any crashes with the provided world save.

Have you managed to identify the steps to reproduce this 'ghost crash,' or has it been resolved by following the workaround mentioned in our previous response?

Kind regards,

Keen Software House QA Department

photo
1

Hello, engineer!


as there has been no reply to this thread in some time, we will close it. If you're still experiencing this issue, please create a new thread.


Kind Regards,

Keen Software House: QA Department

Leave a Comment
 
Attach a file