Daily Report – Persistent BattlEye Error Code PLUM After Full System Reinstall (Request for Escalation) - 16 March 2026, 09:10 UTC, PC
This is a daily follow-up report regarding a persistent BattlEye error (Error Code: PLUM), which continues to occur today.
The issue remains unchanged:
I am consistently getting kicked from the game a few seconds after loading into the tutorial, with the message:
"BattlEye has detected a problem. For more information, visit help.bungie.net and search for error code: PLUM."
---
System Configuration:
OS: Windows 11 Pro 24H2 (fresh clean installation, fully updated)
CPU: AMD Ryzen 9 9800X3D
GPU: NVIDIA RTX 4080 (Driver 595.79)
RAM: 32 GB
Country: Germany
ISP: Deutsche Telekom
Connection: Wired Ethernet
Bungie Account: Gitorian#9112
Platform: Steam / PC
---
Important clarification (to avoid generic troubleshooting overlap):
This is NOT a basic configuration issue. The following has already been fully verified and completed:
- Fresh clean installation of Windows 11 Pro 24H2 (no leftover software, fully updated)
- Latest GPU driver installed (NVIDIA 595.79)
- No third-party antivirus, security tools, overlays, debuggers, or background applications
- Windows Defender is the only active security component (tested with it disabled as well)
- BattlEye fully reinstalled using official scripts (Uninstall_BattlEye.bat / Install_BattlEye.bat)
- All BattlEye executables explicitly allowed in Windows Firewall
- System integrity verified via sfc /scannow
- No VPN, proxy, packet filtering, or network manipulation software active
---
Key observation:
- BattlEye initializes correctly
- The game launches without issues
- The error only occurs AFTER entering gameplay (not at startup)
This behavior does NOT match the scenarios described in the BattlEye FAQ (installation/startup issues).
---
Control test:
- Escape from Tarkov (also using BattlEye) runs without any issues on the same system
This strongly suggests that BattlEye itself is functioning correctly and that the issue may be specific to Marathon.
---
Context from previous reports:
Prior to this, I was consistently encountering Error Code: WEASEL (network-related).
After performing a full OS reinstall to rule out system-level causes, the issue changed to PLUM.
This indicates:
- The problem is likely NOT caused by a misconfigured or corrupted system
- The behavior changed after either the OS reinstall and/or Marathon patch 1.0.5
---
Request:
At this point, all standard troubleshooting steps have been exhausted.
I am specifically requesting:
- More detailed information about what triggers Error Code: PLUM in Marathon during runtime
- Confirmation whether there are known false positives related to recent updates (1.0.5)
- Investigation into potential game-specific BattlEye integration issues
If necessary, please escalate this case to the appropriate technical team (BattlEye integration / networking).
I am able to provide:
- Full services list (ServiWin export)
- Network diagnostics (traceroute, pathping)
- Additional logs or system information upon request
---
Summary:
The issue persists across:
- a completely clean OS environment
- minimal software conditions
- and after verifying BattlEye functionality in other games
This strongly indicates a false positive or a game-specific issue rather than a local system misconfiguration.
Thank you.
Commentaires
Hi there,
Thanks for reaching out.
If you haven't already, please try the troubleshooting steps in our Error Code: MARMOT guide as this error is also related to BattlEye services. If the error persists, BattlEye may be detecting a suspicious version.dll file in your steam folder which could be causing issues with the game. Please try deleting it and try again if so.
For more information about the PLUM error code: https://help.marathonthegame.com/hc/en-us/articles/39001779823252-Error-Code-PLUM
Bungie Support Bungie Support Bungie Support Bungie Support Bungie Support Bungie Support Bungie Support Bungie Support
Hi,
thank you for the response.
I have carefully gone through both the PLUM and MARMOT troubleshooting steps again and can confirm the following:
- The game has been fully reinstalled on a clean Windows 11 24H2 system
- Game files have been verified multiple times
- No corruption was found (chkdsk also reports a clean file system)
- BattlEye has been reinstalled using the official scripts
- There is NO version.dll present in either the Steam or Marathon directories
- No injectors, overlays, or third-party tools are installed or running
Additionally:
- BattlEye works without any issues in Escape from Tarkov on the same system
- The error only occurs AFTER entering gameplay, not during startup
This behavior does not match:
- MARMOT (file corruption)
- or typical BattlEye startup/injection issues
Given that:
- the system is completely clean
- the issue persists after full reinstall
- and only occurs in Marathon during runtime
this strongly suggests a false positive or a game-specific BattlEye integration issue rather than a local configuration problem.
At this point, I have exhausted all documented troubleshooting steps.
I would like to request that this case be escalated to the appropriate technical team (BattlEye integration / networking), as the issue appears to occur during runtime validation rather than installation or startup.
I am happy to provide additional data such as:
- service list exports
- network diagnostics
- or any logs you may require
Thank you.
Vous devez vous connecter pour laisser un commentaire.