I have been encountering this error since the 28th of march, simply came out of the blue.
I would also like to mention that all other apps and games are stable on my PC and I had never encountered these kinds of problems, everything else works but Destiny 2.
After doing a little bit of research online I have done the following only to get the error as soon as I have started the game, did not even get a chance to press enter and it happened
-Removed all files except the folder named Packages and then verified the integrity of game files in steam
-Updated firmware on the SSD also checked and everything else is up to date
-Uninstalled the game, Steam, placed them in another folder other than Program Files(x86) after reinstall
-Changed the language from English to German and even French
-Changed the game priority while it has started to above normal
-Deleted the steam_appid.txt and some other fellow pointed out even the sku_config.txt
-Disabled Windows Game Bar
-Disabled the Full screen optimization
-Enabled running the game as Admin
In the crash report I have found the following:
[i]session_id:
Mon_03302020_170816_003700@x64@76561198323600922@ED_CD_47_75_F9_C9_E76E
halt:
RELEASE_VHALT
halt information:
resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80BC2879 (0x01e1 2169) from package {{w64_sandbox_01e1_3.pkg}} with error 'error riddle failure, {{!0x00000000!}}' install type {{!5!}}[/i]
Please if anyone has any other ideas, even you Bungie, on how to fix this post down here in this topic.
[b]Edit#1:[/b] In the meantime I have made a rollback on the graphics drivers and it seemed to be fine for a while, until I tried to go to The Tower, it kicked me out at first, do not recall the error and then when I tried again it crashed and told me to check files...
the new reason for failure is below, from what I reckon for some reason the game has trouble reading those packages, also after checking files it did the same when i clicked to load in the character.
[i]resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80C3E387 (0x021f 903) from package {{w64_environments_021f_0.pkg}} with error 'error riddle failure, {{!0x00000000!}}' install type {{!5!}}[/i]
[b]Edit#2:[/b] I have tried the following but to no avail still got the same game crashing error, it can read something in those package files...
-updated the graphics drivers back to the latest version
-ran steam.exe as admin although they recommend against it, though to give it a go.
[i]Tue_03312020_093139_018892@x64@76561198323600922@ED_CD_47_75_F9_C9_E76E
halt:
RELEASE_VHALT
halt information:
resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80BAAFEE (0x01d5 4078) from package {{w64_sandbox_01d5_2.pkg}} with error 'error riddle failure, {{!0x00000000!}}' install type {{!5!}}[/i]
[b]Edit#3:[/b] after updating to the latest graphic drivers the most time that the game worked was a round of iron banner and a trip to the Spider. Who is at fault here Nvidia for releasing new drivers or Bungie for not working with Nvidia?
EDIT#4: I have finally sort of solved the problem! Used a wonderful tool called memtest86 and after a rather simple process of elimination I have found that one of my ram dimms was pretty busted, it gave no less than 563 errors in the first 5 min of the test, after taking the messed up dimm out no more crashes. All that is left to do is wait for the replacement to arrive to get back at peak performance.
-
Anyone still checking this thread? I started having this problem 2 days ago out of the blue, and none of the provided fixes are working for me. I've even ran a check on my DIMMs and no errors were generated. Not sure what else to do. Any help is greatly appreciated.
-
1 ReplyEdited by ptzl.: 3/30/2020 3:38:54 PMHaving the same exact problems as well...out of 20-30 times it just barely worked at the lowest graphics once. This didn't happen during my first month playing the Season of Dawn. Did the same methods and still not working. Just found out to delete the steam_api64.dll also didn't work.
-
i dont have this problem i9 9900k 1080ti 32gb 3400mhz 970 pro nvme m.2 512gb 860 nvme m.2 500gb 2tb seagate barracuda 1tb seagate barracuda
-
1 ReplyEdited by MagmaDawg: 3/31/2020 8:11:27 PMHey! This saves me a ton of time whenever I get an issue: 1. Remove the file in your crash folder named "w64_*******.pkg" (I have had plenty of these errors). If you have several folders, remove each file mentioned in the crash.txt files. 2. Run a verify files integrity in Steam. 3. Once done, copy the refreshed/verified packages folder to another location. 4. Next time there's an issue like this, just remove the file again (mentioned in the crash.txt file in the crash folder), but just copy it from the backup packages folder, and paste it into the packages folder in your Destiny 2 installation location. 5. Restart game. Basically, no need to verify the installation of D2 every time it happens, and I have never crashed in the same location again. I believe these errors are RAM related, but the file mentioned in the crash folder just tells you which file was currently loaded/trying to load as the memory issue occurred. For some reason, if that particular file isn't dealt with, it is possible the game will crash again and give you another error of the same w64_****.pkg file. This used to be worse for me during the Blizzard app days, but Steam has been more stable for me. - Also, you might want to look into virtual memory issues; if any. - Look into "XMP" settings for your RAM as well; in your BIOS. At least this should save you time, and not force you to do a verify integrity each time. Also; you should remove running the game as admin. I have, and have had less issues, but unsure if this even affected the game at all, and stability.
-
8 RepliesEdited by Spaceman: 3/31/2020 5:25:34 PMDo this. Hold your windows key and push R type in the box 'dxdiag.exe' Save the text file and either upload it to google drive and share a link, or copy and paste the content to a text dump site like pastebin, and link that. Once you've shared that, while you wait for me to review the information, you should run a scan and repair on your drive. There are two ways to do this, the easiest is to open your file explorer, go to 'My PC' or 'This PC', right click the drive your game is installed on, and go to properties. Go to the tools tab, and select the option to check drive integrity. You'll have to close everything that's running on the drive, or just set it up to scan on your next restart, and do a restart.
-
2 RepliesI also have the same problem . And trust me i tryed EVERITHING - also changing components in my pc (changed all the ram , new gpu , new ssd) beside buying a windows 10 pro . I'm having this error since they moved the game on steam . Was so perfect on blizzard . The only option so solve it for ONLY FEW HOURS is to delete the destiny2.exe than press verify files . Was so shi**y when the game was on hdd now on ssd check files is like 4-5 minutes . The F problem is i got those error's in most inportant things --- pvp or raids ! My components are : Processor : i7-4790k 4 ghz Memory : 24 gb ddr3 1600 freq GPU : GTX 1070 SSD - kingston SV300S37A 240 gb HDD - samsung HD204UI HDD - WDC WD2003FZEX-00Z4S