2.80 BETA crash during rendering, even with SW openGL #62562

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35

Blender Version
Broken: version: 2.80 (sub 48), branch: master, commit date: 2019-03-13 19:14, hash: bbc3ee09e4
Worked: (optional)

Description of error
Now this is an issue I seem to have for quite some time now with 2.8.

Rendering almost any file results in crash.

This is what the console spits out last.
Error: EXCEPTION_ACCESS_VIOLATION
Address: 0x0000000052982D80 (this one seems to change)
Module: C:\Windows\System32\DriverStore}FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvoglv64.dll

As I said this issue has been happening for quite some time, which in turn means this is likely not related to the latest build.
I did however test it and it happens in the latest build as seen above.
What this also means is that this error happened over the past driver versions. 419.35 is the latest from nVidia and this has happened on past versions as well.
Driver was updated not so long ago, I think 2 weeks ago.
Edit: A full reinstall with DDU was also done.
And since I also recently got a new GPU, this happened on my former GTX 750 Ti and my current GTX 1080.

I also tried a couple of things, like running with -d or --debug-gpu, the latter actually gave it more time before it crashed which brings me to a few observations.
Main observation is that the duration it renders, while still being somewhat random, depends on what else is showing in the Blender interface.
I get the faster crashes when I have a 3d viewport open and the image editor, I get the most render time before it crashes if I replace those two with just text editor for example.
Changing those windows while its rendering often causes a crash on changing them.
That said, even after changing those two to text editors it still caused the crashed after some time.
Another observation is that the crash also likes to mess with running YouTube videos, where YT just stops playing them and goes into endless loading.

NOTE: (@iss) Crashes with factory settings. Rendering from console seems to work OK

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35 **Blender Version** Broken: version: 2.80 (sub 48), branch: master, commit date: 2019-03-13 19:14, hash: `bbc3ee09e4` Worked: (optional) **Description of error** Now this is an issue I seem to have for quite some time now with 2.8. Rendering almost any file results in crash. ![D1kt6SEXgAAVaAT.jpg](https://archive.blender.org/developer/F6818006/D1kt6SEXgAAVaAT.jpg) This is what the console spits out last. Error: EXCEPTION_ACCESS_VIOLATION Address: 0x0000000052982D80 (this one seems to change) Module: C:\Windows\System32\DriverStore}FileRepository\nv_dispi.inf_amd64_7a8e74171e1b8492\nvoglv64.dll As I said this issue has been happening for quite some time, which in turn means this is likely not related to the latest build. I did however test it and it happens in the latest build as seen above. What this also means is that this error happened over the past driver versions. 419.35 is the latest from nVidia and this has happened on past versions as well. Driver was updated not so long ago, I think 2 weeks ago. Edit: A full reinstall with DDU was also done. And since I also recently got a new GPU, this happened on my former GTX 750 Ti and my current GTX 1080. I also tried a couple of things, like running with -d or --debug-gpu, the latter actually gave it more time before it crashed which brings me to a few observations. Main observation is that the duration it renders, while still being somewhat random, depends on what else is showing in the Blender interface. I get the faster crashes when I have a 3d viewport open and the image editor, I get the most render time before it crashes if I replace those two with just text editor for example. Changing those windows while its rendering often causes a crash on changing them. That said, even after changing those two to text editors it still caused the crashed after some time. Another observation is that the crash also likes to mess with running YouTube videos, where YT just stops playing them and goes into endless loading. NOTE: (@iss) Crashes with factory settings. Rendering from console seems to work OK

Added subscriber: @Mitsuma

Added subscriber: @ZedDB

Does this happen with cycles or just eevee?

I can confirm that this also happens in Blender 2.8 with Cycles.
2.79 seems stable with GPU rendering from a test I'm currently running which already went through 800 frames in the past 8:30min.

Added subscriber: @LazyDodo

can you run blender_debug_gpu.cmd in the blender folder, reproduce the issue and attach the files it produces?

Here is the Log with Cycles in 2.8.
Quite big because it did render a bunch.
28_cycles.txt

Here is the Eeevee one.
This one actually crashed right as it started (after skipping last rendered frame)
28_eevee.txt

Forgot you might also want the system info file so here is from the last one with eevee:
blender_system_info.txt

Do you get crashes if you render without gui (the -b flag)?
https://docs.blender.org/manual/en/latest/render/workflows/command_line.html

In #62562#640481, @ZedDB wrote:
Do you get crashes if you render without gui (the -b flag)?
https://docs.blender.org/manual/en/latest/render/workflows/command_line.html

It did render fine with console only using eevee in a first test, which was the rest of my original scene. (~12k frames)
I always forget how much faster that is, even on windows. (Save time and render time were a lot quicker.

Kinda lines up with my observation that playing with the UI while rendering can cause a quicker crash.

Does it crash with GUI if you force software rendering?
Download this dll and copying it so its located in the same directory as 'blender.exe' and run Blender normally.

It will be slower but I just want to check if it crashes the same way.

Can confirm that the GUI was slower, like the camera was slower.
The rendering times per frame seemed to be on par with before though in Eevee.

It crashed after 30 frames in my first test.

Just to provide additional info, I made a quick recording of a test, this is still with the .dll file inside, which is why its a bit slow.
2019-03-15_10-36-54.mp4

Does it crash if you use the default settings? You seem to run with some non standard things.

I already reset the usersettings (basically deleting the 2.80 folder in appdata, besides the two addons), in terms of non-standard things there would only be Animation Nodes addon and my small little render button addon.
I did once test removing the my own addon and nothing changed.
Don't think that can cause anything but I will admit its a hack copy/paste job from 2.79 over to 2.80 and I have little clue about python really.
https://github.com/Mitsuma/Blender2.8-RenderButton/blob/master/AddRenderButton.py

I will however do a test with all removed and all settings reset again.
Not sure if any of those two addons could actually cause this issue, although I know this might not be the place for support regarding those addons, well one being my hackjob.

Okay, I think we can eliminate those two addons.

I fully deleted the AppData\Roaming\Blender Foundation\Blender\2.80 folder to reset all user settings, addons and startup file.
On startup I did not let it load 2.79 settings.
I just hit save settings how it is by default on the first screen.
Made a new test scene:
28base.blend
Very simple one, just a sky background, 1 sample, enabled Ambient Occlusion and set a render output.
I split the main view to open a image editor window.
Everything else should be default from the default scene.

And then I just let it render the animation, crash after 1388 frames here.

blender_system_info.txt

blender_debug_output.txt

In case the debug logs are useful again, those are from running the blender_debug_gpu.cmd again but with the complete reset Blender and the test scene from the last comment.
Seems like it doesn't even show the error, in some of the crashes I recorded the error also did not show up at the end, not sure if it just crashes faster then it can log, or how that works.

Added subscriber: @AtomP

I would like to confirm that I am getting regular random crashes when using CTRL-F12 to render my animation. I can play the animation, fine in the viewport.

Using today's build, 06/10/19

When I screen captured the log, I was able to review the screen capture and pull out the last displayed message, an ACCESS_ERROR_VIOLATION Address: 0x000000013FB79AFF

NOTE: I get the crash with denoising both on and off.

Added subscriber: @TheRawMeatball

Added subscriber: @Tareyes

Added subscriber: @MasterJames

I've been getting green flicker with latest NVidia drivers and then also this same crash will occur.

Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000064E9957A
Module  : C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_fd332b7c7ad5fe7e\nvoglv64.dll

GeForce RTX 2080 Ti Driver: 26.21.14.3602 aka 436.02 Date: 2019-08-16

I get the same error in Cycles in 2.8 when having multiple 3D views open at the same time. If I keep open just one view open it doesn't crash. Also running it GUI-less, it doesn't crash.

I'm running a Ryzen 5 2600 and GTX 1060 3Gb

Added subscriber: @iss

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

@Mitsuma is this still an issue with latest build?

Added subscriber: @ideasman42

@ideasman42 Can you confirm this report?

Misunderstanding on new policy, set back to report.

Added subscriber: @foobarbecue

I also have this, using 2.81a and 2.82b, on cycles. Happens with GPU rendering, CPU rendering, combined, and with CUDA disabled.

blender_system_info.txt

blender_debug_output.txt

I've switched to rendering in headless mode. Without the GUI, it works great and I never get this error.

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Added subscriber: @NoHow

Hi all,
it sounds to me like the common problem with heavy GPU computation under Windows.
There is a windows feature called Timeout Detection and Recovery (TDR) which complete resets the GPU after 2sec of freezing (GPU is unresponsive)!
SubstancePainter had the same problems and they wrote a nice tutorial on how to change the "TdrDelay" in the windows registry.
https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html

Hope that fixes your problems. ;)

Ahh, i forgot... it surely applies to cycles rendering too!

Added subscriber: @brecht

It's documented in the Cycles manual:
https://docs.blender.org/manual/en/dev/render/cycles/gpu_rendering.html#the-nvidia-opengl-driver-lost-connection-with-the-display-driver

But, generally when TDR happens Blender should not crash with EXCEPTION_ACCESS_VIOLATION, just abort rendering. And I believe that if TDR happens, Windows will show a popup saying that the driver timed out.

I'm running Win7 64bit and had this problem with MeshRoom. There was no popup with the 'driver time out' mentioned, just a message saying 'MeshRoom stopped working'. Maybe it's different on Win10 or it's related to the MeshRoom architecture,

I looked at the cycles documentation and it feels somewhat 'hidden' to the technicaly unexperienced user.
I can imagine that the linked Microsoft document can throw off some/many users.

Maybe a FAQ entry with a link to a better description on how to fix that would be better?
Something like 'Blender crashes randomly, what could i do?'

The SubstancePainter team did a great Job on describing the problem and providing a step by step tutorial on how to change the registry:
https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html

Just my 2cents

Added subscriber: @TITAN.blender

Hi I have downloaded and installed Blender 4.1 but it will shut down automatically until I open it Thanks for helping me

Sorry Blender 2.8

In #62562#891617, @TITAN.blender wrote:
Hi I have downloaded and installed Blender 4.1 but it will shut down automatically until I open it Thanks for helping me

Please make new report if you have unrealated problem to this topic. https://developer.blender.org/maniphest/task/edit/form/1/
Please follow all instructions there mainly please check if bug is already reported. If it is, you can just subscribe to that report and wait until it is resloved.

No This is a new problem

I don't think it's the TdrDelay thing. I have already modified my registry for Redshift on this matter. It's definitely a Blender bug.

Added subscriber: @Ryan-Stever

I agree with Atomic, I have already done this Tdr thing and I still get this problem. However, I wouldn't blame it on Blender either.

This has been happening to me ever since 2.8 came out so as a result, I gave up on Blender started to look at premium software to solve this issue, but guess what? It happens to me with C4D as well. fml
It doesn't happen to me with Sub Painter or Fusion360 but unfortunately those tools don't help me for rendering.

My uneducated conclusion is - upgrade my pc.
I'm using a dinky Ryzen 5 1600 with a RTX 2070 and apparently my mobo and cpu are not compatible. So, Im grabbing a new cpu and mobo today. Fingers Crossed.

Added subscribers: @fclem, @rjg

The triagers are currently in the process of cleaning up old tickets. This ticket is currently tagged as Bug, but so far this hasn't been confirmed. The comments may not all refer to the same issue. @fclem Is the current tag of "Bug" correct and are there enough information / a known cause for this problem that the ticket could be confirmed?

Removed subscriber: @Tareyes

@Mitsuma I am updating old reports so they are more searchable, and I want to ask if this is still issue for you, since a lot of time has passed, it is possible this has been resolved.

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

It was a hardware issue. I think I suggested there be better ways to detect if it's a hardware problem like a response in a reasonable time etc. so you could still be doing something even though I will set this to invalid as it was not really a Blender code error. It was a new 2080ti at time time clearly rushed out before getting it right, so a nvidia hardware production issue?

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

2.80 BETA crash during rendering, even with SW openGL #62562