{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
11/4/2017 7:05:47 AM
16
FIX FOUND for "Problem reading game content" Crashes
Hi all,
If you're getting random crashes and the workaround of setting the Destiny 2 exe's to run as admin didn't work for you (it didn't for me), I found that the following steps completely fixed my issues with the crashes that started after the 10/30 patch: (i.e, the game exits and a dialog box opens: "Problem reading game content. Please close Destiny 2, run "Scan and Repair" in Blizzards Battle.net then restart Destiny 2 to try again").
My theory is that some of the game data files are being corrupted (possibly by the patching process) and the "scan and repair" option is not correctly detecting these corrupted files for some reason. I found that manually finding the specific files causing the crashes, deleting them, and then running "scan and repair" to redownload only the bad files completely resolved the crashes for me. After the 10/30 patch I was crashing basically within 10 minutes of launching the client and after this fix I've been playing for hours without any issues.
Try this fix and see if it works for you (and share any corrupt filenames here to see if there is a common pattern):
Here are the steps:
Open this folder in windows explorer:
"%TEMP%/Destiny 2/crash_folder/pc_x64/"
(That will expand to: "C:\Users\<YOUR_USERNAME>\AppData\Local\Temp\Destiny 2\crash_folder\pc_x64")
There you will see several crash report folders for all your recent crashes. Open each folder and look for a file named "crash_info.txt". Open this file and look for the following line:
"halt information: data verification failed for package"
Right after that line there is a filename (which may be different for you), such as:
"{{w64_environments_0198_0.pkg offset 41598976 }}"
Note the filename in that line: "w64_environments_0198_0.pkg". This is the name of a corrupt file. Write it down for later.
Check every crash report folder and write down all the corrupt filenames. In my case, I had about 10 crash reports caused by the same 3 corrupt files. (in my case: "w64_environments_0198_0.pkg", "w64_sandbox_01b5_0.pkg", and "w64_sandbox_019b_0.pkg", but it may be different for you.)
Ok, so now we know the files causing the problem. Now go here:
"C:\Program Files (x86)\Destiny 2\packages\" (or wherever you installed Destiny 2)
This folder contains all of the game's data files, including the corrupt files you wrote down. Now find and delete the corrupt files from here (or backup/move them out of this folder). After all the corrupt files are removed from the folder, now run "scan and repair" in the battle.net app. (If you're having trouble finding it, launch the battle.net app, click the Destiny 2 game icon so you're on the "PLAY" button page for Destiny 2, then click the "Options V" dropdown menu, and then click "Scan and Repair". After a few minutes, it will now notice the corrupt files are missing and it will correctly detect the error and download only those files.
That's it, hopefully this fixes your crashes!
-
2019/11/10, still happening. files get corrupted, find them via the above method, delete them, verify takes 15-60 minutes to complete and repair them even if they total 2mbs out of the 85gb game, then reinstalls them (takes all of 5 seconds to reinstall them, go figure), it solves the problem, but the problem resurfaces as little as 5 minutes later, and as much as 5 weeks later, and literally any amount of time in the between
-
I just tried this and im launching the game, it worked when launching the game too coz I get that error when opening the game. Ill just check if it works in game.
-
Edited by Kyo: 10/2/2019 7:19:20 PMstack: 00007FF76E69927F <unknown> 00007FF76E69860A <unknown> 00007FF76E694302 <unknown> 00007FF76F641941 <unknown> 00007FF76E7B52A1 <unknown> 00007FF76E4331D3 <unknown> 00007FF76E433CA1 <unknown> 00007FF76FB94163 <unknown> 00007FFA47B47BD4 <unknown> 00007FFA4868CEE1 <unknown> session_id: Wed_10022019_200812_011200@x64@unknown_pc_user@E9_E2_EF_23_A0_B2_B3E8 halt: RELEASE_VHALT halt information: Invalid Steam configuration fatal error detected, current status was: there is my crash report please help all my crash erport folder are the same
-
Was this ever formally fixed?
-
This solved my problem. Other than other users, I got the error any time I tried to solve a specific quest and not erratically sometime during the game. Hey, Bungie, this is most embarrassing for you that one of your PLAYERS had to come up with this solution. It seems that this problem is far from being new and it is a shame that your support could not come up with a fix. I mean, better to be honest about the buggy repair function than having multiple players not being able to play the game. I will definitively take this into consideration when I think about buying one of your games in the future.
-
I have the same problem. I tried this and still having the issue.
-
I don't want to get too carried away, it could be coincidence but after following the steps I played for hours today without a crash. The longest I've played in months without a scan and repair. Thanks for the post dude!
-
I tried this and it may not have fixed the game completely , but it sure have made it much more playable and with far more time between crashes . Now lets just hope for an actual fix ...
-
This works for me. Unfortunately the crashes keep coming back after a while. Most of the time its some form of the enviroments.pkg, right now for example: "w64_environments_01a2_0.pkg". I hope they'll be able to fix this soon. I really like the game, but it's kinda annoying that I have to delete the files and rerun the repair function.
-
2 RepliesI do not have any file name after that line. It just says (-81). Heres the paste of the crash text after the most recent crash. Which has also been the same reason for every other crash. stack: 00007FF768A5D8CF <unknown> 00007FF768A5CC3A <unknown> 00007FF768A588E2 <unknown> 00007FF769442688 <unknown> 00007FF76925DB61 <unknown> 00007FF768FB1AAB <unknown> 00007FF7690CF4F1 <unknown> 00007FF768E068C6 <unknown> 00007FF7697F8A16 <unknown> 00007FF768E11200 <unknown> 00007FF768B0F175 <unknown> 00007FF768AAB27B <unknown> 00007FF768AAB36E <unknown> 00007FF768AAA5BE <unknown> 00007FF768A70AE2 <unknown> 00007FF768A74379 <unknown> 00007FF768AAA688 <unknown> 00007FF768AAA73F <unknown> 00007FFA6E9F8364 <unknown> 00007FFA70B370D1 <unknown> session_id: Sat_11112017_132701_009536@x64@50967250@A5_58_30_56_FE_08_A09B halt: RELEASE_VHALT halt information: Patchable package registration failed with result (-81) fatal error detected, current status was: init: init.txt version: d2_live tiger_final release pc_x64 60642.17.11.02.1732.d2_live 17.11.02 1732 session_id: Sat_11112017_132701_009536@x64@50967250@A5_58_30_56_FE_08_A09B GPU Device: NVIDIA GeForce GTX 980 Ti GPU VendorId: 4318 GPU DeviceId: 6088 GPU SubSysId: 1234516034 GPU Revision: 161 silo_id: 1665943536958920704 signon_server_reported_content_version: 60525.60480-0 authority-over-current-bubble: false - map slice set 'HASH(0x811c9dc5)':-1, activity slice set -1 authority-over-domain: false world_controller state: bootflow:package_registration environment_string: D2_ProdRetail:75 install type: 5 system_milliseconds: time 4413029 timezone_seconds_offset_from_UTC: 18000 is_current_bubble_authority: false crash_folder_location: C:\Users\Savio\AppData\Local\Temp\Destiny 2\crash_folder\pc_x64\crash_folder_9536_20171111_132734\ world_controller_state_manager status: bootflow:package_registration player_position_x: unknown player_position_y: unknown player_position_z: unknown
-
i have this problem too and i don't know how to fix it. I can't change settings, because it's don't work!
-
This seems to have worked for me! It crashed not even a whole second after loading EDZ and after doing this fix, it has yet to crash after a few hours. So thanks :)
-
3 Repliesthe Crash info that I am getting is mostly called this halt information: resourcerer:load: Failed to load tag 0x80BF4043 (0x01fa 67) with error error bad handle, {{!0x00000006!}} install type {{!5!}} fatal error detected and i have no idea what to do with that info. My game seems to crash around 4 times an hour with most of them being the above error or something very close to it. No matter what I am doing it crashes out and says "Problem reading game content" And yes I have tried every fix that people have suggested with no success so far : /
-
1 ReplyOddly enough, I stopped having this problem after I changed my graphics settings to maximum from medium.
-
Going to try this, I've had these crashes everyday since the "hotfix" soooo... I gota delete this whole folder. Downloads all ready going faster then the 12GB repair crap i had to download today apparently. Have a 100Mb connection but the Repair crap will only use it for about 5min then give up and go to 2mbps... Anyone else have that? But anyway. Commenting to find later, will post results.
-
1 Replydoesnt help. The same new loaded file gave me the error after 30min playing. So the file is corrupted again! Bungie we need a fix for this, the game is unplayable for tons of people!
