Bungie Answered
Game Crashes when I open map
Sometimes when I open to map I crash to desktop, this has happened multiple times to me and my friend causing us to lose all our items
4
Comentarios
Hi there,
Please see our Marathon Storage and System Requirements guide to ensure your system meets the current minimum specs. If it does, please try installing the game on another disk to rule out potential hardware issues.
If you meet the minimum required specs and notice any further consistency to when the crashes occur, please let us know!
Same with me and my friend haven’t lost anything yet but pretty frustrating.
I have a 1TB of free storage, a Ryzen 7 9800X3D, NVIDIA GeForce 3060 Ti, 32gb Ram, and I am on windows 10.
Since I last wrote this the same thing happened twice and happened to my friend once more again, we think it has something to do with the DCON it has only crashed when the DCON icon was on the map or when we pinged the DCON. It has only happened on Perimeter.
happening to me as well 1TB free space as its on a new SSD i7 10thgen 4080 32gb ram
Happening to me too and not a hardware issue. It has happened on Perimeter and Dire Marsh and always when I press M to open my map. The game freezes for 3-5 seconds and crashes. The map screen doesn't appear. It has happened les than 5 times since launch and did not happen at all in 48 hours of Server Slam play as far as I remember.
CPU - AMD Ryzen 9 9900X3D
Motherboard - MSI MAG X870E Tomahawk
GPU - NVIDIA RTX 5080
RAM - 64GB DDR5
Game is installed on a 2TB NVMe drive which is separate from the boot drive.
Same is happening to me as well - have tried some of the troubleshoots of even reinstalling on another drive, but still happened. Twice last night, and just had it happen again tonight.
CPU - Ryzen 9 9950X3D.
RAM - 64GB DDR5.
GPU - NVIDEA RTX 5080.
I also have 2x M.2 NVMe SSD's - both of which have had this issue.
I have also done file verification too.
I also have a friend that this bug has affected as well and their setup is much lower spec's than mine - so this to me doesn't seem like a hardware incompatibility issue.
EDIT:
No idea if it's the same for anyone else, but mine seems to only happen on Perimeter
Thanks for the added details! We're investigating a rise in similar reports on certain AMD CPUs and hope to have it resolved as soon as possible.
I have this issue every now and then on an Intel-based system. My friends have also had this issue mid run.
Specs:
Intel 13700k
32 GB RAM
2TB SSD
5080
Iniciar sesión para dejar un comentario.