GPU always fails to CPU Daz3d

[forbiddenfables1]

Ok, my while rendering ,my GPU always falls back to CPU. at first i thought it may be because the scene is very big but then i tried a render with only a G8 Female in the scene and it happens the same. My daz and studio drivers are upto date.

I've attached the log file of the render of the G8 i did, if anyone can help me please.

The GPU is used in the begining of the rendering but fails in the middle and falls back.

I've tried ticking off the CPU in the advanced render tab....I would use the scene optimizer for bigger scene but if its failing to smaller scenes how can i render smoothly ?

my Specs are :


Any help would be appreciated.

 

[fyl3toys]

I kinda remember that there is more than one option in DAZ for defaulting to the GPU and if you don't have both options checked it will continue to render using the CPU...

Somewhere in the settings. I dont have DAZ currently installed so I cant offer more than that. Sorry.

 

[MissFortune]

The log mentions CPU, which might be the issue here:

2024-01-26 18:47:33.367 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : CPU: Scene processed in 0.106s
2024-01-26 18:47:33.375 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : CPU: Allocated 47.461 MiB for frame buffer

It seems like it might be falling back to the CPU, as fyl3toys mentioned. Make sure they're all off by going to Render Setings > Advanced > Uncheck all of the CPU options > Restart Daz > Try again. This will tell you if you're running into a VRAM issue or not. If you are running out of VRAM, you'll likely get a black image instead of a render, which is often the dead giveaway of that.

 

[forbiddenfables1]

The log mentions CPU, which might be the issue here:



It seems like it might be falling back to the CPU, as fyl3toys mentioned. Make sure they're all off by going to Render Setings > Advanced > Uncheck all of the CPU options > Restart Daz > Try again. This will tell you if you're running into a VRAM issue or not. If you are running out of VRAM, you'll likely get a black image instead of a render, which is often the dead giveaway of that.

Tried it, i tried it with a simple G8 female model in the scene and nothing else, no light no props only a G8, the render starts, goes on for some iterations and suddenly stops before completing, like i said the renders start with GPU and falls back to CPU no matter how much vram there's left, I've got 4GB and i think ONE G8 with no environment should fit, I've got no other applications running.....I've changed DAZ3d versions, driver versions no solution.

 

[jt400]

there is also a tick box (no tick required) to tell Daz not to fallback to CPU - my settings

 

[MissFortune]

Tried it, i tried it with a simple G8 female model in the scene and nothing else, no light no props only a G8, the render starts, goes on for some iterations and suddenly stops before completing, like i said the renders start with GPU and falls back to CPU no matter how much vram there's left, I've got 4GB and i think ONE G8 with no environment should fit, I've got no other applications running.....I've changed DAZ3d versions, driver versions no solution.

I've looked over the log again now that I have more time, it's almost certainly something to do with Daz attempting to fallback to the CPU. It could be a number of things, from the memory on the GPU failing to not have the proper boxes unchecked, to even something like your Windows version.

2024-01-26 18:47:33.256 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER :: 1.6 IRAY rend warn : CUDA device 0 (NVIDIA GeForce GTX 1650) is no longer available for rendering.
2024-01-26 18:47:33.256 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER :: 1.6 IRAY rend warn : All available GPUs failed.
2024-01-26 18:47:33.256 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER :: 1.6 IRAY rend warn : No devices activated. Enabling CPU fallback.
2024-01-26 18:47:33.256 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: CUDA device 0 (NVIDIA GeForce GTX 1650): misaligned address (while initializing memory buffer)
2024-01-26 18:47:33.256 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [ERROR] - IRAY:RENDER :: 1.6 IRAY rend error: All workers failed: aborting render

This basically says it's falling back to the CPU. Then a bit lower:

2024-01-26 18:47:33.367 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : CPU: Scene processed in 0.106s
2024-01-26 18:47:33.375 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : CPU: Allocated 47.461 MiB for frame buffer
2024-01-26 18:47:34.857 Iray [INFO] - IRAY:RENDER :: 1.6 IRAY rend info : Allocating 1-layer frame buffer
2024-01-26 18:47:34.919 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00104 iterations after 26.843 s.
2024-01-26 18:47:36.320 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00105 iterations after 28.244 s.
2024-01-26 18:47:39.149 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00107 iterations after 31.072 s.
2024-01-26 18:47:43.387 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00110 iterations after 35.311 s.
2024-01-26 18:47:47.723 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00113 iterations after 39.647 s.
2024-01-26 18:47:51.955 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00116 iterations after 43.879 s.
2024-01-26 18:47:56.372 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00119 iterations after 48.296 s.
2024-01-26 18:48:00.644 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00122 iterations after 52.567 s.
2024-01-26 18:48:04.941 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00125 iterations after 56.865 s.
2024-01-26 18:48:09.505 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00128 iterations after 61.429 s.
2024-01-26 18:48:15.397 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00132 iterations after 67.321 s.
2024-01-26 18:48:21.149 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: 79.01% of image converged
2024-01-26 18:48:21.185 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00136 iterations after 73.108 s.
2024-01-26 18:48:28.333 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00141 iterations after 80.256 s.
2024-01-26 18:48:28.370 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2024-01-26 18:48:28.371 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(376): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : Expecting restart after abort. Frequent abort and resume in batch mode can severely reduce performance.
2024-01-26 18:48:29.869 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00142 iterations after 81.787 s.
2024-01-26 18:48:32.718 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00144 iterations after 84.637 s.
2024-01-26 18:48:38.411 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00148 iterations after 90.329 s.
2024-01-26 18:48:38.494 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Transaction closed, stopping renderer.
2024-01-26 18:48:38.502 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Device statistics:
2024-01-26 18:48:38.502 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: 45 iterations, 0.120s init, 65.111s render

I'd venture to guess that it's falling back to the CPU and then you're running out of actual RAM (not VRAM), which is causing the render to stop.

If you followed what jt400 posted above in the image as you said, and restarted your system (not just Daz alone.), try rendering again and post the log that results from that. It might help narrow down things. If you're on Windows 10 or 11, make sure "hardware accelerated gpu scheduling" is turned off as it's been known to cause stuff like crashes fairly often.

 

[forbiddenfables1]

there is also a tick box (no tick required) to tell Daz not to fallback to CPU - my settings

View attachment 3303772

Tried this too before coming here, it starts the render and after 5 iterations it just stops poooof!, and yep i tried the render with only just a G8F

 

[forbiddenfables1]

I've looked over the log again now that I have more time, it's almost certainly something to do with Daz attempting to fallback to the CPU. It could be a number of things, from the memory on the GPU failing to not have the proper boxes unchecked, to even something like your Windows version.



This basically says it's falling back to the CPU. Then a bit lower:



I'd venture to guess that it's falling back to the CPU and then you're running out of actual RAM (not VRAM), which is causing the render to stop.

If you followed what jt400 posted above in the image as you said, and restarted your system (not just Daz alone.), try rendering again and post the log that results from that. It might help narrow down things. If you're on Windows 10 or 11, make sure "hardware accelerated gpu scheduling" is turned off as it's been known to cause stuff like crashes fairly often.

Ok did everything you said....still same issue, posting the log file now....

 

[MissFortune]

Ok did everything you said....still same issue, posting the log file now....

Are you just using the base model? Just for the sake of it, select the figure > Parameters > Check the Render SubD. If it's anything above 3 turn it down. I'm not sure what version of Daz you're on, nor which driver, but with 4.22 there's an issue with OutofTouch hair assets that are causing Iray to crash, which could lead to a result that might look like this.

 

[jt400]

What is this in your log file? - OPTX:RENDER - Error synching on OptixPipeline event

Are you using a differnt rendering programe or plugin. Are you using Raytrace and can it be turned off.

 

[MissFortune]

What is this in your log file? - OPTX:RENDER - Error synching on OptixPipeline event

Are you using a differnt rendering programe or plugin. Are you using Raytrace and can it be turned off.

It's part of the Iray engine, I'm guessing, as it shows up with other Iray-compatible softwares like Vray, Octane, etc. I know there was an Octane plugin/addon for Daz a few years ago, but given that OP sounds a bit newer to Daz, I'd imagine he isn't using that.

It's starting to sound like it's less Daz's fault (for once) and more of a hardware issue. Possibly a driver issue. A clean install via NVCleanInstall, a memtest for the GPU might bring something up to. The memory itself could be the problem.