Hey folks! Thanks for the feedback regarding all of this. The system requirements page has been updated to reflect the updated driver requirement. Take care and have a happy holidays!

https://www.sidefx.com/Support/system-requirements/ [www.sidefx.com]

Hello.
I also stuck with the same error. I update Houdini to latest version Houdini FX Version 20.0.547. latest nvidia driver. problem with Karma both XPU and CPU, single frame rendering are fine, but when I try to render frame range, error appear after first frame stop render. I tried on scene with simple box in it, but render is the same. I don't have redshift, but I have instaled V-ray, that works fine. My workstation spec:
Operating System: Microsoft Windows 11 Pro x64
Number of Cores: 32
Physical Memory: 127.21 GB
Number of Screens: 1
Screen 0: 2560 x 1440 at 0,0
Work Area 0: 2560 x 1392 at 0,0
Screen 0 DPI: 108.9

Platform Build: windows-x86_64-cl19.35
Python Version: 3.10
Qt Version: 5.15.2
USD Version: 23.08
UI Scale: 1.000

OpenGL Vendor: NVIDIA Corporation
OpenGL Renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL Version: 4.6.0 NVIDIA 546.33
OpenGL Shading Language: 4.60 NVIDIA
Detected: NVidia Consumer
24564 MB
546.33.0.0

in_am_i
problem with Karma both XPU and CPU, single frame rendering are fine, but when I try to render frame range, error appear after first frame stop render.

Are you getting the same exit code -1073741819?
If it's affecting KarmaCPU too, then it is not GPU driver related, and we'll probably need a repro scene+steps to debug further. Better to file that as a bug than on the forum.

Thanks

brians

in_am_i
problem with Karma both XPU and CPU, single frame rendering are fine, but when I try to render frame range, error appear after first frame stop render.

Are you getting the same exit code -1073741819?
If it's affecting KarmaCPU too, then it is not GPU driver related, and we'll probably need a repro scene+steps to debug further. Better to file that as a bug than on the forum.

Thanks

Thanks for the answer. I already disscused problem with support, and maybe problem was in V-ray, as I just installed Daily Build, without v-ray, and everyhing start working. BTW, all my drivers and updaets is up to date

I'm also getting this error rendering fur with xpu. Houdini 20.0.590. Nvidia driver 551.23. sometimes I get 20 frames, sometimes 2

same here 551.23 got the same error while karma XPU rendering.

p.s. Rolling back to 546.33 fixed the problem.

tbattistetti

brians
Hi guys
Its looking like this is an NVidia driver issue (windows only).
The good news is that it seems fixed in their very latest driver.
Could you please test with 546.33 (available in both studio and game-ready) and let us know if it fixes this crashing issue?
thanks very much!

Confirming, working as expected now!
Cheers!

I have this problem too, but unfortunately the problem persists even with the nvidia driver update (v551.23).
But I should mention that there is no problem with CPU rendering

I get the same error.
I have updated the Nvidia driver to the latest.
Now I can render output multiple images with Karma XPU, but it still stops with an error at random frames.

Houdini 20.0.590
Windows11
NVIDIA GeForce RTX 3050Ti Laptop GPU
nvidia driver(551.23)

Qhuman
same here 551.23 got the same error while karma XPU rendering.
p.s. Rolling back to 546.33 fixed the problem.

What happens if you roll back to 546.33?

brians

Qhuman
same here 551.23 got the same error while karma XPU rendering.
p.s. Rolling back to 546.33 fixed the problem.

What happens if you roll back to 546.33?

Rollback to 546.33 solved the problem. Rendering as usual.

We've found the 550+ NVidia drivers have an issue.
To fix it you can set this environment variable
KARMA_XPU_OPTIX_ENABLE_OPTIXIR=1
but if you drop back to a 545 driver, then it needs to be set back to 0

Please let us know if that solves your issues with the 550+ drivers.

We're waiting on a response from NVidia to confirm the issue on their end, and any kind of estimate on when it might be fixed.

brians
We've found the 550+ NVidia drivers have an issue.
To fix it you can set this environment variable
KARMA_XPU_OPTIX_ENABLE_OPTIXIR=1
but if you drop back to a 545 driver, then it needs to be set back to 0

Please let us know if that solves your issues with the 550+ drivers.

We're waiting on a response from NVidia to confirm the issue on their end, and any kind of estimate on when it might be fixed.

I've 551.52 and with this enviro var set to 1 or 0 issue still occurs. (I dont have hairs in scene). With 546.33 and set to 0 seems to work fine, but other cuda errors (like bad memory adress?) often occurs

sniegockiszymon
I've 551.52 and with this enviro var set to 1 or 0 issue still occurs. (I dont have hairs in scene). With 546.33 and set to 0 seems to work fine, but other cuda errors (like bad memory adress?) often occurs

Ok, this sounds like another driver issue :/
Can you put together a repro scene (+ instructions) and submit as a bug?
thanks a lot

Any news on this?
With drivers below 546.33 i get the exit code -1073741819 when rendering sequences and with 546.33 and above i don't have gpu support. No matter what is set in the houdini.env

Im on latest daily build 20.0.649 and a rtx 3060

SiRpRoHxO
Any news on this?

No, AFAIK the user never logged a bug.

SiRpRoHxO
With drivers below 546.33 i get the exit code -1073741819 when rendering sequences and with 546.33 and above i don't have gpu support. No matter what is set in the houdini.env
Im on latest daily build 20.0.649 and a rtx 3060

We don't get anything like this on our end.
Are you Windows or Linux?
Could you log a bug with a repro scene + specific repro steps? And we will investigate and report back.

thanks

hmm strange, according to the nvidia control panel I'm on 546.33 and GPU isnt working... (Im on Windows)



If you confirm that 546.33 is working on your end, I need to investigate

Otherwise i try to create a repro scene

SiRpRoHxO
hmm strange, according to the nvidia control panel I'm on 546.33 and GPU isnt working... (Im on Windows)
If you confirm that 546.33 is working on your end, I need to investigate
Otherwise i try to create a repro scene

I've tried with 20.0.625 and 546.33, and Karma XPU is working fine for me.
And are you saying with a more modern driver you get no GPU support at all? What happens in the viewport? Is it just sequence rendering that is broken for you? Or is it XPU in general?

thanks

I now did a complete driver removal with DDU and it seems that did the trick.
Updated to latest Nvidia driver and gpu support works again.

so maybe some old driver remains that got in each others way...