Black screen restart crash using compositor rendering for image generation #76015

New Issue

linxuxu · 2020-04-23T05:26:46+02:00

linxuxu commented

2020-04-23 05:26:46 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: TITAN Xp COLLECTORS EDITION/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4ca
Worked: (v2.81.16)

Short description of error
crash using compositor rendering for image generation
(I check the version 2.82a fix the crash addon glTF but still happens when i upgrade)

Exact steps for others to reproduce the error
*F12 render
*add viewer to render layers (backdrop)
*denosie image
the computer Black screen restart

TEST12313.blend

8k image

courtyard_night_2k.hdr

thanks have a nice day !

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: TITAN Xp COLLECTORS EDITION/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `375c7dc4ca` Worked: (v2.81.16) **Short description of error** crash using compositor rendering for image generation (I check the version 2.82a fix the crash addon glTF but still happens when i upgrade) **Exact steps for others to reproduce the error** *F12 render *add viewer to render layers (backdrop) *denosie image the computer Black screen restart [TEST12313.blend](https://archive.blender.org/developer/F8490378/TEST12313.blend) 8k image ![rmtpabip_8K_Roughness.jpg](https://archive.blender.org/developer/F8490385/rmtpabip_8K_Roughness.jpg) [courtyard_night_2k.hdr](https://archive.blender.org/developer/F8490401/courtyard_night_2k.hdr) ![image.png](https://archive.blender.org/developer/F8490405/image.png) thanks have a nice day !

linxuxu commented

2020-04-23 05:26:46 +02:00

Added subscriber: @7shaven

Brecht Van Lommel commented

2020-04-23 13:53:43 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2020-04-23 13:53:43 +02:00

A black screen error indicates a bug in Windows or drivers. There may sometimes be ways for us to work around that in Blender, but usually it's hard.

Intel OpenImageDenoise used for the Denoise node uses modern CPU instructions, and I suspect they are either not supported or not correctly handled by Windows. I've seen similar issues in the past, particularly when using a recent CPU model without using the very latest Windows version.

You could try upgrading from Windows 10 May 2019 Update to November 2019 Update.

Another possible cause may be that CPU not being cooled properly and overheating when using a particularly optimized piece of code like OpenImageDenoise. Though that would only be the case of denoising runs for a while, it's usually too fast to cause this kind of problem.

A black screen error indicates a bug in Windows or drivers. There may sometimes be ways for us to work around that in Blender, but usually it's hard. Intel OpenImageDenoise used for the Denoise node uses modern CPU instructions, and I suspect they are either not supported or not correctly handled by Windows. I've seen similar issues in the past, particularly when using a recent CPU model without using the very latest Windows version. You could try upgrading from Windows 10 May 2019 Update to November 2019 Update. Another possible cause may be that CPU not being cooled properly and overheating when using a particularly optimized piece of code like OpenImageDenoise. Though that would only be the case of denoising runs for a while, it's usually too fast to cause this kind of problem.

linxuxu commented

2020-04-23 18:07:20 +02:00

In #76015#916141, @brecht

Thanks for the answer

I tried it a hundred times , crack shot .

shift +a add any node will trigger black screen when I drop it to the viewer .

my CPU is i9 7900x 32G ram, I had upgraded November 2019 Update already.

> In #76015#916141, @brecht Thanks for the answer I tried it a hundred times , crack shot . shift +a add any node will trigger black screen when I drop it to the viewer . my CPU is i9 7900x 32G ram, I had upgraded November 2019 Update already.

Evan Wilson commented

2020-04-23 19:37:41 +02:00

Added subscriber: @EAW

Evan Wilson commented

2020-04-23 19:37:41 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Evan Wilson commented

2020-04-23 19:37:41 +02:00

No problems here using 2.90 f5b540593c

or 2.82a on a CPU that came out in June 2009.

Operating system: Windows-10-10.0.18362-SP0 64 Bits (18363.778 is the Windows version according to my system's About page)
Graphics card: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 376.51
Intel Core i7 950 3.07 GHz

@7shaven Go to Windows Settings->System->About. What number is shown under "Windows specifications"->"OS build"?

No problems here using 2.90 f5b540593c ![1.jpg](https://archive.blender.org/developer/F8491249/1.jpg) or 2.82a on a CPU that came out in June 2009. ![2.82a_1.jpg](https://archive.blender.org/developer/F8491251/2.82a_1.jpg) --- Operating system: Windows-10-10.0.18362-SP0 64 Bits (18363.778 is the Windows version according to my system's About page) Graphics card: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 376.51 Intel Core i7 950 3.07 GHz --- @7shaven Go to Windows Settings->System->About. What number is shown under "Windows specifications"->"OS build"?

linxuxu commented

2020-04-24 13:48:49 +02:00

win10 1909 18363.815 @EAW

Ankit Meel commented

2020-05-02 15:33:11 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Sergey Sharybin commented

2020-06-24 16:12:30 +02:00

Added subscribers: @lichtwerk, @Sergey

Sergey Sharybin commented

2020-06-24 16:12:30 +02:00

@lichtwerk I'm a bit confused here. To my knowledge the module project is assigned once the issue is reproduced and confirmed. AM I missing something, do we have confirmed "repro" here or is this still needs triaging?

Philipp Oeser commented

2020-06-24 16:41:22 +02:00

In #76015#964367, @Sergey wrote:
@lichtwerk I'm a bit confused here. To my knowledge the module project is assigned once the issue is reproduced and confirmed. AM I missing something, do we have confirmed "repro" here or is this still needs triaging?

This still needs proper triaging.
I sometimes tag modules already if I have report open (but postpone proper triaging to later).
I am unsure if this was defined somewhere [I mean tagging modules only after confirmation took place]?
Doesnt seem to be defined here:
https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook
https://wiki.blender.org/wiki/Process/A_Bugs_Life

If this is somehow problematic, I can change habits, for me this actually has benefits, when scanning through "Needs Triage" reports, it tells me

I probably looked at this before
gives me a module hint (if mindset is already in that module realm it then might fit better to triage this report)

> In #76015#964367, @Sergey wrote: > @lichtwerk I'm a bit confused here. To my knowledge the module project is assigned once the issue is reproduced and confirmed. AM I missing something, do we have confirmed "repro" here or is this still needs triaging? This still needs proper triaging. I sometimes tag modules already if I have report open (but postpone proper triaging to later). I am unsure if this was defined somewhere [I mean tagging modules only after confirmation took place]? Doesnt seem to be defined here: https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook https://wiki.blender.org/wiki/Process/A_Bugs_Life If this is somehow problematic, I can change habits, for me this actually has benefits, when scanning through "Needs Triage" reports, it tells me - I probably looked at this before - gives me a module hint (if mindset is already in that module realm it then might fit better to triage this report)

Dalai Felinto commented

2020-06-24 17:18:08 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2020-06-24 17:18:08 +02:00

Let's move the discussion to the Blender chat, for now I'm removing the tag until the issue is fully triaged.

Ankit Meel commented

2020-07-02 16:38:12 +02:00

Added subscriber: @ankitm

Robert Guetzkow commented

2020-11-03 11:13:59 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-11-03 11:13:59 +01:00

@7shaven Does this issue still occur on your system?

Philipp Oeser commented

2020-11-18 13:28:40 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2020-11-18 13:28:40 +01:00

In #76015#1046866, @rjg wrote:
@7shaven Does this issue still occur on your system?

Yes, since this report is a bit stuck, it would be nice if it - possibly/magically - resolved itself using fresh builds from https://builder.blender.org/download/

> In #76015#1046866, @rjg wrote: > @7shaven Does this issue still occur on your system? Yes, since this report is a bit stuck, it would be nice if it - possibly/magically - resolved itself using fresh builds from https://builder.blender.org/download/

Robert Guetzkow commented

2020-11-25 14:46:54 +01:00

Changed status from 'Needs User Info' to: 'Archived'

Robert Guetzkow closed this issue

2020-11-25 14:46:54 +01:00

Robert Guetzkow commented

2020-11-25 14:46:54 +01:00

Nobody could reproduce the issue and there has been no activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

Nobody could reproduce the issue and there has been no activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

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

Black screen restart crash using compositor rendering for image generation #76015