Linux report:
Manjaro Linux here and GTX 1060 6GB:
Problem is HERE with nvidia 495.xxx drivers.
The problem is GONE with Nvidia 470.86 driver.
With AMD RX card + open source drivers = no problem at all.
I try with Steam-Proton, Wine-lutris, with all are the same.
Only workaround with newer drivers, was to disable AA and lower texture quality to MEDIUM and lower, then glitches will gone. All other options does no efect.
With HIGH and above, texture glitches will appear.
I have it too, even worse than the flickering, I do have complete black boxes, where only dropped items are visible. Canât post pictures in here unfortunately, some areas are just unplayable for me.
Switching to older drivers does not work for me, D2R did not start at all with older drivers. But switching o legacy-view I will try. Since I am using a surface Pro, I was not expecting too much, itâs kind of sad anyway. D3 is running smoothlyâŚ
Happening to me as well. I rolled back to NVIDIA GeForce Game Ready 472.12, and itâs much more stable, but crashed again a short while ago. The blz-log.txt file abruptly stops at 2/7 19:57:09.289, and Windows is showing both system and application error events at 19:57:30.
System log:
Display driver nvlddmkm stopped responding and has successfully recovered.
Application log:
Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere, type 0
Event Name: LiveKernelEvent
So something killed the driver and it took about 20 seconds to recover.
Starting to think there are two separate things going on (for me, anyway): The texture problem, which the driver rollback seems to have resolved, and then the instant crash problem, which might have been happening occasionally before I rolled back, only I thought it was more of the same thing.
Funny enough the exact same issue seems to happen when emulating on linux wine.
So it seems to be specific to NVIDIA and not windows related.
Big black boxes that flash around:
Havenât noticed any other problems. Kind of spooky to deal with in hardcore though.
Same issue here, driving me nuts⌠Sometimes stable, sometimes gives me hell (pun.)
Event viewer shows me error 4101 âDisplay driver nvlddmkm stopped responding and has successfully recovered.â
This only happens in Diablo 2 Resurrected.
I tried;
Reinstall OS (it was new but w/e) - Windows 10
Remove overclock, underclock, add more voltage and do a load of stability tests on the system components (its a new system but regardless)
Install different Nvidia drivers from 471 and up as I read 471 is stable in this thread
Removed all background programs and/or disabled them where possible
Nothing helps.
This seems to be an issue with the graphics overlay over the old D2lod running underneath which causes the graphics driver to go into timeout. The error above points into that direction.
This is something that Blizzard has to sort with Nvidia because so far I see nobody with an AMD card having this type of error where the OS will just restart your graphic card due to lack of response causing the game to CTD.
im still suffering with this issue now as of march 2022, only time i get black boxes is in the throne room act 5, but there is definitely an issue with lightning skills triggering a darkening, like my light radius just lost about 10 yards, i use portal to town, then go back in and everything is light again, very strange
Hey, after some abstinence i recently got back into playing D2R.
Like 2 or 3 days ago, the game randomly keeps crashing without an error - described by other players here in the thread. Most of the time, iâve seen the âblack boxesâ stuttering on the screen before. Especially when there were many effects like hydras, blizzard and poison nova from my merc were flying around at the same time.
My nvidia driver is up to date with the version 512.15.
Never experienced crashes like this before. 
Edit: My Rig: Windows 10 Pro
Nvidia Geforce RTX 3080
Driver Version 512.15
AMD Ryzen 9 5900X 12-Core Processor
32 GB RAM
Res: 1920 x 1080. 144 hz
Hi there,
Just to say that I was a tad disappointed right after the 2.4 update a week ago when this inconvenience was still there (albeit in a really reduced form, the squares appeared only one frame long, which is not very nice for people sensitive to epilepsy, but it was not my case so⌠it was just a bit bothersome).
However, I was glad to notice that, after the update from yesterday, Iâm unable to see black square anymore (Act II, IV and the worldstone keep in Act V).
A big thanks for this fix 
(at least on my side).
â Chouhartem
My configuration:
Here too. Linux, nvidia driver 510.54. I know earlier versions work, but other things are broken when I use those versions.
Still bugged for me. I have a similar configuration, but with Intel and Nvidia hardware.
Configuration:
So ever since the new ladder Iâve noticed Only in Baals throne room as Iâm killing waves sometimes it happens sometimes it doesnât, these black boxes form on the waves and then my game closes, no error, nothing. Is anyone else experiencing this? I play pc Windows 11 3070 TiâŚ
Yes, still happening to me as well. It seems like the crash isnât happening anymore? But the artifacting is as rampant as ever.
One thing I noticed recently is, around the point where the game client used to crash, now just the lighting changesâlike the screen gets way dimmer (a light source/layer shuts off, or something). I think itâs very specifically about how D2R manages ambient light vs VFX light.
I have these artifacts too
After experiencing this on my EndeavourOS rig with the v495 & v510 drivers, I was hoping that the v515 drivers would finally squash this bugâŚand of course, it didnât; maybe even worse now.
I have the same issues mainly in A4 (sometimes at start on character screen) on Manjaro.
Amd r5 3600, gtx 2070 super
kernel 5.15 with matching driver
lightdm, i3wm, picom
I think this is even worse than before, I barely see anything of act 4.
I have the same issues with two of my linux laptops , one Fedora , other is Gentoo.
Fedora laptop is intel 7700hq + 1060 mobile
Gentoo laptop is intel i9-11900H + 3080 mobile
On Gentoo laptop I checked differant nvidia drivers, and it seems to be driver dependent : black boxes occur on 510.73.05-r1 , 510.85.02 , 515.65.01
but did not occur on 470.141.03
Friendly reminder that this remains not fixed. Have tried multiple drivers, multiple power settings, multiple clock settings, with clean and test in between. Also multiple in-game graphics settings, from lowest to highest. Nothing makes any difference. Itâs definitely the game, and specifically (would bet money on it) how the game handles lighting.
Artifacting always occurs around lighting-intensive vfx. At the throne, sometimes instead of crashing, the environment goes really darkâas though one of the primary lighting layers faulted out. Whatever was done around artifacting and lighting in the previous patches was not enough.
Havenât seen a blue acknowledge this thread since the suggestion last October to bug-report it. I intend to submit a bug report every single time I see artifacting until blizz acknowledges it is a real problem.
All right besties, after nearly a year of trying to fix this, I think I figured it out. Still way more testing to do, but I just did about a dozen Shenk catapult storms with gfx settings maxed and zero lagging or crash. Likewise multiple WSK/wave runs wearing dual forts and throwing lightning everywhere, zero artifacting. This was at 3440x1440 and ultra settings.
The solution for me was to disable dynamic power scaling on my graphics card. I locked it at 1 volt, 1890 MHz. The problem is, as weâve all pointed out, D2R doesnât actually need a top-shelf rig. Clock speeds and core temps are low during normal play. But sometimes, like when a bunch of skeletal mages drop on you and all throw ice bolts in the middle of your blizzard, or 11 council members pop hydras on your head and your chilling armor is shooting back, suddenly you need waaay more power. My card appears not to be able to handle the power scaling at the pace D2Râs vfx require. See this YouTube about power-scaling problems with 3080s: RTX 3080 Problems FIXED, no crashes step by step guide - YouTube
In that video, youâll see the creator talking about setting your max voltage to get a line past which the power wonât scale. Thatâs essentially the same as undervolting, and I tried that multiple times with no improvements to the D2R crashing. But the thing is, with typical undervolting, you pick a point on the curve and set max voltage to have a straight line (power-wise) going rightâlocking max hertz and voltage. Left of the undervolt point is still a curve. And this is where the fact that D2R is a puppy comes in. D2Râs normal power needs are so low that, even with undervolting, the jump between normal play and the undervolt limit during something like a Shenk kill is so great that it was enough to crash my cardâlike, half a volt, 90-ish watts, and 1500 MHz.
So instead of undervolting with a curve, I locked my card at 1v. D2R runs like a dream now. And it makes so much sense that I never had artifacting with my old 1060: It was a weaker card and was always running at a higher baseline, so the vfx werenât causing some crazy power fluctuation sine wave.
I have a GeForce NVIDIA RTX 3070 Ti. If you have a similarly robust GPU, and youâre artifacting/crashing, it might be because your card is too powerful. Try to force D2R to play at a fixed voltage and see if it helps. gl
Itâs the second time my game crashes upon ACT V, throne room and before it happens a few black squares pop up on top of the mobsâŚ
Glad you found a fix for a high-powered card. But my 1070, which is very similar in performance to your 1060, has been affected by this since the beginning. I think if GPU prices ever stabilize I may have to switch to AMD.