Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallBlood Moon lag is usually an entity-load problem on the server’s main thread, not a mysterious internet failure. Start by measuring per-core CPU load, memory, disk latency, network round-trip time and logs on an ordinary night and during horde night. Then tune BloodMoonEnemyCount and the multiplayer cap MaxSpawnedZombies one at a time, lower ServerMaxAllowedViewDistance when many players or crossplay are involved, and audit heavy mods. Hardware upgrades help only when your measurements identify the matching bottleneck.
Playing with friends? Godlike.Host runs hosted 7 Days to Die servers from 10 data-center locations, with free DDoS protection.
Why Blood Moon causes lag and TPS drops
A Blood Moon concentrates a large number of active zombies, player actions and path-finding decisions into the same interval. In 7 Days to Die, that work is concentrated heavily on the server’s main thread. When the thread cannot finish its tick on time, the server’s tick rate falls, players see delayed zombie movement, late hit registration and rubber-banding, and the console or log may show repeated timing warnings.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe important distinction is that a Blood Moon-only problem is usually different from a connection problem. The 7 Days To Die Wiki performance guide maps “stutter only on blood moon or horde night” to spawn counts and party size hitting the main thread at once. A server that is smooth on ordinary nights but falls behind when the horde arrives should therefore be tuned at the entity and simulation level before you buy faster internet or more memory.
BloodMoonEnemyCount controls how many zombies can be alive simultaneously per player during a Blood Moon. In multiplayer, MaxSpawnedZombies can override that number with a map-wide cap. The official 7 Days to Die Wiki describes the latter as covering the entire map and warns that changing it has a huge performance impact. Because both settings directly alter entity work, small changes followed by a complete test night are safer than copying a value recommended for a different party size.
#1 Best Overall
- MEET THE NEXT GEN: Consider this a cheat code; Our Samsung 990 PRO Gen4 SSD helps you reach near max performance with lightning-fast speeds; Whether you’re a hardcore gamer or a tech guru, you’ll get power efficiency built for the final boss
- REACH THE NEXT LEVEL: Gen4 steps up with faster transfer speeds and high-performance bandwidth; With a more than 55% improvement in random performance compared to 980 PRO, it’s here for heavy computing and faster loading
- THE FASTEST SSD FROM THE WORLD'S FLASH MEMORY BRAND: The speed you need for any occasion; With read and write speeds up to 7450/6900 MB/s you’ll reach near max performance of PCIe 4.0 powering through for any use
- PLAY WITHOUT LIMITS: Give yourself some space with storage capacities from 1TB to 4TB; Sync all your saves and reign supreme in gaming, video editing, data analysis and more
- IT’S A POWER MOVE: Save the power for your performance; Get power efficiency all while experiencing up to 50% improved performance per watt over the 980 PRO; It makes every move more effective with less consumption
Identify the symptom before changing settings
Use the symptom that occurs first to choose your investigation. Several bottlenecks can look like “lag,” but they require different fixes.
Stutter starts only when the Blood Moon begins
Suspect BloodMoonEnemyCount, MaxSpawnedZombies, party size and scripts that run on each entity. This pattern is the strongest indication of a main-thread ceiling. Lower spawn pressure first, then retest with the same number of players and a similar base layout.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The whole server slows as players join
Several players add simulation, visibility and network work. A single-thread CPU ceiling or a shared virtual CPU can become the limiting factor before total CPU utilization looks high. Check per-core load rather than relying on the average percentage shown by a control panel.
Lag spikes arrive every few minutes
Inspect world-save writes and the latency of the directory that stores the save. Periodic disk stalls can pause the server even when the CPU is not saturated. Compare the timing of the spikes with save messages in the server log.
Players rubber-band or desynchronize
Measure network round-trip time, upload capacity and packet loss on the path between players and the server. Network symptoms can coexist with a CPU problem, but a clean CPU profile and rising latency point away from spawn counts.
Only one player has low frame rate
If other players remain smooth and the server metrics are normal, treat this as a client graphics issue. Changing server zombie limits will not repair a single client’s rendering performance.
Rank #2
- Ideal for high speed, low power storage
- Gen 4x4 NVMe PCle performance
- Up to 6,000MB/s read, 4,000MB/s write
- Includes Acronis cloning software
- 5-year limited warranty
Performance worsens during a long session
Check host temperatures, clock speeds and background processes for thermal throttling or resource contention. A server can pass a short test and still slow later if sustained load reduces CPU frequency.
Build a baseline on a normal night and a Blood Moon
Do not tune by feel alone. Record the same measurements before and during a horde night so every change has a reference point.
- Keep the scenario consistent. Record the number of connected players, the game day, the base location and whether major mods or prefab areas are loaded. Party size directly affects the number of active enemies and the amount of main-thread work.
- Capture CPU data. Record total utilization and, more importantly, utilization for each core or hardware thread. Note the peak during the first spawn wave and the worst sustained value. A single busy core with unused capacity elsewhere is consistent with a main-thread limit.
- Record memory use. Note allocated and free RAM during ordinary play and during the Blood Moon. Also record whether the operating system starts paging. Memory capacity does not solve a CPU-bound tick, but insufficient memory can add disk activity and make every stall worse.
- Measure storage latency. Watch read and write latency for the save directory while the server is running. Mark the timestamp of each noticeable spike and compare it with world-save entries in the server log.
- Measure the network path. Record round-trip time, upload throughput and any packet loss from representative players. For crossplay, check the busiest expected party rather than testing with one local player.
- Save the log. Keep the normal-night and Blood-Moon sections of the server log, including timestamps. These records let you tell a spawn surge from a save pause or a connection event.
Take at least one complete Blood Moon as your baseline. A setting that appears smooth during a short evening can still fail when all waves and players are active.
Understand the two spawn controls
BloodMoonEnemyCount: per-player Blood Moon population
This setting specifies the number of zombies alive simultaneously per player during a Blood Moon. More players therefore increase the potential entity count even when the setting itself is unchanged. Lowering it reduces the amount of enemy simulation and the number of entities that can demand path-finding, targeting and hit processing at the same time.
The official cross-platform help extract lists a range of 4 to 64 for BloodMoonEnemyCount on cross-platform dedicated servers. The exact allowed range and label can change with the game version or platform, so verify the current server documentation before entering a value. The Alpha 20.5 b2 configuration extract lists a default of 8; that is a version-specific reference point, not a universal recommendation.
MaxSpawnedZombies: map-wide multiplayer cap
MaxSpawnedZombies limits the total number of zombies alive across the entire map. In multiplayer it can override the per-player Blood Moon count, so a low cap may prevent the number implied by BloodMoonEnemyCount, while a high cap can allow a much larger simultaneous workload. The Alpha 20.5 b2 configuration extract lists a default of 64.
Rank #3
- SPEED UP PROJECTS. Launch creator applications fast with uncompromising PCIe 4.0 read speeds up to 7,100MB/s,[2] (1TB and 2TB[1] models) and write speeds up to 6,700MB/s[2] (1TB[1]-4TB[1] models).
- CREATE AND STORE MORE. Make more room for your 4K videos and high-resolution images with capacities from 500GB[1] up to 4TB[1] on M.2 2280 built with our trusted 8th generation SANDISK BiCS QLC 3D CBA NAND.
- IT GOES WHERE YOU GO. With an all-new power efficient design, your drive delivers high performance with low power, giving you more time to be productive while on the go.
- UNCOMPROMISED RELIABILITY. With up to 1,200 TBW[3] (4TB[1] model) endurance rating, your drive is designed for creators.
- KEEP YOUR DRIVE UPDATED. Monitor your SSD’s performance and check for updates with the downloadable SANDISK Dashboard application.[5]
The official Wiki’s description is explicit: “This setting covers the entire map. There can only be this many zombies on the entire map at one time. Changing this setting has a huge impact on performance.” Treat the cap as a high-impact control. Do not raise it to compensate for a quiet Blood Moon unless your measurements show that the server has substantial headroom and the intended gameplay requires more simultaneous enemies.
A controlled tuning procedure
Change one variable at a time, keep a backup of the configuration and use the next comparable Blood Moon as the test. If you change two limits together, you cannot tell which one solved the drop or caused a new one.
- Back up the configuration. Stop the dedicated server, copy the current
serverconfig.xmlto a dated backup and note the game version and platform. A backup gives you a known rollback point if the server fails to start or the gameplay change is unacceptable. - Check the effective multiplayer cap. Confirm the current
MaxSpawnedZombiesvalue before adjustingBloodMoonEnemyCount. If the cap is already below the per-player total for your party, changing the per-player value may have no practical effect until the cap is changed. - Lower
BloodMoonEnemyCountin a small step. Choose a modest reduction within the range accepted by your current version. Keep the party size, base and mods as constant as possible. Apply the edit, restart the server and record the new value. - Observe the next Blood Moon. Compare peak per-core load, tick behavior, log timing and player reports with your baseline. Also note the gameplay effect: fewer simultaneous enemies can make horde night less difficult, so discuss the trade-off with the group.
- Reduce
MaxSpawnedZombiesonly if needed. If the server still drops ticks, lower the map-wide cap gradually and repeat the test. Because this cap affects the whole map, it can change ordinary roaming-zombie density as well as Blood Moon behavior. - Stop when the evidence supports the result. Keep the lowest change that delivers stable ticks without removing more challenge than your group wants. If a reduction produces little improvement while CPU remains saturated, investigate mods, view distance or host hardware instead of continuing to cut spawns.
There is no single best value for every party. A setting that works for a solo player can overload a larger group because the per-player count and the number of active players multiply the entity workload.
Lower view distance when visibility multiplies the workload
ServerMaxAllowedViewDistance controls the maximum server-side view distance allowed to clients. The server reference classifies view distance as high impact for memory and performance. On a crowded or crossplay server, lowering it can reduce the amount of world and entity state that must be maintained for many players at once.
Use view distance after you have checked the spawn controls, or when your baseline shows memory pressure and broad simulation work rather than a single Blood Moon spike. Apply a conservative reduction, restart and compare the same metrics. The trade-off is visual range: players may see less distant terrain and activity, so agree on the change before applying it to a shared world.
Mods and prefabs can outweigh small setting tweaks
Audit every mod and large prefab pack when vanilla settings do not explain the drop. A heavy script that runs frequently or adds many active entities can consume more main-thread time than several small configuration changes combined. The 7 Days To Die Wiki performance guide recommends removing the worst heavy-script offender rather than chasing a collection of minor tweaks.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- HUGE SPEED BOOST: Get random read/write speeds that are 40%/55% faster than 980 PRO; Experience up to 1400K/1550K IOPS, while sequential read/write speeds up to 7,450/6,900 MB/s reach near the max performance of PCIe 4.0*
- BREAKTHROUGH POWER EFFICIENCY: Use less power and get more performance; Enjoy up to 50% improved performance per watt over 980 PRO, plus optimal power efficiency with max PCIe 4.0 performance**
- SMART THERMAL CONTROL: Samsung's own nickel-coated controller delivers effective thermal control; With its slim size, 990 PRO is a perfect fit for desktops and laptops that meet the PCI-SIG D8 standard***
- THE CHAMPION MAKER: Up to 65% improvement in random performance enables faster loads for an ultimate gaming experience on PS5 and DirectStorage PC games****
- SAMSUNG MAGICIAN SOFTWARE: Get the most out of your SSD with Samsung Magician's advanced yet intuitive optimization tools; Monitor drive health, protect valuable data, and receive important updates for your 990 PRO
A practical mod audit
- Record the active mod list and the order in which the server loads it.
- Disable one suspect mod or prefab pack in a test copy of the world, not the live save, and repeat the same Blood Moon scenario.
- Compare the log, per-core CPU peak and tick behavior with the baseline.
- Restore compatible mods one at a time if the test identifies a clear offender, and keep the offending package disabled or replace it with a lighter alternative.
Do not remove a mod from a valuable live world without a backup. Some packages add blocks or entities that the save expects; a controlled test copy protects the original world while you isolate the script or prefab responsible.
When hardware is the limiting factor
CPU: prioritize single-core performance
The performance guide prioritizes strong single-core performance because 7 Days to Die still leans heavily on one main thread. A host with many slower cores can show low total utilization while one core is saturated. Look for that pattern in your baseline before moving to a higher-core but lower-clock option.
Plan for 20–30% CPU headroom during horde nights and large crossplay parties. This is a planning target from the performance guide, not a guaranteed tick-rate threshold. Leave that margin for spawn surges, player building activity, saves and background work rather than sizing the machine to the average load on a quiet night.
RAM: capacity depends on workload
The guide recommends 16–24 GB of RAM for modded servers and 32 GB for large crossplay servers. These figures describe workload categories, not a promise that every world needs the upper number. Check actual allocation and paging first. Adding RAM will not fix a saturated main thread when memory is already sufficient.
Storage: use fast NVMe for the save directory
Fast NVMe SSD storage is recommended for the save directory because world-save writes and loading benefit from low latency. Storage is the appropriate upgrade when your timeline shows recurring save-related stalls or high disk latency. It will not cure a CPU-bound Blood Moon spike; entity work remains on the main thread even after the save is moved to faster media.
Network: size upload for crossplay
The performance guide specifies a minimum of 10 Mbps upload per eight players for crossplay. Treat that as a minimum planning figure for the stated party size, not a guarantee of smooth play under every workload. Measure actual upstream capacity and latency at the server location, and leave margin for other traffic.
Best Value
- This product has been replaced by our latest generation. Please search for the SANDISK Optimus GX 7100 NVMe SSD
- HIGH-OCTANE GAMING. Experience speeds up to 7,250MB/s read and 6,900MB/s write (1-2TB models), with up to 35% faster performance than previous generation.
- PURPOSE-BUILT. Designed for serious on-the-go gamers, with a PCIe Gen4 interface and SANDISK’s next generation TLC 3D NAND.
- MORE TIME TO CLEAR THAT CHECKPOINT. Built with laptops and handheld gaming devices in mind, with up to 100% more power efficiency over the previous generation.
- DO MORE WITH DASHBOARD. Ensure your drive is optimized for prime performance with the downloadable WD_BLACK Dashboard (Windows only).
Crossplay and version limits to verify
The official cross-platform help extract lists ServerMaxPlayerCount up to 8 and BloodMoonEnemyCount from 4 to 64 for cross-platform dedicated servers. These limits and labels are version-sensitive. Before copying a value, confirm the current game build, dedicated-server platform and whether the setting is exposed by your host panel or only in serverconfig.xml.
The default values cited here—8 for BloodMoonEnemyCount and 64 for MaxSpawnedZombies—come from an Alpha 20.5 b2 configuration extract. Do not assume those defaults remain unchanged in a later release. Record the version beside every baseline and configuration backup so a future update does not make an old comparison misleading.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Choose the fix that matches the bottleneck
| Fix | Immediate workload effect | Gameplay effect | Primary bottleneck addressed | Scaling value |
|---|---|---|---|---|
Lower BloodMoonEnemyCount |
Fewer Blood Moon zombies per player | Reduces horde pressure | Main-thread entity work | Useful when party size drives the spike |
Lower MaxSpawnedZombies |
Lowers the map-wide simultaneous zombie cap | Can reduce Blood Moon and roaming density | Main-thread entity work across the map | Controls total population as player count grows |
Lower ServerMaxAllowedViewDistance |
Reduces server-side visibility workload and memory pressure | Shortens distant visibility | Memory and broad simulation work | Especially relevant to crowded or crossplay servers |
| Remove a heavy mod or prefab pack | Eliminates its recurring script or entity work | Removes that content or behavior | Main thread and entity scripts | Often stronger than many small tweaks |
| Move saves to NVMe SSD | Reduces save-directory I/O latency | No direct difficulty change | Disk stalls during world saves | Helps recurring I/O spikes, not CPU-bound hordes |
| Upgrade single-core CPU | Adds main-thread capacity | No direct gameplay change | Persistent CPU ceiling | Leaves more room for larger parties |
| Add RAM | Reduces memory pressure when capacity is insufficient | No direct gameplay change | Paging and memory exhaustion | 16–24 GB suits modded workloads; 32 GB suits large crossplay workloads |
| Increase upload capacity | Provides more network headroom | No direct difficulty change | Bandwidth and connection latency | Crossplay planning starts at 10 Mbps per eight players |
Common mistakes and recovery steps
Changing several settings at once
Restore the backup, select one variable and repeat the test. Without a single-variable change, an improvement cannot be attributed confidently and a gameplay compromise may be larger than necessary.
Raising the cap because zombies disappear
First determine whether the cap is intentionally protecting the server. Raising MaxSpawnedZombies increases map-wide entity work and can turn a stable horde into a main-thread collapse. If the server already drops ticks, raising the cap is the wrong recovery action.
Using total CPU percentage only
Inspect per-core load. A main-thread ceiling can hide behind a moderate total percentage on a multi-core host.
Buying RAM for a CPU problem
Check paging and memory use first. If one core is pegged while memory remains available, prioritize spawn tuning or stronger single-core performance instead.
Recommended Free Tools
Blaming the network for a save pause
Align timestamps from player reports, network measurements, disk latency and the server log. A spike that coincides with a world-save write is a storage investigation, even if players describe it as rubber-banding.
Testing with a different party size
Repeat the test with the same or deliberately documented number of players. Because BloodMoonEnemyCount is per player, changing party size changes the workload and invalidates a direct comparison.
A repeatable maintenance checklist
- Record game version, platform, party size and active mods.
- Measure CPU per core, total RAM, disk latency, network RTT, upload and packet loss.
- Keep separate normal-night and Blood-Moon log excerpts.
- Confirm effective
BloodMoonEnemyCountandMaxSpawnedZombiesvalues. - Change one setting, back up the file and restart before the next controlled test.
- Check
ServerMaxAllowedViewDistancewhen memory or crowded crossplay visibility is the issue. - Audit heavy scripts and prefab packs before making many small tweaks.
- Retest after game updates because ranges and defaults can change.
- Keep 20–30% CPU headroom for horde nights and large crossplay parties.
- Match hardware to evidence: single-core CPU for main-thread limits, NVMe for save I/O, RAM for paging, and upload capacity for network saturation.
Bottom line
Start with measurement, not hardware shopping. Blood Moon stutter most often comes from too many simultaneous entities and too little main-thread capacity. Tune BloodMoonEnemyCount, verify and then adjust MaxSpawnedZombies, reduce view distance for crowded servers, and remove the heaviest mod when scripts are responsible. Use the documented 16–24 GB modded-server and 32 GB large-crossplay RAM guidance, 10 Mbps upload per eight crossplay players, and 20–30% CPU headroom as planning points, while confirming every limit against your current game version.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
