Render preview in Cycles freezes Blender 2.74 when using both GPU cores #44933

Closed
opened 2015-06-03 00:02:32 +02:00 by TravLR · 10 comments

System Information
Ubuntu 15.04 64-bit, PC - Gigabyte 990FXA-UD3 Rev. 4 motherboard, AMD FX-9590 CPU, 16GB DDR3 1866mhz RAM, 2x Nvidia Geforce GTX 660 graphics cards

Blender Version
2.74

Short description of error
When I try to use both Nvidia 660's I have in my PC (by selecting "Geforce GTX 660 (2)" in the Compute Device of User Preferences), the program freezes during render preview (Pressing Shift+z) almost immediately, with only the checkerboard background displayed. If I select the top "Geforce GTX 660", preview and render runs fine. If I select the bottom "Geforce GTX 660", it freezes. If I select the very top option "Geforce GTX 660(2x)", it freezes. Still image and final/video rendering works great -- uses both GPU's and cuts render time in half. It is only during render preview that this happens.

Exact steps for others to reproduce the error

  1. Create new blender project.
  2. go to User Preferences > System > Computer Device, then choose "Geforce GTX 660 (2x)"
  3. Close User Preferences
  4. Press Shift+z or go to Viewport Shading > Rendered.
  5. EFFECT viewport shows checkerboard background, but application freezes and becomes unresponsive, requiring it to be force closed.
**System Information** Ubuntu 15.04 64-bit, PC - Gigabyte 990FXA-UD3 Rev. 4 motherboard, AMD FX-9590 CPU, 16GB DDR3 1866mhz RAM, 2x Nvidia Geforce GTX 660 graphics cards **Blender Version** 2.74 **Short description of error** When I try to use both Nvidia 660's I have in my PC (by selecting "Geforce GTX 660 (2)" in the Compute Device of User Preferences), the program freezes during render preview (Pressing Shift+z) almost immediately, with only the checkerboard background displayed. If I select the top "Geforce GTX 660", preview and render runs fine. If I select the bottom "Geforce GTX 660", it freezes. If I select the very top option "Geforce GTX 660(2x)", it freezes. Still image and final/video rendering works great -- uses both GPU's and cuts render time in half. It is only during render preview that this happens. **Exact steps for others to reproduce the error** 1. Create new blender project. 2. go to User Preferences > System > Computer Device, then choose "Geforce GTX 660 (2x)" 3. Close User Preferences 4. Press Shift+z or go to Viewport Shading > Rendered. 5. *EFFECT* viewport shows checkerboard background, but application freezes and becomes unresponsive, requiring it to be force closed.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @TravLR

Added subscriber: @TravLR
Sergey Sharybin was assigned by Bastien Montagne 2015-06-03 09:54:32 +02:00

Added subscribers: @mont29, @ThomasDinges, @MartijnBerger

Added subscribers: @mont29, @ThomasDinges, @MartijnBerger

Does final render with progressive refine works fine for you? Does setting tile size to 1024x1024 makes final render to stuck?

Does final render with progressive refine works fine for you? Does setting tile size to 1024x1024 makes final render to stuck?
Author

Sergey,

Confirmed, both final render with progressive refine checked works without issue, and setting the tile size to 1024x1024 works fine without issue. Final render doesn't seem to show any signs of problems. It's only when I use preview render in the viewport that I get the checkerboard background and Blender freezes. Mind you, this only happens when I select it to use both GPU's on my machine, or when I select the bottom GPU only. Selecting the top GPU works fine, but it cuts my rendering capability in half because I'm only using 1 of 2 GPU's in my system.

Sergey, Confirmed, both final render with progressive refine checked works without issue, and setting the tile size to 1024x1024 works fine without issue. Final render doesn't seem to show any signs of problems. It's only when I use preview render in the viewport that I get the checkerboard background and Blender freezes. Mind you, this only happens when I select it to use both GPU's on my machine, or when I select the bottom GPU only. Selecting the top GPU works fine, but it cuts my rendering capability in half because I'm only using 1 of 2 GPU's in my system.
Author

I also swapped the graphics cards around to see if perhaps one of them was defective. Even with them switched, I got the same result: choosing the bottom GPU froze Blender during render preview, but choosing the upper GPU worked fine. I know it's also not defective PCIe ports, because SLI works fine in games on the Windows side, and Blender renders using both GPU's without issue.

I also swapped the graphics cards around to see if perhaps one of them was defective. Even with them switched, I got the same result: choosing the bottom GPU froze Blender during render preview, but choosing the upper GPU worked fine. I know it's also not defective PCIe ports, because SLI works fine in games on the Windows side, and Blender renders using both GPU's without issue.
Member

Added subscriber: @Blendify

Added subscriber: @Blendify

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Neither of the developers or artists around here can reproduce the issue. It's likely something to do with particular hardware configuration. It might be a good idea to check if someone from blenderartist had similar problem.

Also, now when you're mentioning SLI -- you need to disable it. It might easily cause issues with Cycles.

So thanks for the report, but archiving for until someone from the developers can reproduce the issue.

Neither of the developers or artists around here can reproduce the issue. It's likely something to do with particular hardware configuration. It might be a good idea to check if someone from blenderartist had similar problem. Also, now when you're mentioning SLI -- you need to disable it. It might easily cause issues with Cycles. So thanks for the report, but archiving for until someone from the developers can reproduce the issue.
Author

Understood. Appreciate the open communication. I'll test once 2.75 has officially been released to see if the problem still occurs then. :)

Understood. Appreciate the open communication. I'll test once 2.75 has officially been released to see if the problem still occurs then. :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#44933
No description provided.