{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/8/2019 3:45:12 PM
27
Hello,
Thank you for your report. We have escalated this issue for investigation.
English
-
Edited by Pickles Von Brine: 8/16/2019 11:21:33 PM[b]everyone, check your motherboard support page for bios update containing agesa 1.0.0.3ABB. This has the destiny 2 fix. Also be sure to have the latest chipset driver. As a temp fix the chipset driver did fix my issue till the bios update was available. download the latest and chipset driver for your chipset from AMD directly. AMD has issued a fix to their partners and mobo manufacturers should be rolling out or have finished rolling out the bios update for your board. If the updates are not available for you the. You just have to wait. It is outside of AMD and Bungie at this point and in the hands of motherboard manufacturers. AMD provides their agesia update as a binary that the manufacturers have to integrate into their bios. [/b]
-
Here is another .dmp file for you. https://drive.google.com/file/d/1Ybd9NAy3SvbAdAUSVGX5lCDoHkdBD2FG/view?usp=sharing I am not updating the drivers just yet as I don't like some of what I have read that they do to the system, and will wait for hopefully what will be fixed via the BIOS updates (when they come out). Hope this helps.
-
Alright so apparently here's a possible fix (it fixed it for me) https://community.amd.com/community/gaming/blog/2019/07/30/community-update-5-let-s-talk-clocks-voltages-and-destiny-2
-
Edited by Sneek: 8/4/2019 8:06:07 PM
-
Edited by Boldly Going Nowhere: 7/25/2019 11:15:16 PMIt's been over 2 weeks now. Can we at the very least have a status update please?
-
BUMP Same issue here. Ryzen 3600 and B350 mother board. Game does not start.
-
Please, status update.
-
Edited by Pickles Von Brine: 7/19/2019 6:15:15 PMIssue is on AMD's side, not Bungie's. [quote]we just got told to pull (was undergoing validation prior) 1003 ABA version: "... found that PCIE speed of BXB-C downgraded from gen4 to gen2,..." so its not surprising that bugs emerge since the source has hidden bugs that only gets unraveled with thorough testing. combine that with trying to get firmwares out in a tight time frame, kinda damn if you do (release f/w quickly) and damn if you dont (dont release fw quickly) situation[/quote] Quote from an ASUS rep. All board partners are still waiting on a AEGISA update to apply to their bios. The update when released will be 1003ABA or some variant of that.
-
I am concerned that the understanding of the situation is unclear. This is not a blame game. We are not looking at where the problem is, but what the fastest path to resolution is. We know this is a hardware defect that requires an AMD CPU microcode to be addressed. However, this defect can be worked-around in software, meaning, modifying the D2 binary so that it stops using the specific hardware functionality that causes the issue. A software workaround is likely going to take some days, and is strictly under the operational control of Bungie, meaning that the problem goes away under full control of the software company. A hardware fix, regardless of what you may think, will take weeks if not months to propagate to user systems. A BIOS release requires a heavy qualification that can easily take weeks, and that is assuming that the microcode does not have secondary defects and -blam!- happens between AMD and motherboard vendors. Some vendors already commented that they will not release a new BIOS for their affected systems in at least 2 months. One path that is not being explored that could also work is a microcode release to the operating system. Both Linux and Windows have ways to apply microcode patches to the processor on runtime. Overall, if we look at the fastest path that will unblock Destiny 2 players with these systems is for Bungie to produce a software workaround, and hence why the pressure is now on Bungie. I hope that is a good enough explanation of why Bungie has to own the action here, despite not being the culprit.
-
Edited by Pickles Von Brine: 7/19/2019 6:58:48 PMThere could be a software workaround, but it really depends on how far RdRAND is incorprated into the game itself. If it is heavily ingrained, it is possible a whole re-write may be required. Something like that is definitely out of the question. Either way, it still stinks no matter how you look at it. A lot of this falls on AMD's part. During validation they used Ubuntu 18.04 instead of 19.04. The issue is present on 19.04 and newer versions of Linux kernel with Systemd. A post from a Gigabyte Rep level 2 [quote]GBT_Matthew GIGABYTE Mobo Dept 2 points · 20 hours ago Actually a few things broke on 1003aba. We reported it Monday, AMD verified and pull it shortly there after. Hence my post on Tuesday about there being no ETA. We are back to a holding pattern waiting for new code. Once we get it we will begin validating it for release.[/quote]
-
If this was a everis issue and losing money, y’all would have fixed it within 24 hrs.
-
They are losing money because a lot of people are unable to play the game entirely....
-
Yes, berating them into fixing it will surely expedite the process 😒
-
Any update?
-
Any updates today?
-
Any update?
-
There hasn't been anything from Bungie since Monday, right? I've reached out on Twitter and Reddit for any sort of status update and still nothing. Starting to get frustrating.
-
Any update?
-
And what about escalating other critical issues? Like for example the UI crashes that are 100% reproducible and have been reported here on the forums but repeatedly ignored. Where are we supposed to report issues like that if the forums aren't the place? This issue appears to get attention but crashes don't. Why? Do you not realize it is unacceptable to have policies in place penalizing players for activity quitting when that can be so easily triggered by crashes caused by simply transferring an item in the app, then exiting or entering player and/or vendor inventory while the item transfer animation is up, for example? At the very least crash bugs like that should be listed in the known issues.
-
Thank you!
-
Edited by BNGHelp1: 7/8/2019 5:56:18 PMHello, Are you able to create a crash dump for the game? When you try to log into the game and it hangs, right click on the process in Task Manager and select "create dump file." Then, paste it in a text site such as PasteBin or DumpText and share a link to it here.
-
I've sent you a dump in a message (just to let the rest of the thread know).
-
https://drive.google.com/file/d/1pOxUwwaW0-Rj-IFUtj-Dje9e417Mkm4y/view?usp=sharing Text is gibberish inside of any text editor and even windbg.exe, but I've saved it in case you guys are able to do anything with it.
-
Hey I forgot I put my old hardware back into my system. I am not using Ryzen right now.
-
I have sent Reddit to help
