Creating Full Dumps
This section will explain how to create useful debugging dumps (called .dmp files) in order to assist with troubleshooting. If you encounter a crash, set up your environment to capture the next time it happens.
NOTE: Creating full dumps is for Windows servers only. This method is currently not supported on Linux.
- ProcDump v9.0 or newer.
- Make sure your server is running.
- Open a command prompt where you extracted procdump to. Use an ELEVATED command prompt for this (should say “Administrator” in the title bar).
- Type in the following command:
This registers procdump as a debugger to capture certain crashes.
procdump64.exe -accepteula -i
- Open task manager, click
"Details". Locate the largest
FXServer.exe. There should be a
"PID"column. Note down the number.
- Go back to your command prompt and type in:
procdump64.exe -accepteula -e -h -mp pidhere
pidhereis the number you noted down previously. If you get an error, make sure your
- Wait for the server to crash. When it does, it will write a large .dmp file to the procdump folder.
- Compress this file (e.g.
.zip) and upload it to DropMeFiles or equivalent.
- Run the following in your command prompt to unregister the debugger when you are done:
procdump64.exe -accepteula -u
You can now analyze the dump file (using VS2019+, click ‘Debug with Native Only’ and load symbols) or supply it to whomever requested it. If you are certain you have found a bug, report it on our forum or in the Discord #server-bugs channel with as much detail as possible. Using OneSync? Please report OneSync bugs here.