Start here
01Symptom↓02Step 1: narrow down the case↓03Step 2: update server and client↓Symptom
- Fans spin up, game FPS drop, and Task Manager shows the valheim_server process using a lot of CPU even with few players connected.
Step 1: narrow down the case
- In Task Manager, compare the server's CPU load once with the game closed and once with it running.
- Check: if the load only rises while the game runs with V-Sync on the same PC, the described bug fits.
Step 2: update server and client
- In your Steam library under Tools, update the Valheim Dedicated Server application to 1.0.20 or later, and the game too. Stop the server with Ctrl+C in the console window first.
- Iron Gate notes that closing via the X can leave the server running in the background. Check Task Manager for leftover processes before restarting.
Step 3: keep your start script
- Steam resets start_headless_server.bat on updates. Iron Gate recommends editing a copy; after updating, check that name, world, port and password are still correct.
Stopgap for older builds
- If you cannot update the server immediately, temporarily disable V-Sync in the client. This is inferred from the patch note, not an official workaround.
If the load stays high
- After the update, high load can have other reasons, such as many players, large bases or mods. Test a backed-up copy of the world without mods and compare again.
Related guide
Sources and current status
Frequently asked questions
Does this affect a server on a separate machine?
According to the patch note, only when the client runs with V-Sync on the same computer.
Why is the server still running after closing it?
Iron Gate recommends stopping the server with Ctrl+C; the X can leave it running in the background.
Will the update delete my server world?
No, the world is stored in the save folder. Back it up before every update anyway.
How do I recognise the server process?
In Task Manager it is called valheim_server. The start script start_headless_server.bat launches it on the line that begins with "start valheim_server".
Did this fix help?
Your answer helps us improve these troubleshooting steps.