Page 1 of 1
failed to free page-locked memory
Posted: Sat Nov 30, 2019 11:32 pm
by samsue
Hi
I'm having trouble with my slave render.
Any suggestions? I couldn't find anything about it.
Re: failed to free page-locked memory
Posted: Mon Dec 02, 2019 6:44 am
by samsue
- Could it be a problem Hardware? If so, how could it test?
- When they installed one of the video cards, they didn't see that the cooler
was not running freely, because the video cards are too close to each other.
This caused the video card to self-shut down.
Could this have damaged the video card? How can I test it?
- How to see if the video card is rendering?
**This only happens in scenes that reach out-of-core. Smaller scenes have no problem at all.
Re: failed to free page-locked memory
Posted: Mon Dec 02, 2019 6:21 pm
by coilbook
samsue wrote:- Could it be a problem Hardware? If so, how could it test?
- When they installed one of the video cards, they didn't see that the cooler
was not running freely, because the video cards are too close to each other.
This caused the video card to self-shut down.
Could this have damaged the video card? How can I test it?
- How to see if the video card is rendering?
**This only happens in scenes that reach out-of-core. Smaller scenes have no problem at all.
you can install msi afterburner to see when card is rendering
I think the card is ok.
We had similar problem when we got memory error when we didn't have enough vram even though we enabled out-of-core. I think out-of-core only works with textures. Sometimes to much high poly mesh can cause this error like if you scatter itoo trees where each tree is 1 nil of polys.
I wonder if the error can also be cause where important large texture is split between vram and out-of-core or moved to ram and octane needs it cause the crash.
Re: failed to free page-locked memory
Posted: Thu Dec 05, 2019 2:57 pm
by samsue
is this behavior normal? The frequencies are quite different.
Re: failed to free page-locked memory
Posted: Thu Dec 05, 2019 3:40 pm
by paride4331
Hi samsue,
try to set "debug mode" in Nvidia control panel.
Regards
Paride
Re: failed to free page-locked memory
Posted: Fri Dec 06, 2019 12:15 pm
by samsue
paride4331 wrote:Hi samsue,
try to set "debug mode" in Nvidia control panel.
Regards
Paride
Nothing has changed, the number one board is still working at maximum speed and the others are not.
this problem that you have seen before? is it something octane related or could it be problem harware?
Re: failed to free page-locked memory
Posted: Sun Dec 08, 2019 7:08 pm
by samsue
samsue wrote:is this behavior normal? The frequencies are quite different.
According to what I could see, it seems that if the scene is not big enough, it ends up not using all the video cards.
Re: failed to free page-locked memory
Posted: Sun Dec 08, 2019 7:09 pm
by samsue
coilbook wrote:samsue wrote:- Could it be a problem Hardware? If so, how could it test?
- When they installed one of the video cards, they didn't see that the cooler
was not running freely, because the video cards are too close to each other.
This caused the video card to self-shut down.
Could this have damaged the video card? How can I test it?
- How to see if the video card is rendering?
**This only happens in scenes that reach out-of-core. Smaller scenes have no problem at all.
you can install msi afterburner to see when card is rendering
I think the card is ok.
We had similar problem when we got memory error when we didn't have enough vram even though we enabled out-of-core. I think out-of-core only works with textures. Sometimes to much high poly mesh can cause this error like if you scatter itoo trees where each tree is 1 nil of polys.
I wonder if the error can also be cause where important large texture is split between vram and out-of-core or moved to ram and octane needs it cause the crash.
Looks like you're right, I saw that too.