AMD GPU & Cycles: Memory access fault by GPU node-1 Reason: Page not present or supervisor privilege

Description:

Blender 4.0.2-10 crashes when using HIP Cycles (rx 6800, rocm 5.6.1) The same does not happen with blender 4.0.2-9, same file, same version of rocm, same configurations.

The error in the terminal is:

Memory access fault by GPU node-1 (Agent handle: 0x7092c2daa300) on address 0x708fde7ac000. Reason: Page not present or supervisor privilege. IOT instruction (core dumped) blender

Additional info:

tested with 'classroom' blender sample file from:

https://download.blender.org/demo/test/classroom.zip

with regards to rocm 5.6.1, all new versions (5.7.1 and 6.0) have caused problems and crashes for users -- rocm 5.6.1 is stable across multiple applications (tested pytorch and blender up to 4.0.2-9). See below recent forum post on the matter:

https://bbs.archlinux.org/viewtopic.php?id=290424

Also see bug reports on rocm:

https://bugs.archlinux.org/task/80326#comment223998

rocm-hip-sdk#2 (closed)

• package version(s): blender 4.0.2-10

Steps to reproduce:

1. open classroom.blend file
2. go to 'Render' Panel
3. set Render Engine to Cycles
4. set Feature set to Supported
5. set Device to GPU Compute (make sure to select HIP back end using the AMD GPU in the preferences)
6. go to 'Sampling' options (within the 'Render' panel)
7. check Noise Threshold check box in Sampling-> Viewport
8. check Denoise checkbox in Sampling-> Viewport
9. check Noise Threshold check box in Sampling-> Render
10. check Denoise checkbox in Sampling-> Render
11. Change 'Viewport Shading' to 'Rendered'
12. if the segfault does not trigger immediately, try switching between 'Viewport Shading' 'Rendered' and 'Material Preview'
13. The segfault triggers for me after switching between 'Viewport Shading' 'Rendered' and 'Material Preview' a couple of times
14. the issue triggers for me straightforwardly on a number of other personal files I am not in the position of sharing. File classroom.blend is reproducing the issue as described in points above. Possibly other files from Blender Files do the same (not the standard start-up cube)