EDIT: Immediately after posting the below I ran a copy of Studio 4.5 which is installed on a work computer. And guess what? Yes, it’s the same (and Blender). This is an HP workstation, and completely different to my own, but it does have a Quadro. I noticed it was updated last week, so it’s looking like my vendor is right and it’s the drivers. I’ll be trying some options shortly and will post the results, as it looks like others will be having this issue, unless it’s caused by my own personal aura!
UPDATE: Yep, I rolled back the driver and it’s fine. So if you are suddenly having this issue roll back the driver and wait until a new driver comes out in the hope that will they have fixed the issue. As I said my Quadro 600 has a new release today and I’ll try this on Friday and see if they fixed the issue of the previous driver (Nov 2nd) which was giving me grief.
(Now I have to apologize to my vendor for my scepticism!)
Edit: Release 304 (307.45) on the NVIDIA site today fixed the problem. Simon, there is and update 307.45 for the FX 1700, so I would try that for your card.
Thanks for the new comments. The vendor is suggesting it’s the drivers. I’m sceptical (as I said to them, unless there was something very wrong with the previous update), but a new driver for my card was released by Nvidia today (my card is a Quadro 600, not a 400—I don’t know what I was thinking) so I will try that on Friday. I’ve found the card from work; it’s a Quadro FX 380. Should be adequate for temporary use, assuming swapping out the card solves the issue. I’ll be stumped if it doesn’t.
By the way, the errors are just as bad in Blender, if not worse, so I’m discounting DAZ Studio being behind this problem.