Game not launching is related to non AVX & AES-NI support. [Temporary fix solution in thread]

[Alex]

Statement : 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.

Analysis : 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.

Observation : 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.

Query : 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.

Commentary : 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.

Temporary fix : 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.

Explanation : 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 you have a newer or older 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 incompetent organic meatbag matter as fuel.

[Oneleg]

Originally posted by Colgarra:

Originally posted by Mordred:

The issue is related to the bridge offset AVX (Advanced Vector Extensions) 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 & AVX2 technology.

If you get an instruction of the AES-NI extension set in your dxDiag logs (AES Instructions) then you most likely can't launch the game because of an illegal instruction being read on data due to non supported AVX for your CPU. For instance, a old (2008) Bloomfield i7-950 CPU will get an AES-NI extension set like AESKEYGENASSIST because of non support AVX assembly.

TL'DR ; Bungo, needs to disable force check AVX offset or people with older CPU technology won't be able to launch the game on steam.

Could this be my problem Bungie...?

Intel Core i7 CPU 920 @ 2.67GHz, 12 GB RAM, NVIDIA Geforce GTX 970
Win 10 Pro 64-bit

[Oneleg]

ich habe die selbe cpu und auch bei mir läuft es nicht

[Schizhawk]

Worked for me too. Mordred you saved my day ! Thx a lot.

[Sierra]

I cant find anything related to AES-NI in my bios :(
motherboard MSI P55 cd53
cpu: xeon x3450 (I dont think it supports AES-NI)

[FutPens]

I need my fix!
Does anyone know of a way to edit a .txt file to remove the need for AES-NI possibly? *fingers crossed

[necronomicon]

My CPU doesn't support AES-NI. Sadly...

[Anonimo]

Why would this change in a patch? If 5 or so hours before the patch, the game is running fine (as it has since I bought it years ago), why is it that it's an issue with our machines after the patch? What coders would ever exclude a set of CPUs, which is literally what I am reading above. Mine's an i7-7700. Everything else on steam works. BTW: the different "meatbag" references made me smirk.

[nickydo]

Your suggestion worked for me. I have an i7 6700K and followed the instructions given. Game now launches. Thank you very much for your input, what the hell is going on at Bungie?

[Denbo]

I have a i7 9700k and im getting crashing in playlist activities ever since new season started.

[Mr.Cypher504!]

Also did they add any forced SSE4.1 instruction set for this patch ? That also might be a reason being I have a older CPU and that instruction set is not supported with my CPU being its pretty out of date.

This looks like the same crashes I get when trying to run SSE4.1 games due to my CPU does not support that instruction set and only supports SSE2.1 . So the game will launch but crash immediately after a few seconds after launching.

CPU I'm Running is AMD Phenom II X4 965 Processor @ 3.4ghz .Yes its old and outdated but still runs most games fine and worked well with D2 for the past 3 years or so I have played the game.

[Alex]

Originally posted by nickydo:

Your suggestion worked for me. I have an i7 6700K and followed the instructions given. Game now launches. Thank you very much for your input, what the hell is going on at Bungie?

Commentary : Incompetence

[Alex]

Originally posted by Mr.Cypher504!:

Also did they add any forced SSE4.1 instruction set for this patch ? That also might be a reason being I have a older CPU and that instruction set is not supported with my CPU being its pretty out of date.

This looks like the same crashes I get when trying to run SSE4.1 games due to my CPU does not support that instruction set and only supports SSE2.1 . So the game will launch but crash immediately after a few seconds after launching.

CPU I'm Running is AMD Phenom II X4 965 Processor @ 3.4ghz .Yes its old and outdated but still runs most games fine and worked well with D2 for the past 3 years or so I have played the game.

Query : I don't know if Bungo use SSE4.1.

[Elite_LL]

Why not to reset the game to the old stable version and work on the new patch for some more time needed? You will lose 90% customers if you cannot fix it soon. Im already moved to free SW old republic....

[Matzomania]

Guten Abend,

bei mir startet das Spiel auch nicht; bis zu dem update gestern lief es einwandfrei.
Meine CPU ist 10 Jahre alt und es ist schon eine ganz schöne Frechheit der Verantwortlichen eine CPU als Müll zu bezeichnen um die eigene Unfähigkeit zu verbergen.
MFG

[Aether The Protogen™]

so what could be my problem? I played it just fine on the 6th. this is what mine is
Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz 3.20 GHz