3Ds MAX 2022 arnold GPU renderer crashing on render

[mmrajchel]

Over the past few days I have been rendering some animations at 720p as a motion test for a client. The plan was to do them all at 720p and then go back after the fact and render at 1080p for the final deliverable. Everything has been going fine until I got to one of my files. I did the following, lets call this scene "Scuffed"

Opened scuffed. Change output location and resolution. Hit render.
Arnold gpu renderer renders the first frame and then throws an error on the render messages and then crashes to desktop. 

Things Ive tried.
-Drivers for nvidia are up to date
-Arnold is up to date
-3ds max 2022 is up to date
-Tried opening the file and re-rendering it without changing anything (other than the file location and name). still crashes
-tried turning off denoiser. still crashes.
-tried opening one of the other files from the project and they seem to render fine.

Ive attached the quick screen grab of the error message. 

Please help, on a deadline and freakin out just a tiny bit. 

[RobH2]

If you read the error message it looks like you are running out of memory. What's your machine and how much RAM do you have? Open Task Manager and watch your RAM in the 'Performance' tab and see if the RAM runs out just before the crash. 

[mmrajchel]

I'll double check that. Should be fine though. I've got 32 gig of ddr4, though I wasn't watching the memory during the test. Will report back later. 

[RobH2]

You could possibly write the OP of this thread a PM and see if they solved it.

https://answers.arnoldrenderer.com/questions/33205/3ds-max-2022-arnold-gpu-rendering-error.html 

Here's another that might be the answer: 

https://answers.arnoldrenderer.com/questions/31544/3ds-max-2021-arnold-gpu-rendering-error.html 

(From that thread): "Thanks, for providing the crashing scene, I can confirm it crashes.

It looks like this might be happening when there are two image nodes that point to the same texture. While we work on a fix, you might be able to work around this by removing one of the duplicate image nodes and instead reusing one of the image nodes.

This probably also explains why merging scenes caused a problem, since each scene contained an image node pointing to the same texture."

[mmrajchel]

Ill have to reach out to them and see what happened. 
On the one threads advice, I went through and double checked my textures to see if any of them were sharing bitmaps. there was one that was sharing but wasnt being used so i deleted it and still ended up with the same result, only this time, it didnt abord the render or the program. It through up this error and continues to render frames but not to completion (each frame that it rendered was somewhat blurry and had some glitched artifact to it. )

Ive attached the error message as well as my current usage. As you can see, at the time of crash, there was really no GPU usage, but for whatever reason my cpu was pinned to 100 percent.

[RobH2]

Sorry I couldn't help. That's a new one that I haven't seen before.

I'm wondering what would happen if you reverted back a couple of releases of the NVidia driver? I had a problem once and I did that and it went away. Be sure to check "Clean Install" when you reinstall and then reboot. Worth a try. NVidia drivers install pretty fast these days. I'd try that and an ENU reset at the same time and see if it goes away. Be sure to save your old ENU so you can revert if necessary. 

If it solves it, then install the next NVidia driver in the versions. If still OK, now install the latest one. Then if OK, replace your original ENU. 

[CiroCardoso3v]

Check on Arnold Answers. You have the Devs there that can have a look at those logs.