Bungie Answered
Game is constantly crashing after the 1.05 Update
Just reporting to ensure these crashing posts are being noticed. I've been playing the game since the Server Slam, not a single crash/issue until the 1.05 patch released. This seems to be heavily effecting Intel Core Ultra users. I've tried updating the Intel Management Engine and that did not resolve the issue. There are many posts on r/Marathon with Intel Core Ultra users having the same exact crashing issues after the 1.05 patch.
My System Specs
- Intel Core Ultra 7 265KF
- GSkill Royal 7200MHz DDR5 32GB
- AMD Radeon 6950 XT
2
Commentaires
Hello there,
Thank you for your report.
We have received reports of an uptick in crash incidents following the latest update to Marathon. At this time, we're investigating the underlying cause of this. In the meantime, if you haven't already tried doing so, you may wish to reinstall Marathon. This can sometimes help with crashing. The following guide contains information which may help you with this.
Hello again everyone,
The fix I came up with yesterday was:
Updating your BIOS (dont do any tuning apart xmp/expo) and Intel Management Engine.
After that I suggest also:
Go to the location where your game is installed, for me its C:\Program Files (x86)\Steam\steamapps\common\Marathon\battleye
Right click on Uninstall_BattlEye -> Run as Administrator -> uninstall it
Then
Right click on Install_BattlEye -> Run as Administrator -> install it
You can also just delete the insides of this folder and game/steam will redownload it back.
If that doesnt work then I am out of ideas and this probably needs official fix.
Just wanted to report some feedback. After updating my BIOS to the latest release the crashing issues appear to be resolved. I did also update the Intel Management Engine to the latest release as well (grabbed that from my motherboard manufacturer website), not sure if that matters. But Tommy had reported that may resolve the crashing issues as well. Thanks again to Tommy, IME update and BIOS update appears to have fixed the issue.
Vous devez vous connecter pour laisser un commentaire.