NVIDIA GeForce Game Ready Driver 364.72 WHQL

H

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
The folks at NVIDIA send word that the brand new GeForce 364.72 Game Ready Driver WHQL is out now. These drivers bring full support for the Oculus Rift virtual reality headset, optimizations and enhancements for virtual reality games such as EVE: Valkyrie, Chronos, and Elite Dangerous, and the latest support for NVIDIA VRWorks.
 
Hopefully these will fix the black screen lockup bug from the last ones. Nothing like building a new system, having it lockup randomly with a black screen. Spending hours testing everything only to discover its the video drivers.
 
p.i.m.p said:
i've never had problems with 364.51

on a EVGA 960 GTX 4GB
Click to expand...

I have a Asus Strix 980. The system would lock 4 out of 5 times after leaving it, not allowing the system to sleep only the monitor in power save. I could game for hours without issue, then it would just randomly lock while web browsing.

Drewis said:
ha Lothar, no shit....

how long did it take you ?
Click to expand...

Not that much of my actual time, but running a full deep pass memtest on 32GB of RAM and AIDA64 stress testing took about a day and a half.
 
Are these okay for Win7, or are we waiting for hot fix.
 
9P69eRR.jpg

v8OBvzO.jpg


not sure what's going on here.
 
^

That's why I never upgrade right off the bat anymore. I wait and see what others have to say first!
 
On Reddit's Nvidia sub, there are tons of users complaining about 364.72 "frying" their cards. One of the most active topics claims it's "bricking cards left and right".

Is this some sort of April Fools joke or is the Reddit PC gaming community made up of complete morons?
 
crusty_juggler said:
On Reddit's Nvidia sub, there are tons of users complaining about 364.72 "frying" their cards. One of the most active topics claims it's "bricking cards left and right".

Is this some sort of April Fools joke or is the Reddit PC gaming community made up of complete morons?
Click to expand...
Every time a new driver comes out, there will be a massive thread on Nvidia's forums where people post their issues. This happens with every driver.
In recent weeks, Reddit has begun citing those threads as source for proving "The driver is BROKEN!"

From that thread:
there are hundreds of posts on reddit and the nvidia forums of people saying the latest driver update is bricking hardware.
Click to expand...

Hundreds? Really?
0 posts about it on /r/pcgaming, /r/hardware, /r/pcmasterrace. 0 posts on this forum, too.

I see literally 1 post about it and it's that thread with no source. No blog posts, WCCF Articles, nothing.
 
Last edited:
Still bricking cards? It's been two straight driver releases! What the fuck are they doing?
 
i don't understand how a driver can kill a card in the manner that that one thread on the nvidia forum shows.
 
Well, I'm not certain about killing graphics cards, but I do know that they can kill Laptop LCDs (and certain desktop LCDs).

How? For some fucked up reason, with Windows 10 (EDIT: or Windows 7/8 with Windows 10 ready updates) and Nvidia drivers and certain laptop screens (like my AW M18X R2) it can OVERWRITE the EDID. It wouldn't be a big deal, but the M18X R2 can't boot without detecting the built in screen.

So what did Nvidia do? Ignored the problem while dozens (admittedly there aren't thousands of us) of us had to buy new or used $200 screens (I had 3 brick on me before I found out about the issue) so that we could re-flash our soft bricked laptop screens. That was about a year ago now - still nothing from them. And that's why I'll never buy a Dell or an Nvidia product again.
 
Last edited:
  • Like
Reactions: Yakk
like this
I don't know what is happening with those users, but I did notice my Titan X is running hotter than on the 361.75 driver. Playing Dying Light the other night it was getting up to 80C when before the update it would be in the low 70s. It's a good thing I already made the fan curve more aggressive since it's starting to get hotter outside.
 
Odellus said:
i don't understand how a driver can kill a card in the manner that that one thread on the nvidia forum shows.
Click to expand...
It can't. Those people are dumb. Did you see the users claiming Nvidia altered their cards' BIOS with a driver update?

Notice how on more...ahem "knowledgeable" forums there are zero complaints about "bricked" GPUs. Yet places like Reddit and the Nvidia forums have threads filled with users claiming their cards are destroyed. It's all an overreaction to run-of-the-mill GPU driver bugs from novice PC gamers.

Sad thing is, stuff like this gets picked up by clickbait bloggers at places like WCCFtech and Destructoid and spreads like wildfire among the ignorant.
 
crusty_juggler said:
It can't. Those people are dumb. Did you see the users claiming Nvidia altered their cards' BIOS with a driver update?

Notice how on more...ahem "knowledgeable" forums there are zero complaints about "bricked" GPUs. Yet places like Reddit and the Nvidia forums have threads filled with users claiming their cards are destroyed. It's all an overreaction to run-of-the-mill GPU driver bugs from novice PC gamers.

Sad thing is, stuff like this gets picked up by clickbait bloggers at places like WCCFtech and Destructoid and spreads like wildfire among the ignorant.
Click to expand...

Glad someone else picked up on this. Hanging out at places with less retarded people like [H], Overclock.net, and Guru3D always paints a different story compared to Reddit or the Nvidia forums. Reddit is the worst, people will up vote the shit out of posts that sensationalistic and often factually wrong. Just people who don't know what they are talking about circle jerking other uninformed users.

Also the Steam forums have a few sub forums where the entire user base is pants-on-head mentally challenged :eek:
 
I noticed over on TPU forum that someone has a bricked 290X card. The nvidia driver is more evil than we realized!
 
well I have one issue with this drivers and is the fact that it make my 980TI unable to run at boost clocks after certain periods of time and/or while few benchmarks.. easiest way to test/reproduce is with GPU-Z render test as when the bug is present it will not go above 1190mhz... reverted to 364.51 working good again..
 
Araxie said:
well I have one issue with this drivers and is the fact that it make my 980TI unable to run at boost clocks after certain periods of time and/or while few benchmarks.. easiest way to test/reproduce is with GPU-Z render test as when the bug is present it will not go above 1190mhz... reverted to 364.51 working good again..
Click to expand...

I've been noticing this issue for a while now since I got the drivers for ROTTR. What's odd is that when I overclock my card it maintains the boost clock like it should. Weird.
 
You must log in or register to reply here.
Back
Top