Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
I run 364.51 and haven't had any issues, and I use Iray as my primary viewport mode most of the time (I change Render Settings > Progressive > Update Interval to 0 and it's pretty close to real time for me).
Some other settings for the curious:
Windows 7 x64
I7-2600K 3.4Ghz (auto-clocks up to around 4.4Ghz as load demands)
16GB DDR3 Corsair Vengeance
EVGA 770 4GB FTW Edition (single card - dual monitor setup (dvi))
Corsair AX1200 Power Supply
Daz 4.9.1.30
Interface/Iray options are attached (I never use interactive mode).
I have an AMD R9 290 for my main monitor and a Titan X dedicated for renders (no monitor). The new nVidia drivers will still make the UI sluggish if you select interactive mode for previews. And the new nVidia drivers will still crash.
Hmm this looks very helpful, thanks KurzonDax. I might give this a try as well.
Just a note of caution - I read somewhere that Windows produces this driver error in order to pre-empt and avoid occurrences of the "blue screen of death". Some people on a techie forum were saying that if you increase the tolerance here it can translate into fewer driver crashes but more bsod's. So it might be a bit of a catch 22 situation.
As it turns out, the registry setting mentioned in that KB article already exists in Win10, and is already set to the prescribed value of 8, so no help there for me. I finally got so frustrated with it a couple of days ago, I took my machine back down to essentially bare metal. I wiped the C drive completely (all of my content and project files are on a separate drive set) and reinstalled Windows 8.1 with Nvidia 359.81 drivers.
At first, I immediately began getting random driver crashes. It didn't matter what program I was using at the time. So I pulled my second video card out. Still got crashes. By then, I was ready to throw the computer through the window and straight out into the street. From there I planned to run over it numerous times with my truck until some level of sanity returned.
Fortunately, I regained composure, and swapped out the first card with the second. Driver crash. At this point, I began wondering if my power supply might be going bad. It's a 1300 watt supply, so I knew it had enough juice to power everything, but maybe the 12v rail was flaking out. This seemed a bit spurious to me though, because nothing else in the system was exhibiting strange behavior.
Then I had an epiphany of sorts. Well, maybe not that dramatic. I unplugged the monitor cable from the bottom display port and plugged it in to the top one (the 980 Ti has three display ports). I figured there was not much left that I hadn't tried. Upon booting the system back up, sweet, sweet stability had returned to the system. I went in to the Nvidia control panel and changed two settings that I had seen mentioned several times during my research. Both are under the 3D settings. First, I changed Power Management Mode to "Prefer maximum performance". Second I changed Thread Optimization to "On" (it defaults to "auto").
I had little hope the system would remain stable, though, so I fired up Studio and loaded the most render intensive scene I have that fits in the video card RAM and started the render. Three hours later, no crashes. The GPU had been plugging along nicely at ~98% utilization the whole time.
I reinstalled the second card. The drivers picked up the added card just fine, so I launched Studio again, and re-ran the render. No issues. Over the next day or so, I rendered multiple scenes with no more driver crashes, so last night, I took the plunge and upgraded back to Win10. Things are still stable. I did, however, turn off the option for Windows to automatically install drivers from Windows Update.
I realize most Nvidia cards only have one Display Port connection, or none at all. I honestly have no idea why switching ports had any impact, or why it had worked flawlessly for some time before the crashes started. However, if you haven't changed the two settings I mentioned above in the Nvidia control panel, it's probably worth a shot. From what I read, leaving the power setting on adaptive can result in weird behavior due to fluctuating voltages. It also seems that the thread optimization being set to auto can cause the card to (in laymen's terms) get confused, resulting in the drivers crashes as an attempt to reset the card back to a stable state.
Just an update for everyone. I've had an answer to my ticket to technical support and they have confirmed that there is an incompatibility between Iray and the latest Nvidia drivers that use VR compatibility. They're working on it, but in the meantime suggested that I roll back to the 353.82 version drivers as these are confirmed to work correctly.
Also see this...
http://www.daz3d.com/forums/discussion/comment/1067046/#Comment_1067046
Bumping this thread to see if there is any new information as I just started getting this today....