[solved] NVIDIA rendering issue

Cherubit

Since yesterday I've been having this problem when I try to render an image with Iray. The whole machine freezes, and the only solution is to force reset.

When I try to open the Nvidia Control panel, I get the following message:

But still, when I'm on DS, and I have the viewport set to Nvidia Iray, it works!

Apparently there's some compatibility issue.

Has anyone had this in the past?

Does anyone know the solution?

Drivers are up to date. Already tried restarting, uninstalling and reinstalling, in different orders, nothing worked.

It is important for me to be able to Render images the proper way so that I can have them in full size.

Silent Winter

The viewport works but not render to window?  Have you tried rendering to file?  (Can't see the progress but at least we'd know if it was working).

If Nvidia panel says you're not connected, it sounds like a problem at the card end rather than Daz.  Have you tried taking out the graphics card and putting it back in?   Sometimes things come loose, even if you don't move the machine (it's usually the RAM for me but it could be the GC too).

Cherubit

 

Silent Winter said:

The viewport works but not render to window?  Have you tried rendering to file?  (Can't see the progress but at least we'd know if it was working).

If Nvidia panel says you're not connected, it sounds like a problem at the card end rather than Daz.  Have you tried taking out the graphics card and putting it back in?   Sometimes things come loose, even if you don't move the machine (it's usually the RAM for me but it could be the GC too).

What`s rendering to file? I've never heard of it before :O

I hope it's not the card, it's new. i'll buy a HDMI cable tomorrow. My monitor is connected to the motherboard rather than the GPU. But since it has worked since april like that, i'm trying to find a solution still today...

How can I take out the card? I need to open my computer right? I don't have the correct tools for that yet :/ maybe i can also buy them tomorrow.

Do you get the same message when it's related to RAM?

Silent Winter

You don't usually need tools to take out the card - the side panel of the desktop will come off by unscrewing the screws at the back (which often have handles so you don't even need a screwdriver).  Then it's just a case of unclipping the card, taking it out, putting it back in gently but firmly (it'll lock into place).  Edit: Though actually there may be a need for a screwdriver to screw in the card at the back.

If you've never done it before, you might want to look up a video on youtube to see how it's done.

When I've had RAM issues I've usually just had the blue screen of death (BSOD) - just needed to remove and reseat it.

Render to file is an option in the general render settings.  Where it says 'Render target'  change 'new window' to 'direct to file' - might not work but worth a try.  This can also be faster sometimes as the system doesn't need to update the render window at the same time. (But you also can't see how well the render is doing)

JamesJAB

Depending on if your computer is a store brand or a custom build... Could be your power supply wearing out. (Store brand computers are notorious for having very wimpy power supplies)

Cherubit

Silent Winter said:

You don't usually need tools to take out the card - the side panel of the desktop will come off by unscrewing the screws at the back (which often have handles so you don't even need a screwdriver).  Then it's just a case of unclipping the card, taking it out, putting it back in gently but firmly (it'll lock into place).  Edit: Though actually there may be a need for a screwdriver to screw in the card at the back.

If you've never done it before, you might want to look up a video on youtube to see how it's done.

When I've had RAM issues I've usually just had the blue screen of death (BSOD) - just needed to remove and reseat it.

Render to file is an option in the general render settings.  Where it says 'Render target'  change 'new window' to 'direct to file' - might not work but worth a try.  This can also be faster sometimes as the system doesn't need to update the render window at the same time. (But you also can't see how well the render is doing)

It seems like Render to Target works!!! It hasn't frozen nor anything, so we will see :D :D :D :D 

(waiting...)

Ok it works!!!!!

Do you know why it works but in new indow doesn't? :/ knowing the reason is the first step to fixing the problem :P

Thank you so much! Part of my problem is fixed :) At least now I get to work on my promos again. I will have to admit that I love watching it render though...

Do you think it could be bad contact? Do I still need to open my compy?

I have RAM problem sometimes too, when I have huge scenes i get black screen, sometimes before I get a message telling me to close other programs due to lack of memory... I only have 8GB, my GPU has 6GB, but I can't use those nice environments sold here, too heavy for my machine.

Cherubit

And now it's working again when i change target back to window. That is a crazy issue! I wonder if it was all the uninstall+reinstall of drivers...

Thank you again! :D

Cherubit

JamesJAB said:

Depending on if your computer is a store brand or a custom build... Could be your power supply wearing out. (Store brand computers are notorious for having very wimpy power supplies)

How can I find out if it's the power supply?

I have a GTX 1060 6gb, and my power supply is ATX 600W VS600 Corsair.

Cherubit

taemimun said:

 

Silent Winter said:

The viewport works but not render to window?  Have you tried rendering to file?  (Can't see the progress but at least we'd know if it was working).

If Nvidia panel says you're not connected, it sounds like a problem at the card end rather than Daz.  Have you tried taking out the graphics card and putting it back in?   Sometimes things come loose, even if you don't move the machine (it's usually the RAM for me but it could be the GC too).

What`s rendering to file? I've never heard of it before :O

I hope it's not the card, it's new. i'll buy a HDMI cable tomorrow. My monitor is connected to the motherboard rather than the GPU. But since it has worked since april like that, i'm trying to find a solution still today...

How can I take out the card? I need to open my computer right? I don't have the correct tools for that yet :/ maybe i can also buy them tomorrow.

Do you get the same message when it's related to RAM?

I said too fast, I think it's rendering only with CPU :(

JamesJAB

taemimun said:

JamesJAB said:

Depending on if your computer is a store brand or a custom build... Could be your power supply wearing out. (Store brand computers are notorious for having very wimpy power supplies)

How can I find out if it's the power supply?

I have a GTX 1060 6gb, and my power supply is ATX 600W VS600 Corsair.

I wouldn't worry about your power supply then. It's plenty strong and from a good brand. Looks like priority number one should be to at least double your system RAM to 16GB.

Silent Winter

taemimun said:

taemimun said:

 

Silent Winter said:

The viewport works but not render to window?  Have you tried rendering to file?  (Can't see the progress but at least we'd know if it was working).

If Nvidia panel says you're not connected, it sounds like a problem at the card end rather than Daz.  Have you tried taking out the graphics card and putting it back in?   Sometimes things come loose, even if you don't move the machine (it's usually the RAM for me but it could be the GC too).

What`s rendering to file? I've never heard of it before :O

I hope it's not the card, it's new. i'll buy a HDMI cable tomorrow. My monitor is connected to the motherboard rather than the GPU. But since it has worked since april like that, i'm trying to find a solution still today...

How can I take out the card? I need to open my computer right? I don't have the correct tools for that yet :/ maybe i can also buy them tomorrow.

Do you get the same message when it's related to RAM?

I said too fast, I think it's rendering only with CPU :(

Try a very simple scene (to make sure you're not going over the GPU limit (though I've only got 3Gb and rarely go over on even 3 figures + background).

If it's not working on a basic cube with one light, I'd open up the comp (or get someone who knows what they're doing to help) and try to reseat that GPU and RAM.

 

On a side note, since you mentioned it:  One trick with those big environments is to remove parts you don't need (out of camera, hidden behind other things, lights that aren't really affecting the scene).  Then reduce the resolution of the maps with this script:

https://www.daz3d.com/forums/discussion/137161/reduce-texture-sizes-easily-with-this-script/p1

(read through the thread for tips on using it).

 

Padone

@Taemimun

You said you have your monitor wired to the mobo AND your viewport set to iray. In my opinion this is generally not a good thing to do.

If you wire the monitor to the mobo then windows will use the integrated card for the viewport. This has the advantage that the GPU is free for rendering. But as far as I know this way you shouldn't be able to use the GPU for the viewport. So in this case you should use the OpenGL viewport.

If you want both the viewport and the rendering to be iray then you should wire the monitor to the GPU.

 

Cherubit

JamesJAB said:

taemimun said:

JamesJAB said:

 

 

I wouldn't worry about your power supply then. It's plenty strong and from a good brand. Looks like priority number one should be to at least double your system RAM to 16GB.

 

Silent Winter said:

Try a very simple scene (to make sure you're not going over the GPU limit (though I've only got 3Gb and rarely go over on even 3 figures + background).

If it's not working on a basic cube with one light, I'd open up the comp (or get someone who knows what they're doing to help) and try to reseat that GPU and RAM.

 

On a side note, since you mentioned it:  One trick with those big environments is to remove parts you don't need (out of camera, hidden behind other things, lights that aren't really affecting the scene).  Then reduce the resolution of the maps with this script:

https://www.daz3d.com/forums/discussion/137161/reduce-texture-sizes-easily-with-this-script/p1

(read through the thread for tips on using it).

 

Padone said:

@Taemimun

You said you have your monitor wired to the mobo AND your viewport set to iray. In my opinion this is generally not a good thing to do.

If you wire the monitor to the mobo then windows will use the integrated card for the viewport. This has the advantage that the GPU is free for rendering. But as far as I know this way you shouldn't be able to use the GPU for the viewport. So in this case you should use the OpenGL viewport.

If you want both the viewport and the rendering to be iray then you should wire the monitor to the GPU.

 

Bought a HDMI-HDMI cable to connect monitor to GPU. Now when I try to open the NVIDIA control panel it opens and doesn`t give me the Display message in the first post.

Viewport renders perfectly and FAST. Like it should.

Normal render: Daz set to only render with GTX 1060 6GB. Renders relatively* well when i first start Daz. After the 3rd render or so, when trying to render, memory usage in task manager goes super high and the computer freezes completely. It`s Daz using all the RAM (8 GB). I didn`t have this before, it used to work perfectly with the RGB cable connected to the Mother Board. And it was so fast! And Daz didn`t consume my RAM like that.

*relatively because it still freezes for around 3 minutes before deciding it actually wants to render this time.

So much headache, this is a new computer :( I've even tried old drivers. I'm almost sure that's not the problem.

I don't know what else to do. 

Padone

Well, you did resolve the rendering issues by wiring the monitor to the GPU. Memory issues are another story and are quite common. Below something that may help.

https://www.daz3d.com/scene-optimizer

I don't get what you mean for "it used to work perfectly with the rgb cable connected to the mobo". What I understood is that you can't render with it. If you have a configuration that works fine then just go back to it. What's the problem then ?

 

EDIT: Basically you should have two options now. And in any case the scene optimizer may help.

1) Wire the monitor to the GPU. This way you can use iray both for the viewport and rendering. But of course it takes more memory since the vram is shared among the windows desktop plus the daz viewport plus the iray rendering.

2) Wire the monitor to the MOBO. This way you can't use iray for the viewport and you need to use OpenGL instead. But the GPU is free for iray rendering only so you have more free vram.

mjc1016

taemimun said:

 

*relatively because it still freezes for around 3 minutes before deciding it actually wants to render this time.

That's normal...there are a lot of behind the scenes things going on BEFORE the first pixel shows up in the render window.  It is NOT 'frozen'.

Also, you will run out of memory on the video card if you do several renders without closing/saving the completed ones.

Silent Winter

There's a memory purge script around somewhere (should be under Scripts->Utilities in the content pane) - which clears RAM (but not VRAM apparently).  You can use that between renders.

Changing the viewport to wireframe before rendering will free up some memory on the GPU, also using that texture reduction script will help loads (anything not right in the camera's face won't need its full-size textures anyway so you won't be reducing quality).

 

Edit: And to quote RH from another thread:

Are you closing the render windows or leaving them open? Each open window will continue to hold GPU memory so that it can resume the render.

Cherubit

Thank you everyone!

Problem was solved!

I talked to a microsoft technician and he uninstalled my last update. At the same time I found out that my mesh resolution was very high. Now i'm not that sure which of he two cases was causing the problem, but it's fixed! *phew* I can finally work on my products again :))

(There's a way to uninstall updates in Update History > Uninstall Updates) then the technician used a software called wushowhide.diagcab to hide the update :)