Capturing a full crash dump from FXServer

What you see

• The server process exits with no useful log output
• Crashes repeat with no clear resource named

What usually causes it

• A native-level crash that leaves nothing in the console

Worth checking first

• Check the server console and log for the last lines before the exit
• Establish whether it correlates with a specific resource or deploy

Safe steps, one at a time

• Staff only, Windows servers only — Cfx.re states this method is not supported on Linux
• Cfx.re's documented sequence: procdump64.exe -accepteula -i to register, procdump64.exe -accepteula -e -h -mp <pid> against the FXServer.exe PID, and procdump64.exe -accepteula -u to unregister afterwards
• A dump contains whatever was in server memory at the time. Treat it as sensitive: it can contain tokens and player data. Never attach one to a public ticket

When to stop and ask staff

Server-side. Involve a developer before capturing dumps on the live server.