Upgrade from 2.78a to 2.78c, Now have cycles issues. #50868

New Issue

Tom Buxton · 2017-03-06T09:49:04+01:00

Tom Buxton commented

2017-03-06 09:49:04 +01:00

System Information
Operating system and graphics card

I'm on Windows 10 Pro 64 bit and my display driver is the official Intel HD Graphics 4000 driver from Intel Corporation version 9.17.10.4229 which (according to Windows) is up to date.

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen) - 2.78c
Worked: (optional) - 2.78a

Short description of error
Hi,

I just upgraded from 2.78a to 2.78c and now I can't use Cycles. If I enable cycles, then switch to the material viewport, blender crashes to desktop. Everything worked perfectly under 2.78a. I reset to factory settings and I've tried deleting my userpref.blend and startup.blend files. I've also tried removing blender completely from the machine and reinstalling 2.78c from scratch to make sure there was nothing left over from the 2.78a installation.

I ran in debug mode --debug-cycles and it seems that my CPU and GPU combination has been skipped due to it being unsupported. I don't know if this was the case before the upgrade because Cycles just worked then so I didn't need to check! After enumerating the OpenCL devices, we get an EXCEPTION_ACCESS_VIOLATION exception....

C:\Program Files\Blender Foundation\Blender>blender --debug-cycles
found bundled python: C:\Program Files\Blender Foundation\Blender\2.78\python
I0302 20:44:44.263504 4604 blender_python.cpp:182] Debug flags initialized to:
CPU flags:
AVX2 : True
AVX : True
SSE4.1 : True
SSE3 : True
SSE2 : True
CUDA flags:
Adaptive Compile: False
OpenCL flags:
Device type : ALL
Kernel type : DEFAULT
Debug : False
I0302 20:44:44.377579 4604 device_cuda.cpp:1363] CUEW initialization failed: Error opening the library
I0302 20:44:44.378581 4604 device_opencl.cpp:58] CLEW initialization succeeded.
I0302 20:44:44.400095 4604 opencl_util.cpp:741] Enumerating devices for platform Intel(R) OpenCL.
I0302 20:44:44.400599 4604 opencl_util.cpp:812] Ignoring device Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz, not officially supported yet.
I0302 20:44:44.401595 4604 opencl_util.cpp:812] Ignoring device Intel(R) HD Graphics 4000, not officially supported yet.
Error: EXCEPTION_ACCESS_VIOLATION

I did notice, in the user preferences System panel under Cycles Compute Devices, it just says None. Previously, this gave me the option to choose CPU or GPU, I think, so I'm guessing my combination must have been supported in 2.78a.

Exact steps for others to reproduce the error
Start from factory settings after fresh install.
Switch to Cycles.
Select Material viewport shading.
Blender exits to desktop.

**System Information** Operating system and graphics card I'm on Windows 10 Pro 64 bit and my display driver is the official Intel HD Graphics 4000 driver from Intel Corporation version 9.17.10.4229 which (according to Windows) is up to date. **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) - 2.78c Worked: (optional) - 2.78a **Short description of error** Hi, I just upgraded from 2.78a to 2.78c and now I can't use Cycles. If I enable cycles, then switch to the material viewport, blender crashes to desktop. Everything worked perfectly under 2.78a. I reset to factory settings and I've tried deleting my userpref.blend and startup.blend files. I've also tried removing blender completely from the machine and reinstalling 2.78c from scratch to make sure there was nothing left over from the 2.78a installation. I ran in debug mode --debug-cycles and it seems that my CPU and GPU combination has been skipped due to it being unsupported. I don't know if this was the case before the upgrade because Cycles just worked then so I didn't need to check! After enumerating the OpenCL devices, we get an EXCEPTION_ACCESS_VIOLATION exception.... C:\Program Files\Blender Foundation\Blender>blender --debug-cycles found bundled python: C:\Program Files\Blender Foundation\Blender\2.78\python I0302 20:44:44.263504 4604 blender_python.cpp:182] Debug flags initialized to: CPU flags: AVX2 : True AVX : True SSE4.1 : True SSE3 : True SSE2 : True CUDA flags: Adaptive Compile: False OpenCL flags: Device type : ALL Kernel type : DEFAULT Debug : False I0302 20:44:44.377579 4604 device_cuda.cpp:1363] CUEW initialization failed: Error opening the library I0302 20:44:44.378581 4604 device_opencl.cpp:58] CLEW initialization succeeded. I0302 20:44:44.400095 4604 opencl_util.cpp:741] Enumerating devices for platform Intel(R) OpenCL. I0302 20:44:44.400599 4604 opencl_util.cpp:812] Ignoring device Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz, not officially supported yet. I0302 20:44:44.401595 4604 opencl_util.cpp:812] Ignoring device Intel(R) HD Graphics 4000, not officially supported yet. Error: EXCEPTION_ACCESS_VIOLATION I did notice, in the user preferences System panel under Cycles Compute Devices, it just says None. Previously, this gave me the option to choose CPU or GPU, I think, so I'm guessing my combination must have been supported in 2.78a. **Exact steps for others to reproduce the error** Start from factory settings after fresh install. Switch to Cycles. Select Material viewport shading. Blender exits to desktop.

Tom Buxton commented

2017-03-06 09:49:04 +01:00

Changed status to: 'Open'

Tom Buxton commented

2017-03-06 09:49:04 +01:00

Added subscriber: @Blametom

Joey Ferwerda commented

2017-03-06 17:09:21 +01:00

Added subscriber: @TheOnlyJoey

Joey Ferwerda commented

2017-03-06 17:09:21 +01:00

So, HD 4000 is not supported and never has been as of now.
Intel's OpenCL implementation is not at a level where it can be used for GPU rendering, so if it did turn up it was a bug since it should not.

It might still try to use the GPU mode which crashes, which means there are still some old configuration files left.

So, HD 4000 is not supported and never has been as of now. Intel's OpenCL implementation is not at a level where it can be used for GPU rendering, so if it did turn up it was a bug since it should not. It might still try to use the GPU mode which crashes, which means there are still some old configuration files left.

Sergey Sharybin commented

2017-03-08 14:51:24 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2017-03-08 14:51:24 +01:00

While CPU OpenCL is not officially support, this should simply be silently hidden from the interface and no crash should happen.

Some questions:

Does the crash happen when you go to User Preferences -> System?
Does the crash happen when you run blender from the command line with --factory-startup command line argument?
Does the crahs happen if you additionally set CYCLES_OPENCL_TEST=NONE environment variable?

While CPU OpenCL is not officially support, this should simply be silently hidden from the interface and no crash should happen. Some questions: - Does the crash happen when you go to `User Preferences -> System`? - Does the crash happen when you run blender from the command line with --factory-startup command line argument? - Does the crahs happen if you additionally set `CYCLES_OPENCL_TEST=NONE` environment variable?

Tom Buxton commented

2017-03-08 19:31:15 +01:00

Hi Sergey,

In answer to your questions.

No, The system does not crash when I go to User Preferences -> System. In there, however, under the Cycles Compute Devices, it just says None.

Blender still crashes after starting with --factory-startup

Blender still crashes after setting environment variable CYCLES_OPENCL_TEST with value NONE.

Kind Regards,
Tom

Hi Sergey, In answer to your questions. No, The system does not crash when I go to User Preferences -> System. In there, however, under the Cycles Compute Devices, it just says None. Blender still crashes after starting with --factory-startup Blender still crashes after setting environment variable CYCLES_OPENCL_TEST with value NONE. Kind Regards, Tom

Sergey Sharybin commented

2017-03-08 19:46:24 +01:00

This is expected that there's no compute devices in user preferences: you don't have CUDA and none of the OpenCL devices are officially supported (you can ovveride that using CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 environment variable for tests but suggest first we first fix the crash).

Is your blender itself 32 or 64 bit?
Is the issue happening with default cube scene?
Does the issue happen with 2.78b?
Does the issue happen with 2.78a (just so we know there is nothing changed in the system since you used 2.78a) ?
Does this happen with latest builds from builder.blender.org ?

This is expected that there's no compute devices in user preferences: you don't have CUDA and none of the OpenCL devices are officially supported (you can ovveride that using CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 environment variable for tests but suggest first we first fix the crash). - Is your blender itself 32 or 64 bit? - Is the issue happening with default cube scene? - Does the issue happen with 2.78b? - Does the issue happen with 2.78a (just so we know there is nothing changed in the system since you used 2.78a) ? - Does this happen with latest builds from builder.blender.org ?

Tom Buxton commented

2017-03-09 10:18:12 +01:00

Hi Sergey,

I'm away at the moment without the laptop in question, so I'll have to wait until tomorrow evening or Saturday to do some testing with 2.78a, 2.78b and the latest builds on this machine.

However, I can answer some of your questions now.

I'm using the 64bit version of blender
The issue is happening with just the default cube scene

I'll get back to you about the other questions, however, 2.78a was working fine for me before I upgraded. I'll confirm at the weekend that it is still working after reverting back to that version.

Kind Regards,
Tom

Hi Sergey, I'm away at the moment without the laptop in question, so I'll have to wait until tomorrow evening or Saturday to do some testing with 2.78a, 2.78b and the latest builds on this machine. However, I can answer some of your questions now. - I'm using the 64bit version of blender - The issue is happening with just the default cube scene I'll get back to you about the other questions, however, 2.78a was working fine for me before I upgraded. I'll confirm at the weekend that it is still working after reverting back to that version. Kind Regards, Tom

Sergey Sharybin commented

2017-03-09 10:22:30 +01:00

One more thing to test: get opengl32.dll from http://download.blender.org/ftp/sergey/softwaregl/ and put it next to blender.exe. This will switch Blender to fully software OpenGL mode which is slower but will let us to know if there's some real blender bug or something tricky is happening in the particular driver.

Paul Danielson commented

2017-03-11 04:35:03 +01:00

Added subscriber: @MichaelDanielson

Paul Danielson commented

2017-03-11 04:35:03 +01:00

I hit an apparently similar problem after I installed 2.78c 64-bit on a Windows 10 laptop with two display adapters: HD4000 and NVS5200M. 2.78c opened the console shell, then crashed. The crash was repeatable. I don't have the source installed, but the debugger reported the crash was in a kernel call made from the OpenCL driver. Using --factory-startup, 2.78c started up. I checked File->User Preferences->System, and Cycles Compute Device was set to None. I did not save anything. After starting once with --factory-settings, I am now able to start without --factory-settings without crashing.

This same laptop experienced a possibly related problem with previous versions of Blender, reported in #45720.

I hit an apparently similar problem after I installed 2.78c 64-bit on a Windows 10 laptop with two display adapters: HD4000 and NVS5200M. 2.78c opened the console shell, then crashed. The crash was repeatable. I don't have the source installed, but the debugger reported the crash was in a kernel call made from the OpenCL driver. Using --factory-startup, 2.78c started up. I checked File->User Preferences->System, and Cycles Compute Device was set to None. I did not save anything. After starting once with --factory-settings, I am now able to start without --factory-settings without crashing. This same laptop experienced a possibly related problem with previous versions of Blender, reported in #45720.

Sergey Sharybin commented

2017-03-11 11:28:19 +01:00

@MichaelDanielson, think that's other issue from the reported here, since your crash goes to OpenCL while the report is about crash in Material shading which does not use OpenCL (unless i'm missing something ofcourse). In that case please make it a separate report, so we don't mix troubleshooting steps together, since that always ends up in a report which is very difficult to follow. In any case, please test the following:

Check if you can reproduce the material shading viewport crash.

Check if you can reproduce the OpenCL crash by following following steps:

Delete or backup "C:\Users\<user>\Application Data\Blender Foundation\Blender\2.78"
Open Blender 2.78a and save the user preferences\starrtup file
Open Blender 2.78c and see if it crashes with OpenCL

Once again, let's stick to material shading crash in this report and make a new one for OpenCL crash.

P.S. Any chance that someone with Blender compilation skills can reproduce the issue? That would help a lot to have a backtrace.

@MichaelDanielson, think that's other issue from the reported here, since your crash goes to OpenCL while the report is about crash in Material shading which does not use OpenCL (unless i'm missing something ofcourse). In that case please make it a separate report, so we don't mix troubleshooting steps together, since that always ends up in a report which is very difficult to follow. In any case, please test the following: Check if you can reproduce the material shading viewport crash. Check if you can reproduce the OpenCL crash by following following steps: 1. Delete or backup `"C:\Users\<user>\Application Data\Blender Foundation\Blender\2.78" ` 2. Open Blender 2.78a and save the user preferences\starrtup file 3. Open Blender 2.78c and see if it crashes with OpenCL Once again, let's stick to material shading crash in this report and make a new one for OpenCL crash. P.S. Any chance that someone with Blender compilation skills can reproduce the issue? That would help a lot to have a backtrace.

Tom Buxton commented

2017-03-11 11:32:20 +01:00

Hi,

I've managed to do a bit of testing today.

Uninstalled 2.78c. Reinstalled 2.78a. Crash is now occurring in that version too even though I was happily using 2.78a for months before I upgraded. Perhaps something switched during the upgrade that did not switch back during the uninstall?
Deleted folder in Appdata/Roaming (just to make sure there was nothing left over in there) - Crash still occurs.
Tried 2.78b. Crash still occurs.
Tried installing latest build 2.78-2d3c443-Windows64. Crash still occurs.
Tested with your opengl32.dll file. Blender does not crash! Woohoo! However, as you said it would be, is too slow for every day use.
Removed 2.78-2d3c443-Windows64. Cleared out appdata/roaming folder. Reinstalled 2.78c. Tried with Environment variable CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 set (just to see what happens). Crash still occurs.

Kind Regards,
Tom

Hi, I've managed to do a bit of testing today. - Uninstalled 2.78c. Reinstalled 2.78a. Crash is now occurring in that version too even though I was happily using 2.78a for months before I upgraded. Perhaps something switched during the upgrade that did not switch back during the uninstall? - Deleted folder in Appdata/Roaming (just to make sure there was nothing left over in there) - Crash still occurs. - Tried 2.78b. Crash still occurs. - Tried installing latest build 2.78-2d3c443-Windows64. Crash still occurs. - Tested with your opengl32.dll file. Blender does not crash! Woohoo! However, as you said it would be, is too slow for every day use. - Removed 2.78-2d3c443-Windows64. Cleared out appdata/roaming folder. Reinstalled 2.78c. Tried with Environment variable CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 set (just to see what happens). Crash still occurs. Kind Regards, Tom

Sergey Sharybin commented

2017-03-11 11:45:52 +01:00

@Blametom, i would put my bets on Windows 10 being "smart" and re-installing good drivers with something else (happens a lot with NVidia users, screwing up their GPU rendering). From quick look around it seems your driver 9.17.10.4229 was released back in 2015 - [x]. From a bit more quick looking around, there is a much newer version of driver for your card - [x]. Totally worth updating and see if the issue still happens.

P.S. Apart from user config in Appdata and possibly registered file bindings (opening .blend from Explorer) Blender does not do any modifications on the system. During un-installation all bindings are removed. Appdata we keep untouched because someone might have custom addons in there. So if you uninstall blender and remove it's appdata you'll be at "factory settings".

@Blametom, i would put my bets on Windows 10 being "smart" and re-installing good drivers with something else (happens a lot with NVidia users, screwing up their GPU rendering). From quick look around it seems your driver 9.17.10.4229 was released back in 2015 - [x]. From a bit more quick looking around, there is a much newer version of driver for your card - [x]. Totally worth updating and see if the issue still happens. P.S. Apart from user config in Appdata and possibly registered file bindings (opening .blend from Explorer) Blender does not do any modifications on the system. During un-installation all bindings are removed. Appdata we keep untouched because someone might have custom addons in there. So if you uninstall blender and remove it's appdata you'll be at "factory settings". - [x] https://downloadcenter.intel.com/download/24971/Intel-HD-Graphics-Driver-for-Windows-7-8-64-bit - [x] https://downloadcenter.intel.com/download/25977/Intel-Graphics-Driver-for-Windows-10-and-Windows-7-8-1-15-33-?product=81499

Tom Buxton commented

2017-03-11 12:11:03 +01:00

Thanks Sergey,

I literally had to force those new drivers to install as Windows kept insisting that the existing drivers were more up to date. Anyway, success! I finally got them to override the existing drivers and blender is now functioning correctly again with the new drivers.

Must have just been coincidence that maybe Windows had updated the display driver at the same time as I upgraded blender!

Thank you so much for your help.

Kind Regards,
Tom

Thanks Sergey, I literally had to force those new drivers to install as Windows kept insisting that the existing drivers were more up to date. Anyway, success! I finally got them to override the existing drivers and blender is now functioning correctly again with the new drivers. Must have just been coincidence that maybe Windows had updated the display driver at the same time as I upgraded blender! Thank you so much for your help. Kind Regards, Tom

Sergey Sharybin commented

2017-03-11 13:52:50 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2017-03-11 13:52:50 +01:00

Sergey Sharybin self-assigned this 2017-03-11 13:52:50 +01:00

Sergey Sharybin commented

2017-03-11 13:52:50 +01:00

That's great to hear!

@MichaelDanielson, please make sure your drivers are up to date as well. And if it is so and you can still reproduce the crash, please open a new report with all relevant info to that particular crash.

That's great to hear! @MichaelDanielson, please make sure your drivers are up to date as well. And if it is so and you can still reproduce the crash, please open a new report with all relevant info to that particular crash.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Upgrade from 2.78a to 2.78c, Now have cycles issues. #50868