How to See the Project Zomboid Error Log
B41/B42 common
Find console.txt and the multiplayer server logs, then capture the useful lines without sharing private paths or unrelated log noise.
Read this guideStart with the symptom you can see, save the current log, and use the matching guide before changing files.
B41/B42 common
Find console.txt and the multiplayer server logs, then capture the useful lines without sharing private paths or unrelated log noise.
Read this guideB42 current
Separate startup black screens from loading and multiplayer black screens, then test display settings, overlays, files, and logs safely.
Read this guideB41/B42 common
Find console.txt and the multiplayer server logs, then capture the useful lines without sharing private paths or unrelated log noise.
Read this guideB42 current
Separate startup black screens from loading and multiplayer black screens, then test display settings, overlays, files, and logs safely.
Read this guideB42 current
Use the first Build 42 stack trace to separate mod, file, server-setting, and memory problems before applying a targeted fix.
Read this guideB41/B42 common
The red Project Zomboid error number is a counter, not a fixed error code. Use its timing and console.txt to find the actual cause.
Read this guideB41/B42 common
Diagnose startup, save-load, in-game, and hosting crashes separately with console.txt, logs.zip, crash files, vanilla tests, and safe fixes.
Read this guideB41/B42 common
Diagnose Play-button resets, immediate exits, console errors, and inaccessible folders before using destructive reinstall or user-folder fixes.
Read this guideB41/B42 common
A log-first guide to the Project Zomboid “unexpected error occurred” message, with safe checks for vanilla, modded, and Build 42 games.
Read this guideConfirm whether you are using Build 41 or Build 42 before following version-specific paths, menus, or server settings.