Windows 10 Pro Workstation becomes unstable during Cycles Render (Blue screens or Freezes)
Closed, ArchivedPublic

Description

System Information
Operating system and graphics card

Windows 10 Pro
64 bit
Version 1607
OS Build 14393.1358

Processor: Intel Core i7-6700K CPU @ 4 GHz
Installed Ram: 32 GB

Graphics Cards
Two NVIDIA GeForce GTX 970
Driver: 23-Feb-2017 21.21.13.7878

Update: Downloaded and applied the latest drivers for NVIDIA GTX 970
Driver version 27-Jun-2017 22.21.13.8476

No change after the update.

Blender Version
Broken: 2.78c 2017-02-24 14:33

Workstation immediately becomes unstable when using Cycles Render.

Exact steps for others to reproduce the error

  1. Open any tutorial files from the "Introduction to Materials" course from PluralSight course. This is a fairly simple scene.
  1. Regardless of the Cycles Compute Device setting under Blender User Preferences (May be set to None, CUDA with one GTX 970 selected or CUDA with both GTX 970 selected-render produces instability with any of these settings)

    Render with Cycles makes the system unstable. Often producing the blue screen: Gathering Information... or extremely slow response.
  1. Follow the course instruction - as soon as Cycles Render engages, the workstation becomes unstable.
  1. No instability encountered if I use CUDA to leverage Mathematica on the same workstation or a VS 2017 project.

Details

Type
Bug

Hi I enconter similar issues.
I'm using windows 10 1703
Try enabling open shading language under render settings. Let me know if that helped.

Hi Peter - will try that. Is this a setting under File | User Preferences?

It is there:


Whenever i try render without enabled OSL Blender freeze on shaders updating for around 5 minutes.

Try removing the display driver with Display Driver Uninstaller and install just the display driver without any extras. Worked for me.

Thank you, I will try these suggestions and report back!

Can you try dropping opengl32.dll from http://download.blender.org/ftp/sergey/softwaregl/win64/ into your blender folder and see if the stalling goes away? (remove once you are done testing cause it will slow things down significantly)

can you also attach a file to reproduce the error? If it's not reproducible on other PCs, you may have installed the same update as https://developer.blender.org/T52064.
In the enterprise I work for, all windows 10 machines are unstable at least once a weak, windows 7 is nearly impossible to crash.

Hi Matali23 - yes I will upload the file. I have been discussing this with one of our hardware gurus at my workplace. He offered some recommendations:

  • Make sure the latest nVidia drivers are installed. I did this using drivers downloaded from nVidia (not the drivers recommended by Windows 10 Update). This had no impact on the problem.
  • Disable Node Interleave in BIOS. I will try this if I can find it in BIOS...
  • If disabling Node Interleave does not work, disable VT-D in BIOS

The Windows 10 BSOD Errors are HYPERVISOR ERROR and only occur if I use Blender Cycles on my Windows 10 machine with two GTX 970s. No error occurs on Windows 7 or Windows 10 machines that do not have the GTX 970s.

Bastien Montagne (mont29) closed this task as "Archived".Wed, Jul 19, 11:22 AM
Bastien Montagne (mont29) claimed this task.

Well… This is most certainly related to a specific hardware/driver/OS/software combination… Afraid we cannot help here really, feel free to keep communicating here if you manage to find more, but until there are some solid elements showing there is indeed a Blender bug involved, will close the report.

This is probably a hardware and configuration issue related to NVidia GTX 970 boards.

Disabling VT-D in BIOS did not remedy the problem.

Would ask anyone with a configuration using GTX-970 with success to share details of their configuration.

The working theory from my hardware gurus was that the Blender Cycles is stepping on node interleave. However, if I disable in BIOS, I still have the problem on a machine with two GTX-970s.

For a machine with no GTX-970s - no problems what-so-ever.