Unusual display colors and Blender crashes to desktop #57661

New Issue

paul cutting · 2018-11-06T20:59:07+01:00

paul cutting commented

2018-11-06 20:59:07 +01:00

I updated my intel hd graphics 4600 to the latest driver version. Now the Blender 2.8 3d display area is black. The only way to get it to show anything is to switch to the modeling tab and use the hand icon to move just slightly. That will yield a 3d display that shows the grid in grey, the cube object in varying colors per face and a background that is pink at the top and grades to white at the bottom. Clicking on the various tabs will show similar displays. Switching to the "Scripting" tab will show the small 3d display at the upper left in black with a grid of varying colors and completeness. Zooming in and out will cause grid lines to appear and disappear. Eventually, clicking on a tab will cause blender to crash. The error message reads "The display driver stopped responding and has recovered". It is usually either "Animation" or "Render" tabs that cause this problem.system-info.txt

I updated my intel hd graphics 4600 to the latest driver version. Now the Blender 2.8 3d display area is black. The only way to get it to show anything is to switch to the modeling tab and use the hand icon to move just slightly. That will yield a 3d display that shows the grid in grey, the cube object in varying colors per face and a background that is pink at the top and grades to white at the bottom. Clicking on the various tabs will show similar displays. Switching to the "Scripting" tab will show the small 3d display at the upper left in black with a grid of varying colors and completeness. Zooming in and out will cause grid lines to appear and disappear. Eventually, clicking on a tab will cause blender to crash. The error message reads "The display driver stopped responding and has recovered". It is usually either "Animation" or "Render" tabs that cause this problem.[system-info.txt](https://archive.blender.org/developer/F5413058/system-info.txt)

paul cutting commented

2018-11-06 20:59:07 +01:00

Added subscriber: @Animfactor

Philipp Oeser commented

2018-11-07 11:01:47 +01:00

Added subscribers: @fclem, @lichtwerk

Clément Foucault was assigned by Philipp Oeser

2018-11-07 11:01:47 +01:00

Philipp Oeser commented

2018-11-07 11:01:47 +01:00

Dont have that hardware here.

Which was the driver version that was working?
Failing version seems to be 4.3.0 - Build 10.18.14.5057? (from system-info.txt)

Hm, even though this seems to be a pure driver issue, I would kindly ask @fclem for his opinion on possible workarounds? Or advise to downgrade driver for the time being?

Dont have that hardware here. Which was the driver version that was working? Failing version seems to be 4.3.0 - Build 10.18.14.5057? (from system-info.txt) Hm, even though this seems to be a pure driver issue, I would kindly ask @fclem for his opinion on possible workarounds? Or advise to downgrade driver for the time being?

Clément Foucault commented

2018-11-07 11:08:55 +01:00

If the previous driver was working then yes, I would advise to downgrade. There is little we can do for this stuff other than reporting that behavior to intel.

Philipp Oeser commented

2018-11-07 12:24:18 +01:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2018-11-07 12:24:18 +01:00

Philipp Oeser commented

2018-11-07 12:24:18 +01:00

@fclem: do you ususally do this (report to intel)? Or is this duty of original report author? (or my?)

Since we only have limited information [just the wording of this report -- no screenshots etc.] I would then kindly ask @Animfactor to report over at Intel.
Have no experience doing this, but looks like:
https://software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/532646
https://software.intel.com/en-us/forums/graphics-driver-bug-reporting
is the way to go...

I would go ahead and close this as archived for now, we can always come back later if anything comes out of a bugreport at Intel... all agree?

@fclem: do **you** ususally do this (report to intel)? Or is this duty of original report author? (or my?) Since we only have limited information [just the wording of this report -- no screenshots etc.] I would then kindly ask @Animfactor to report over at Intel. Have no experience doing this, but looks like: https://software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/532646 https://software.intel.com/en-us/forums/graphics-driver-bug-reporting is the way to go... I would go ahead and close this as archived for now, we can always come back later if anything comes out of a bugreport at Intel... all agree?

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

Unusual display colors and Blender crashes to desktop #57661