Crash and shutdown on accessing System tab in User Preferences #45720

New Issue

Dave S-B · 2015-08-07T10:50:06+02:00

Dave S-B commented

2015-08-07 10:50:06 +02:00

System Information
Windows 7 Pro, AMD Radeon HD 6490M, HP Pavilion DV7 laptop with Intel i7

Blender Version
Broken: 2.75, 2.75a
Worked: 2.74

Short description of error
Blender shuts down suddenly when clicking on the System tab in user preferences, also when selecting "System Info" in the Help menu (which is why I've included the system-info file generated from a 2.74 version).

Exact steps for others to reproduce the error
Open Blender > Go into User Preferences > Click on System tab (crashes)
Open Blender > select Help > System Info from the menu (crashes)

**System Information** Windows 7 Pro, AMD Radeon HD 6490M, HP Pavilion DV7 laptop with Intel i7 **Blender Version** Broken: 2.75, 2.75a Worked: 2.74 **Short description of error** Blender shuts down suddenly when clicking on the System tab in user preferences, also when selecting "System Info" in the Help menu (which is why I've included the system-info file generated from a 2.74 version). **Exact steps for others to reproduce the error** Open Blender > Go into User Preferences > Click on System tab (crashes) Open Blender > select Help > System Info from the menu (crashes)

Dave S-B commented

2015-08-07 10:50:06 +02:00

Changed status to: 'Open'

Dave S-B commented

2015-08-07 10:50:06 +02:00

Added subscriber: @dave.sb

blender-admin commented

2015-08-07 10:50:06 +02:00

#46834 was marked as duplicate of this issue

Julian Eisel commented

2015-08-07 14:51:36 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2015-08-07 14:51:36 +02:00

Changed status from 'Open' to: 'Resolved'

Julian Eisel closed this issue

2015-08-07 14:51:36 +02:00

Julian Eisel self-assigned this 2015-08-07 14:51:36 +02:00

Julian Eisel commented

2015-08-07 14:51:36 +02:00

This was fixed already, you can try again using latest builds form buildbot .

Closing this for now, we can reopen if the bug isn't fixed. Thanks for the report.

This was fixed already, you can try again using latest builds form [buildbot ](https://builder.blender.org/download/). Closing this for now, we can reopen if the bug isn't fixed. Thanks for the report.

Dave S-B commented

2015-08-11 15:34:33 +02:00

Changed status from 'Resolved' to: 'Open'

Dave S-B reopened this issue

2015-08-11 15:34:33 +02:00

Dave S-B commented

2015-08-11 15:34:33 +02:00

This is still happening in version 2.75.4 (from buildbot blender-2.75-c150645-win64.zip). Another place it crashes is when selecting Cycles as the renderer.

Bastien Montagne commented

2015-08-12 16:21:28 +02:00

Added subscribers: @Sergey, @mont29

Bastien Montagne commented

2015-08-12 16:21:28 +02:00

Please:

Ensure both your OS and drivers are fully up-to-date.
Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
Try to tweak OGL settings in UserPreferences, System tab.
Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
Attach here the report generated by Help -> System Info.
Launch Blender from the command line and attach here any error printed out in the console.
Try to place this dll next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not).

This sounds like the GPU device querying bug, though, @Sergey?

Please: * Ensure both your OS and drivers are fully up-to-date. * Try to start Blender in factory settings (`--factory-startup` commandline option) (this will ensure whether this is a userpref or addon issue or not). * Try to tweak OGL settings in UserPreferences, System tab. * Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.). * Attach here the report generated by Help -> System Info. * Launch Blender from the command line and attach here any error printed out in the console. * Try to place [this dll](http://download.blender.org/ftp/sergey/softwaregl/win64/opengl32.dll) next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not). This sounds like the GPU device querying bug, though, @Sergey?

Dave S-B commented

2015-08-13 22:24:35 +02:00

factory-startup : same issues happen
I can't get into the Settings tab in UserPreferences, so not able to change anything there.
GPU driver settings had no effect.
Help -> System Info just crashes Blender.
Command line : only error was "Error: EXCEPTION_ACCESS_VIOLATION".
Software OGL : same issue

Sorry this isn't more helpful :(

- factory-startup : same issues happen I can't get into the Settings tab in UserPreferences, so not able to change anything there. GPU driver settings had no effect. Help -> System Info just crashes Blender. Command line : only error was "Error: EXCEPTION_ACCESS_VIOLATION". Software OGL : same issue Sorry this isn't more helpful :(

Julian Eisel removed their assignment 2015-08-14 22:09:12 +02:00

Bastien Montagne commented

2015-08-21 16:30:24 +02:00

You still did not answered about GPU drivers, what’s exact version you are using (i.e. are they fully up to date)? Some drivers used to segfault when querying about their capacities (which is what happens when showing 'system' tab or running system info), iirc…

Dave S-B commented

2015-08-21 17:15:18 +02:00

Sorry, I have the latest versions that are available. I've been looking into it though, and there's something more important (probably) - the laptop has dual switchable graphics (I never even new this!). It uses the on-board graphics, which is Intel HD graphics (hardware ID PCI\VEN_8086&DEV_0116&SUBSYS_1659103C&REV_09), for menial tasks and somehow switches to the AMD card for more demanding applications (hardware ID of the AMD card is PCI\VEN_1002&DEV_6760&SUBSYS_1659103C&REV_00). Blender version 2.74 is reporting the card in use as the Intel one. I'm attaching the system-info from that just in case it's any use.system-info.txt

Sorry, I have the latest versions that are available. I've been looking into it though, and there's something more important (probably) - the laptop has dual switchable graphics (I never even new this!). It uses the on-board graphics, which is Intel HD graphics (hardware ID PCI\VEN_8086&DEV_0116&SUBSYS_1659103C&REV_09), for menial tasks and somehow switches to the AMD card for more demanding applications (hardware ID of the AMD card is PCI\VEN_1002&DEV_6760&SUBSYS_1659103C&REV_00). Blender version 2.74 is reporting the card in use as the Intel one. I'm attaching the system-info from that just in case it's any use.[system-info.txt](https://archive.blender.org/developer/F226364/system-info.txt)

Sergey Sharybin was assigned by Bastien Montagne

2015-08-21 17:46:36 +02:00

Bastien Montagne commented

2015-08-21 17:46:36 +02:00

Added subscriber: @Psy-Fi

Bastien Montagne commented

2015-08-21 17:46:36 +02:00

Assigning to Sergey since iirc he has some testing tools for those cases… @Psy-Fi you may also have some insights here?

Sergey Sharybin commented

2015-08-24 13:00:04 +02:00

Does this happen with latest builds from builder.blender.org?

it's also a bit confusing, is it a laptop with both discrete and integrated video cards?

Does this happen with latest builds from builder.blender.org? it's also a bit confusing, is it a laptop with both discrete and integrated video cards?

Dave S-B commented

2015-08-24 20:49:48 +02:00

I've just downloaded and tried the Blender-2.75.0-git.4f61de6-AMD64 build - same thing happens.

Yes, that's right - it's a laptop with on-board (Intel) graphics and discrete AMD Radeon too, although the info from Blender 2.74 (which works ok) only mentions the Intel graphics. Here's a link to the product support page for the laptop if you want the gory details - http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv7-6b00-Entertainment-Notebook-PC-series/5145684/model/5177030#Z7_3054ICK0KGTE30AQO5O3KA30R1.

I've just downloaded and tried the Blender-2.75.0-git.4f61de6-AMD64 build - same thing happens. Yes, that's right - it's a laptop with on-board (Intel) graphics and discrete AMD Radeon too, although the info from Blender 2.74 (which works ok) only mentions the Intel graphics. Here's a link to the product support page for the laptop if you want the gory details - http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv7-6b00-Entertainment-Notebook-PC-series/5145684/model/5177030#Z7_3054ICK0KGTE30AQO5O3KA30R1.

Sergey Sharybin commented

2015-08-25 15:44:49 +02:00

Think latest Catalyst still supports your GPU, please try upgrading it because it smells like graphics card driver issue.

Dave S-B commented

2015-08-26 11:16:15 +02:00

I've just installed the latest AMD drivers using their auto-detect installer and now my computer's lost all accelerated graphics completely. So nothing can use OpenGL at all, including Blender. I'm going to have to get back to you after sorting it out..... :-( Feel free to close the issue or put it as very low priority - it smells like driver/card issues to me too now.

Campbell Barton commented

2015-08-26 11:37:01 +02:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2015-08-26 11:37:01 +02:00

Paul Danielson commented

2015-11-04 18:23:55 +01:00

Added subscriber: @MichaelDanielson

Paul Danielson commented

2015-11-04 18:23:55 +01:00

This was happening to me too, on a laptop running Windows 7 Professional. Many laptops (this particular one is a Dell E6530) have two graphics chips: the built-in Intel hardware is used for driving the main laptop display when low power consumption is required. The "real" chip (NVS5200M on this laptop) is used when multiple displays are connected, and when plugged in.

I had been running 2.71 with no problems. I upgraded to 2.76 and got the instant crash when switching to the User Preferences->System tab, or choosing the Cycles renderer. After thrashing around a bit, I tried shutting down Blender, disconnecting the external display, and restarting Blender. The crash no longer happened. Then I shut down Blender, reconnected the external display, and restarted Blender. The crash did not reappear. Now that I have access to the System tab, I have been able to select the Compute Device, and I can pick CUDA (and see the correct graphics card listed), and still no crash. Rendering with Cycles works fine. It seems like 2.76 is getting initially confused about the graphics card when multiple drivers/screens are present, and tries something illegal. Once it has been started in a simpler environment, theproblem goes away on subsequent restarts. I have not tested this across a hard reboot yet, but at least the workaround seems simple, even if the problem recurs.

This was happening to me too, on a laptop running Windows 7 Professional. Many laptops (this particular one is a Dell E6530) have two graphics chips: the built-in Intel hardware is used for driving the main laptop display when low power consumption is required. The "real" chip (NVS5200M on this laptop) is used when multiple displays are connected, and when plugged in. I had been running 2.71 with no problems. I upgraded to 2.76 and got the instant crash when switching to the User Preferences->System tab, or choosing the Cycles renderer. After thrashing around a bit, I tried shutting down Blender, disconnecting the external display, and restarting Blender. The crash no longer happened. Then I shut down Blender, reconnected the external display, and restarted Blender. The crash did not reappear. Now that I have access to the System tab, I have been able to select the Compute Device, and I can pick CUDA (and see the correct graphics card listed), and still no crash. Rendering with Cycles works fine. It seems like 2.76 is getting initially confused about the graphics card when multiple drivers/screens are present, and tries something illegal. Once it has been started in a simpler environment, theproblem goes away on subsequent restarts. I have not tested this across a hard reboot yet, but at least the workaround seems simple, even if the problem recurs.

Sergey Sharybin commented

2015-11-18 12:08:50 +01:00

Please test latest builds from builder.blender.org. There were some fixes in related areas.

Bastien Montagne commented

2015-11-21 22:48:31 +01:00

Added subscriber: @MarcoNeumann

Bastien Montagne commented

2015-11-21 22:50:37 +01:00

Also related: #46637.

Paul Danielson commented

2015-12-06 08:45:15 +01:00

The crash reappeared after I installed the latest Dell updates today, which included something new for the video subsystem. The nVidia GeForce Experience software reported the driver as being up to date (and the same version = 353.82 on an NVS5200M ) both before and after the Dell update, so I'm not sure what Dell added. With 2.76 release, the trick of unplugging the external monitor stopped working; I could not find a way to avoid the crash.
I downloaded the Dec 6 build for Win 64 from builder.blender.com. With that build installed, the workaround works again, i.e. if I shut down Blender, unplug the external monitor, then start Blender and switch to Cycles the crash does not happen. If I then plug in the monitor, I can move Blender to the external monitor without problems. I can stop and start Blender as desired and the problem does not reappear. However, if I reboot the laptop the problem reappears, and I have to start Blender once with the external monitor unplugged. If there are any experiments you would like me to run, let me know.

The crash reappeared after I installed the latest Dell updates today, which included something new for the video subsystem. The nVidia GeForce Experience software reported the driver as being up to date (and the same version = 353.82 on an NVS5200M ) both before and after the Dell update, so I'm not sure what Dell added. With 2.76 release, the trick of unplugging the external monitor stopped working; I could not find a way to avoid the crash. I downloaded the Dec 6 build for Win 64 from builder.blender.com. With that build installed, the workaround works again, i.e. if I shut down Blender, unplug the external monitor, then start Blender and switch to Cycles the crash does not happen. If I then plug in the monitor, I can move Blender to the external monitor without problems. I can stop and start Blender as desired and the problem does not reappear. However, if I reboot the laptop the problem reappears, and I have to start Blender once with the external monitor unplugged. If there are any experiments you would like me to run, let me know.

Paul Danielson commented

2015-12-12 03:35:27 +01:00

This problem seems to have been corrected by 2.76b release.

Ole Larsen commented

2017-05-16 16:16:56 +02:00

Added subscriber: @OleLarsen

Ole Larsen commented

2017-05-16 16:16:56 +02:00

This comment was removed by @OleLarsen

*This comment was removed by @OleLarsen*

nicholas spry commented

2018-05-19 10:32:32 +02:00

Added subscriber: @thoiter

nicholas spry commented

2018-05-19 10:32:32 +02:00

I'm having this same issue in 2018 (Blender crashes when selecting Cycles or selecting the System tab under user prefs). Does anyone know if there was a fix for this other than disabling screens? I have a two monitor setup on a desktop PC and I don't really want to be disabling a monitor every time I use Blender.
All my drivers are up to date and I'm using Blender 2.79.

I'm having this same issue in 2018 (Blender crashes when selecting Cycles or selecting the System tab under user prefs). Does anyone know if there was a fix for this other than disabling screens? I have a two monitor setup on a desktop PC and I don't really want to be disabling a monitor every time I use Blender. All my drivers are up to date and I'm using Blender 2.79.

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

Crash and shutdown on accessing System tab in User Preferences #45720