NVIDIA TITAN XP Pascal display error #53179

New Issue

Lorenz · 2017-10-27T13:09:19+02:00

Lorenz commented

2017-10-27 13:09:19 +02:00

System Information
Windows 8.1 64bit
NVIDIA TITAN XP Pascal

Blender Version
2.79 Hash: 5bd8ac9

Short description of error
I change the old TITAN X (Maxwell) to the new TITAN XP Pascal
With the new Titan PASCAL !! i have display error in the solid mode see attachment.
With the TITAN X Maxwell Architecture works anything fine.
The new Cards are checked by the NVIDIA support and anything works fine, driver etc. is actually.
In other programs no problem.

Exact steps for others to reproduce the error
v2.76
Cycles
NVIDIA TITAN XP Pascal
Solid mode
turn the mouse and display error (attachment)

**System Information** Windows 8.1 64bit NVIDIA TITAN XP Pascal **Blender Version** 2.79 Hash: 5bd8ac9 **Short description of error** I change the old TITAN X (Maxwell) to the new TITAN XP Pascal With the new Titan PASCAL !! i have display error in the solid mode see attachment. With the TITAN X Maxwell Architecture works anything fine. The new Cards are checked by the NVIDIA support and anything works fine, driver etc. is actually. In other programs no problem. **Exact steps for others to reproduce the error** v2.76 Cycles NVIDIA TITAN XP Pascal Solid mode turn the mouse and display error (attachment) ![image_846.png](https://archive.blender.org/developer/F1069479/image_846.png)

Lorenz commented

2017-10-27 13:09:19 +02:00

Changed status to: 'Open'

blender-admin commented

2017-10-27 13:09:19 +02:00

#53433 was marked as duplicate of this issue

blender-admin commented

2017-10-27 13:09:19 +02:00

#53382 was marked as duplicate of this issue

Lorenz commented

2017-10-27 13:09:20 +02:00

Added subscriber: @Horst2199

Lorenz commented

2017-10-28 15:44:47 +02:00

Update: the orange color comes always from the origin point

Ray molenkamp commented

2017-10-28 16:46:07 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2017-10-28 16:46:07 +02:00

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/macOS, Official releases come with blender-softwaregl
On MS-Windows: Download this dll and copying it so its located in the same directory as 'blender.exe' and run Blender normally. Once done testing be sure to remove it cause things will be a lot slower
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.

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/macOS, Official releases come with blender-softwaregl On MS-Windows: Download [this dll ](http://download.blender.org/ftp/sergey/softwaregl/win64/opengl32.dll) and copying it so its located in the same directory as 'blender.exe' and run Blender normally. Once done testing be sure to remove it cause things will be a lot slower 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.

Lorenz commented

2017-10-28 17:31:14 +02:00

ok test is finish:
with the opengl32.dll blender works very slow but fine and no orange display errors again.
Is this now a driver problem or bug inside blender?

ok test is finish: with the opengl32.dll blender works very slow but fine and no orange display errors again. Is this now a driver problem or bug inside blender?

Lorenz commented

2017-10-28 19:23:03 +02:00

This comment was removed by @Horst2199

*This comment was removed by @Horst2199*

Lorenz commented

2017-10-28 20:04:24 +02:00

I test with the same driver and GPU with blender v2.8 (without the opengl32.ll) also and blender works fine, so i think there is a problem with 2.79 ?

I test with the same driver and GPU with blender v2.8 **(without the opengl32.ll)** also and blender works fine, so i think there is a problem with 2.79 ?

Ray molenkamp commented

2017-10-29 02:44:21 +02:00

Changed status from 'Open' to: 'Archived'

Ray molenkamp closed this issue

2017-10-29 02:44:21 +02:00

Ray molenkamp self-assigned this 2017-10-29 02:44:21 +02:00

Ray molenkamp commented

2017-10-29 02:44:21 +02:00

if the problem goes away with the opengl32 replacement, it's a gpu driver bug, the rendering code in 2.79 and 2.8 are quite different, so 2.8 just isn't triggering the issue.

Lorenz commented

2017-10-29 12:23:25 +01:00

all other 3d applications works fine, games substance painter etc.
the cards are testet with the NVIDIA Tool and no problems, but Blender v2.79 can not handle correctly the GPU and it is a driver bug from NVIDIA ?
And again the v2.79 works fine with the old TITAN X maxwell and with the pascal not, the interesting thing is, the old maxwell and the new pascal use the same GPU driver 388 WHQL.
So i must have the the driver bug before in the maxwell but without problems.
Ok Blender says driver bug, NVIDIA says Blender problem

all other 3d applications works fine, games substance painter etc. the cards are testet with the NVIDIA Tool and no problems, but Blender v2.79 can not handle correctly the GPU and it is a driver bug from NVIDIA ? And again the v2.79 works fine with the old TITAN X maxwell and with the pascal not, the interesting thing is, the old maxwell and the new pascal use the same GPU driver 388 WHQL. So i must have the the driver bug before in the maxwell but without problems. Ok Blender says driver bug, NVIDIA says Blender problem

Lorenz commented

2017-10-29 12:27:20 +01:00

one information mor: when i change to CPU i have the same problem in the solid mode ?

Vuk Gardašević commented

2017-11-03 08:49:52 +01:00

Added subscriber: @VukGardasevic

Vuk Gardašević commented

2017-11-03 08:49:52 +01:00

In #53179#468178, @Horst2199 wrote:
one information more: when i change to CPU i have the same problem in the solid mode ?

Please can you explain what does this mean exactly? Using the opengl32.dll in the blender unpacked/install folder?

Some general tips about recognizing GPU issues (drivers usually, sometimes OS updates affecting them, more rarely hardware issues):

If several release versions of Blender are affected (like 2.76, 2.77, 2.78c etc.)
Running Blender in software mode (OpenGL rendering is done on the CPU with the opengl32 dll) doesn't show the issue
If other applications are working fine doesn't mean that the issue is not in the driver itself (as patch notes, hotfixes etc. show for game releases improving performance, correcting crashes). Generally, older cards have more mature drivers - many issues were fixed during the production/support period, until they've reached EOL (end of life) when there is no more support for new software/changes. That means that older software should work fine most of the time. An example for EOL is the support for AMD GCN 1 cards concerning the OpenCL compiler. However since the card is new it's probably driver maturity.
It's possible that the issue itself can be on the Blender side, however since other cards are not affected it could be some corner case that have to be usually addressed in the code with some specific hack that has to be added in this case. Examples in the past were some hardware limitations affecting older Nvidia architecture in Cycles concerning the texture limit.

> In #53179#468178, @Horst2199 wrote: > one information more: when i change to CPU i have the same problem in the solid mode ? Please can you explain what does this mean exactly? Using the `opengl32.dll` in the blender unpacked/install folder? Some general tips about recognizing GPU issues (drivers usually, sometimes OS updates affecting them, more rarely hardware issues): - If several release versions of Blender are affected (like 2.76, 2.77, 2.78c etc.) - Running Blender in software mode (OpenGL rendering is done on the CPU with the opengl32 dll) doesn't show the issue - If other applications are working fine doesn't mean that the issue is not in the driver itself (as patch notes, hotfixes etc. show for game releases improving performance, correcting crashes). Generally, older cards have more mature drivers - many issues were fixed during the production/support period, until they've reached EOL (end of life) when there is no more support for new software/changes. That means that older software should work fine most of the time. An example for EOL is the support for AMD GCN 1 cards concerning the OpenCL compiler. However since the card is new it's probably driver maturity. - It's possible that the issue itself can be on the Blender side, however since other cards are not affected it could be some corner case that have to be usually addressed in the code with some specific hack that has to be added in this case. Examples in the past were some hardware limitations affecting older Nvidia architecture in Cycles concerning the texture limit.

Lorenz commented

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

Information from:
LazyDodo (LazyDodo) triaged this task as "Incomplete" priority.
LazyDodo (LazyDodo) added a comment.

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/macOS, Official releases come with blender-softwaregl
On MS-Windows: Download this dll and copying it so its located in the same directory as 'blender.exe' and run Blender normally. Once done testing be sure to remove it cause things will be a lot slower
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.

if the problem goes away with the opengl32 replacement, it's a gpu driver bug, the rendering code in 2.79 and 2.8 are quite different, so 2.8 just isn't triggering the issue.

Lorenz:
so i make the test with the opengl32.dll and blender works fine but without the opengl32.dll i have the orange display error.
The new TITAN XP are Hardware testet and works fine and i install the new driver 388.13 WHQL
Windows 8.1 46bit was updatet also.
Now i have no idea to solve the problem.
With the Blender v2.8 the cards works fine but LazyDodo wrote this are a different render code, so the problem are solved when v2.8 are official but with 2.79 i can not work because the orange display error concealed the mesh, i can not see what i make.

**Information from:** LazyDodo (LazyDodo) triaged this task as "Incomplete" priority. LazyDodo (LazyDodo) added a comment. 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/macOS, Official releases come with blender-softwaregl On MS-Windows: Download this dll and copying it so its located in the same directory as 'blender.exe' and run Blender normally. Once done testing be sure to remove it cause things will be a lot slower 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. if the problem goes away with the opengl32 replacement, it's a gpu driver bug, the rendering code in 2.79 and 2.8 are quite different, so 2.8 just isn't triggering the issue. Lorenz: so i make the test with the opengl32.dll and blender works fine but without the opengl32.dll i have the orange display error. The new TITAN XP are Hardware testet and works fine and i install the new driver 388.13 WHQL Windows 8.1 46bit was updatet also. Now i have no idea to solve the problem. With the Blender v2.8 the cards works fine but LazyDodo wrote this are a different render code, so the problem are solved when v2.8 are official but with 2.79 i can not work because the orange display error concealed the mesh, i can not see what i make.

Brecht Van Lommel commented

2017-11-23 18:09:01 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2017-11-23 18:09:01 +01:00

Changed status from 'Archived' to: 'Open'

Brecht Van Lommel reopened this issue

2017-11-23 18:09:01 +01:00

Brecht Van Lommel commented

2017-11-23 18:09:01 +01:00

I've seen this problem with the Titan Xp and recent drivers on Windows, but did not investigate it yet.

It may be a driver bug, but it can just as well be a bug in how Blender uses OpenGL. And if it is a driver bug, we can report it to NVIDIA.

I've seen this problem with the Titan Xp and recent drivers on Windows, but did not investigate it yet. It may be a driver bug, but it can just as well be a bug in how Blender uses OpenGL. And if it is a driver bug, we can report it to NVIDIA.

Brecht Van Lommel commented

2017-11-23 18:09:13 +01:00

Added subscriber: @zeauro

Vuk Gardašević commented

2017-11-30 21:41:21 +01:00

Added subscriber: @ToumiX

Matej Kovacic commented

2018-03-30 01:43:22 +02:00

Added subscriber: @MatejKovacic

SlyNine commented

2018-04-23 20:44:04 +02:00

Added subscriber: @SlyNine

SlyNine commented

2018-04-23 20:44:04 +02:00

I'm having the same issue. Multiple Blender versions, I've switched motherboards (from 2 separate Intel X99s to a Ryzen 2700x just installed today) multiple drivers, multiple formats. The only two things that remain are Blender and this Titan X (pascal first version) Remember, there is two different versions of the Titan X pascals. Switching out the video card solves the issue.

Ray molenkamp removed their assignment 2018-06-15 22:50:50 +02:00

Brecht Van Lommel was assigned by Ray molenkamp

2018-06-15 22:50:50 +02:00

Luke Hayne commented

2018-07-07 19:00:17 +02:00

Added subscriber: @Photini

Luke Hayne commented

2018-07-07 19:00:17 +02:00

I have just installed the new Titan Xp and I am having the same problems, does anyone know if this has been solved yet? I can enter use preferences and disable cuda and disable Titan, I then re-enable them both and save user settings which sometimes solves the problem, also switching between cpu and gpu can sometimes cure the problem.

I have just installed the new Titan Xp and I am having the same problems, does anyone know if this has been solved yet? I can enter use preferences and disable cuda and disable Titan, I then re-enable them both and save user settings which sometimes solves the problem, also switching between cpu and gpu can sometimes cure the problem. ![Screenshot (85).png](https://archive.blender.org/developer/F3894194/Screenshot__85_.png)

Lorenz commented

2018-07-08 09:17:11 +02:00

I am working with this problem few months very easy,
Switch from the solid Mode to render Mode (Waithing for finish Rendering) and back again to the solid Mode this solve the problem in this Open Session, if you close this blend file and Open again you have to do the Same steps again.
It looks like to force blender there are a titan xp Card here please used it.
In every new or open blend file i have to do this steps at first to working fine in the solidmode.
I am testing 2.8 with the Titanx XP also..... No Problems, so i am waiting for the official 2.8 and this solve the problem to

I am working with this problem few months very easy, Switch from the solid Mode to render Mode (Waithing for finish Rendering) and back again to the solid Mode this solve the problem in this Open Session, if you close this blend file and Open again you have to do the Same steps again. It looks like to force blender there are a titan xp Card here please used it. In every new or open blend file i have to do this steps at first to working fine in the solidmode. I am testing 2.8 with the Titanx XP also..... No Problems, so i am waiting for the official 2.8 and this solve the problem to

Kevin Whitfield commented

2018-08-08 21:15:08 +02:00

Added subscriber: @kevinw

Kevin Whitfield commented

2018-08-08 21:15:08 +02:00

I'm getting the same issue, but would like to add that it's also affecting the drawing of the windows.
Blender 2.79b
NVIDIA TITAN Xp 24.21.13.9882 (398.82)

I'm getting the same issue, but would like to add that it's also affecting the drawing of the windows. Blender 2.79b NVIDIA TITAN Xp 24.21.13.9882 (398.82) ![blenderOpps.png](https://archive.blender.org/developer/F4161164/blenderOpps.png) ![blenderOpps2.png](https://archive.blender.org/developer/F4161171/blenderOpps2.png) ![blenderOpps2.png](https://archive.blender.org/developer/F4161227/blenderOpps2.png)

Brecht Van Lommel commented

2019-06-17 12:43:55 +02:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-06-17 12:43:55 +02:00

Brecht Van Lommel commented

2019-06-17 12:43:55 +02:00

For me this is fixed with latest drivers in 2.79 and 2.80.

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

NVIDIA TITAN XP Pascal display error #53179