Is the new Nvidia Geforce Driver 378.49 causing my OC to crash?

[BNWilliams007]

I just now updated my Geforce Game Ready Driver to version 378.49 and when I was asked to restart my PC, my monitors were unable to detect an output. So then I had to manually turn off and turn on my PC and when it booted up, I was presented with this screen: http://i.imgur.com/I2X7GTl.jpg

After that I pressed F1 to get into my bios and load my default optimized settings my computer was able to boot into the desktop just fine. Has this new 378.49 Geforce Driver made my OC unstable? Has anyone else had this problem? My OC had my i7 6700k overclocked to 4.6Ghz and my ram overclocked to 3200Mhz.

Here are my PC specs if it helps: https://pcpartpicker.com/user/BNWilliams007/saved/Yg2CmG

Thank you for your time.

 

[Deniedstingray]

If the only change between no crashing and crashing was you downloading the new update, then it must have been.

 

[BNWilliams007]

This is the first time that an Nvidia driver has caused something like this. Does this occur often for Nvidia users? If so, how do people normally fix this problem, do they just wait for an update from Nvidia?

 

[Deniedstingray]

This is the first time that an Nvidia driver has caused something like this. Does this occur often for Nvidia users? If so, how do people normally fix this problem, do they just wait for an update from Nvidia?

I cannot say for sure. But it is a common troubleshooting method to just look at changes you made prior to issues and revert back to the settings that worked. I would rollback the driver and try again in a week or so.

 

[BNWilliams007]

Oh ok so you're suggesting to uninstall the new Nvidia Driver then reload my OC settings and then try updating to the new Nvidia driver within a week or so?

 

[Deniedstingray]

Roll it back to the previous one, if you know how to do that. Then try again in about a week, yes. If this is a problem im sure they will fix it.

 

[BNWilliams007]

Oh ok, I never heard of that term before, but I did a quick Google search and now have an idea of what to do. I'll do it tomorrow though since it's getting late, thank you for your help.

 

[Deniedstingray]

Oh ok, I never heard of that term before, but I did a quick Google search and now have an idea of what to do. I'll do it tomorrow though since it's getting late, thank you for your help.

No problem, Happy gaming!

 

[huckjam]

I had the same issue last night, I just got off work and sat down to play some games and noticed geforce experience crying about an update so I figured why not just get it over with and installed the update. It restarted and then I couldn't boot my pc, most times it was getting right to the login screen then I would get a blue screen saying "DPC_WATCHDOG_VIOLATION" over and over sometimes I would be able to log in and then try to start a game but soon as fullscreen kicked in I would get the blue screen. To fix I just booted into safe mode and uninstalled the new geforce driver then installed the old version and everything is working like normal since. I played games for about 4 hours since then with no issue so just give a rollback a try and you should be good.

 

[Luqqas]

I had the same issue last night, I just got off work and sat down to play some games and noticed geforce experience crying about an update so I figured why not just get it over with and installed the update. It restarted and then I couldn't boot my pc, most times it was getting right to the login screen then I would get a blue screen saying "DPC_WATCHDOG_VIOLATION" over and over sometimes I would be able to log in and then try to start a game but soon as fullscreen kicked in I would get the blue screen. To fix I just booted into safe mode and uninstalled the new geforce driver then installed the old version and everything is working like normal since. I played games for about 4 hours since then with no issue so just give a rollback a try and you should be good.

Same happened to me. Running Windows 10 up-to-date. Everything was working fine until I updated nvidia drivers to 378.49. After that, screen freezes after login to desktop and blue screen comes up with dpc_watchdog_violation error. This is the first time an nvidia driver crashed my pc.

 

[K_6___]

same here, after restart my pc freezes and sometime can't detect gpu.
roll back not working, i've to uninstall gpu and install driver ver.372.70 from asus website. and everything work fine now.
i'll stick with this version for now

 

[BNWilliams007]

So I uninstalled my Nvidia Drivers using DDU and then reinstalled Geforce Driver 376.33 yesterday and everything seemed to work fine. However today it seemed like my computer had a difficult time booting up as my screens weren't detecting anything and then my PC turned itself off, but then it quickly turned itself back on and booted into my desktop just fine so hopefully everything is alright now. Thank you everyone for your feedback.

 

[BNWilliams007]

Sorry for the double post but when I tried to boot up my computer again today, my screens again could not detect anything so I manually reset my computer and I got that bootup error message again. I then headed into my bios but didn't change any settings, exited, and then my computer was able to boot into my desktop with no problems with my OC profile. Does anyone by any chance have any idea as to why my computer is occasionally having trouble booting up? Thank you for your time.

 

[skataras]

I have exactly the same problem like you. random restarts after the error, chash with the error ( nvidia windows kernel mode driver version 378.49 stoped working) even after the format. before this update everything was ok. after that nothing ok. yes i did the ddu thing didnt work. any solution or wait for the next update from nvidia?

 

[BNWilliams007]

I had trouble booting up my computer again today. It was stuck at the motherboard manufacturer screen so I had to manually turn off and turn on my computer and then it booted into my desktop just fine. I'm glad to hear that I'm not the only person having issues with this though. I hope Nvidia announces something regarding these issues soon since I think this has something to do with the recent Gerforce Driver update.

 

[p3yn]

I had the gtx860m, and THIS driver (378.49) caused bsod in my Lenovo Y50-70 laptop, with Win10 Pro. I Uninstall it then rollback to earlier version and had not any issue after that.

Hope it helps!

Best regards

 

[Peter_208]

Same problem here. I also have GTX 860M video card (ASUS G551JM laptop). Rollback the previous driver solved the freezing.

If you also have this GPU, then you maybe remember that there was a problem about a year or 1,5 year ago with the officially nvidia driver. This problem only affected the GTX 860M cards. We had to wait almost a year for a working hotfix from nvidia.
Maybe we have a similar issue now, so the only thing we can do to rollback the driver to version 376.33.
And maybe open a thread on the officially nvidia forums and start whine again

 

[kunjila kobasa]

I had the gtx860m, and THIS driver (378.49) caused bsod in my Lenovo Y50-70 laptop, with Win10 Pro. I Uninstall it then rollback to earlier version and had not any issue after that.

Hope it helps!

Best regards

Same thing here mate!

Lenovo Y50-70 with Windows 10 64x and 860m. After newest graphics driver update I would get random or less random BSOD's with CLOCK WATCHDOG TIMEOUT error. This would happen on windows startup mostly, on welcome screen, sometimes even 2-3 times in a row before it could boot to desktop. Otherwise it would cause frequent stalling, specially on start-ups.

And I couldn't play GTA 5 at all, after launching it I would get the broken screen (don't know how to say it...but that with distorted color) and in best case, the music would start and I would get kicked out with message that it's not working and message from windows that Windows 10 blocked GTA5.exe access to graphics hardware.

After uninstalling drivers with DDU I was able to start GTA 5 with intel HD graphics, of course with horrible fps, but it worked!
Then I installed back the 378.49 drivers and same problems all over again...rolling back to 376.33 seems to solve the problem!

 

[Matthew Sandford]

Confirmed, Lenovo Y70-70 with 860M - after several bluescreens I couldn't boot into Windows anymore. Luckily had a Linux partition so just backed everything up and reinstalled, nice waste of a couple hours of my life tho -.-

 

[pranav8988]

I just created a topic on the nvidia forum : https://forums.geforce.com/default/topic/991203/geforce-drivers/gtx-860m-crashing-and-giving-bsod-on-378-49/

I also had a chat with the nvidia support , they are asking for a dmp file regarding the BSOD but i had resetted my windows and got back with 376.33 so i don't have that log anymore.

Kindly posts your grievances regarding the 860m on the forum link given above.

Thanks
A lenovo y50-70 user

 

[pranav8988]

This was the chat with the nvidia support , here have a look :
Zia: Hi, my name is Zia. How may I help you?
Pranav Rawat: Hi! I own a Lenovo y50-70 laptop with nvidia GTX 860m graphics card. Lately after installing 378.49 Driver, my windows is crashing and freezing. Most of the time i get a BSOD saying clock_watchdog_timeout.
Zia: I apologize for the inconvenience caused and I'll do my best to assist with the issue
Zia: Have you over clock the card?
Pranav Rawat: No my card is not overclocked. I have tried clean installation. I also have resetted and updated my windows 10.
Zia: Please install the below driver and see if it helps:

http://www.nvidia.com/download/driverResults.aspx/113444/en-us

378.49 is game ready driver for Resident evil 7, if you have the same game installed then only it would help with this driver or else you may revert back to previous driver as above and check
Zia: NOTE: Please select Custom (Advanced) while installing the graphics drivers and on the next screen please place a check mark on perform a clean install
Pranav Rawat: Yes the previous versions work totally fine.
Zia: Then please use the same till we release next driver
Pranav Rawat: http://www.tomshardware.com/answers/id-3312531/nvidia-geforce-driver-378-causing-crash.html
^but about the 378.49 , i am certainly not the only one with this problem.
Zia: Yes, we are aware about this
Pranav Rawat: Alright, so do i hope that the next release of the driver would be perfectly fine?

Zia: Yeah, it should be, however could you help me with the dmp file for bsod with that driver so we can escalate the case as well
Pranav Rawat: Umm actually i just had to reset my windows 10 because the bsod wasnt letting me sign in. So i don't think i'll be able to provide you with that.
Zia: Oh, we need dmp file so we can forward the case to l2 team and they need to analyze the dmp file for root cause of the issue
Zia: Or if you want you may wait till next driver release
Pranav Rawat: Umm what i can do is, i can ask people on the forum experiencing the same issue and get you the dmp file.
Zia: You may update the same driver 378.49 then if you came across Bsod it would generate DMP file in window
Pranav Rawat: Hahaha, i really had a very hard time because the BSODs as i almost got locked out and would have lost my data, So i am refraining to install the driver again, but as soon i'll get the dmp file from someone else via this forum: http://www.tomshardware.com/answers/id-3312531/nvidia-geforce-driver-378-causing-crash.html
I'll get back to you.
Zia: Sure, thank you for all your efforts and I am sorry for the trouble due to this
Pranav Rawat: Ah, its okay it had happened earlier with some of the drivers around last year and all the 860m users got a stable and a working driver after the next 3 releases. I hope Nvidia figures the problem this time a bit earlier.
Zia: Sure, we will do that
Pranav Rawat: Thanks. Should i disconnect?
Zia: Sure, you may
Pranav Rawat: Thanks again, bye
You have disconnected.

 

[pranav8988]

This is the first time that an Nvidia driver has caused something like this. Does this occur often for Nvidia users? If so, how do people normally fix this problem, do they just wait for an update from Nvidia?

Yes we just rollback to the previous stable driver and wait. :/
Last year, a Similar problem had been faced by many 860m users and we had to wait for the next 3 driver releases till we actually got a stable driver.

 

[pranav8988]

http://nvidia.custhelp.com/app/answers/detail/a_id/4378
new hotfix driver, did anyone try this yet?

 

[BNWilliams007]

http://nvidia.custhelp.com/app/answers/detail/a_id/4378
new hotfix driver, did anyone try this yet?

I just installed that driver and so far my OC has booted to the desktop just fine, I haven't ran a game yet though but am currently browsing the web and no crashes are happening.

 

[kunjila kobasa]

http://nvidia.custhelp.com/app/answers/detail/a_id/4378
new hotfix driver, did anyone try this yet?

I just installed that driver and so far my OC has booted to the desktop just fine, I haven't ran a game yet though but am currently browsing the web and no crashes are happening.

But you own a GTX 1080, right?
That's completely different story my friend
I think most of us in this topic reported issues with 860m
I guess it's not a big of a deal to have a bit outdated drivers until they come up with the real solution...it's not that gaming performance is going to suffer anyway...just the anoying Geforce Experience crying to get thi crap driver update