Random and unpredictable segmentation fault crashes

Game Talk The Garage
1

Running experimental build 2026-10-22-1939 on Windows 11.

The only mods are the default ones: Dark Days Ahead, Disable NPC Needs, and Portal Storms Ignore NPCs.

At any given time with no way to predict or prevent it the latest experimentals will just crash all on their own. I can’t raise this as an issue on GitHub because I’ve lost access to the e-mail I used for the account there to a two-factor authentication loop.

This is the crash.log file:

crash.log

#0
(dbghelp: debug_write_backtrace+0xbe@0,000,7FF,725,45C,D9E[cataclysm-tiles.exe+0x1,2ac,d9e]),
#1
(dbghelp: log_crash+0x1fe@0,000,7FF,725,458,91E[cataclysm-tiles.exe+0x1,2a8,91e]),
#2
(dbghelp: signal_handler+0x63@0,000,7FF,725,458,CE3[cataclysm-tiles.exe+0x1,2a8,ce3]),
#3
(dbghelp: seh_filter_exe+0x162@0,000,7FF,726,127,27E[cataclysm-tiles.exe+0x1,f77,27e]),
#4
(dbghelp: __scrt_common_main_seh'::1’::filt$0+0x16@0,000,7FF,726,435,7DA[cataclysm-tiles.exe+0x2,285,7da]),
#5
(dbghelp: _C_specific_handler+0x9f@0,000,7FF,726,0F6,787[cataclysm-tiles.exe+0x1,f46,787]),
#6
(dbghelp: _chkstk+0x9f@0,000,7FF,CB6,EC6,4AF[ntdll.dll+0x166,4af]),
#7
(dbghelp: RtlWow64GetCurrentMachine+0x655@0,000,7FF,CB6,E24,065[ntdll.dll+0xc4,065]),
#8
(dbghelp: KiUserExceptionDispatcher+0x2e@0,000,7FF,CB6,EC5,DEE[ntdll.dll+0x165,dee]),
#9
(dbghelp: boost::serialization::singleton<std::set<boost::serialization::void_cast_detail::void_caster const * __ptr64,boost::serialization::void_cast_detail::void_caster_compare,std::allocator<boost::serialization::void_cast_detail::void_caster const * __ptr64> > >::is_destroyed+0x27,101@0,000,7FF,C2F,115,AF1[amdxc64.dll+0x1,1f5,af1]),
#10
(dbghelp: AmdExtD3DCreateInterface+0x10,20b@0,000,7FF,C2D,FB2,5EB[amdxc64.dll+0x92,5eb]),
@011
(dbghelp: @0,000,7FF,C62,618,97A[D3D12Core.dll+0x18,97a]),
#12
(dbghelp: D3D12_INTERNAL_BindGraphicsResources+0x5f1@0,000,7FF,724,6A7,2F1[cataclysm-tiles.exe+0x4f7,2f1]),
#13
(dbghelp: D3D12_DrawPrimitives+0x24@0,000,7FF,724,6A5,0A4[cataclysm-tiles.exe+0x4f5,0a4]),
#14
(dbghelp: SDL_DrawGPUPrimitives_REAL+0xd7@0,000,7FF,724,604,567[cataclysm-tiles.exe+0x454,567]),
#15
(dbghelp: Draw+0x523@0,000,7FF,724,6E6,953[cataclysm-tiles.exe+0x536,953]),
#16
(dbghelp: GPU_RunCommandQueue+0x3c1@0,000,7FF,724,6E7,F51[cataclysm-tiles.exe+0x537,f51]),
#17
(dbghelp: FlushRenderCommands+0x31@0,000,7FF,724,61A,BB1[cataclysm-tiles.exe+0x46a,bb1]),
#18
(dbghelp: SDL_SetRenderTarget_REAL+0xe0@0,000,7FF,724,627,240[cataclysm-tiles.exe+0x477,240]),
#19
(dbghelp: permanent_render_target_bind+0xaf@0,000,7FF,724,917,8BF[cataclysm-tiles.exe+0x767,8bf]),
#20
(dbghelp: display_buffer_draw_scope::~display_buffer_draw_scope+0x4e@0,000,7FF,724,7CE,E4E[cataclysm-tiles.exe+0x61e,e4e]),
#21
(dbghelp: ui_adaptor::redraw_invalidated+0x6a2@0,000,7FF,724,86F,632[cataclysm-tiles.exe+0x6bf,632]),
#22
(dbghelp: game::do_turn+0xa35@0,000,7FF,725,50B,465[cataclysm-tiles.exe+0x1,35b,465]),
#23
(dbghelp: `anonymous namespace’::run_game_loop+0xdc@0,000,7FF,724,5D7,E2C[cataclysm-tiles.exe+0x427,e2c]),
#24
(dbghelp: WinMain+0x4f1@0,000,7FF,724,5D8,A11[cataclysm-tiles.exe+0x428,a11]),
#25
(dbghelp: __scrt_common_main_seh+0x106@0,000,7FF,726,0F4,242[cataclysm-tiles.exe+0x1,f44,242]),
#26
(dbghelp: BaseThreadInitThunk+0x17@0,000,7FF,CB6,3CD,DA7[KERNEL32.DLL+0x2d,da7]),
#27
(dbghelp: RtlUserThreadStart+0x2c@0,000,7FF,CB6,DDE,E4C[ntdll.dll+0x7e,e4c]),

It’s pretty hard to make it do this on command. I did some testing and found that it occurs most consistently when spawning at a golf course and walking away from it, but it’s happened everywhere and it’s making the latest experimentals completely unplayable. Does anyone know if there’s something I can turn on or off to stop it?

2

An update in case anyone reading this is having this problem: There’s already an issue for it on GitHub

and someone in the comments has a solution: On the main menu, go to Settings and scroll to Graphics

image
image957×603 4.93 KB

As shown here, expand “Graphical Display Options” and scroll down to “GPU Backend”. This is from a fresh install of 2026-10-25-0052 and as of that version the default setting is “Automatic”. Change it to “Vulkan”, then exit, ensuring that you confirm saving settings.

After that you have to close and restart the game. Tests have confirmed this is part is required, as simply changing the setting still results in the crash. After changing it and restarting I’ve tested with a save that was repeatedly producing the crash and it stopped.

I can’t comment on the issue in GitHub, but if whoever opened it and whoever suggested the solution there is reading this: Thank you very much. I really like the changes in the experimentals versus the last Stable but it was getting hard to put up with the crashes.