Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://help.bungie.net/hc/en-us/articles/360049196011-Error-Code-BEAGLE
Not much, but maybe the best course of action is to completely uninstall the game and not touch it for now.
AppID 1085660 update canceled : Failed updating depot 1085661 while unpacking bad chunk "e9f94c282b2f74bceb1c84f7bde955c42f9ba618" (Unpack failed (c:1057728,u:0,b:0)) (Suspended) "qn-00201-hyvlmdrid01-0226400a-2.steam-content-dnld-1.qwilted-cds.cqloud.com/cache4-atl1.steamcontent.com/depot/1085661/chunk/e9f94c282b2f74bceb1c84f7bde955c42f9ba618"
[2022-09-20 10:27:37] Failed unpacking chunk "e9f94c282b2f74bceb1c84f7bde955c42f9ba618" from "qn-00201-hyvlmdrid01-0226400a-2.steam-content-dnld-1.qwilted-cds.cqloud.com/cache4-atl1.steamcontent.com/depot/1085661/chunk/e9f94c282b2f74bceb1c84f7bde955c42f9ba618" (Unpack failed (c:1057728,u:0,b:0))
There are a few more errors about write gaps in the files HTTP invalid responses, CRC check failed, Received 404 (Not Found) responses, and more info about corrupted chunks of data. I've checked my network connection and it's fine--tried with and without a VPN connection because someone mentioned that in a google search. Something is obviously wrong when it tries to unpack, and I can see all of the downloaded files in the downloading folder, but Steam just doesn't recognize it and keeps redownloading, verifying and asking me to resume.
Yep. Running Steam as Admin, and disabled McAfee's Scanner and Firewall temporarily. I didn't know what to do about the HTTP invalid or the 404 stuff in the log, so I unplugged the router for a bit and plugged it back in. Flushed the DNS as well. Re-doing everything again to see if that did something.
I never even knew that was there! Fortunately (or unfortunately, for troubleshooting purposes) The problem just randomly went away, I installed a 4th time and when it still had the same issue I gave up and went to bed. I woke up the next day and ran the game again just to see what would happen, and it worked fine. If it comes up again I'll try that repair option and report back.
A guy having the same issue renamed this Destiny 2 folder in AppData (can just rename the folder to something like Destiny 2 backup). he said it stored crash logs from D2. If you don't have hidden files and folders enabled in Windows on your system, just open Windows search and then type in Run and open the Run app. in the dialogue, just type %appdata% and hit enter. This will dump into the Roaming folder. Look for that D2 folder and if you see one there rename it. Then go up one Directory and go into the Local folder and look for a D2 folder there and if you see one do the same thing. Then test boot the game and see if that fixes it for you.
if that doesn't work, another guy who was getting Beagle errors on boot and then crashing replaced his RAM and it went away after that. i know you tested your memory, but maybe just try re-seating the modules in their DIMM slots and see if that magically fixes it. If not and your are only using two sticks, swap both into the adjacent DIMM slots. Memtest should have also checked the DIMM slots on the motherboard as part of that test, but couldn't hurt to try it at least.
It reminds me of a story once where a guy found that multiple pre-built laptops with suspiciously slow NVMe SSDs were slow because they were not properly seated with sufficient force to complete all pin contacts between the drive and the slot. As a result, the drives only had access to PCIe x1 lane bandwidth, as opposed to all x4 lanes. Reseating those drives solved the problem, but it was nonetheless a peculiar tale that seemed loosely relevant to this matter.