His problems legit here is his log:
https://cdn.discordapp.com/attachments/338002217170632704/569685313493008397/unknown.png
English
-
Same here, same place, same issue with exactly same error, this is from dxdiag log P1: destiny2.exe P2: 6690.0.0.0 P3: 5c92e671 P4: destiny2.exe P5: 6690.0.0.0 P6: 5c92e671 P7: c0000005 P8: 0000000001292421 P9: P10:
-
Yea it may be Bungie problem if i had to guess. As I did have DUCKLZZZ perform a clean installation, made sure all drivers were up to date, had him roll back drivers, and CPU integrity tested. It could have have to do with the Revelry as BNGHelp6 said in his response. But then that would be on Bungie's side.
-
What do you mean logs
-
Edited by Kiro - 13: 4/21/2019 11:59:18 PMSo I am guessing your useing windows 10. in the bottom left hand corner of the screen adjacent to the windows start button you should have a white bar that says "Type here to search". type "event viewer" into this. a windows program called Event Viewer should pop up. left click it. this will show errors your system has encountered during the hardware's life or how long the logs go back. It will likely look like a mess to you and asking you to find the exact log when the system crashed and the log for when the game froze would be unreasonable in this case, since you seem to be a novice. not that its a bad thing just I know the average users limit. So instead i would like you to open this "event viewer" and attempt to get the game to crash, if it also freezes your computer that is fine as well. when either or occur open the event viewer(or tab to it if the system did not freeze) and find the error log with the latest time stamp. take a screen shot. save said screen shot. Also edit out any personal information that may be on the screen shot as a rule of thumb.
-
https://cdn.discordapp.com/attachments/338002217170632704/569685313493008397/unknown.png
-
Does that work?
-
Alright let me do that