Attempting sandbox mode hard crashing to desktop.

[sonic sinew]

Anyone able to go into sandbox mode? I Just got the update and now when entering sandbox mode the game will not load past the inital loading screen. Can still hear audio and move mouse just never finishes loading. as seen here.
https://gyazo.com/19b7637ff5b5b5b6e031660d751d3e18

EDIT: I Put all my settings on the lowest possible settings just to test things and Now it's actually hard crashing to desktop when trying to go into sandbox mode.

The following UE Error is given.

LoginId:84db8bf94b36183898bbbc85b02d488b
EpicAccountId:121cc34df69c4765a43393b3abd36e91

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION writing address 0xffffffffffffffe8

TheCrust_Win64_Shipping
TheCrust_Win64_Shipping
TheCrust_Win64_Shipping
TheCrust_Win64_Shipping
TheCrust_Win64_Shipping
TheCrust_Win64_Shipping
TheCrust_Win64_Shipping
TheCrust_Win64_Shipping

Analysis of the Stack Trace

The stack trace indicates a crash in TheCrust_Win64_Shipping executable. Here's what we can infer:

Key Observations

1. Faulting Function:

   TheCrust_Win64_Shipping!png_get_uint_16+0x... (multiple occurrences)
   

   • This suggests an issue in png_get_uint_16, a function used to read 16-bit values from a PNG file.

2. Multiple Calls to png_get_uint_16:

   • The repeated presence of png_get_uint_16 suggests a corrupted PNG file or an invalid memory reference while reading image data.
   • The crash could be due to out-of-bounds access, an invalid pointer dereference, or corrupt PNG headers.

3. References to strerror():

   TheCrust_Win64_Shipping!src_strerror+0x...
   

   • This function is typically used to retrieve error messages related to standard C library functions (e.g., file I/O errors).
   • This suggests the game tried to handle an error, but the handling itself failed, leading to an access violation.

4. Kernel Calls & Exception Handling:

   • ntdll!NtWaitForSingleObject
   • KERNELBASE!WaitForSingleObjectEx
   • These indicate that the program was waiting for something (e.g., a file read or a thread) before the crash happened.

---

Possible Causes

1. Corrupt or Missing PNG File

• If a texture or UI image is missing or corrupted, the game may be attempting to read an invalid memory location.
• This could happen due to:
  • A corrupted installation
  • Modifications to game files
  • Broken texture files

2. Heap Corruption / Buffer Overflow

• If png_get_uint_16 is reading beyond allocated memory, it could indicate a heap corruption bug.
• The error could be triggered by:
  • A bad pointer in memory.
  • A buffer overrun when decoding PNG data.
  • Improper error handling for PNGs.

3. Graphics Driver Issue

• If PNG decoding is related to texture loading, an outdated or buggy graphics driver could be involved.
• Try updating your GPU drivers.

4. Game Bug

• If this issue occurs consistently, it may be a game bug where invalid PNGs are being loaded incorrectly.

---

ATTEMPTED FIXES

❌ Verify Game Files
-Verified Game files no fix.

❌Tried different graphic settings.
All Maxed / all minimum
With and Without LOD disabled.

❌Check for Corrupt PNG Files

• Didn't see anything that looked off

❌Updated GPU Drivers

• See additional screenshot.

❌Try Running in Windowed Mode

• Attempted in Fullscreen/Borderless and Windowed mode

✅ Reinstall the Game
Reinstalling now.
EDIT: Full reinstall of the game fixed whatever the issue was.

Looks like a fresh install of the game fixed something.