Page MenuHome

Cycles viewport crash when switching to "Rendered" mode.
Closed, InvalidPublic


System Information
Operating system: Windows 7 SP1 64 bit
Graphics card: Nvidia GeForce GT 740

Blender Version
Latest 2.8

Short description of error
When switching in attached file to Rendered mode in Cycles - Blender always crashes at the "Updating Integrator" or 1-st frame render, screen goes black for several seconds and error pops up
"Nvidia windows Kernel Mod Driver, version 436.30 stopped responding and was succesfully recovered".

Exact steps for others to reproduce the error
In attached .blend file just switch to Rendered mode - and it will crash.

P.S. Most probably it's due to too high values in Noise texutre in material/World nodes, also adding a floor under a screwd cube in some attempts caused crush (when i've tried to clean it as much as possible).

UPD: Lowering Clipping End from 1000m to 100m helped, also, looks like the whole problem was in Screw modifire on the cube - by increasing values in it it crushed again even at lowered clipping distance!

  1. Deleting materal from plane with bricks prevent crushing; (prevents = switching to Rendered mode after this step no longer crushed Kernel driver and Blender with it)
  2. Deleting node "Noise texture" in World shading also prevents crushing;
  3. Deleting cube with Screw modifre also prevetns crushing.



Event Timeline

Philipp Oeser (lichtwerk) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Mon, Sep 23, 12:42 PM

Cannot reproduce here [linux, 970m, 435.21 drivers].

Just to make sure:

  • Please download the latest build from
  • Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

Please report back if this changes anything.

Zeraun (Zeraun) added a comment.EditedMon, Sep 23, 4:42 PM

It works on both Latest Build and on 2.8 with factory settings;
It's due to the fact that Factory Settings uses only CPU for rendering. On both versions switching to this Render setting fixes the crush issue;
However, current and Latest Build both crushes on the "GPU COMPUTE" device setting in the Scene tab when my Grpahic card is switched on in Edit-Preferences-System-Cycles Render Devices-CUDA .

So: CPU works, GPU Crushes.
(Remind: it's "Nvidia windows Kernel Mod Driver" who is to blame, most probably. No wonder that switching GPU Compute off stops him too, and makes everything work well)

Most likely a limitation of GPU computing indeed, we'd need to know your driver version though, and please ensure that it is the latest available from official nvidia website.

You can also launch Blender from the command line with --debug-cycles option and attach as text file here any error printed out in the console (do not paste it directly in comment).

Zeraun (Zeraun) added a comment.EditedWed, Oct 2, 3:48 PM
  1. Yep, i'm using latest driver version; GeForce Game Ready Driver, version 436.48, release date (Month/Date/Year) 10.1.2019
  1. After spending half an hour searching for "what is --debug-cycles" i surrendered. A step-by-step guide for dummies, please, i am not a programmer, nor found any understandable guide on how to do it.

UPD: learned how to start blender from CMD, but sill no idea how add --debug-cycles (

Don’t want to be rude, but seriously… will give you all you need to know in the two or three first answers…

There's people in the world who never really used CMD, and i'm one of them. This commands tells NOTHING on how and in which order they should go;
However, after reading about CMD itself and one more half an hour later i figured all out, here's the .txt file with all that console recorded:

Bastien Montagne (mont29) claimed this task.

OK thanks, that looks like it’s confirming that you are just hitting the limits of your GPU here, GT 740 is a pretty low-level entry one from 2014, with only 1GB of memory… It won’t make miracles. You can follow the link given at the end of those messages (, but this probably won't help much in that case.

Anyway, no bug here, just your hardware limitation.

It's 2 GB actually, but anyway - thanks for claering things up, will jsut render at CPU if GPU crushes.