{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/3/2019 9:04:52 PM
20
I still have the problem "Problem reading game content."
Hello everyone,
I've been playing Destiny 2 normally since it came out on steam but when I bought the DLC (Forsaken) yesterday I started throwing that error and I can't access the game.
I did what the support had said to do when this happen and I already deleted the file "steam_appid.txt" and the .exe does not have the option to open as administrator.
Then I saw that the problem was still emerging and I tried several things like checking the files and even reinstalling the game, but the problem continues.
If you have any other solution than the one you already gave to continue enjoying all the content of the game, I would appreciate it.
- Law
-
Have you got any over clocks and have you tried under clocking your gpu?
-
Edited by MCBublik: 10/7/2019 8:04:49 PMSame problem. Before it was - broccoli. I was fix it, like in this video -https://www.youtube.com/watch?v=HySYWSXcTcU . I was played near 1 hour, and game crashed again. And started "Problem reading game content." In blizzard i wasn't have any problems
-
1 ReplyBNGHelp6 thanks for answering. I already said that i verify the game and I clear my download cache before and still can't let me in. There are many people with this problem, we need new solutions.
-
8 RepliesHi. Thanks for your report. If you're still having this issue after deleting the "steam_appid" file, you may want to [url=https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335]verify the integrity of your game files[/url] in the Steam app to see if that helps with your issue. You may also want to [url=https://support.steampowered.com/kb_article.php?ref=3134-TIAL-4638]clear your download cache[/url].
-
I also had the same problem, sometimes I couldn't even start the game without crashing. I also found out that I only had 128 mb of VRAM to work with because I had my monitor connected to my motherboard instead of the graphics card, and once I switched the plugs my graphics became better and the error stopped coming up for me and I could play multiple hours. Hope this helps!
-
2 RepliesSame issue. Going to leave the things I've tried here in case it helps anyone. - deleted steam_appid.txt - ran file validation (at least 3-4x over testing) - uninstalled and reinstalled the game - ran revo uninstaller to scrape the registry and reinstalled on a different drive - cleared download cache - checked steam_appid.txt is not in any other folders - memtest comes back clean The game ran with no issues under Blizzard launcher ~6 months ago. Same system, same specs, no major changes. Game crashes within seconds of starting every time, occasionally it can load through to gameplay but crashes within ~30 seconds. File validation comes back clean. I'd really like to play, hope someone finds something :(
-
1 ReplyI had this on my new PC. I've tried everything then I tested my RAM and it turned out it was faulty. I used MemTest86 it takes up to few hours to finish the test, but it will show you if there's any problem. Since I changed the RAM problem is gone. Maybe this help.
-
1 ReplyEdited by ChickenSir: 10/6/2019 5:52:28 AMI am also suffering from this issue or bug, as i think it is. While i have been experimenting with many ways of trying to fix this. I have noticed some really odd things happen. [b]Game Crashes When:[/b] - Exploring (Patrol) - Strikes - Adventures - Missions - Gambit [b]Game Does Not Crash When:[/b] - In social spaces (Tower and Farm) - Crucible (PvP) - Dungeons (Shattered Throne) - Raids (Leviathan, Last Wish, SoTP) - Zero Hour - Whisper of the Worm And finally, probably the most odd thing about this issue, is the [b]game does not crash when icons fail to load in.[/b] These include inventory icons, enemy icons, etc.. As well as this, when player models fail to load in. Just a few things i felt like pointing out. Thought i have not found a fix, i hope some day Bungie notices this issue and tries to implement some sort of solution. Whether that be more video settings, or even a fix for the issue itself. What i don't understand, is why some aspects of the game work, and some don't. It just makes no sense. EDIT: Game worked fine on launch day, played it for 12 hours. EDIT 2: Added Zero Hour, about to test Whisper EDIT 3: Added Whisper
-
I'm running into the same issue and have done everything advised by bungie and anyone else with suggestions. I posted a thread with all my troubleshooting steps but nothing yet. Bumping for visibility, hopefully we'll hear something soon.
-
I am having the same problem. Made a thread about it earlier today but got no response. The crash_info.txt file seems to say something about failing to load tags. "Failed to load tag with path '<N/A>' and description '<N/A>' 0x80BE26CB (0x01f1 1739) from package {{w64_edz_activities_01f1_1.pkg}} with error 'error bad handle, {{!0x00000006!}}' install type {{!5!}} fatal error detected"
-
i have the same problem here tried lots of stuff but nothing works
-
1 ReplyI had this a few times on the BattleDOTNet launcher, but I did the "scan and repair" that it said to do and I never saw the problem again. Does steam have a similar function?
-
I'm in the same boat, bump
-
same here pal. Sometimes the game will run for a few minutes until it inevitably crashes
-
Somebody please. This is ridiculous. Cant even play the game.
-
I am having the same problem as well. Still no fix. Sometimes I can play for a few hours, sometimes a few minutes before that error pops up. I tried: -Deleting the steam_appid file -Memory test with 0 faults after 10 passes -Lowering memory speed, even underclocking it -Checked to make sure my CPU and GPU were not being overclocked -Upgraded all of my drivers -Verified integrity of game files -Cleared my download cache Nothing is working. If I can't figure out a solution soon, I may have to request a refund with steam.
-
I'm having the same problem since yesterday, tried restoring the pc, installing the game in another hd, clearing the download cache, verifying the integrity of the files... Yet nothing helps......
-
Same issue. Don't know what else to do. I gave exceptions to my antivirus, downloaded it three times and nothing is helping. Same issues. Does everyone's crash reports look the same? You can find it through C:\Users\*Name*\AppData\Temp\Destiny2\ Just type in \Appdata in the top file menu if you don't see it in the file explorer. Every error is due to the resourcerer not loading a tag.
-
Edited by Onkel Amok: 10/4/2019 10:02:08 AMSame here: - Steam "repair files2 does not solve the problem - no "steam_appid.*" file - cleared download cache already - deleted all files expcept the "package" folder under "\Steam\steamapps\common\Destiny 2\" and redownloaded all necessary files through steam repair again - unclick the option- Enable the steam Overlay does not solve the problem Played Destiny 2 via Blizzard launcher before without issues and also yesterday without issues with steam. Happend since the newest Steam/Destiny 2 update. [b]Actual solution (for me):[/b] I use COMODO Firewall, which usually triggers, if modifications in any kind appear. This time (first time ever), it did not trigger gain. I disabled all components and reenabled them again and see: It got triggered while starting Destiny 2 and I could allow different kinds of communication/access again. So: Check your security suite and disable some components just for tests. I never had this for any game in the past years - but never say never.
-
Edited by Grumpy Hrych: 10/4/2019 6:43:13 PMSame here
