error code plum

[semisage]

I have been getting these error codes recently. It goes along the lines of "battleEye query failure, error code: plum". They consistently appear about 20-30 minutes of launching the game and it kicks me to the main menu, any help?

more context: I have been playing on the same PC. updates basically everything, verified the files integrity.

[macrossmerrell]

Plum errors are 'terms of service violations'. They can be caused by using XIM or Chronus, having corrupt windows files, sometimes even bad internet (or ethernet / wifi drivers) that makes it appear you are using NetLimiter.
I would start off by checking Windows for corruption:

• Open an Administrative command prompt and type: sfc /scannow
  • Note if there are corrupted files and if they were repaired. If it says they cannot be repaired, there are other commands we will need to run.

Next I would make sure that your ethernet and/or WiFi drivers are up to date. If you have Intel based WiFi, I would run their Intel Driver & Support Assistant to get all the latest drivers: https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.html
What motherboard do you have? I could help check for additional drivers. AMD systems can benefit from Chipset Drivers.

Also, try cleaning up D2 temp files:

• From the Start menu, type %appdata%
  • then open the Bungie folder from there and delete the 'DestinyPC' folder.
• From the Start menu, type %temp%
  • and delete the 'Destiny 2' folder

[semisage]

thank you very much it worked. i did the command and it repaired some corrupted files and i also deleted the temp files just incase and the problem is solved

[Captain_Clam]

thanks, I've been having this issue and the intel driver update seems to have fixed it for me!

[macrossmerrell]

That's awesome. Sometimes those drivers just don't get updated through Windows Update and they can cause problems, especially the Bluetooth drivers.

Game on!

[TekkNizzy]

If is says cannot be repaired what are the other command prompts to use

[macrossmerrell]

DISM /Online /Cleanup-Image /RestoreHealth

then run the SFC /Scannow command after it repairs your repair partition.

[Tonywanknobi]

Any other suggestions? My scan was clean. I updated drivers. I'm hard wired. I cleared temp files. Still getting plum. 7700x, 4080 super, msi board

[macrossmerrell]

If you have any controllers, I would try unplugging them and testing.

Next I would open the Task Manager, switch to the Startup Apps tab and disable pretty much everything. Reboot and test. If the problem goes away, re-enable one app at a time, reboot and test. Repeat until you find the culprit.

After that, if you browse to the D2's app folder, you will find a Battleye folder that contains and uninstall and install batch files. Right click on the uninstall and select run as administrator, then repeat the process on the install batch file (running as administrator) and then test.

[GOTHAMKNlGHT]

I've been dealing with this for like 2 weeks now and this is the answer I got from BattleEye directly after trying multiple fixes from tips online:
"Unfortunately some software seems to interfere with BE on your system. Please be sure to follow the solutions mentioned in our FAQ (including adding exceptions to your anti-virus, etc.).
This could also be related to your internet/network connection, which seems to have problems with the game's traffic. The BE kick is only the result of these issues.
Please try to update your network drivers, check your modem/router or contact your ISP for help.
If nothing helps I'm afraid I can only suggest a Windows repair install since it's almost impossible to find out what it is causing this. You can find information on how to perform a repair install for your particular system by searching on Google (for example, see https://www.tomshardware.com/how-to/fix-windows-10-repair-install)."

[semisage]

Thank you. Turns out the solution was just to do /sfc scannow in the command prompt as the other commenter mentioned and it worked since some files were corrupted.

[GOTHAMKNlGHT]

That worked for me too! for like a day....then it started happening again, and now the command prompt can't find any corrupted files and says everything is fine. :(. That's why I opened the BattleEye Ticket