Page MenuHome

Black screen restart crash using compositor rendering for image generation
Needs Triage, NormalPublic

Description

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: rB375c7dc4caf4
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

8k image

thanks have a nice day !

Event Timeline

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.

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 (EAW) changed the task status from Needs Triage to Needs Information from User.Apr 23 2020, 7:37 PM

No problems here using 2.90 rBf5b540593cd5

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


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

Ankit (ankitm) changed the task status from Needs Information from User to Needs Triage.May 2 2020, 3:33 PM

@Philipp Oeser (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 (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)

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