{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Gaim Onn:
11/1/2017 5:11:00 AM
7
Problem reading Game Content Run Scan and Repair ( Game Crashing on Mission Starts)
**Update** The game now crashes even outside of missions. ANYWHERE ANYTIME.
The game played fine yesterday for several hours and several missions. Today it crashes every time I start a mission. I can free roam or do public events no problems for hours. But once I start a mission the game crashes. I have ran the Scan and Repair Several times in Battle.net. I have also Uninstalled both Destiny 2 and Battle.net. I reinstalled them both and still have the issues. Below is my system info. System is not over-clocked. All drivers and Windows is Up To Date. I do notice in Task Manager that after the crash Battle.net seems to push my CPU up to 100% usage.
Complete error message reads ( Problem Reading Game Content. Please close Destiny 2, run 'Scan and Repair' in Blizzard Battle.net App then restart Destiny 2 to try again. )
BATTLE TAG Gaim Onn
Destination/Activity ANYWHERE ANYTIME
Operating System: Windows 10 Home 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
Language: English (Regional Setting: English)
System Manufacturer: Micro-Star International Co., Ltd.
System Model: GT73VR 6RF
BIOS: E17A1IMS.10D
Processor: Intel(R) Core(TM) i7-6820HK CPU @ 2.70GHz (8 CPUs), ~2.7GHz
Memory: 16384MB RAM
Available OS Memory: 16328MB RAM
Page File: 22796MB used, 9914MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
Card name: NVIDIA GeForce GTX 1070
Manufacturer: NVIDIA
Chip type: GeForce GTX 1070
DAC type: Integrated RAMDAC
Device Type: Full Device
Device Key: Enum\PCI\VEN_10DE&DEV_1BE1&SUBSYS_11B71462&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 16252 MB
Dedicated Memory: 8089 MB
Shared Memory: 8163 MB
Current Mode: 3840 x 2160 (32 bit) (60Hz)
HDR Support: Supported
-
Update on 11/2 has not addressed this issues. Still having this fail/crash. It seems to be something directly related to Battle.net service and or Bungie servers. Being that Destiny is a continuous, Always online, Always connected game. The servers at Bungie or the connection via Battle.net is getting broken which triggers a “failed to read game content” crash/disconnect. For a game that is strongly reliant on server connectivity. These bugs should have been worked out in the beta and in the two months PC players had to wait after console launch. Let’s get this fixed quick Bungie. In the meantime...Us gamers will give you a few weeks to get it right while we head over to Call of Duty and Wolfenstein 2. We’ll check back to see how things are going in a couple weeks.... maybe?!
