JavaScript is required to use Bungie.net

Servicio de alertas
Hoy, todos los títulos de Destiny estarán fuera de línea temporalmente debido a operaciones programadas de mantenimiento. Permanece atento a @BungieHelp para conocer las novedades.

Ayuda

Ayúdanos a ayudarte.
Editado por Beans: 4/11/2020 8:20:16 AM
1

Error reading game content + infinite loading times

So I've asked about this before, and this is the last time I will so I'm just going to throw as much information about the problem that I have as physically possible. [b]CONTENTS[/b] 1. The Problem 2. Computer Information 3. Crash Information 4. Attempted Solutions (In comments) 5. Miscellaneous Information (In comments) [b]1. THE PROBLEM[/b] There are two main problems with the game that I experience, both of which happen as commonly as the other. Usually if it's not one of them messing me up it's the other, so they'll be labelled problems A and B, for future reference. [i][u]Problem A[/u][/i] Ever since the season of the drifter, I've been practically unable to do anything beyond crucible in Destiny 2. Whenever I am loading into the activity (ship in slipstream, or flying over the surface of the planet), the game hangs and crashes, and the following message pops up: https://media.discordapp.net/attachments/480379404011175946/628792301409533985/unknown.png [i][u]Problem B[/u][/i] Sometimes, I [i]do[/i] make it past the loading screen, but then after transiting through a number of areas [i](the number of areas I can travel between varies dependent on the planet, more on that later on)[/i], my inventory and pursuits tabs stop working, my UI loses text and icons, and the next time I try to move out of the area in any way or form (be it by changing character, leaving the area, exiting to desktop), the game crashes. If needed for future reference I can and most likely will record the next time it happens on video. [b]2. COMPUTER INFORMATION[/b] I must also put it here that before Season of the Drifter, while the game wasn't [i]pretty[/i] at least it was fully functional and still [i]playable[/i]. It's in light of this fact that I've made it as far into the game as I have, having played pretty much every game mode (so I was able to access every single map in the game, including raid locations) extensively up till these problems started ruining my experience. Yes, I'm running Destiny 2 on a laptop, and yes, I have little to no computer experience. CPU: Intel(R) Core(TM) i5-6287U CPU @3.10Hz (I think there's four of them) GPU: Intel(R) Iris(R) Graphics 550 GPU Driver Version: 26.20.100.7263 Total Available Graphics Memory: 8252 MB Dedicated Video Memory: 128 MB System Video Memory: 0 MB Shared System Memory: 8124 MB Operating System: Windows 10 Home 1909 (OS Build: 18363.720) DxDiag: https://drive.google.com/drive/u/0/folders/1uPP18HY0x9TwHkvVhBz4l4hYV2_2PV7D Also, yes, more heresy for you to insult me on if you're that kind of person: I run Destiny 2 on a Macbook Pro with Bootcamp. [b]3. CRASH INFORMATION[/b] I went into as many different places to gather as much crash information as I could think of, so they'll be labelled as well. [i][u]Most recent Crash Report from Crash Folder. Crash type A[/u][/i] stack: 00007FF6211F90AF <unknown> 00007FF6211F843A <unknown> 00007FF6211F40C2 <unknown> 00007FF6221F5031 <unknown> 00007FF6212534AF <unknown> 00007FF621252150 <unknown> 00007FF621257137 <unknown> 00007FF62125755F <unknown> 00007FF621257361 <unknown> 00007FF6212309CE <unknown> 00007FF62123C745 <unknown> 00007FF621217384 <unknown> 00007FF621214D11 <unknown> 00007FF6212175B1 <unknown> 00007FF62124FF73 <unknown> 00007FF621250034 <unknown> 00007FFBECE17BD4 <unknown> 00007FFBED66CED1 <unknown> session_id: Sat_04112020_145513_005404@x64@76561198309591498@ED_21_59_6C_2C_BD_AB55 halt: RELEASE_VHALT halt information: resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80BC2066 (0x01e1 102) from package {{w64_sandbox_01e1_0.pkg}} with error 'error bad handle, {{!0x00000006!}}' install type {{!5!}} fatal error detected, current status was: init: init.txt version: d2_live tiger_final release pc_x64 82717.20.03.25.1715.d2_live 20.03.25 1715 session_id: Sat_04112020_145513_005404@x64@76561198309591498@ED_21_59_6C_2C_BD_AB55 GPU Device: Intel(R) Iris(R) Graphics 550 GPU VendorId: 32902 GPU DeviceId: 6439 GPU SubSysId: 22876267 GPU Revision: 10 silo_id: 1665943536984677376 signon_server_reported_content_version: 82598.82598-2 authority-over-current-bubble: false - map slice set 'HASH(0x22723fad)':3, activity slice set 24 authority-over-domain: false world_controller previous_state: activity:initial_slice_set_loading world_controller state: activity:physics_join world_controller state_reason: unavailable environment_string: D2_ProdRetail:468 install type: 5 change-world: loaded strike_intrepid game_instance: 000000005EB739CB game_is_playback: false activity_tier: e_activity_tier.one activity-slice-set-index: 24 map-slice-set-index: 3 in-public-bubble: false AH active workspace: <no active workspace> activity_host_fireteam_is_connected: yes activity_host_last_fireteam_session_id: Fri_04102020_192902_046952@x64@game_svc_lp$@N07SH07SRV024 activity: strike_intrepid system_milliseconds: time 15208239 timezone_seconds_offset_from_UTC: -28800 is_current_bubble_authority: false crash_folder_location: C:\Users\Jester\AppData\Local\Temp\Destiny 2\crash_folder\pc_x64\crash_folder_5404_20200411_145702\ primary_bap_server_ip_address: 205.209.20.104 primary_bap_server_port: 7500 world_controller state_status: activity:physics_join (goal:002:activity:in_world) (requested tasks: 0x0000000000000001) (active tasks: 0x0000000000000001) (pending tasks: 000000000000000000) player_position_x: unknown player_position_y: unknown player_position_z: unknown [i][u]Screenshot from Crash Folder. Crash type A[/i][/u] https://drive.google.com/drive/u/0/folders/1YrUmId5d88dQVz4C9yl9NOdxzGizwGI5 [i][u]Taken from Computer Management Window, Application Error. Crash type A[/i][/u] - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Hang" /> <EventID Qualifiers="0">1002</EventID> <Level>2</Level> <Task>101</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-04-11T06:54:41.620238000Z" /> <EventRecordID>1393</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-CCUDRN3</Computer> <Security /> </System> - <EventData> <Data>destiny2.exe</Data> <Data>17182.0.0.0</Data> <Data>209c</Data> <Data>01d60fcd6e0c2757</Data> <Data>4294967295</Data> <Data>C:\Program Files (x86)\Steam\steamapps\common\Destiny 2\destiny2.exe</Data> <Data>a014968c-b806-48a1-b0a0-16f778c77d5f</Data> <Data /> <Data /> <Data>Top level window is idle</Data> <Binary>54006F00700020006C006500760065006C002000770069006E0064006F0077002000690073002000690064006C00650000000000</Binary> </EventData> </Event> [i][u]Taken from Computer Management Window, Information. Crash type A[/i][/u] - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-04-11T06:54:42.879824300Z" /> <EventRecordID>1394</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-CCUDRN3</Computer> <Security /> </System> - <EventData> <Data>2011763424573542415</Data> <Data>5</Data> <Data>AppHangB1</Data> <Data>Not available</Data> <Data>0</Data> <Data>destiny2.exe</Data> <Data>17182.0.0.0</Data> <Data>5e7bfd35</Data> <Data>d51d</Data> <Data>67246080</Data> <Data /> <Data /> <Data /> <Data /> <Data /> <Data>\\?\C:\Users\Jester\AppData\Local\Temp\WER9735.tmp.version.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9755.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97B4.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER97C1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9830.tmp.txt \\?\C:\Users\Jester\AppData\Local\Temp\WER9841.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_destiny2.exe_ee75abcb29fcd15268d94ddbe4bd883451a3cc_e3f9256e_cab_08fff556-88ab-4e4f-84bd-49e8f5c0219e\minidump.mdmp WERGenerationLog.txt</Data> <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_destiny2.exe_ee75abcb29fcd15268d94ddbe4bd883451a3cc_e3f9256e_08fff556-88ab-4e4f-84bd-49e8f5c0219e</Data> <Data /> <Data>0</Data> <Data>a014968c-b806-48a1-b0a0-16f778c77d5f</Data> <Data>268435456</Data> <Data>a43f4e7d27717de6cbeb382d05d4500f</Data> <Data>0</Data> </EventData> </Event>

Publicando en idioma:

 

Pórtate bien. Echa un vistazo a nuestro Código de conducta antes de publicar tu mensaje. Cancelar Editar Crear escuadra Publicar

Ver el resto del tema
  • Editado por Beans: 4/11/2020 8:19:44 AM
    [b]4. ATTEMPTED SOLUTIONS[/b] So far, I've tried (to no avail; none of these helped in any way): 1) Reinstalling Destiny 2 2) Reinstalling Steam 3) Deleting the appid.txt file 4) Deleting every file except for the Packages folder, then verifying game files 5) Launching Destiny 2 as an administrator, and disabling full-screen optimisations 6) Changing the language on steam 7) Whitelisting Destiny 2 from Windows Security 8) Utilising the crash_folder's information, delete package files that were associated to the crashes and then verify on steam [i](do note that every crash seemed to have a different package file involved, and some of them didn't even involve package files)[/i] 9) Clearing out space on my computer (60-100 GB at a time in the form of other games) 10) in light of my VRAM mentioned above, I attempted to use the Registry Editor to increase my allocated VRAM to 1024 MB, to at least have enough allocated for Destiny 2. That went about as well as you'd expect. 11) Update drivers 12) Roll back drivers 13) Using Task Manager, set the process priority of destiny2.exe to above normal, high, or realtime 14) ensure that I have the MS C++ redistributables and .NET frameworks required 15) Since I'm using Bootcamp, reinstall the entirety of Bootcamp

    Publicando en idioma:

     

    Pórtate bien. Echa un vistazo a nuestro Código de conducta antes de publicar tu mensaje. Cancelar Editar Crear escuadra Publicar

    4 Respuestas
    No se te permite acceder a este contenido.
    ;
    preload icon
    preload icon
    preload icon