OpenImageDenoise crash / computer restart #94333
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#94333
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10 (x64)
Graphics card: GTX970
Blender Version
Version 3.0.0
Short description of error
Finish rendering when Denoise processing should take place, the computer restarts. This happens with the Cycles rendering on the GPU, when the "Use nodes" checkbox is checked in the "Composting", and the "Denoising Data" checkbox is unchecked on the right panel. Regardless of the scene, be it a simple cube or a complex scene like 512 or 1024 samples, the PC always reboots at the end.
Под конец рендера когда должно происходить обработка Denoise, происходит перезагрузка компьютера. Происходит это с рендером Cycles на GPU, когда в "Composting" включена галочка "Use nodes", а на панели с права отключить галочку "Denoising Data". Независимо от сцены, будь то простой куб или сложная сцена, например 512 или 1024 семпла, всегда в конце происходит перезагрузка ПК.
Exact steps for others to reproduce the error
I attach a screenshot of the settings and the scene file itself.
Прикрепляю скриншот настроек и сам файл сцены.
Bug.blend
Added subscriber: @Nefsky
Added subscriber: @Alaska
Changed status from 'Needs Triage' to: 'Needs User Info'
The fact your computer restarts indicates some other issue. Maybe you have an unstable overclock on your CPU, RAM, GPU.
Maybe your power supply isn't powerful enough for your components?
Maybe Windows is corrupt in some way.
If you want, you can test Blender 3.1 Alpha with all the latest bug fixes to see if that helps, but it's highly likely that the issue is with your computer, not Blender.
Blender 3.1 Alpha: https://builder.blender.org/download/daily/
Thanks for the answer, it is always preloaded at the end of the render with the specified settings in the screenshot. No matter what the scene, it will be rendered in 3 hours or 1 minute.
Try to run the attached scene and press F12. I doubt that the problem is just me.
Bug.blend
Testing with the attached file in Blender 3.0 with a RTX 3060 running driver version 470.94 on Linux with a Ryzen 9 5950X, I was not able to observe Blender crashing or my computer restarting.
The issue is high likely to be something wrong with your computer.
Thanks for the answer. I tested version 3.1 Alpha, unfortunately I have the same problem there.
My computer is not overclocked, I render complex scenes in 3D max and Corona, there are no problems there. The computer was assembled about 5 years ago, during this time I have seen this for the first time. All stress tests of memory, CPU and GPU, which I conducted for up to half an hour, are successful, so I decided to write to you. For some reason, in blender 3 versions at the end of the render, when the processing of samples comes to an end, regardless of whether 512 samples or 4096, always at the very end, when denoise is apparently processed. Try to restart your computer and then immediately make a test of my scene in version 3, then it will be clear for sure.
I also noticed that the computer does not always restart, but always if you restart the computer yourself and after the restart, open the scene and press F12 to render, and at the end the computer restarts itself.
If it's not difficult, try making 1024 or 2048 samples in my scene and test it.
Hmm ... I tried to record video for you via GeForce Experience where the reboot occurs, but when capturing the video, the reboot does not happen, everything works fine. Weird...
The issue could be related to your GPU driver (I'm just trying ideas to see if anything helps). Are you able to try installing the latest drivers from Nvidia's website? https://www.nvidia.com/Download/index.aspx
I have also noticed the occasional issue when using the 49X drivers. And so after testing the latest GPU driver are you able to re-test with the latest 47X GPU driver? https://www.nvidia.com/Download/Find.aspx?lang=en-us
Added subscriber: @PratikPB2123
I have the latest drivers installed. Also tried and installed 472 GPU driver, the problem remained.
Did some more tests and here's what I found out. I installed the Steam version of Bender and the problem disappeared, everything works fine now. Steam is installed on a different SSD, and before that there was a portable version on the system SSD M.2 (Samsung SSD 970 EVO Plus 250GB), could this be the problem?
my system, suddenly come in handy
I'm not entirely sure why you experience issues with Blender on one storage device and no issues on another. If that is the issue, then it is hard for us to reproduce the issue for us to try and fix. I personally have multiple storage devices in my computer and running Blender from each of them doesn't result in the issues you're experiencing.
Unfortunately, after manually restarting the computer and running the blender and the scene for the test, the computer rebooted again. I myself can’t understand what the reason is. Today I ran 3DMark stress test for an hour and there were no problems.
It’s just interesting that the failure occurs at the very end of the render, whether it’s in a minute if the scene has 512 samples, or in an hour, if there are a lot of samples, also at the very end of the render at the same values. That is, for example, if I set 1024 render samples, then the failure will always occur at 1008 steps, always regardless of the scene.
And only if the "Use nodes" option is enabled on the "compositing" tab and the "Denolsing Data" option on the right is disabled at the same time. In all other options, there are no problems.
Changed status from 'Needs User Info' to: 'Needs Triage'
I don't know what's going on and I personally can't reproduce this issue on my computer, I will leave the triaging of this bug report to someone else.
As a side note: You say your computer reboots. What exactly happens? Does the render finish, the screen then turns black and the computer turns on again? Or does the screen turn blue, show an error, then the computer turns off and on again?
Thank you for your time. For example, I render 1024 samples, press F12, the render starts, at 1008 samples there is a slight pause, apparently there is an attempt to remove noise at the end of the render and after that a reboot occurs. Perhaps the problem is only with me, try to open the scene that I sent you in Blender 3 versions, then press F12 and if the render is completed successfully, then close the blender and then open it and repeat 3-4 times, if everything is fine, then the problem is apparently just me.
If I do not use noise control in "compositing" with the "Use nodes" option enabled and the "Denolsing Data" option disabled, then everything works fine. So I just won't do that and everything will continue to work fine.
Thanks again.
Added subscriber: @Archivist15
I have Win 10 pro 64, downloaded the blend file and compositing executed. Can't reproduce the fault.
The reason for butting in, was to ask Vitaliy to run CMD prompt with admin rights (right click - run as admin) and do a sfc /scannow. See how that goes.
His situation sounds similar to mine a little while back.
After a series of bad luck events involving faulty new ram and a dying ssd, Blender 3.0 behaving strangely. It lead to a clean windows 10 install, noticed that Windows Update for whatever reason seems to corrupt system files.
For me sfc fixed windows system files and seems to be running okay now.
I'm one user, the more people test and share if it works for them or not, the better.
Merry Christmas!
Thanks for the advice Julian. I did a system files check, no problem with that. The blender and the render itself are working fine, the only thing is that if use noise control in "compositing" with the "Use nodes" option enabled and the "Denolsing Data" option disabled, then at the end of the render, when noise cleaning is in progress, the computer restarts.
Added subscriber: @lichtwerk
Could this be related {#94127}?
Changed status from 'Needs Triage' to: 'Needs User Info'
Since noone could reproduce, I am afraid we have to move this to the Unconfirmed tag with the following consequences:
I would advise to watch #94127 / #76668 since these could be related...
Added subscriber: @brecht
It's clearly something in OpenImageDenoise that is leading the computer to restart. It's unlikely this is related to the GPU. I would guess either some SIMD instruction, or something related to thread scheduling.
In general Blender should not be able to cause a computer restart like this, that basically always indicates a problem in the operating system, drivers or hardware. Ideally we'd still have a way to work around this, but it's difficult to figure out what the cause is.
When rendering in Blender 3, the computer restartsto OpenImageDenoise crashOpenImageDenoise crashto OpenImageDenoise crash / computer restartAdded subscriber: @Raimund58
Added subscriber: @da9els
I'm having this problem as well but can't reproduce from OP's 'bug.blend' or default cube with factory default settings - only changed render to cycles.
I have several .blend files which will crash the computer when using Open Image Denoiser. I've experienced the same issue with Optix (and from what I read it is not uncommon either) but now only OID hard crashes my machine.
I've also had scenes producing a blank / transparent (#93838) in earlier blender builds with different driver. Some of these I could eliminate by copying meshes, camera and light to another instance of blender.
How ever, the issue is similar (no problem rendering the scene but as soon as denoiser is applied, computer crash) and I've tried a few scenarios to see if I could isolate the problem.
I've been testing in:
· Blender 3.0 / 3.1 (Several different builds - Cycles / CylecsX / K-Cycles)
· Windows 10 x64 (with. Nvidia Studio Driver 511.09 / Nvidia Game Ready Driver 511.79)
· Manjaro 21.2.4 (Kernel 5.15 / Nvidia proprietary 510)
The result is the same regardless of OS or drivers.
My machine is a i9 7900X / RTX 3070.
The system is running rock solid on all other accounts.
I'm assuming that it's related to a specific combination of settings / add-ons / scene properties. I will keep testing and compare OP's bug.blend to a known culprit .blend of my own.
That means I'm not the only one with such a problem.
No. I've seen several threads around the webz talking about similar problems with denoising.
Added subscriber: @Gim.Pact88.99s2b
Hello, I also have similar problem. My pc reboot itself right when cycle render start denoising process. From what I've tested and observed, it appear that the OpenImageDenoise caused it, but when I rendered with optix denoiser, it rendered fine without any problem. I have tested on two different blend files and same problem occurs when the denoising process starts. Originally, when I was rendering in my office (intel cpu + rtx 2070) there were no problem whatsoever when rendering with OpenImageDenoiser, but using the same file on my pc at home (amd cpu + rtx 3060), the problem occurs. Could it be a combination of hardware and drivers update?
Hello again, I've manage to solve my problem. At first, I tried rendering my scene with OID at 50% resolution of 1902x1080, it rendered without problem. Bumping it to 75% caused my pc to reboot. Switching from game ready driver to nvidia studio driver did not help, same problem still occurs. After that, I changed both my cpu clock ratio and cpu vcore to auto and try rendering again the same scene with 100% of the resolution, this time it rendered fine. Furthermore, I've tried rendering with both nvidia studio driver and game driver and also bump the resolution to 200% and it rendered fine without problem. I hope this helps whoever have the same problem as me.
@Nefsky hi, still experiencing this? Have you made any upgrades on OS/Hardware/BIOS side by now? This might have fixed the crash.
Can you check again (this time in 4.1): https://builder.blender.org/download/daily/