Has any developer been able to reproduce the issue on this one? I'd greatly appreciate the help, as I seem to have identified the drivers as being a contributing factor to the crash.

Ok, I have a much clearer picture of the problem now. It appears to be directly related to the AMD GFX drivers that I'm using. Originally, when this was posted, I was using the most current version of the drivers:
win10-radeon-software-adrenalin-2020-edition-20.8.1-aug4

Richard Antalik had previously indicated that I had provided every necessary piece of information and had marked it to Needs Developer to Reproduce. There is no further information that I can provide - if there was, I would certainly provide it but I have made every effort to give everything.

Hi Brecht,

In T79198#991040, @ver (verrafa) wrote:

In T79198#990176, @Peter (highonsnow) wrote:

(I just left a comment under the other thread) This is odd - I can't find that GPU Scheduling setting, or Hardware Accelerated GPU Scheduling mentioned under the Graphics/Display settings screens in Windows 10.. I've looked up step by step guides and I'm missing that part completely!

Try the latest version. I seems it was added with the windows 10 2004 update. I think it is not Blenders fault. Something changed with the cuda / windows drivers. But i am so happy that i can continue rendering on two graphics cards.

It seems for me you looked at the right position.

I have upgraded Windows 10 to release 2004. Issue persists on various versions of Blender (2.82, 2.91).

Unfortunately I'm not able to upgrade to 2004 as it's not available for my machine, yet.

Default Cube rendering GPU Cycles for all attempts below:

(I just left a comment under the other thread) This is odd - I can't find that GPU Scheduling setting, or Hardware Accelerated GPU Scheduling mentioned under the Graphics/Display settings screens in Windows 10.. I've looked up step by step guides and I'm missing that part completely!

This is odd - I can't find that GPU Scheduling setting, or Hardware Accelerated GPU Scheduling mentioned under the Graphics/Display settings screens in Windows 10.. I've looked up step by step guides and I'm missing that part completely!

I've just tested the default cube on 2.91.

I seem to have that, their numbers are confusing but the documentation shows: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-7-2

Same type of crash, however even though I was doing a GPU render, the CPU maxed out for approx 30-60 seconds, sitting at 100% before easing off again, and then the crash occurred.

I'll try 2.91 and get back to you!

I'm after finding a similar report of the issue: https://developer.blender.org/T75319

Hi RIchard,

PS: I have since changed GPU to an AMD Radeon RX 5700, same issue (included in the log above)

Ok, so I'm having a rendering issue on 2.83 also, when trying to render via Cycles and GPU selected.

Just to clarify, I wasn't operating at full RAM at the time of render, there was still plenty of RAM available for Blender at the time of crashing.

I attempted to render the model after closing down a few applications and it appears it might have been a RAM availability issue. I would ask however, if it should be an expected behaviour for Blender to crash out and close down if RAM expectations were not being met. It might be worth looking into testing Blender in certain constrained environments, where there are other applications running and it's not getting the full juice that it would like for a large mesh to render on Cycles (GPU selected only).

Hi Hans,

The model is quite a tall model, approx 208m high. The original version of the model which is scaled much shorter (exact same mesh, just the non-resized version, units show only a approx 5m tall) appears to render fine. The crash is experienced when attempting to use Cycles GPU rendering of the larger scaled (same) model.