JavaScript is required to use Bungie.net

Forums

Edited by Al3x: 2/11/2021 1:50:30 AM
29
[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.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • HI, thx it helped me. But what exactly this command affect? This is my PC for work and I would like to understand if it affects the quality of work of my PC in a bad way and I should switch each time for game and work

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Nope Nope Nope: 2/10/2021 5:01:13 PM
    But I don't think AVX are the culpirit. As I wrote in the OP many DxDiag reports from perople affected by the issue have AVX capable HW, yet they are affected. They are in general those to whom I asked specifically if the hotfix did any good for them.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:37:13 PM
    Commentary : It doesn't mean the issue of those people is AVX related, could be something else.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Nope Nope Nope: 2/10/2021 5:20:14 PM
    Exactly, I pointed it out because there was a rumor AVX were the cause but I wanted to investigate to see if the rumors checked out, which they didn't indeed. It could have looked like it was becausse AVX initially, since many CPU affected are aren't AVX enabled and because of precedents in the game industry, but many CPU in the reports are AVX enabled and yet they are affected. It looks to me more like something about GPU memory allocation failing, and I cannot poit out anything but looking at the reports many GPU affected are GTX 1xxx serie or lower. Yet even some AMD R570... So maybe they compiled with some GPU extension optimization not present in every hw?

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:37:30 PM
    Commentary : Some of the dxdiag I looked at have AES-NI extension set assembly errors even on some i7 and i5. The issue is with AVX or/and AES-NI on older or newer generation processors. For instance, a old (2008) Bloomfield i7-950 CPU will get an AES-NI extension set like AESKEYGENASSIST because of non support AES-NI instruction set.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • like me

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:37:36 PM
    Commentary : 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 instruction set for your CPU.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I appreciate your input, thanks for pinching in. Hope Bungie deploy a fix soon. What do you think about this one for instance? https://pastebin.com/81UC8THL This guy has a i5 9400F which is AVX and AES-NI capable (https://ark.intel.com/content/www/us/en/ark/products/190883/intel-core-i5-9400f-processor-9m-cache-up-to-4-10-ghz.html)

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:37:49 PM
    Answer : 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.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Nope Nope Nope: 2/10/2021 6:08:36 PM
    that is not my report, my CPU is a Nahlem, not AVX enabled at all :D If you really want to be sure you should ask advice all the people that I've asked about the hotfix at least, those I'm sure their CPU supports AVX because I've checked, just maybe they have disabled them...

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:38:01 PM
    Commentary : A) Old non supported AVX & AES-NI processors. B) Overclocked processors with AVX disabled. C) Newer generation like 9th or 10th with non supported AVX & AES=NI and only AVX-2 supported. Either way, it shouldn't be an issue in the first place if Bungo didn't force silent check it.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I've never seen a game requiring avx 512, avx and avx2 some, but avx512 was a server/WS reserved technology, at least until yesteday, or if you wanted to use your CPU to heat an hoven for a weird marketing flex...

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I'm just reading along as this fascinates me...I'm one of the ones that is AVX2 compatible but still cannot launch. i7-7700, no overclocking here; skimming thru my DxDiag, no sign of an AES-NI extension when I search for it in the log. Could have missed it, but interesting theory. Hopefully they figure it out soon.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:38:13 PM
    Statement : I may have found a temp fix. If you know how to access your bios, switch your mobo AES-NI to ENABLE under advanced settings. Save your bios settings and restart your computer.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Welp, it opened - made it thru the first, short cutscene and then immediately was met by my old friend Broccoli. Updated DxDiag: https://pastebin.com/V8dacMFg

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:38:32 PM
    Analysis : If you encounter a crash, please send me the logs. Good to know my fix worked for you.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Logs are above; guess you could say it worked and it didn't in my case.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • The log you just posted shows that your latest errors are down to the video driver somehow crashing

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Yep, welcome to my Broccoli error code that has plagued me for literal months now. It's great, super fun, I love the game barely being playable because of it and being soft-banned from Gambit.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Edited by Al3x: 2/10/2021 10:38:48 PM
    Query : can you send me the crash log from : AppData\Local\Temp\Destiny 2\crash_folder\pc_x64

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Nope, ignore the first one, that was pre-BIOS fix: stack: 00007FF7AF81AC76 <unknown> 00007FF7AF81965A <unknown> 00007FF7AF816B72 <unknown> 00007FF7AEFBF1A2 <unknown> 00007FF7AEA1EB19 <unknown> 00007FF7AEF0EA9B <unknown> 00007FF7AEF22FB9 <unknown> 00007FF7AEF2BB2D <unknown> 00007FF7AF017D2F <unknown> 00007FF7AF018FD9 <unknown> 00007FF7AF0965FD <unknown> 00007FF7AF09441F <unknown> 00007FF7AF8638A1 <unknown> 00007FF7AF2E4920 <unknown> 00007FF7AF837FE9 <unknown> 00007FF7AF3DFFE8 <unknown> 00007FF7AF820F41 <unknown> 00007FF7AF2BEE33 <unknown> 00007FF7AF2BF106 <unknown> 00007FFCDA247034 <unknown> 00007FFCDA8BD241 <unknown> session_id: Wed_02102021_135811_006576@x64@76561198118797953@9F_74_93_1C_F4_75_8DB9 halt: RELEASE_VHALT halt information: Graphics: device lost or removed. fatal error detected, current status was: init: init.txt version: v500_live.main tiger_final release pc_x64 91415.21.02.09.1134.v500_live.main 21.02.09 1134 session_id: Wed_02102021_135811_006576@x64@76561198118797953@9F_74_93_1C_F4_75_8DB9 GPU Device: NVIDIA GeForce GTX 1070 GPU VendorId: 4318 GPU DeviceId: 7041 GPU SubSysId: 275846987 GPU Revision: 161 silo_id: 1665943537004338176 signon_server_reported_content_version: 91124.91124-3 authority-over-current-bubble: false - map slice set 'HASH(0xe49f5c47)':0, activity slice set 1 world_controller previous_state: activity:physics_join world_controller state: activity:in_world world_controller state_reason: unavailable environment_string: D2_ProdRetail:768 install type: 5 change-world: loaded cine_512_pce.cine_512_pce game_instance: 5BF7CDEBEF2A1DCE game_is_playback: false activity-slice-set-index: 1 map-slice-set-index: 0 in-public-bubble: false AH active workspace: <no active workspace> activity_host_fireteam_is_connected: yes activity_host_last_fireteam_session_id: Thu_02042021_121722_201272@x64@game_svc_lp$@N07SH08SRV021 current phase: HASH(0x4e2db386).BUNDLE(0x4e2db386).HASH(0xe49f5c47).BUNDLE(0x200d6b28) activity_tier: e_activity_tier.one system_milliseconds: time 447618 timezone_seconds_offset_from_UTC: 18000 is_current_bubble_authority: false language_system: english language_ui: english language_audio: english language_current: english crash_folder_location: C:\Users\Roy\AppData\Local\Temp\Destiny 2\crash_folder\pc_x64\crash_folder_6576_20210210_140347\ primary_bap_server_ip_address: 205.209.21.103 primary_bap_server_port: 7501 world_controller state_status: activity:in_world (goal:003:activity:in_world) player_position_x: unknown player_position_y: unknown player_position_z: unknown

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Release_Vhalt is a video driver problem alright.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Drivers are completely up to date, and I even did a wipe & fresh driver install this weekend to try and fix it. Going to try reseating the card tonight, but past that I'm out of ideas. And of course this is the only game that gives me GPU errors.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • It could also be an app running in background interfering. Have you checked your OS for possible corruptions in system files?

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • I'll have to look again; tried booting it up in safe mode last week and the same thing happened, so had somewhat ruled that out. Steam cache dumped, heck full reinstall of Steam and Destiny yesterday before discovering this was a widespread thing, full driver wipe & reinstall, several passes with CC Cleaner...Season of the Hunt was full-on Season of the Broccoli for me. Good times.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon