hello, for me installing the latestgame ready drivers instead of the studio drivers (471.41 - WHQL) solved the issue for now.
older studio drivers also produced the same problem for me here.

hey i have the same issue with eevee on nvidia studio drivers. started today after i installed the latest studio drivers from nvidia. very annoying. its definately a nvidia driver issue, since it literally wasnt there 10 minutes ago.

Could this be related to the GPU memory being hit at maximum on the GTX1050? Is there a way to know the used graphic memory at the moment of the crash? This card is being rated at 2GB of VRAM...

For any other poor souls who end up on this page, I had the same problem and fixed it by downloading the latest driver from the AMD website. Windows update and the "update driver" button in Device Manager did nothing. For what it's worth, I selected the "factory reset" option in the AMD installer, although I doubt it matters.

Sorry for the silence; I was hospitalized recently

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Hi @Jose (Neko-san), is this still a problem for you in recent releases like 2.93.0 and when using recent nVidia drivers (version 460 onwards)?

I'll assume it's solved then, if it comes back we can reopen the report.

Have you tried to switch off the viewport denoising when using the rendered preview?

In T84461#1170898, @Philipp Oeser (lichtwerk) wrote:

After Brechts comment: just checking if this is still an issue?

Checking to see if there was ever a solution to this.. I updated my drivers , rolled them back , and updated again.. Nothing fixed.. it did change at one point from atio6axx.dll causing the issue to ntdll.dll that caused the crash, but now its back to atio. This is very frustrating. I have tried multiple different versions of Blender.. Oh and it was working just fine this just started randomly one day (nothing changed) , but it seems to be effecting not only blender but sketchup as well as nanocad!..

@Philipp Oeser (lichtwerk) , check T88521#1165792 (Author of the ticket said the problem is fixed in 3.0.0)

After Brechts comment: just checking if this is still an issue?

@Nelly (nellsterr) can you report your exact device detail. This is stored inside the system-info.txt file that can be generated from Blender's help menu. I will see if we have added this device to the whitelist.

I'm still facing the same problem after 4 months.. Has anyone found a solution? My driver version: 21.3.2 (Up to date). I want to get version 20.11.3 but I don't know how I can roll back to that version as I never had it installed. If anyone could send me an installation file for it?

@Nelly (nellsterr) , I would suggest Render properties -> Preformance -> High Quality Normal . This will fix the problem for me (but this should not be the permanent solution)

Have there been any mesa updates that fix this ?
Still, upload the blender help menu -> save system info text file in the top level description.
I think we can confirm this since there are two reports with easy to redo steps.

This may have been worked in around in rB3e472d87a8d1: Cycles OpenCL: disable AO preview kernels, which solves an issue that could happen specifically in the viewport.

Im not shure what Number my drivers are exactly but i have installed from 2 Days the newest so it should be the newest driver

@Florian Kamenz (HEYPictures) , Did you try the version of the nvidia driver @jw (jw) are using or an even newer version?
You write here the versions of the driver that you are testing and with which you still reproduce the problem.

I have the same problem with a Radeon (TM) R7 M340. using Adrenaline 2020.

@jw (jw) I mean the Rendersamples over 1000 than you have a better Chance to see Artifacts (not in every frame) try with a Sequenze with 15 frames. Than you should see.

In T77202#1148463, @Florian Kamenz (HEYPictures) wrote:

@jw (jw) Its definitely still there. If rendered the scene ones more and its even worse.

@jw (jw) Its definitely still there. If rendered the scene ones more and its even worse.

In T77202#1148170, @jw (jw) wrote:

Hi, I've tried to reproduce this today with

• Windows 10 w/ latest NVIDIA studio drivers (462.31-desktop-win10-64bit-international-nsd-dch-whql.exe)
• Blender 2.92.0
• RTX 3090

I see no artifacts in any of the 150 frames (bloom enabled, 256 volumetrics).
I also tried the oldest readily downloadable versions of Blender (2.83.12) and nvidia drivers (game-ready flavour this time, 456.55-desktop-win10-64bit-international-whql.exe), and I don't get any artifacts with that combination either.
If this still happens for you, can you please specify which versions you're using nowadays and confirm that updating doesn't fix it?

Hi, I've tried to reproduce this today with

• Windows 10 w/ latest NVIDIA studio drivers (462.31-desktop-win10-64bit-international-nsd-dch-whql.exe)
• Blender 2.92.0
• RTX 3090

@YAFU (YAFU) I have absolutely not an Idea if i done the Report right. And the only reaction from Nvidia was yesterday. They have asked if it is still a Problem.

@Christophe Leyder (shotalot) , Does that mean that you can reproduce the problem with the .blend file on the first post of the report? What is your graphics card?

In T77202#1094766, @YAFU (YAFU) wrote:

Just out of curiosity, has anyone reported this to nvidia?

Apparently it is a Windows problem only.

The macOS version (10.12) is now no longer supported.
Since the author didn't reply for over a week. closing.

I still have this problem, if that helps.
(Sapphire Pulse) RX 5700 XT (with driver version from adrenalin 21.3.2); Blender 2.92; Default scene, viewport just won't work. Although, rendering will work.
EDIT: I still have this issue with the Adrenalin version 21.4.

The issue still occurs. Tested with Blender 2.93 hash 09d7d88cc42a and Blender 2.92. Here is a screen capture in case it's helpfull. I have 2 GPUs and for the test purpose I disabled one of them in the preferences.

The problem is still present for me in both 2.92 and 2.93 Alpha 09d7d88cc42a

I was able to replicate the problem the first time today with the Default Cube.

Split kernel error: failed to load kernel_holdout_emission_blurring_pathtermination_ao

But after the kernels compiled again when reloading the file, the problem disappeared.

Can anyone confirm that they still have this issue? I got no clear replies so far. I can't reproduce any issue with my RX 5700 XT card with latest master.