Modeling - Freeze - Crash Graphics Card - White screen
Open, NormalPublic

Description

System Information
Operating system : Windows 10 Famille - 64 bits - 16 Go RAM
graphics card : GTX 580 x2

Blender Version
Broken: 2.78 def365e
Worked: 2.75a c27589e

Short description of error
During modeling, freeze, crash graphics card, white screen.
Require to kill the process.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
1 / Modeling on a cylinder
2 / Putting a Subsurf
3 / Add cuts
Bam! Freeze! White screen

Splash screen blender broken

Process back

White screen

Windows error report
Windows error report

Blender fichier
Vaisseau.blend1

Vaisseau.blend

Details

Type
Bug

Can't seem to repro, added some loopcuts to cylinder.000, seemed just peachy, could be a driver bug.

To check for that you can try dropping the opengl32.dll from here http://download.blender.org/ftp/sergey/softwaregl/win64/ into your blender folder and try again. (be sure to remove it when you're done testing, software opengl doesn't have the best performance)

I did this test last time. The result was a big freeze.

What I can not explain: why blender 2.75a works. Why 2.78 does not work. Same conditions of use for both versions.

Blender 2.75a:

  • Modeling: OK
  • Rexturing / Mapting under Cycles: OK

Blender 2.78 all versions and bluidbot:

  • Modeling: Crahs (loop cut)
  • Rexturing / Mapting under Cycles: OK

So it's not a driver bug. When this bug is when I add loop cut on an object in edit mode.

Removing all project tags but BF Blender for until we now what actually causes the issue.

Please, let us handle the project tagging.

Its highly likely that this bug is specific to your hardware/driver configuration.
These kinds of display issues are often caused by OpenGL driver bugs.

While its possible a software error in Blender,
its worth checking if this functions correctly...

  • After upgrading graphics card drivers.
  • On a different system (with different hardware/drivers).
  • Using a Software OpenGL renderer...
    • On Linux, Official releases come with blender-softwaregl
    • On MS-Windows: Downloading 'opengl32.dll' from download.blender.org/ftp/sergey/softwaregl and copying it so its located in the same directory as 'blender.exe' (make sure to grab the 64-bit version)

If this is a driver bug, or we can't link to this to an error in Blender's code,
the report may be closed as a driver error,
so please help us determine whether this is a bug in Blender or not.

Aaron Carlisle (Blendify) triaged this task as "Incomplete" priority.Tue, Dec 27, 8:55 PM

Thank you for answering

Its highly likely that this bug is specific to your hardware/driver configuration.
These kinds of display issues are often caused by OpenGL driver bugs.

It would seem that this may come from there. But why would it work perfectly with previous versions?

While its possible a software error in Blender,
its worth checking if this functions correctly...

  • After upgrading graphics card drivers.

I upgraded to the latest NVidia drivers.

  • On a different system (with different hardware/drivers).

Indeed, I have not tested on my laptop. But I do not think I'd do it until I'm sure it's OK level bug. Alas, when I see the todo bug list ...

  • Using a Software OpenGL renderer...
    • On Linux, Official releases come with blender-softwaregl

Lost, I have no more Linux available to test.

I tested this option. Big fat lag ... impossible to run Blender. It's as if you do shoot the scene and you have time to drink your coffee and read a good Shakespire same time!

If this is a driver bug, or we can't link to this to an error in Blender's code,
the report may be closed as a driver error,
so please help us determine whether this is a bug in Blender or not.

I maintain that Blender works in its previous versions. Since version 2.77, big concerns regardless of the version, not stable, stable or ongoing!

Please let me know what Blender is doing while I'm using it. This may be useful to see if it's not a "null point"

Sometimes it will fail to work on older hardware because Blender updates its code to new standards.
The 'opengl32.dll' is going to be slower because it runs the entire UI on the CPU and thus illuminating possible GPU issues.
It is critical that you wait through the lags and test. If you find that it still happens with the dll-file then we we know that it is a bug with Blender and will be willing to look more into this specific issue.
However, like what other people have said after testing leads me to believe that this is a hardware issue. If using the dll-file gives correct results then there is nothing we can do because the issue comes from your hardware.

Also you say that you are running windows 10 family but that does not exist https://en.wikipedia.org/wiki/Windows_10_editions So something seems wrong on your end.

Would this imply that the embedded version of OPEN-GL of my graphics cards is exceeded?

Is it wise to block the material yet not so old? Especially since others use versions even older than my cards?

To get back on the dll, this is far from being so obvious. What do we mean by "It's critical that you wait through the lags and test." ?

In addition, here is a view of the driver version used and up to date currently.

Aaron Carlisle (Blendify) closed this task as "Invalid".Thu, Jan 5, 8:01 PM
Aaron Carlisle (Blendify) claimed this task.

No reply in more than a week... closing

Julian Eisel (Severin) reopened this task as "Open".Thu, Jan 5, 8:28 PM

Eeeh, the author did reply, AFAICS this task is pending action from us.

Bastien Montagne (mont29) raised the priority of this task from "Incomplete" to "Normal".Fri, Jan 13, 1:31 PM

This indeed smells like GPU/driver issue… Even though GTX 580 is a bit old, it should still be supported for sure, afaik.

You mention 2 GPUs though, maybe you could try running with only one and see whether it fixes the problem? Also, sometimes newer drivers with older GPUs can actually introduce new bugs instead of removing them… That’s why software OGL, as slow as it is, is a good test - if it does not crash with it, then there is 99% of probability that the issue is with your current GPU driver.

Maybe someone from OGL team having similar hardware can test? @Mike Erwin (merwin)?

In the mean while, you may check those additional points:

  • Try the latest build from our buildbot.
  • 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 OGL settings in UserPreferences, System tab (open it by changing type of e.g. 3DView in main window, not as new window).
  • Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
  • Attach as text file here the report generated by Help -> System Info (do not paste it directly in comment).
  • Launch Blender from the command line with -d option and attach as text file here any error printed out in the console (do not paste it directly in comment).

PS: as for 2.75 running OK, well, Blender also evolves and tends to use more modern features in newer versions, like more shaders etc.

Thank you for bringing me these few answers.

I do not use any add-ons. I even prefer to use the basic configuration.

However, I have 2 questions.
1 / For tests, is it imperative to use the DLL?
2 / On Windows, how to have the console?

GTX 580 is a few years old but very capable GPU. It should be supported for 2.7x and even 2.8x

Try this with the latest Blender version:

Open command prompt (windows key, type "cmd").
Navigate to Blender's install location with the "cd" command. On my system it lives at
C:\Program Files\Blender Foundation\Blender>

type "blender --debug-gpu" to run it with extra OpenGL debugging.

For simplicity. I downloaded the latest version, unzipped as from the bluidbot.
I put the dll as requested and navigated with the command prompt.
Some returns now with attached files.Test-opengl_dll.blend1

Test-opengl_dll.blend

quit.blend

Test-opengl_dll2.blend

cmd-2.txt

cmd.txt

If it helps.

Add Comment