Halo Master Chief Collection, Halo Reach Crashes after turning V-Sync Off
Hi.
I started having lag out of nowhere and decided to try turning off V-Sync for a minute to see if it helps. The game crashed instantly and even after turning it back on, it keeps crashing with similar logs. What gives? Stuck temp file or something? It has been rock solid through every other Halo campaign until I tried turning V-Sync Off.
AMD Ryzen 5800X3D 32G AMD 9070XT
Proton-GE 10-32
Launch Options used globally in User_Settings.py:
#Disable eventfd-based in-process synchronization primitives
"PROTON_NO_ESYNC": "1",
#Disable futex-based in-process synchronization primitives
"PROTON_NO_FSYNC": "1",
#Enable NTSync
"PROTON_USE_NTSYNC": "1",
#Enable Wayland
"PROTON_ENABLE_WAYLAND": "1",
#Enable HDR
"PROTON_ENABLE_HDR": "1",
#Enable per-game shader cache
"PROTON_LOCAL_SHADER_CACHE": "1",
#Enable experimental WOW64
"PROTON_USE_WOW64": "1",
#Set primary monitor
#"WAYLANDDRV_PRIMARY_MONITOR": "DP-1",
#FSR4 Upgrade
"PROTON_FSR4_UPGRADE": "1",
#Enable MangoHUD for every game
"MANGOHUD": "1",
Setting PROTON_USE_WOW64=0 just for Halo fixes it, but it was never necessary before I tried to disable V-Sync in Halo Reach
Logs:
PID: 152956 (MAIN_THREAD)
UID: 1000 (techa)
GID: 1000 (techa)
Signal: 11 (SEGV)
Timestamp: Sun 2026-03-01 16:14:02 EET (30s ago)
Command Line: $'Z:\\mnt\\Games-1\\SteamLibrary\\steamapps\\common\\Halo The Master Chief Collection\\MCC\\Binaries\\Win64\\MCC-Win64-Shipping.exe'
Executable: /home/techa/.local/share/Steam/compatibilitytools.d/Proton-GE Latest/files/bin/wine64-preloader
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@autostart.service
Unit: user@1000.service
User Unit: app-steam@autostart.service
Slice: user-1000.slice
Owner UID: 1000 (techa)
Boot ID: REDACTED
Machine ID: REDACTED
Hostname: ph-kiara
Storage: /var/lib/systemd/coredump/core.MAIN_THREAD.1000.REDACTED.152956.1772374442000000.zst (present)
Size on Disk: 288.9M
Message: Process 152956 (MAIN_THREAD) of user 1000 dumped core.
Module /run/host/usr/lib64/libvulkan_radeon.so from rpm mesa-25.2.4-2.fc43.x86_64
Module /run/host/usr/lib64/libvulkan_lvp.so from rpm mesa-25.2.4-2.fc43.x86_64
Module /run/host/usr/lib64/libvulkan_dzn.so from rpm mesa-25.2.4-2.fc43.x86_64
Module /run/host/usr/lib64/mangohud/libMangoHud.so from rpm mangohud-0.8.2-2.fc43.x86_64
Module /run/host/usr/lib64/libsystemd.so.0.41.0 from rpm systemd-258.4-1.fc43.x86_64
Module /run/host/usr/lib64/libspdlog.so.1.15.3 from rpm spdlog-1.15.3-3.fc43.x86_64
Module /run/host/usr/lib64/libfmt.so.11.2.0 from rpm fmt-11.2.0-3.fc43.x86_64
Module /run/host/usr/lib64/libVkLayer_MESA_device_select.so from rpm mesa-25.2.4-2.fc43.x86_64
Module /run/host/usr/lib64/libdrm_amdgpu.so.1.131.0 from rpm libdrm-2.4.131-1.fc43.x86_64
Module /run/host/usr/lib64/libelf-0.194.so from rpm elfutils-0.194-1.fc43.x86_64
Module /run/host/usr/lib64/liblzma.so.5.8.1 from rpm xz-5.8.1-4.fc43.x86_64
Module /run/host/usr/lib64/libxml2.so.2.12.10 from rpm libxml2-2.12.10-5.fc43.x86_64
Module /run/host/usr/lib64/libedit.so.0.0.76 from rpm libedit-3.1-57.20251016cvs.fc43.x86_64
Module /run/host/usr/lib64/libcap.so.2.76 from rpm libcap-2.76-3.fc43.x86_64
Module /run/host/usr/lib64/libSPIRV-Tools.so from rpm spirv-tools-2026.1-2.fc43.x86_64
Module /run/host/usr/lib64/libudev.so.1.7.11 from rpm systemd-258.4-1.fc43.x86_64
Module /run/host/usr/lib64/libxshmfence.so.1.0.0 from rpm libxshmfence-1.3.2-7.fc43.x86_64
Module /run/host/usr/lib64/libxcb-shm.so.0.0.0 from rpm libxcb-1.17.0-6.fc43.x86_64
Module /run/host/usr/lib64/libxcb-randr.so.0.1.0 from rpm libxcb-1.17.0-6.fc43.x86_64
Module /run/host/usr/lib64/libxcb-sync.so.1.0.0 from rpm libxcb-1.17.0-6.fc43.x86_64
Module /run/host/usr/lib64/libxcb-xfixes.so.0.0.0 from rpm libxcb-1.17.0-6.fc43.x86_64
Module /run/host/usr/lib64/libxcb-present.so.0.0.0 from rpm libxcb-1.17.0-6.fc43.x86_64
Module /run/host/usr/lib64/libzstd.so.1.5.7 from rpm zstd-1.5.7-2.fc43.x86_64
Module /run/host/usr/lib64/libdrm.so.2.131.0 from rpm libdrm-2.4.131-1.fc43.x86_64
Module /run/host/usr/lib64/libvulkan.so.1.4.341 from rpm vulkan-loader-1.4.341.0-1.fc43.x86_64
Module /run/host/usr/lib64/libffi.so.8.2.0 from rpm libffi-3.5.2-1.fc43.x86_64
Module /run/host/usr/lib64/libwayland-client.so.0.24.0 from rpm wayland-1.24.0-1.fc43.x86_64
Module /run/host/usr/lib64/libxcb.so.1.1.0 from rpm libxcb-1.17.0-6.fc43.x86_64
Module /run/host/usr/lib64/libGLdispatch.so.0.0.0 from rpm libglvnd-1.7.0-8.fc43.x86_64
Module /run/host/usr/lib64/libXext.so.6.4.0 from rpm libXext-1.3.6-4.fc43.x86_64
Module /run/host/usr/lib64/libX11.so.6.4.0 from rpm libX11-1.8.12-1.fc43.x86_64
Module /run/host/usr/lib64/libGLX.so.0.0.0 from rpm libglvnd-1.7.0-8.fc43.x86_64
Module /run/host/usr/lib64/libGL.so.1.7.0 from rpm libglvnd-1.7.0-8.fc43.x86_64
Module /run/host/usr/lib64/libunistring.so.5.0.0 from rpm libunistring-1.1-10.fc43.x86_64
Module /run/host/usr/lib64/libXau.so.6.0.0 from rpm libXau-1.0.12-3.fc43.x86_64
Module /run/host/usr/lib64/libidn2.so.0.4.0 from rpm libidn2-2.3.8-2.fc43.x86_64
Module /run/host/usr/lib64/libxcb-dri3.so.0.1.0 from rpm libxcb-1.17.0-6.fc43.x86_64
Module /run/host/usr/lib64/libX11-xcb.so.1.0.0 from rpm libX11-1.8.12-1.fc43.x86_64
Module /run/host/usr/lib64/libexpat.so.1.11.1 from rpm expat-2.7.3-1.fc43.x86_64
Module /run/host/usr/lib64/libz.so.1.3.1.zlib-ng from rpm zlib-ng-2.3.3-1.fc43.x86_64
Stack trace of thread 152958:
#0 0x00007f13da188c20 save_context (/home/techa/.local/share/Steam/compatibilitytools.d/Proton-GE Latest/files/lib/wine/x86_64-unix/ntdll.so + 0x4ac20)
#1 0x00007f13da18aaa4 segv_handler (/home/techa/.local/share/Steam/compatibilitytools.d/Proton-GE Latest/files/lib/wine/x86_64-unix/ntdll.so + 0x4caa4)
#2 0x00007f13da273290 __restore_rt (/run/host/usr/lib64/libc.so.6 + 0x1a290)
#3 0x00007f13da39fe01 __memmove_avx_unaligned (/run/host/usr/lib64/libc.so.6 + 0x146e01)
#4 0x00007f13d961dea7 n/a (/memfd:1289a019-64ac-6bbb-2ea5-c778a2 (deleted) + 0x1dea7)
ELF object binary architecture: AMD x86-64
At this point I just want to know what is wrong and if it can be fixed by deleting whatever change in the prefix is causing issues all of a sudden
Posted Mar 1, 2026, 2:32 PM UTC
20