AVX Issues / Game Launches, then Crashes on Older Processors (CPU)

Sneak-1438 · September 26, 2021, 7:46am

Just get your refund guys. I got mine. Re-buy the game a week or two later. Diablo 4 will most likely have the same issue, do not buy on launch. Always buy 2 weeks after launch.
Note to Blizz next time:
Stage 1 - Beta Test
Stage 2 - Week 1 - Open game for purchase for 5000 people. Solve issues/problems (less stress on servers)
Stage 3 - Week 2 - Open game for purchase for additional 10,000 people. Solve issues/problems
stage 4 - Week 3 - Game released to entire consumers world wide with no purchase cap. By this stage most major issues should have been resolved and minor issues left.

Results: Happy Customers and trust in company. anyway that is my two cents .

Fredi-11624 · September 26, 2021, 8:08am

My brother gets the same issue, cannot start a single game.
However, he uses the exact same computer as I used during Beta with ONE exception.
He uses his own mainboard and CPU (Phenom 965).

Today, we will also replace it with my old i5 2600 that already worked during beta.
So, if that will work, I can confirm that the mainboard/cpu combo was the issue at least for us.

He was not able to start the game at all so far. During beta with my Cpu/MB, there was no issue at all.

ghfreak-1119 · September 26, 2021, 8:27am

the Phenom, doesnt support AVX, but you should have luck with the I5 since it does support AVX, it wasn’t suppose to be a requirement to play the game but between beta and launch, it for some reason became enabled

Holyrocklee-2133 · September 26, 2021, 8:34am

“For some reason” i wonder what are the reasons… =)

Turtlezorg-1445 · September 26, 2021, 8:36am

@SimuLiu - Can you go back to that priest booth and ask for the AVX fix?

dilod2-2345 · September 26, 2021, 8:50am

Вот выдержки из моего файла отчёта dxdiag. Ошибка у меня точно такая же как и у всех тут, игра попросту не запускается.

------------------
System Information
------------------
      Time of this report: 9/26/2021, 12:34:44
             Machine name: DILOD2
               Machine Id: {007BFC14-580D-4A52-892A-63AD1A400E12}
         Operating System: Windows 10 Pro 64-bit (10.0, Build 19043) (19041.vb_release.191206-1406)
                 Language: Russian (Regional Setting: Russian)
      System Manufacturer: To Be Filled By O.E.M.
             System Model: To Be Filled By O.E.M.
                     BIOS: Default System BIOS (type: BIOS)
                Processor: AMD Phenom(tm) II X6 1055T Processor (6 CPUs), ~2.8GHz
                   Memory: 8192MB RAM
      Available OS Memory: 8190MB RAM
                Page File: 4421MB used, 5048MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
 DirectX Database Version: 1.0.8
           DxDiag Version: 10.00.19041.0928 64bit Unicode

---------------
Display Devices
---------------
           Card name: NVIDIA GeForce GTX 750 Ti
        Manufacturer: NVIDIA
           Chip type: NVIDIA GeForce GTX 750 Ti
            DAC type: Integrated RAMDAC
         Device Type: Full Device (POST)
          Device Key: Enum\PCI\VEN_10DE&DEV_1380&SUBSYS_36811458&REV_A2
       Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 
 Device Problem Code: No Problem
 Driver Problem Code: Unknown
      Display Memory: 6102 MB
    Dedicated Memory: 2007 MB
       Shared Memory: 4095 MB
        Current Mode: 1680 x 1050 (32 bit) (59Hz)
         HDR Support: Not Supported
    Display Topology: Internal
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.643555,0.332031), Green(0.288086,0.600586), Blue(0.153320,0.077148), White Point(0.313477,0.329102)
   Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
        Monitor Name: Generic PnP Monitor
       Monitor Model: BenQ FP222Wa
          Monitor Id: BNQ7707
         Native Mode: 1680 x 1050(p) (59.954Hz)
         Output Type: HD15
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
      Advanced Color: Not Supported
         Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_19c79fb6254e3b11\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_19c79fb6254e3b11\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_19c79fb6254e3b11\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_19c79fb6254e3b11\nvldumdx.dll
 Driver File Version: 30.00.0014.7212 (English)
      Driver Version: 30.0.14.7212
         DDI Version: 12
      Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.7
 Hardware Scheduling: Supported:False Enabled:False 
 Graphics Preemption: DMA
  Compute Preemption: DMA
            Miracast: Not Supported
      Detachable GPU: No
 Hybrid Graphics GPU: Not Supported
      Power P-states: Not Supported
      Virtualization: Paravirtualization 
          Block List: No Blocks
  Catalog Attributes: Universal:False Declarative:True 
   Driver Attributes: Final Retail
    Driver Date/Size: 13.09.2021 4:00:00, 1056296 bytes
         WHQL Logo'd: n/a
     WHQL Date Stamp: n/a
   Device Identifier: {D7B71E3E-50C0-11CF-C46B-8F160DC2D335}
           Vendor ID: 0x10DE
           Device ID: 0x1380
           SubSys ID: 0x36811458
         Revision ID: 0x00A2
  Driver Strong Name: oem8.inf:0f066de3a79f2f53:Section024:30.0.14.7212:pci\ven_10de&dev_1380
      Rank Of Driver: 00CF2001
         Video Accel: 
         DXVA2 Modes: {86695F12-340E-4F04-9FD3-9253DD327460}  DXVA2_ModeMPEG2_VLD  {6F3EC719-3735-42CC-8063-65CC3CB36616}  DXVA2_ModeVC1_D2010  DXVA2_ModeVC1_VLD  {32FCFE3F-DE46-4A49-861B-AC71110649D5}  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeMPEG4pt2_VLD_Simple  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  {9947EC6F-689B-11DC-A320-0019DBBC4184}  {33FCFE41-DE46-4A49-861B-AC71110649D5}  {6AFFD11E-1D96-42B1-A215-93A31F09A53D}  {914C84A3-4078-4FA9-984C-E2F262CB5C9C}  
   Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
        D3D9 Overlay: Supported
             DXVA-HD: Supported
        DDraw Status: Enabled
          D3D Status: Enabled
          AGP Status: Enabled
       MPO MaxPlanes: 1
            MPO Caps: Not Supported
         MPO Stretch: Not Supported
     MPO Media Hints: Not Supported
         MPO Formats: Not Supported
    PanelFitter Caps: Not Supported
 PanelFitter Stretch: Not Supported

Компьютер проходит по системным требованиям, мне не понятно почему игра не запускается, хотя бета работала.

MiniNinja-1168344 · September 26, 2021, 8:52am

almost 72 hours after release and can’t even launch, they care about locked out characters =]]

Turtlezorg-1445 · September 26, 2021, 8:59am

Они по ошибке включили функцию AVX в текущий билд, и на старых процессорах без поддержки AVX игра сразу вот так вылетает. В бэте этого небыло. В четверг это определили и надеятся что в понедельник починят.

ZaC-2114 · September 26, 2021, 9:02am

day 4 , no refund possible, no patch - WP Blizzard

Clo4k3D-2800 · September 26, 2021, 9:08am

My computer supports AVX and I still have the same issue.

FPU * Implements i387 floating point instructions
MMX * Supports MMX instruction set
MMXEXT - Implements AMD MMX extensions
3DNOW - Supports 3DNow! instructions
3DNOWEXT - Supports 3DNow! extension instructions
SSE * Supports Streaming SIMD Extensions
SSE2 * Supports Streaming SIMD Extensions 2
SSE3 * Supports Streaming SIMD Extensions 3
SSSE3 * Supports Supplemental SIMD Extensions 3
SSE4a - Supports Streaming SIMDR Extensions 4a
SSE4.1 * Supports Streaming SIMD Extensions 4.1
SSE4.2 * Supports Streaming SIMD Extensions 4.2

AES - Supports AES extensions
AVX - Supports AVX instruction extensions
AVX2 - Supports AVX2 instruction extensions
AVX-512-F - Supports AVX-512 Foundation instructions
AVX-512-DQ - Supports AVX-512 double and quadword instructions
AVX-512-IFAMA - Supports AVX-512 integer Fused multiply-add instructions
AVX-512-PF - Supports AVX-512 prefetch instructions
AVX-512-ER - Supports AVX-512 exponential and reciprocal instructions
AVX-512-CD - Supports AVX-512 conflict detection instructions
AVX-512-BW - Supports AVX-512 byte and word instructions
AVX-512-VL - Supports AVX-512 vector length instructions
FMA - Supports FMA extensions using YMM state
MSR * Implements RDMSR/WRMSR instructions
MTRR * Supports Memory Type Range Registers
XSAVE - Supports XSAVE/XRSTOR instructions
OSXSAVE - Supports XSETBV/XGETBV instructions
RDRAND - Supports RDRAND instruction
RDSEED - Supports RDSEED instruction

Huberthans-2747 · September 26, 2021, 9:13am

You do not have the same issue.

The game wouldnt even start at all before this patch. Now its a blackscreen because our systems do not have 2xxx or 3xxx RTX cards and no AVX, so it seems.

Most of the x58 systems dont have an EFI support, so our systems have no RTX generation grafic cards installed because these cards need an UEFI

Valsazaar-1144 · September 26, 2021, 9:14am

For newcomers to the thread, just a quick recap:

Everyone in this thread who should be here is suffering from the game loading to a black screen then crashing. No videos play, nothing else happens, it’s just black screen and crash. If you have any content show and play or sound or any error in your bliz log other than an NVIDIA_NGX_d3d12.init error, this isn’t the same issue being described in this thread.

The issue we all have in common is our processors don’t support AVX instruction sets. A lot of people here have worked to narrow down the most likely cause being the AI/ML driven Nvidia NGX beta upscaling routines accidentally including the wrong binary targeting SSE4 / AVX compatible environments instead of the universal binary (which was probably what was used in Beta and why we all had no issues).

Blizzard has shown zero effs about resolving the issue promptly because right now it benefits them to have fewer players hammering away at their disastrously prepared servers that are already completely overwhelmed. Even if they could fix this (or have fixed this) we will not see a patch for this until this coming week.

If you cant stomach the hurricane of excrement that is this launch, I would suggest you bounce and process a refund for the game. Otherwise, let’s all join hands and pray that somebody at Blizzard is actually capable and inclined to resolve this issue early this coming week.

Valsazaar-1144 · September 26, 2021, 9:15am

I would suggest you check your blz.log file in the game directory - I doubt you have the same issue this thread is about.

Azmodan-2657 · September 26, 2021, 9:31am

Checked my System for AVX with HWinfo. No AVX for my i5… so no D2R at all. Blizz said they aren´t sure if the issue is AVX-related, but it seems as if it is

Valsazaar-1144 · September 26, 2021, 9:37am

Well, in all fairness the issue is AVX related, but the real issue that all of us in this thread are really struggling with and disgusted by is the complete absence of support from a multi billion dollar experienced software company following a major release with huge, glaring, significant, game breaking problems affecting tens of thousands of users.

Any other industry, the programmers and leads would be crunch timing and getting these issues fixed. Instead, they all went home for the weekend (with the exception of Drak apparently, much respect), because hey, they’ve already got our money, we’re just the suckers that preordered and have slightly older systems.

I can guarantee you they will fix all the issues that the streamers are encountering before any AVX fix goes live.

Arestes-2413 · September 26, 2021, 9:39am

Are you sure this is Nvidia-related? Because I have the same issue as described in this thread and my CPU is Intel Xeon X5690 which does not support AVX, but my GPU is an AMD Radeon RX Vega 64.

Valsazaar-1144 · September 26, 2021, 9:41am

This is still related.

The Nvidia NGX thing is essentially a standalone library handling image upscaling using ML/AI routines. Just the sort of handy thing to be using if you wanted to remaster a 20 year old game but didn’t want to have to create new assets for every single thing you wanted better fidelity on.

Arkaine-2233 · September 26, 2021, 9:47am

I had the exact same issue as others in this thread since the beginning (i7 950 no avx) and since the patch, even with an RTX 3060, I have the blackscreen then crash (but with a different error messge in logs).

[Render/4] [<>:0]: NVIDIA DLSS not available on this hardward/platform., FeatureInitResult = 0xbad00000, info: NVSDK_NGX_Result_Fail

So I guess your asomptions are wrong.

Valsazaar-1144 · September 26, 2021, 9:53am

This is just a variant on the same error message, not surprising given you are on an RTX card.

DLSS is related to the same things, it’s deep learning / ML / AI image processing, and the init for the NGX SDK has failed.

Same error, different wording. You definitely belong in this thread asking for an AVX patch

Sen-1384 · September 26, 2021, 10:06am

I do it … because I’m pissed at blizzard