Store Page
Destiny 2
All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

Destiny 2

Store Page
View Stats:
Global Achievements
Destiny 2 > General Discussions > Topic Details
Yakumo Feb 13 @ 8:45pm
After all these years these two bugs really bug me
After all these years these two bugs really bug me

- On every system I've had, and from many posts I've seen for many others, the game will always lock up after 3 or 4 hours play.

- You can play entire PVP matches with lots of players rendered correctly but the moment the score screen comes up suddenly it can't render any of the players. (I really dislike that you have to hover just to get their names as well, it makes the very limited time you have to give awards even worse).

Oh, three actually, trailing clothes stretching hugely out of bounds, I wish the developers would constrain the physics better, or perhaps it's one of the bugs contributing to what the Windows memory leak detector is picking up when the game eventually locks up.
Last edited by Yakumo; Feb 14 @ 8:17am
< >
Showing 1-2 of 2 comments
Harty Shaw Feb 14 @ 2:09am 
sorry guy, it seems hardware and maybe heat problem, i never had these issues, but u didnt post any info on your computer so nobody can help.
#1
Yakumo Feb 14 @ 8:15am 
I didn't post this as a new issue, I posted this as these are the issues that have bugged me the most for seven years.
It's done this on every system I've ever had, through every motherboard, CPU, RAM, GPU upgrade and clean OS install, there is no overheat or other issue. Currently 13900k that's been thoroughly checked for signs of the Intel voltage problem and a 4090 that has seen hundreds of hours in newer more demanding games without issue.

I've seen several forum posts with the same complaints over the years such as https://www.reddit.com/r/DestinyTechSupport/comments/7c6b9x/destiny_2_pc_freeze_and_crash_without_error/ from seven years ago.

It doesn't give an error code, it doesn't usually leave any Windows Event log trace except very occasionally it will show that it triggered Windows memory leak detection. This below log is from my system, but the thread from years ago had the same RADAR_PRE_LEAK_64 -

Fault bucket 1207550635281449465, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: destiny2.exe
P2: 34168.0.0.0
P3: 10.0.26100.2.0.0
Last edited by Yakumo; Feb 14 @ 9:46am
#2
< >
Showing 1-2 of 2 comments
Per page: 1530 50

Destiny 2 > General Discussions > Topic Details
Date Posted: Feb 13 @ 8:45pm
Posts: 2

Discussions Rules and Guidelines