Display Driver Nvidia Windows kernal mode driver stopped working...
tl155180
Posts: 994
Has anyone seen this error before? "Display Driver Nvidia Windows kernal mode driver version 364.51 stopped working and has successfully recovered."
I just started getting it recently and its now happening every time I render with Iray. I tried looking up solutions on Google but they all talk about the gpu overheating and mine isn't. This only happens with Daz Studio Iray - nothing else (games etc). I tried updating to the latest graphics drivers but it hasn't helped at all.
Any ideas please?
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 should probably point out that I'm using DS 4.8
According to GPU-Z my gpu sits at about 64 degrees with fan speed 45% while Iray is working. Power consumption sits between 50-60%, so god knows that the problem is all of a sudden.
Roll back to a before 364 driver...it looks like it still may be having problems.
Sadly I was on a pre- 364 driver before and it was still happening then as well. I think I was on something like 361.75 before.
This is very frustrating. I can't complete a single render anymore.
I was getting this, along with Power_State_Driver_Failure. I finally went to my laptop support (since I was still under warranty) and watched what they did...
1. Flashed the bios with a new driver. I had done this before, not sure if this step was necessary.
2. Rebooted.
3. Uninstalled all of my NVIDIA drivers from Add / Remove Programs.
4. Rebooted.
5. Downloaded the latest NVIDIA driver package.
6. Did a custom install of the package and made sure that "Clean Install" was selected.
7. Rebooted.
You can probably skip 1 & 2 if you aren't running a Dell or Alienware. They seem to have issues with an old BIOS handling power properly.
361.91 woked for me,,,
I have same problem,, then roll back . 364 could not remove the problem. do not know about 362 etc,,though.
mm,, but your case is only happen for render? my case was only happen with new ds 4.9 version, and
some driver recently offered.
uu,,, I changed driver from AMD to Nvidia, for iray puropose , (and hope,, it should be more stable,,)
but after all,, these problem seems happen with new version combination,,(aprication and driver) for ever,,
My errors only happened while using DS too. So I would bet dollars to donuts its the NVIDIA driver.
Thanks guys. Yeah I strongly suspect its something to do with Nvidia and drivers, but I've tried 3 different drivers now and still having the same problem. It only started like 3-4 days ago. Before that it was all fine. The weird thing is that I haven't changed anything on my PC in the mean time.
Trying out drivers version 362 now.
I've had this happen twice on my newer pc (about a year old). The last time I was doing a render in Daz Stuido 4.8 (I think). It didn't cause any problem though. My render finished OK. Not what I was doing the other time.
This used to happen from time to time on my old pc. But I think I had an ATI card in that one. It never caused any problem when it happend. I think it used to happen on the old pc while I was on the internet occassionally. It did cause the screen to re-draw, I think. The screen would freeze for a moment as I remember. Maybe that would have caused an issue with the render. Not sure.
If it is with Iray be careful, I had an issue with my old 1.2gig 570GTX (yes it was an old card and probably the main reason but still) I had been rendering a few pictures in Iray until one day while rendering my video card died.. And since Iray was rendering at the time I knew that was the cause of it.. The thing is that the card never over heated either during rendering but it is still getting stressed and it could one day decide to let go..
Eitherway I am dearth to use Iray again, and the video card that I do have now I don't want to go belly up at the moment as I can't afford a new video card right now..
Well the version 362 drivers seem to be holding stable so far. I've managed to get through a 1.5 hour render, so thats encouraging. Will probably have to test it more to be sure its improved though.
That is good I am using the 362.00 ones as well after the other ones I had threw up a nasty crash while playing a game.. If you look on the Nvidia forums after a new driver release there are quite a few unhappy folk wishing that there would be at least one good and stable driver release..
Unfortunately the drivers have not fixed the issue. I'm still getting CTD every time I try a long render in Iray with the message about nvidia drivers. I've tried everything I can think of - a disk cleanup, defrag, virus checks, monitoring gpu temp - but nothing is helping. Its only happening with DS Iray. All games etc are running fine.
Before I give up and attempt a fresh re-install of Daz Studio, does any kind techie out there have any ideas please?
Also, does anyone know if its still possible to do a fresh install of 4.8?
Interesting timing on this. I've been battling the same problem for about a week. The only way I've managed to stabilize it so far is this:
It's been stable for a couple of days now. However, I can say one thing for sure. It's pretty definite that it's not an issue being cause by Daz Studio. I had the driver crashes occur even when Studio wasn't running.
Based on a bunch of googling I did trying to figure this out, the driver crash occurs when the video card gets in to some sort of unstable state. The card essentially resets itself to get back to normal operation. This can be caused by several different things, but The most common is the card getting too hot. Obviously when you're doing a render, the card is working pretty hard and will be at a higher temperature than normal. My working theory is that something with the latest drivers is causing the cards to reset at a lower temperature than they should be.
There is another thread here about Daz Studio crashing with certain NVIDIA drivers during Iray preview. I don't know if it is related, but you might want to take a look at that thread, too. Please submit a help request to get Daz to take a look at these problems.
Thats interesting. Thanks KurzonDax, I have tried several different nvidia drivers and the one I settled on was 362.00 using the install method recommended by nvidia (I still get crashes with that) but I might try your fresh install guide and see if it helps. The funny thing is that sometimes it will let a render go for a little while before crashing, whilst other times it will choose to crash almost immediately. Given that Iray is an nvidia product it would be pretty poor of them if their drivers were causing the issue... so I'm not so sure. I was using one set of drivers fine for the last few months without any crashes and then the crashes suddenly started occurring even though I hadn't updated the drivers at all.
Thanks barbult. I might submit a ticket as well then...
The sad thing is that these crashes are putting me off buying anything more until I know if DS is gonna work again. So I'm missing out on all these great deals
I am having the same problem in Poser 11 for about 3 weeks now, so I'd say it is definitely nVidia related.
Logically I would agree, but I don't understand why I had the same nvidia drivers since November last year and they were working fine with Iray, no crashes at all, right up until about the start of March and then everything suddenly went south on the same drivers. I hope it is the drivers, but I've tried all of the latest versions and every single one causes these crashes for me. Even 362.00 is flaky for me.
Have we all got 970 GTX's? Maybe its a 970 issue?
I'm on 358.91; not seeing any pressing need to update, most since have been game-ready.
I'll probably check out the next complete release, but am unlikely to change it on my disk image backup until I've tested it thuroughly.
If you can't resolve it, and sometimes even using safe mode to uninstall doesn't clear away all the crap, try Display Driver Uninstaller. It will completely remove everything; it will reboot to complete uninstalls so save stuff first.
http://www.majorgeeks.com/files/details/display_driver_uninstaller.html
Note, the link is for information; I'm not specifically recommending the site for downloads.
For what it's worth, I was having the problem sporadically with a 970, then with a 980 Ti and the 970 both installed, until I did the clean driver install I described above.
I took out the 970 just for grins, and have been running with just the 980 Ti for a few days without issue. This morning, I installed a second 980 Ti that I had been holding off putting in and so far, no crashes on the 362 drivers.
Having said all of that..... I built a PC for my son a couple of weeks ago and put a 960 in his. He plays several different games on it, all of which are graphics intensive, but hasn't had any problems with the 960. I say that not to imply this is a Studio/Iray issue, but more to say that it sort of sounds like a driver issue with the 970. I'm going to install the 970 in his computer this weekend and see what happens. Not sure what OS everyone is running, but I'm on Win10, so it's certainly possible the issue is with Windows and not the drivers at all.
On a seemingly unrelated note, now I'm trying to figure out why Studio is jacking my CPU to 100% while rendering to the 980 Ti. I've eliminated all the usual suspects (scene too big, etc.). Going to post something in the Nuts and Bolts forum in a few.
Hmmm, it is starting to sound like it might be an issue with the 970 in Iray. Thats annoying because I didn't buy my card very long ago. I'm on Windows 7 still, by the way.
Well.... uhg. Just had the driver crash with the dual 980's during a render. What's weird this time, though, is the render continued running.
And now for a double uhg. The drivers have since crashed three times, no make that four times while trying to write this post.
What is the exaqct error when the crash happens?
It was in the op - "Display Driver Nvidia Windows kernal mode driver version 364.51 stopped working and has successfully recovered."
I'm getting it all the time these days, no matter which drivers I use
Argh, thats a pain! What version of DS are you using by the way? 4.8 or 4.9?
This is an issue that has been plaguing many releases...not just the latest. It is also something that is affecting cards from just about every manufacturer. It is also not consistent...some things can run without causing it; others just thinking about starting them up causes it. It is NOT Iray or Studio specific.
Some relief has been reported by making sure your motherboard has the latest BIOS upgrade AND OS version driversl--some has been reported after manually editing the registry to increase the TDR timeout (mostly on Win7...but a few on Win10).
It seems to have gotten worse/more widespread since February's round of Windows updates (but then again, there's been driver updates in that time frame, too).
I managed to roll back to 358.91 this afternoon. This did solve one problem, my CPU doesn't spike to 100% while rendering now. Unfortunately, I got the display driver crash again, this time killing a render in progress. So I did some more googling tonight and ran across this article from Microsoft support. It requires adding a registry value that gives the graphics drivers more time to respond to the operating system. I might give it a shot in the morning to see what sort of impact it has. The good news is this apparently is applicable to Windows Vista and up. I'm not convinced this will help, but it might for situations where the GPU is under a heavy load.
https://support.microsoft.com/en-us/kb/2665946
Are those of you experiencing this running with your monitor(s) attached to the video card you're using for Iray renders? From the KB article it sounds like Windows is getting upset about the time delay in doing a windows screen update.
Back when I was jsut starting with Iray I only had one video card - a GT 740 - and if I used it for Iray renders the video response became soooo slow I couldn't even get windows solitaire to play well. And I did get this crash a couple of times. Now I have a video card just for Iray and the 740 is dedicated to the monitors only - and I've had no problem since.
So the permanent fix, I'm afraid to say, may be to spend a few dollars and get a low-end video card that supports OpenGL 4.2 (or whatever Studio requires now) dedicated to the monitor(s).
I'm on DAZ Studio 4.9.1.30 and when I add the new Apartment or the Conservatory to my scene at try to iRay render (after converting non-PBR maaterial with DAZ Uber iRay Base) I get a fast DAZ Studio crash near the time I'm expecting the 1st write to the canvas. If I use a plain MPCyclorama or the Drawbridge (part of one of the castle sets) it works OK. I have a Intel HD Graphics 3000 video HW though.