Project Zomboid Keeps Crashing

Close background applications, launch once, and reproduce the crash at the same action if possible.
Save console.txt and logs.zip. If the game created an hs_err_pid file in the installation folder, keep the newest one.
Try the Alternate Launch for a startup crash so its console remains visible.
Test without mods on a new save. If the crash stops, isolate the mod set in batches.
Verify game files if a base-game resource is missing.
If the log reports out-of-memory, reduce background load and demanding settings; if it names graphics, update the relevant GPU driver and test without overlays.

Branch by crash stage

Before the menu: launch options, configuration, graphics initialization, or inaccessible folders.
Only one save: save data or a mod used by that world; protect the save before testing.
During longer play: memory, hardware/driver, or content loaded by a particular action or area.
While hosting: use the host/server log and separate server memory, ports, and mod downloads from client crashes.

The Indie Stone support: repeated crashes — Official log and memory diagnosis example.
Steam support: Project Zomboid crashes — Support discussion using console and crash evidence.
Build 42 startup-crash report — Build 42 community case with developer support guidance.