Page MenuHome

Blender cycles Render with GeForce 1080
Closed, DuplicatePublic

Description

System Information
windows 10, nvidia gtx 1080. GeForce driver 387.92

Blender Version
Broken: 2.79
Worked: (optional)

Short description of error
Blender closes if cycles render is activated with GeForce 1080
Exact steps for others to reproduce the error
With standard Blender startup file:
Try to activate cycles render > Blender closes
Try to go to user preferences>System > Blender closes

Details

Type
Bug

Event Timeline

Sergey Sharybin (sergey) triaged this task as Needs Information from User priority.

Just tried on freshly updated Windows 10 (with all updates from October) and same NVidia driver version (did a clean-install using installer from nvidia site) and can not reproduce the issue.

Please run blender.exe from command line (cmd.exe) with --debug-cycles command line argument. Make blender to crash and attach the full log (as a file) here. That could give some extra clues.

ok i will do that. have access to that pc tomorrow.
It happens with a GeForce 1080. I have 2 other PCs with other Nvidia cards and there evrything works fine.

That's probably unrelated, this sounds more like T52064, which was a corrupted Nvidia driver installation. This can be verified by checking if another program like CUDA-Z crashes as well. In the latest builds from https://builder.blender.org/download/ we now avoid crashing for that case (which may be the same as this report, but not sure). But GPU rendering still won't work.

I suggest a totally clean driver install:

  • Uninstall any NVidia, AMD and Intel graphics drivers
  • Download latest driver from nvidia.com
  • Install, with clean install option checked
  • Reboot computer

ok thnx. will do that tomorrow as soon as i have access to that machine.
I will also install and try with cuda-z
I use Touchdesigner heavily on that machine, and that works well. And TD make massive use of the graphics card.

What I did

  1. Run cuda-z on unchanged pc - successful. No problem (strange)
  2. removed all nvidia drivers
  3. Installed all nvidia drivers as fresh installation
  4. Run Blender, changed from blender render to cycles render. Rendered an image>sucessful

Thank you, please close this bug

Brecht Van Lommel (brecht) claimed this task.

Great, closing the bug then.

knut lagies (knutL) reopened this task as Open.Oct 27 2017, 12:40 PM

The exact same problem is back again. Was a few days away from my machine. Today try to render in cycles:
Problem back exactly as described above.
Re-installed all nvidia drivers: no success, problem stays. cuda-z shows no problems, just works fine

Started blender from cmd tool and copied cmd output (see below)
Cant find the log file: Where should it be located ?

C:\Program Files\Blender Foundation\Blender>blender --debug-cycles
Read prefs: C:\Users\knut\AppData\Roaming\Blender Foundation\Blender\2.79\config\userpref.blend
found bundled python: C:\Program Files\Blender Foundation\Blender\2.79\python
I1027 12:26:40.247156 11508 blender_python.cpp:186] Debug flags initialized to:
CPU flags:

AVX2   : True
AVX    : True
SSE4.1 : True
SSE3   : True
SSE2   : True
QBVH   : True
Split  : False

CUDA flags:
Adaptive Compile: False
OpenCL flags:

Device type    : ALL
Kernel type    : DEFAULT
Debug          : False
Single program : True
Memory limit   : zu

cmolcore imported with success! v1.01
I1027 12:27:39.888792 11508 device_cuda.cpp:2096] CUEW initialization succeeded
I1027 12:27:39.889292 11508 device_cuda.cpp:2098] Found precompiled kernels
I1027 12:27:40.063704 11508 device_opencl.cpp:58] CLEW initialization succeeded.

C:\Program Files\Blender Foundation\Blender>ee

Closing as duplicate of another bug. It's still a mystery why some users are having this problem, we're trying to figure it out.