• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Nvidia GeForce 364.51 WHQL driver

N

nvgpu

Senior member
http://www.geforce.com/whats-new/articles/tom-clancys-the-division-game-ready-drivers-released

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

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

https://forums.geforce.com/default/...thread-released-3-7-16-/post/4829220/#4829220

As some of you have already noticed and thanks in large part to your help in getting us information about the critical installation issue that some people endured, we have replaced yesterday’s driver (364.47) with today’s new driver (364.51).

This driver has been submitted to Microsoft for WHQL-approval and we will update the driver package online as soon as it's certified. At that point we'll create a new feedback thread for the WHQL driver. In the meantime feel free to continue using this thread for 364.51 feedback.
Click to expand...
 
Last edited:
Another piece of crap from Nvidia. I had to go into safe mode to remove it since it crashed Windows a few seconds after throwing up a bunch of artifacts. 362.00 killed my Dying Light performance and 364.47 isn't even usable. Time to DDU and install 361.91 for my 970.
 
AVOID! Complete garbage.

Had to do a safe reboot and disconnect my 2nd monitor to revert back to an older driver version.
 
This is so frustrating. I recently left the red camp after 10 years and moved to the green. I love my 980ti. But dang. Part of the reason I switched was generally people loving Nvidia drivers. Go figure, I drop a ton of cash and switch... now their drivers are junk!

Guess it's back to red next gen =(
 
Ummm...I've got a theory, let's see if anyone else can confirm it. Anyone who is having the issues that seem to be happening with these, try not allowing any overclocking/voltage etc. tools to load and see if they work ok for you. I just installed these a bit ago and I was having lockups, etc. I didn't allow the Galax OCing tool to load and *so far* they have been ok, that's not to say it won't happen in 5 minutes though.
 
YBS1 said:
Ummm...I've got a theory, let's see if anyone else can confirm it. Anyone who is having the issues that seem to be happening with these, try not allowing any overclocking/voltage etc. tools to load and see if they work ok for you. I just installed these a bit ago and I was having lockups, etc. I didn't allow the Galax OCing tool to load and *so far* they have been ok, that's not to say it won't happen in 5 minutes though.
Click to expand...

They admitted they screwed up, and this is going on without O/Cing.
You can either disable/disconnect all but one monitor and install them, or wait for the fix.
 
I didn't even have to apply an overclock, just allowing the tool to load did it. Not to say this was causing the issue, may be happenstance, but it hasn't happened since not allowing it to load (admittedly short period of time). I was trying to bench The Division, just as I got to the first playable section Ubi's servers went down....lol, maybe tomorrow.
 
Elixer said:
They admitted they screwed up, and this is going on without O/Cing.
You can either disable/disconnect all but one monitor and install them, or wait for the fix.
Click to expand...
I installed with a single monitor system and still got the lockup. Nothing in this version I really need anyway, so I'll stay with my restored driver for now.
 
https://forums.geforce.com/default/...thread-released-3-7-16-/post/4829220/#4829220

As some of you have already noticed and thanks in large part to your help in getting us information about the critical installation issue that some people endured, we have replaced yesterday’s driver (364.47) with today’s new driver (364.51).

This driver has been submitted to Microsoft for WHQL-approval and we will update the driver package online as soon as it's certified. At that point we'll create a new feedback thread for the WHQL driver. In the meantime feel free to continue using this thread for 364.51 feedback.
Click to expand...

Links updated in first post.
 
Thanks for the update. I noticed that they pulled yesterdays driver in favor of this new one as it's no longer listed on their website. When the new driver finishes downloading I'll install it and see what happens.
 
Huh, just updated to 364.51, and on reboot, I ran into a nvlddmkm.sys BSOD.
Seems something is still funky with these drivers.

Might have to do a clean wipe of them.
 
xorbe said:
This is a complicated topic, and can results from a great number of issues - hardware, overclocks, driver, even malware.
Click to expand...

I agree. The 364.47 gave me those errors at stock clock constantly. The machine is used for only gaming and browser only goes to Nvidia's website for driver downloads. No other software is installed besides steam, origin and uplay and also benchmarking tools.

I did use ddu to uninstall the 364.47. The new drivers gave me a TDR when I was pushing the clock. But otherwise it seems like it's working well.
 
How is that WHQL working out? Are they still giving people the warm fuzzies?

I'm going straight to the beta 364.51 drivers.
 
mojothehut said:
This is so frustrating. I recently left the red camp after 10 years and moved to the green. I love my 980ti. But dang. Part of the reason I switched was generally people loving Nvidia drivers. Go figure, I drop a ton of cash and switch... now their drivers are junk!

Guess it's back to red next gen =(
Click to expand...

Their drivers have always been this bad.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top