Application blocked from accesing graphics hardware

[thomasderijk]

Hi!

I've been getting this error message for a while now, but starting today its also doing it when in the C4D render que.
Doesnt matter which shots im rendering,

"Application c4d.exe has been blocked from acessing graphics hardware"
The shot in the render que shows and error, and it goes to the next shot.
This one renders a few seconds and then also shows an error

sometimes c4d freeze at this point but most of the times i can keep animating
requires a complete computer restart to use octane again

Tried everything:
different GPU
new (development release) plugin version
completely reinstalled both octane and drivers (bu wiping them completely in safe mode and then reinstalling
reinstalled c4d
turned off motion blur
clay rendering mode
turned of all anti virus and firewall software

only when i dont render in pathtracing or pmc it seems to be more stable

i have two gpu's,
using one or the other doesnt make much difference, although using the 980 i in the pci 1 slot seems to be most stable
the other one is a regular 980

I also switched them around, and using one or the other as display gpu also doesnt make different

they are never going above 65 degrees in temperature.

Also: nvidia forums just kept telling me to reinstall drivers but ive done that about 4 times now
phoning with my pc seller support but they also have no clue

so was wondering if anyone ever had this problem?
thanks

[thomasderijk]

did some test and anything under 40 - 50 frames with motion blur at 2 samples seems to render fine
anything above that stopts after a few minutes and makes me have to restart everything

Msi afterburner is showing nothing out of the usual, both cards are using around 1gb v ram and are around 3000 mhz memory clock
1300 core clock. 60 percent power, and around 70 degrees celcius

also: this just started happening yesterday all of a sudden,
no driver or windows updates happened in between so that cant be it...

Once the process has been blocked, octane will try to go the next render in the que. It will go trough the startup phase but once it tries to render an actual frame it gets an error and goes to the next one

[aoktar]

can you check task manager do you have unclosed copies of C4D when it happened?

[thomasderijk]

thank you for your reply

No there are no extra ones open, this does happen sometimes after that crash but i have to close the hidden one before i can start c4d again.

I did notice just now:
My RAM was nearing its 8gb limit when it happened, but im not sure why it would be using so much ram.
The only thing i can think of it out of core textures (not sure what that does)
but i am only using one image texture in the project, the rest is only default basic materials.

The texture i am using is 10 mb..

I am no disabling the out of core textures and seeing if it makes a difference

[thomasderijk]

this time the error happened even faster,

the RAM used was less, but the PAGE FILE was at max all the time, but only after 8 minutes the error came on.

I am also in contact with my computer helpdesk to see if maybe i have a broken gpu, but so far no luck with them

[aoktar]

I don't that's directly about plugin and renderer. Because I've seen that error first time. Can you pos some images about errors when this happen? Would be nice who's logging. Also post ram vram amounts and console and octane log outputs.

[thomasderijk]

yes it feels like it is windows related, but it only happens when using octane, when i am using c4d normally even with heavy stuff it does not happen which is weird

here is the octane log for this try, it happened immediately
And also added is the afterburner log for a second try, this has been rendering for 6 minutes now.
Nothing unusual as far as i can tell.

The actual error message goes away super fast, but yes it seems it is not octane related because the forum here does not mention it once.
On the nvidia forums there are a lot of people who have it but nobody seems to have a final fix

[aoktar]

I don't have much idea here. There is kernel crash but i don't think that's causing this or direct reason is that. Have you tried different drivers? maybe old one also when this started? After some installations or changes on system. Worth to check.

[thomasderijk]

yes checking now, rolling back to the oldest drivers i can find that will still work ; )

thanks

[zoppo]

Maybe it is a defective Vram?

https://www.raymond.cc/blog/having-prob ... ts-memory/