{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Nope Nope Nope:
2/11/2021 11:10:01 PM
37
[SOLVED] The game on Steam won't launch after Update 3.1.0 ... and still won't even after the Feb 10th Hotfix
UPDATE 2021/02/11: THIS UPDATE FIXED THE ISSUE!
https://twitter.com/BungieHelp/status/1359962107760971776
[quote]We will be deploying a Steam-only update at 2 PM PST (2200 UTC) to help resolve issues causing players to be unable to launch Destiny 2 after Update 3.1.0.
Players will need to quit and restart Destiny 2 and Steam to take this update.[/quote]
----- OLD -----
[b]BREAKTHROUGH: USER FIX FOUND!!!!!
Enable AES-NI in your bios.
If your CPU isn't AES-NI capable then you have to wait for Bungie to release an hotfix.
https://www.bungie.net/en/Forums/Post/258271957?sort=0&page=0&path=1
[/b]
UNANSWERED QUESTIONS:
- Currently all the CPUs from PC minimum requirements on Bungie website do have AES-NI indeed, but...
- Had the game always been requiring AES-NI capable CPUs? It was working correctly before update 3.1.0 even without such instruction set, honestly I can't remember the old minimum requirements
- Was this change ever mentioned in any TWAB? Maybe with some time in advance so we could prepare instead of being suddenly gated out from the whole game one day from the next?
- Are we really getting a fix or this change in hardware requirements is intended and will then stay?
----- original post ----
I can try to start the game from Steam (or even directly clicking on the executable file from the game folder), then I can see the Destiny2.exe process in the process list, then after running there for 30-40s and without even taking the screen space from the system it terminates without any notice. (i.e. the process terminates before it can load into the GPU)
Verified files.
Disabled cache in Nvidia Panel.
Started as Admin.
Started in win 7 compatibility.
Started with no full screen optimization.
Started with Steam Overlay off.
NEW: Clean Installed old Nvidia drivers (after deleteing every temp or shader cache folder in my system, every one) ... no results
NEW: chkdsk /f /r (no need for /x for me, the game files are not on the system drive) ... no errors or bad sectors and no results
NEW: tried to launch from an alt account on the same machine ... no results
EDIT: Forgot I tried deleteing cvars, no results
NEW: finally fully updated my windows 10 to v20H2 version from v2004.... no result
It all won't change anything, the process always terminates silently.
Win 10 Pro 64b - i7 920@Stock - 24GB - GTX 1080 - sata SSD system drive and game drive
EDIT: the issue appeared with update 3.1.0, never had this issue before, it seems a common issue:
https://steamcommunity.com/app/1085660/discussions/0/3103512736625444507/
UPDATE 2021/02/10: @BNGHelp7 [b][u]Still not launching[/u][/b] even after the mini patch just released on Steam (https://twitter.com/BungieHelp/status/1359358417358319619)
UPDATE 2021/02/10: Bungie finally acknowledged the issue, yay!
https://twitter.com/BungieHelp/status/1359559966483382274
English
#Help
-
100 RepliesHi there, Thanks for your report. Could you grab us your DxDiag so we can pass it along to the developers? • Press (Windows Key + R) to bring up the Run dialog box, enter this command “dxdiag” without quotation marks. • Click on “Save all information”. • Copy the text and use a text dump website (i.e. PasteBin.com) to paste the information. Please don't use Google Drive. • Create a link and post it here.
-
1 ReplyI got the same problem, thanks for the info!
-
29 RepliesEdited by Al3x: 2/11/2021 1:50:30 AM[b]Statement :[/b] The issue is related to AVX (Advanced Vector Extensions) and AES-NI trying to force into the non supported CPU's to register instructions on data, process isn't working due to runtime error for exception illegal instruction. Not all CPU's support AVX. Generally, CPU's with the commercial denomination "Core i3/i5/i7/i9" support them, whereas "Pentium" and "Celeron" CPU's don't. Any CPU's before Sandy Bridge (2nd generation) 2011 by Intel won't support AVX technology. If you did not understand anything past this point, it does not matter. I don't understand computer code either. What you must understand is the watery bulbous meatbags working at Bungo are at fault, I suppose I should not call them such, not to refer to them by their meatbag status in the future. [b]Analysis :[/b] Additionally, If you get an instruction exception error of the AES-NI extension set in your dxDiag logs or in your crash logs AppData\Local\Temp\Destiny 2\crash_folder\pc_x64 then you most likely can't launch the game because of non supported AES-NI x86 instruction set architecture for microprocessors from Intel and AMD before 2008. [b]Observation :[/b] For instance, a old 2008 Bloomfield i7-950 CPU will get an AES-NI extension set error like "AESKEYGENASSIST" in the crash logs because it doesn't support AES-NI instruction sets. Some newer processors like the (9th and 10th generation) do not support AES-NI. [b]Query :[/b] If your CPU is overclocked and you have AVX by setting "CpusupportsAVX" to 0, you will get an instruction set error. Try turning AVX offset to 2 which puts those instructions back on. Don't mess with any overclocking settings, if you don't know what to do, you could potentially overheat your processor and cause severe computer malfunction, I do not suggest to take this course of action as it would be bad for your computer. [b]Commentary[/b] : The liquidious bipedal fleshbags working at Bungo, need to disable the silent force check for AVX or people with older or newer CPU technology that don't support the above instruction sets won't be able to launch the game on steam. [b]Temporary fix[/b] : If you know how to access your bios, switch your mobo AES-NI to ENABLE under advanced settings CPU configuration. Save your bios settings and restart your computer. [b]Explanation[/b] : If your mobo doesn't have AVX or AES-NI support like me then you need to wait for the organic meatbags working at Bungo to implement a fix because A) your processor is old or B) you have a newer generation processor with no AVX or AES-NI support. A CPU which does not support AVX or AES-NI code can of course not run AES-NI and AVX-specific program written with AVX or AES-NI in mind on an incompatible x86 CPU: it simply doesn't recognize them. That would be the equivalent of trying to start a car engine with organic matter as fuel.
-
11 RepliesSo in General did Bungie say if they are working on it / fixing it this hotfix or nothing ? because i did not see any information on social media .... Only info im getting is from this Forum. And honestly helped me to understand this situation because some People in the community care atleast. Just wondering when they finally fix it because i really want to start by now.
-
Does everyone spend more time fixing destiny versus playing it?
-
1 ReplyWhat about PS4
-
3 RepliesEdited by Crisidelm: 2/10/2021 10:04:23 PMThe minimum requirements in the CPU compartments list three CPUs (two for Intel, one for AMD) that indeed support the AES instruction sets (the Pentium G4560 does support it, it's written under Security & Reliability: Intel® AES New Instructions Yes). So, they can argue that indeed it is a minimum requirement.
-
9 RepliesHi again, Are you running any antivirus software that may be conflicting with Steam launching the game? Did you already successfully download the new 3.1.0 update as well?
-
4 RepliesI was gonna share that aes-in thing but as always you’re on top of it already! Lol! Much love. Unless i did something wrong, that fix unfortunately did not work for me :(
-
3 RepliesI'm running a first gen i5 and I cannot find any avx settings in my bios.
-
1 ReplyI am having the same problem here too. Updated drivers. reinstalled the game. restarted pc. Did a hard reset. It won't even launch on after update.
-
same problem .... good start of the season tho
-
1 ReplyI accepted an invitation from my mate, and got a error message something like /connect:a5ae190f010010000000. Does someone know what it mean?
-
1 ReplyI am also having this problem, was hoping after the hotfix that it would be fixed but it still fails to launch my specs are GTX 480 i7 950 12gb ram
-
2 RepliesHave you tried deleting the Destiny 2 cvars file?
-
1 ReplyChiming un as another data point. I also am having the same problem. Game worked fine for me until the weekly reset yesterday. I tried all of the same debugging tips as OP to no avail. I too have an older cpu that does not support avx (amd phenom ii x4) Dxdiag report: https://pastebin.com/CB2fggg2
-
Following thread, have the same problem!!!
-
Potentially related; I was having massive Broccoli errors all of last season, to the point where I completely wiped and reinstalled my drivers this weekend and even that didn't fix it. Anyone else who currently can't get in have that issue? Honestly I'm hoping this is the final form of the Broccoli error and now it will finally be resolved...
-
So having the same Problem here and tried everything my Game just wont launch , looked at my anti virus and nothing it just wont start at all.... Honestly quite dissapointed because i was really hyped about this season. But now the real Problem just imagine the fact that new players wanted to play Destiny in this new season bought and installed the game. But they cant play the game for now 2 days and their friends rush the Leveling and activities there wont be any fun for thoose players and they will just quit the game . sorry for my poor englisch it is not my main Language
-
8 RepliesEdited by nunoncastors: 2/10/2021 12:35:14 PMI'd just like to add my name to the list. I've been through pretty much the exact same steps as Nope nope Nope. The game is fully patched, I've tried various combinations of drivers, settings, etc with little effect. The game crashes shortly after launch via steam with the same illegal exception error others have reported. Stack dump looks like this: CHKIMG_EXTENSION: !chkimg -lo 50 -db !destiny2 253 errors : !destiny2 (7ff68cb6104e-7ff68cb6114d) 7ff68cb61040 03 09 7a 14 e9 bd 0f 84 4e c4 67 16 b1 69 *c9 *0f ..z.....N.g..i.. 7ff68cb61050 *11 *01 *66 *0f *ef *c0 *48 *83 *c4 *08 *f3 *c3 *0f *1f *40 *00 ..f...H.......@. 7ff68cb61060 *48 *83 *ec *08 *48 *c7 *c0 *ff *ff *ff *ff *48 *85 *c9 *0f *84 H...H......H.... 7ff68cb61070 *73 *04 *00 *00 *4d *85 *c0 *0f *84 *6a 04 *00 *00 *41 *ba *00 s...M....j...A.. 7ff68cb61080 *08 *00 *10 *0f *10 *01 *0f *57 e4 *44 *23 *15 *34 *fe *66 *03 .......W.D#.4.f. 7ff68cb61090 *49 *8d *40 *10 *81 *fa *00 *01 *00 *00 *0f *84 *c0 *02 *00 *00 I.@............. 7ff68cb610a0 *81 *fa *c0 *00 *00 *00 *0f *84 *a4 *01 *00 *00 *81 *fa *80 *00 ................ 7ff68cb610b0 *00 *00 *0f *85 *28 04 *00 *00 *ba *09 *00 *00 *00 *41 *81 *fa ....(........A.. 7ff68cb610c0 *00 *00 *00 *10 *0f *84 *86 *00 *00 *00 *41 *0f *11 *00 *66 *0f ..........A...f. 7ff68cb610d0 *3a *df *c8 *01 *e8 *3e *04 *00 *00 *66 *0f *3a *df *c8 *02 *e8 :....>...f.:.... 7ff68cb610e0 *2c *04 *00 *00 *66 *0f *3a *df *c8 *04 *e8 *21 *04 *00 *00 *66 ,...f.:....!...f 7ff68cb610f0 *0f *3a *df *c8 *08 *e8 *16 *04 *00 *00 *66 *0f *3a *df *c8 *10 .:........f.:... 7ff68cb61100 *e8 *0b *04 *00 *00 *66 *0f *3a *df *c8 *20 *e8 *00 *04 *00 *00 .....f.:.. ..... 7ff68cb61110 *66 *0f *3a *df *c8 *40 *e8 *f5 *03 *00 *00 *66 *0f *3a *df *c8 f.:..@.....f.:.. 7ff68cb61120 *80 *e8 *ea *03 *00 *00 *66 *0f *3a *df *c8 *1b *e8 *df *03 *00 ......f.:....... 7ff68cb61130 *00 *66 *0f *3a *df *c8 *36 *e8 *d4 *03 *00 *00 *0f *11 *00 *89 .f.:..6......... 7ff68cb61140 *50 *50 *33 *c0 *e9 *9e *03 *00 *00 *0f *1f *80 *00 *00 f2 90 PP3............. CONTEXT: (.ecxr) rax=00007ff68f1fab30 rbx=0000000000080000 rcx=0000000aeccff290 rdx=0000000000000009 rsi=00007ff68cb50000 rdi=0000000000000000 rip=00007ff68cb610ce rsp=0000000aeccff240 rbp=0000000aeccff3c0 r8=00007ff68f1fab20 r9=0000000000000081 r10=0000000000000000 r11=00007ff68f1fac20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei ng nz na po cy cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010287 destiny2+0x110ce: 00007ff6`8cb610ce 660f3adfc801 aeskeygenassist xmm1,xmm0,1 Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff68cb610ce (destiny2+0x00000000000110ce) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 EDIT: I'm 90% certain this is an AVX issue for me as my CPU does not support the instruction set. However, if that is the case, ffs, lads. A bit of a heads up would have been nice.
-
1 ReplyEdited by Ares: 2/9/2021 10:40:23 PMBeen trying to log the F*** in for hours now, nothing! The game wont launch, not even a message about anything. Christ, give us some info atleast, wtf! Have hoped for some adultness in this game atleast. Seems like the already left the office tbh
-
Great, they updated it yet it still doesn't work. Just great.
-
well reported... did the same steps and nothing works come on guys... you really want us to wait for tomorrows maintenance without any help ? that's preposterous - people play money to play this game, you remember ?
-
Same, also verified local files. I’m most bummed about not being able to buy the new daily mod that will reset at normal time today. How long before that mod is available again. Ugh...
-
1 Replyтакая же проблема, начинает запускаться и тут же вылетает
