Blender Crashing when switching to Cycles or trying to open the systems tab in the preferences #46637
Labels
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
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#46637
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I have searched in the forums and found quite a few similar reports, which allude to an issue with Intel OpenCL Drivers. My machine does not seem to have Intel OpenCL drivers installed.
Running Window 7 SP1x64 Enterprise
GPU - Nvidia Quadro 600, with latest drivers installed - 354.35
CPU - Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 3601 Mhz, 4 Core(s), 8 Logical Processor(s)
16GB RAM
Dell Precision #3600
Here is what i get from command prompt:
c:\Program Files\Blender Foundation\Blender>blender --factory-startup -d --debug-cycles
Switching to fully guarded memory allocator.
Blender 2.76 (sub 0)
Build: Sun 10/11/2015 10:11 AM Windows
argv- [x] = blender-app.exe
argv- [x] = --factory-startup
argv- [x] = -d
argv- [x] = --debug-cycles
read file
ordered
OBCube
OBLamp
OBCamera
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
found bundled python: c:\Program Files\Blender Foundation\Blender\2.76\python
ED_undo_push: Blender Render
I1029 17:44:29.780628 6488 device_cuda.cpp:1084] CUEW initialization succeeded
I1029 17:44:29.780628 6488 device_cuda.cpp:1086] Found precompiled kernels
I1029 17:44:29.810629 6488 device_opencl.cpp:3617] CLEW initialization succeeded.
With our IT support, we have uninstalled all NVIDIA drivers, rebooted, and did a clean install of the latest, but this did not resolve the issue.
I also tried installing blender on a colleague's workstation, with the same specs but Quadro K600 instead of 600, and it also crashes when attemting to switch to cycles or opening the systems tab in user preferences.
Changed status to: 'Open'
Added subscribers: @mont29, @AdamPreisler, @electroman, @Dimitar
#46834 was marked as duplicate of this issue
Tried the latest official build from https://builder.blender.org/download/ - blender-2.76-a15a395-win64.zip and the same issue persists.
Added subscriber: @Blendify
Added subscriber: @Sergey
Can you try setting
CYCLES_OPENCL_TEST
environment variable to NONE before running blender and see if it makes any difference?Something like this in the terminal will do it:
"set CYCLES_OPENCL_TEST=NONE" works
allows cycles to work and i can also go into the system tab of user settings
could this be somehow set in a way where I wouldn't have to start through the command prompt each time?
Alternatively, could some driver issue be causing this?
I also tested Blender on a third colleague's workstation with same configuration as my PC, NVidia Quadro 600, and the same issue occurs.
Would love to hear if there is a way to execute what Sergey suggested without having to start Blender from the command prompt each time, running, set CYCLES_OPENCL_TEST=NONE
This sounds like a driver issue which was not possible to solve from our side for some older AMD cards for example. Fixing such things would require some of the devs to be able to reproduce the issue.
Meanwhile i'll blow dust form our clinfo application which does intense logging, so we can gather a bit more information from you.
In the mean time you can make a simple .bat file that goes like:
Thanks for the .bat file definition!
Please run clinfo ftp://ftp.blender.org/sergey/clinfo/ and attach the output here.
I tried running both versions but they crash. I suspect it might be due to the fact that I have restricted admin privileges on my workstation, here at my office.
Run them from the command line and see if they give any debug prints.
It needs a .dll quick fix is to put it into the folder with
blender.exe
and run it from thereThis comment was removed by @Blendify
Even from the blender folder, run from the command prompt, it still crashes. Here is the info it produces:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
I've updated the clinfo binaries with a possible fix applied. Please download the new ones from the same location and try running them from the command line.
You might also want to test latest builds from builder.blender.org. Same fix was applied there.
The latest x64 official build from builder.blender.org still crashes following the same steps.
When trying to run clinfo downloadedfrom your ftp, I get an error saying that the program can't start because MSVCP120D.dll is missing from my computer. I also tried placing clinfo into the blender root folder, and it still outputs the same error.
Seems i've compiled it with a wrong target type (debug vs. release). Uploaded new builds, please give it a try!
clinfo crashes, when i try to run it. I get the following output in command prompt:
That's annoying.. First ever call to OpenCL crashes..
I've uploaded clinfo-workaround binaries to ftp://ftp.blender.org/sergey/clinfo/ Mind testing them as well?
clinfo-workaround-win64.exe still crashes.
Here is the output before it crashes:
Could this be somehow related to admin rights? I am in a corporate environment without admin access to my workstation.
Hard to tell, from researching the problem there are two common issues:
If you can run blender and/or clinfo as an administrator and report back that'd give us additional information.
I downloaded older x64 versions of Blender from http://download.blender.org/release. With 2.75, the same behavior as described above occurs. However, with 2.74 (and earlier versions), Cycles and the systems tab on the settings panel works.
I also, I have tested 2.76b on more workstations at the office with same specs as my machine, and they all continue to exhibit the same issues.
This is because in pre-2.75 versions OpenCL was disabled by default and crash happens on exact code which queries whether there are any OpenCL platforms installed on your system. What makes it more complicated, the crash happens inside the driver itself so we can only hope to find a workaorund from our side.
Did you test if running blender/clinfo from admin helps?
Hi Sergey,
I tried running clinfo and clinfo workaround with admin privileges, and both still crash. Additionally, I downloaded the latest winx64 build from builder.blender.org and running it as admin, it also crashes with cycles.
I also had a chance to test on a higher spec rendering workstation in the office with Nvidia Quadro K4200, and it also exhibits the same behavior.
I have also double checked and I have the latest GPU drivers installed.
Removed subscriber: @AdamPreisler
One more thing to test. Download OpenCL.dll from ftp://ftp.blender.org/sergey/cl-icd/ and put it next to clinfo.exe and run clinfo again and see if crash still happens. This is an official ICD loader from Khronos, so in theory it should eliminate possible bugs in the drivers and/or OS.
It still crashes:
This seems to be something wrong with Intel OpenCL SDK by the looks of it. Things to try:
Let us know if something from this helped.
One more thing, i've updated OpenCL.dll files on Ftp, added some extra debugging which might help investigating what exactly is wrong with the OpenCL SDK, so if upgrading Intel OpenCL doesn't help please re-download OpenCL.dll and attach updated log.
Your suggestion to update the opencl driver runtime from Intel solved the issue. Now I can start Blender, directly and it doesn't crash.
Prior to upadting the driver, I tried running clinfo and clinfo workaround with the dll you supplied, but it still kept crashing:
So I updated the opencl driver.
Here is the output from clinfo after the update:
The only issue I can foresee is that in the attempt of teaching colleagues how to use Blender, I will also have to ask IT to update the openCL Driver, since I have limited admin privileges specifically for resolving this issue only.
Thanks for your help!
Changed status from 'Open' to: 'Resolved'
The updated library was not intended to fix the crash, it was just adding extra debug prints to see where exactly the crash happens. And it happens in the
clGetPlatformIDsKHR
which is coming fromIntelOpenCL64.dll
.So it's purely SDK's crash which is likely fixed in it's new version :) So thanks for the report, closing it as solved now :)
Added subscriber: @MarcoNeumann
Added subscriber: @Iokanaan
I know this thread is marked as solved and closed, but I had the exact same problem for a long time as well, and wanted to add my eventually rather obvious two pennies worth.
I had installed version 2.76b when I initially bumped into this problem. I removed all user preferences, did an Intel HD graphics 4600 rollback and later reinstalled the newest version (10.18.14.4332, which I think has the most recent OpenCL drivers as well - I can't make any sense out of Intel's confusing page), and had no luck with Blender 2.75 as well. then I tried 2.74, and it was working fine (because, as I read on the forums, OpenCL was by default disabled in this build) until a reboot. I removed all prefs and config on any reinstall.
after following up on advice given in multiple threads concerning this exact same issue - using that custom made .bat file by Aaron mentioned on this page is the only thing that comes to mind right now - the two installed versions 2.76 and 2.74 were running properly during a couple of weeks, until I opened an old .blender file and set the rendering type to Cycles Render. this reintroduced the initial problem.
then I checked the DirectX diagnostic, and my dedicated GPU didn't show, because by default Windows will use the onboard video card. so I set my GTX as default preferred graphics processor, and both Cycles Render and the System tab in the user preferences are working again.
the solution for me, in short: change the graphics processor utilized by Blender from the onboard to the dedicated GPU.
OS: Windows 7 Home Premium SP1 64-bit
CPU: Intel i7-4720HQ
GPU: NVIDIA GTX 970M with driver version 361.91
Added subscriber: @RonHatfield
I also ran into this. If you're looking for a workaround you might try the following:
Open a blender file done in Cycles. This should give you access to the system tab in user preferences. In the system tab, change the Cycles compute device from None to CUDA and ensure your graphics card is listed and checked. Save the User Settings.
Added subscriber: @TheNumericDolfin
I have no idea why this has been marked as resolved. Still does not work.
This program is essentially unusable until they get around to fixing this. So basically this program will never be usable.
Uninstalled and reinstalled, now does not even open. Good job Devs, you have successfully destroyed what might have been good software.
The issue was solved for an original author.
For new issues, even if someone else had similar one, make a new report with all the details requested from the bug report template.
It is the exact same, unresolved issue. Completely unfixed.