[CRASH] Data Error : Diablo IV detected corrupted data and was unable to automatically repair the damage

Technical Support
21

Hey Mantix,

Thank you for your reply and for trying to help me.

I have done everything you have mentioned and the game is still not working.

The game was working without any issue until the update 5 days ago happened when hell broke loose and the game simply refused to work again.

Indeed, this is a work laptop but I have increased the “Available Physical Memory” and again, same error.

This is said as I really enjoyed the game and wanted to play it but it seems that the only option available at this point is to request a refund.

Since the game was working fine on launch and until the update they done 5 days ago it’s clear that this is not an issue on my side but it is something they have done which crashed the game…

22

Hey everyone,

I hope this helps somebody. I tried literally everything until I decided to turn down the resolution. I believe the issue is due to lack of VRAM because after turning down the resolution I don’t have the corrupted data issue anymore.

For reference I am using a RTX 2080 TI which has 11 GB of VRAM and I was playing at 2k resolution on Ultra settings. I have now changed the resolution percentage to be at 69% and changed the settings to Medium instead of Ultra.

23

Graphics resolution did nothing for me. However, I was able to correct my issue, kind of. The issue was getting really annoying. So I tried a few things. A reinstalled, did not work. I saw some posts about issues with Samsung m.2 drives and certain games and I just happened to have another one getting ready for another pc build. I put the new one in and copied all the game files to it. Both of them Samsung EVO 980 pros. The issues seemed to go away for a few hours, but then came back. I also had a crucial M.2 I kept around as a spare. It is what the EVO replaced. Once again, I copied all the game data over. No issues whatsoever. I’ve been good for a couple days now and not so much as a hiccup. The crucial drive is in the exact same M.2 slot as the Samsungs. So that rules out a faulty M.2 slot. Hope this helps someone. Luckily had had M.2s laying around, but it looks like an issue with Samsung m.2 drives or it least it was for me.

24

Yeah I have noticed the game fills the VRAM almost right to the brim. The Samsung drive is interesting as I have one and its working fine, but… I’m using Microsoft surface NVM Express Controller driver (don’t judge :face_with_peeking_eye: its bare bones but works great :sweat_smile:) also running latest Firmware on it and I don’t run the Samsung Magician software with ram cache (or Rapid Mode) enabled either. If you have a Asus Mobo try using the Ramcache software in place of Rapid Mode or disable the lot and see if it helps.

25

they need to fix this issue asap

27

I noticed this being an issue and tried extensively to figure it out.

Pre-Notice Yes, I never even launched the game before updating to the newest launch-day GPU Driver for the game, I DDU’ed in SafeMode, ensured Windows did not Install a base Driver when restarting (System Properties / View Advanced System Settings - Hardware - Device installation Settings - NO), and explicity installed NVIDIA GeForce Experience and grabbed the latest Game Ready Driver Version 535.98 2023-05-30

The game seems to randomly Unallocate 1 Megabyte MB of storage right before / while crashing. This effectively seems de-partition that 1MB from the rest of the Volume Regardless of SSD Storage Over Provisioning or Performance settings.

Sometimes you may crash instantly on loading/Queue, may crash on the character select screen not even touching or selecting anything, may crash after selecting the Characters and clicking play, and may even crash randomly moment into playing or many minutes into playing the game.

It seems that when this happens the Corrupted data mentioned may be that 1MB that is not long available to the drive. Through Basic Windows Disk Partitioning there was no way to actively Extend the main Volume/Partition of the SSD to reclaim that 1MB un-allocated.

I’ve actively tried clearing/Deleting the ProgramData Battle net and Blizzard Entertainment Files/folders, Attempted “Updating” the game as it suggests in the
Battle net Launcher, attempted Scan and repairing the Game.

But, it either will give a “Whoops something went wrong Message” or being unable to find the target location error / it not existing in a weird inital case for me it was COMPLETELY Disconectting my drive.… weirdly though, where the Files would no longer be navigatiable via File Explorer nor CMD prompts Stating that the Location doesn’t exist… any location/folder/file on the drive. It would no longer Show in Samsung Magician (which is a consistent issue after the 1MB unallocates).

But, for some reason would still show the full partition as Online in Windows Disk Parititoning…

Tried Running in VARIOUS combinations all Blizzard / Battle net / Diablo IV - 4 Software / Applications as or not as Administrator regardless of my local accounts security settings, regardless of basic UAC, Regadless of File/Folder access security settings

I’ve additionally Deleted the ProgramData Battle net and Blizzard Entertainment Files/Folders, the installation path of the launcher; the game folders entirely, etc. Then went into Windows Uninstall and removed all lingering listings of any of the apps / software. Completely restarted the computer, reinstalled the Battle net Launcher, resintalled the game… and the same issues occured.

NO OVERLAYS were on, not a Battle net overlay, not a Discord overlay even if it were open or not, not steam overlays, no Rivatuner overlays, etc. All Services were set to bare-bones NVIDIA, Windows, Blizzard/battle net services if applicable, aside from audio service (Realtek / Creative Technology, or my FocusRite services). Additionally, to ensure most / if not all unecessary background processes were killed / stopped, I Used & also tested NOT USING specifically-explicitly-manually ONLY the program called “ProcessKiller” Version 1.0.0 (Details says 1.0)/ 2.0 (Whitelist.txt and the UI says 2.0) Provided ‘in’ Tronscript, Version 12.0.3 - reddit[DOT]com/r/TronScript , C:\Users\brand\Desktop\Tron v12.0.3 (2022-09-11)\tron\resources\stage_0_prep\processkiller\ by Reddit User reddit[DOT]com/user/cuddlychops06

I should note I only tried the Server Slam Beta before this and Had the SAME issue initally on the SAME Drive; however, Did not document what I did to ‘fix’ or stop the game from doing this before. It may have just fixed itself while still being on my 980 PRO.

I have since not being able to fix this after like 3 hours of troubleshooting, moved this to my C: Drive : (Local Disk) C:\Program Files (x86)\Diablo IV

[PC] - 2023-06-1

Battle[DOT]net - Storage Path C:\Program Files (x86)\Battle[Dot]net\

GAME: Diablo IV - 4 Version 1.0.2.42016 Ultra Graphics Preset, DLSS Quality, High-Definition Texture Pack Downloaded - Storage Path (980 Pro) D:\Program Files (x86)\Diablo IV\ … All Security Permissions on this entire D: drive were set to Full Control for all Users, Authenticated Users, Administrators, and my Local account. If Prompted by UAC YES / ALLOW was selected.

Windows 10 Version 10.0.19045 Build 19045 / Windows 10 Pro - 22H2 - Version 19045.2965 Experience - Windows Feature Experience Pack 1000.19041.1000.0

MOBO: Gigabyte Z370 LGA 1151 Aorus Gaming 7 (rev. 1.0) (300 Series) BIOS Version F15 - 2021-11-29

CPU: Intel i9 9900k @ all cores 4.9 Ghz

GPU: NVIDIA EVGA ICX GAMING 2080 Super - Game Ready Driver Version 535.98 2023-05-30, NVIDIA CONTROL PANEL SETTING Default for global, and Default on ALL the Blizzard / Battle[Dot]net/ Diablo 4 Launchers / exectuables .exe

Monitor: Acer Predator XB271HU bmiprz 27" @ 144Hz - Driver Version 1.0.0 - Provider ACR G-Sync Enabled for Full-Screen and Windowed apps

RAM: XMPed 32 GB (two 16 GB kits) DDR4 Corsair Vengeance LPX 3000 MHz C15 (PC4 24000) - BOTH CMK16GX4M2B3000C155

Storage: Samsung 980 Pro SSD PCIe NVMe Gen4 Gaming M.2 2TB - MZ-V8P2T0B (Samsung Magician Version 7.3.0, 980 Pro SSD Firmware Version 5B2QGXA7 Settings @ Full Performance 10% Over Provision & Tested Default Standard Optimization)

Benchmark Results: (Default Benchmark settings) - Sequential Read 3557 MB/s, Sequential Write 3405 MB/s, Random Read 852050 IOPS, Random Write 797119 IOPS.

S.M.A.R.T Results: all “Good”, Extended SMART Self-Test: ~35 Minutes long… ALL GOOD

Keyboard: Corsair Gaming K70 Rapid Fire (RGP0021) - BIOS 1 (Defaults) (Reds LED only)

Mouse: Logitech G502 Hero

28

I have been binging the game after I installed it and Battle.net on the Same Drive: my C: Drive.

I tested again today (all fresh uninstall - reinstalls) and keepting Battle.net on my C: drive and then Diablo 4 on my D: drive. I was okay for a few minutes then the same general thing happened; didn’t disconnect the SSD entirely. But, it did corrupt data and then the repair and fix in Battle.net failed even after restarting the app.

Restarting the PC let me load to Character Select and it broke again.Currently doing a fresh uninstall reinstall and putting both on my D: drive and then going to test.

LOLuninstalled Battle.net and Diablo, Deleted Folders in Program Files and Progam Data.

Restarted; Reinstalled Battle.net fresh to 980 Pro, Restarted; Reinstalled Diablo 4 to 980 Pro, Restarted.Got to the Character select screen, within 10 seconds it just corrupted data again.

29

Hi Rammonon,

That’s some very peculiar behavior indeed.

  1. Do you overclock? (Meaning, XMP, CPU, do you leave everything on AUTO etc… beyond most peoples belief Auto still Overclocks.)
  • If so, try reset CMOS and set to stock then test, XMP does not inherently mean you have the most stable RAM overclock out of the box.

Your CPU’s max stable RAM setting is DDR4-2666, try that speed with the suggested Latency settings from your RAM’s XPM settings also set RAM voltage to 1.35v and test (do not set XMP and set this after the reset of course).

I have other suggestions about RAM but will leave that for now.

  1. Are you using Samsung Magician software with Rapid Mode on?
  • This with an unstable RAM overclock can cause corrupt data.

I recommend runing CMD (admin) then CHKDSK on the drive, type “chkdsk [drive letter]: /x /r”, replacing “[drive letter]” with the letter of the drive you want to scan. For example, to repair the C drive, enter “chkdsk C: /x /r”. ( can take some time so suggest making a coffee and relax :sweat:).

  1. For the Samsung Drives, try installing basic Microsoft drivers for Disk drives, and the Microsoft surface NVM Express Controller driver for the storage controllers (Samsung drivers might be bugged).
  1. Try lowering the Graphic Texture settings by 1.
  • erm… “Unallocate 1Mb partition from the rest of the Volume” are you running more than one OS? But Im pretty sure that is a secondary label at the end of the volume and is required by GPT; a disk without it is corrupted and may not be recognized by all systems.
30

Data corruption usually happens when hard drive is failing or system RAM is failing, where all I/O data is buffered before saving to storage media.
Check full run of memtest:

https://memtest.org\

And come back with results.

31

i paid over 70 bucks for a game i cant play

FIX THIS BLIZZARD

2 Likes
32

I dropped D4 before I end main company…
Corrupting data every 30-60m is so annoying, especially on boss fights :+1:

And of course it’s not even out of the question to try hardcore mode :rofl: :rofl: :rofl:

33

issue persist, when it will be fixed?.

System Information

  Time of this report: 7/4/2023, 13:31:09
         Machine name: 
           Machine Id: 
     Operating System: Windows 11 Pro 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250)
             Language: Spanish (Regional Setting: Spanish)
  System Manufacturer: Gigabyte Technology Co., Ltd.
         System Model: X570 AORUS ULTRA
                 BIOS: F36d (type: UEFI)
            Processor: AMD Ryzen 9 5900X 12-Core Processor             (24 CPUs), ~3.7GHz
               Memory: 65536MB RAM
  Available OS Memory: 65458MB RAM
            Page File: 12476MB used, 57078MB 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.4.6
DxDiag Version: 10.00.22621.0001 64bit Unicode

Display Devices

       Card name: NVIDIA GeForce RTX 3090
    Manufacturer: NVIDIA
       Chip type: NVIDIA GeForce RTX 3090
        DAC type: Integrated RAMDAC
     Device Type: Full Device (POST)
      Device Key: Enum\PCI\VEN_10DE&DEV_2204&SUBSYS_38811462&REV_A1
   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: 57069 MB
Dedicated Memory: 24340 MB
Shared Memory: 32729 MB
Current Mode: 2560 x 1440 (32 bit) (144Hz)
HDR Support: Supported
Display Topology: Extend
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.682617,0.308594), Green(0.278320,0.647461), Blue(0.149414,0.066406), White Point(0.312500,0.329102)
Display Luminance: Min Luminance = 0.351100, Max Luminance = 417.711792, MaxFullFrameLuminance = 417.711792
Monitor Name: Generic PnP Monitor
Monitor Model: AORUS FI27Q-P
Monitor Id: GBT2707
Native Mode: 2560 x 1440(p) (59.951Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Supported (BT2020RGB BT2020YCC Eotf2084Supported )
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: AdvancedColorSupported
Driver Name: C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll
Driver File Version: 31.00.0015.3640 (English)
Driver Version: 31.0.15.3640
DDI Version: 12
Feature Levels: 12_2,12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 3.1
Hardware Scheduling: DriverSupportState:Stable Enabled:True
Displayable: Not Supported
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Discrete
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 22/06/2023 19:00:00, 774232 bytes
WHQL Logo’d: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-6144-11CF-EA79-8E180EC2D235}
Vendor ID: 0x10DE
Device ID: 0x2204
SubSys ID: 0x38811462
Revision ID: 0x00A1
Driver Strong Name: oem3.inf:0f066de31b9ca1c8:Section028:31.0.15.3640:pci\ven_10de&dev_2204&subsys_38811462
Rank Of Driver: 00CF0001
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_ModeHEVC_VLD_Main10 {20BB8B0A-97AA-4571-8E99-64E60606C1A6} {15DF9B21-06C4-47F1-841E-A67C97D7F312} DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {9947EC6F-689B-11DC-A320-0019DBBC4184} {33FCFE41-DE46-4A49-861B-AC71110649D5} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {DDA19DC7-93B5-49F5-A9B3-2BDA28A2CE6E} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {6AFFD11E-1D96-42B1-A215-93A31F09A53D} {914C84A3-4078-4FA9-984C-E2F262CB5C9C} {8A1A1031-29BC-46D0-A007-E9B092CA6767}
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: Not 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

       Card name: NVIDIA GeForce RTX 3090
    Manufacturer: NVIDIA
       Chip type: NVIDIA GeForce RTX 3090
        DAC type: Integrated RAMDAC
     Device Type: Full Device (POST)
      Device Key: Enum\PCI\VEN_10DE&DEV_2204&SUBSYS_38811462&REV_A1
   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: 57069 MB
Dedicated Memory: 24340 MB
Shared Memory: 32729 MB
Current Mode: 1440 x 2560 (32 bit) (170Hz)
HDR Support: Supported
Display Topology: Extend
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.655273,0.324219), Green(0.208984,0.713867), Blue(0.146484,0.050781), White Point(0.313477,0.329102)
Display Luminance: Min Luminance = 0.060300, Max Luminance = 436.208008, MaxFullFrameLuminance = 436.208008
Monitor Name: Generic PnP Monitor
Monitor Model: M27Q
Monitor Id: GBT270D
Native Mode: 2560 x 1440(p) (59.940Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Supported (BT2020RGB BT2020YCC Eotf2084Supported )
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: AdvancedColorSupported
Driver Name: C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_5218d4313424e84c\nvldumdx.dll
Driver File Version: 31.00.0015.3640 (English)
Driver Version: 31.0.15.3640
DDI Version: 12
Feature Levels: 12_2,12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 3.1
Hardware Scheduling: DriverSupportState:Stable Enabled:True
Displayable: Not Supported
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Discrete
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 22/06/2023 19:00:00, 774232 bytes
WHQL Logo’d: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-6144-11CF-EA79-8E180EC2D235}
Vendor ID: 0x10DE
Device ID: 0x2204
SubSys ID: 0x38811462
Revision ID: 0x00A1
Driver Strong Name: oem3.inf:0f066de31b9ca1c8:Section028:31.0.15.3640:pci\ven_10de&dev_2204&subsys_38811462
Rank Of Driver: 00CF0001
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_ModeHEVC_VLD_Main10 {20BB8B0A-97AA-4571-8E99-64E60606C1A6} {15DF9B21-06C4-47F1-841E-A67C97D7F312} DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {9947EC6F-689B-11DC-A320-0019DBBC4184} {33FCFE41-DE46-4A49-861B-AC71110649D5} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {DDA19DC7-93B5-49F5-A9B3-2BDA28A2CE6E} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {6AFFD11E-1D96-42B1-A215-93A31F09A53D} {914C84A3-4078-4FA9-984C-E2F262CB5C9C} {8A1A1031-29BC-46D0-A007-E9B092CA6767}
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: Not Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 4
MPO Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
MPO Stretch: 10.000X - 0.500X
MPO Media Hints: resizing, colorspace Conversion
MPO Formats: NV12,P010,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM
PanelFitter Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
PanelFitter Stretch: 10.000X - 0.500X

34

Still an issue. Reinstalled Battle.net, didn’t fix it. Cleared app data files, didn’t fix it. Restarts fix it. Its definitely a bug with battle.net.

35

Yup still an issue. Every time I try to load the game back up after taking a small break it gives me the error. Then I have to sit around for 20-30min for it to scan and repair my files before I can play.

36

Hi Im facing this issue with Diablo 4 as well.
Tried to update and repair will hit error and I notice the SSD is dismount after hitting this error every time.
Getting this issue like 3 weeks ago, reinstalled, updated driver still getting random crash
What can be done is only restart my PC

ssd model : PNY CS3040 gen4

Updated with event viewer error.
A corruption was found in a file system index structure. The file reference number is 0x1300000000009c. The name of the file is “\Blizzard\Diablo IV”. The corrupted index attribute is “:$I30:$INDEX_ALLOCATION”.

1 Like
37

Same problem here since yesterday after newest Win11 update.

2 Likes
38

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.