[USE AT YOUR OWN RISK, WIDESPREAD BRICKS!] nVIDIA GeForce Drivers v364.72 Findings & Fixes

I keep saying it. If there's a "game ready driver", ignore it. Just don't even bother. If a driver comes out not prepping for some game or other, then we check.

This is getting beyond ridiculous.

 

I'll get on it later. I went to bed last night lol

 

I'm not a cat, I have just one life. So if I decide to update a driver on Nvidia GPU (from R338/ R344) I am to use DDU.

PEEEEE-RI-OOOOO-OOOD! Ba-Dumsh!

 

Indeed, I am going back to 362.00 just to be on the safe side:


Geforce 980 ti dont working anymore driver 364.72 Pc shut down about overheating.

 

The amounts of failures due to this driver is a bit concerning, see:

https://forums.geforce.com/default/...-driver-feedback-thread-released-3-28-16-/34/

 

Heh, this doublepost I can approve

Spoiler

 

when I saw this.....I seriously had the laugh of the day ROFL!

Here is another, not funny as yours but very true:

Spoiler

Their moderators are too lazy to even clean the spam:

Spoiler

 

i guess this a no.

 

Maybe Nvidia is on a payroll?

 

Depends. Do you want to fry your GPU?

 

what version are you on?

 

364.51.

 

I am thinking of going back to 362.00 but my 6th sense tells me we should expect a new driver within the next couple of days

 

If your current driver works fine, don't bother. Why fix what isn't broken.
I was running 364.47 IIRC (don't remember the exact number, just the fact that it was pulled after release), once The Division came out. It ran well. Then I decided to go back to 362.00, but with it I had some texture flickering in The Division. After OS reinstall I decided to go with 364.91 and will stay with them for a while.

 

Although the new Nvidia 364.72 driver has been causing some people problems, it's helped my GT80 980m SLI sustain the highest boost clocks so far, +135 +400.

Before 364.72 I had to choose between a high Core clock or a High Memory clock +135 +300 or +125 +400 - I couldn't sustain both at the same time.

I have run a number of benchmarks / games / apps and they all run stable with my GPU settings at +135 +400 with 364.72

I posted a new SteamVR score as well, with the sustained boost clocks + VR Optimizations in 364.72, my Score went up from 9.5 to 9.8 !
http://forum.notebookreview.com/threads/steamvr-performance-test.788566/page-8#post-10233160

 

Might be related, might not... friend installed the latest drivers on his 680m and his GPU is now like... dead. Lots of issues, windows disabled the device after installation due to problems etc etc. I will check it out eventually to see if it had anything to do with the drivers, or if his GPU downright died.

 

That seems to be a theme with the failures reported with 364.72, cards from the GTX 6xx series.

 

after seeing this post, I have no doubts (click on the spoiler please):

http://forum.notebookreview.com/thr...72-findings-fixes.789930/page-6#post-10232695

 

This driver hasn't really caused any issues for me but I'm going to go to 362 just to be safe. I just got GTA V and if anything would fry my cards, I'd rather not risk it.

 

As others have reported, since 362.00 all drivers lose gsync option for p751dm-g models, with the LG panel. I opened a support ticket with nvidia and sent them monitor info reports and system reports to look into the issue.

They were prompt to solve the missing a hw id in driver inf issue couple months ago, again after a lengthy email conversation with some tech dude on their side.

Hopefully they will fix it by next driver release.

Sent from my Nexus 5 using Tapatalk


Le:

Discussion Thread Response Via Email (Farzana)04/05/2016 04:52 AM

Hello Andrei,

Your case is being escalated to our Level 2 Tech Support group. The Level 2 agents will review the case notes and may attempt to recreate your issue or find a workaround solution if possible. As this process may take some time we ask that you be patient and a Level 2 tech will contact you as soon they can to help resolve your issue.

Best Regards,
NVIDIA Customer Care

 

looks like i'll be playing quantum break with the 362.00 driver then!

 

@Ethrem

I think this driver deserves a warning tag. See: http://forum.notebookreview.com/thr...0-owners-lounge.776183/page-363#post-10236042

and:

Spoiler

http://forum.notebookreview.com/attachments/doublepost-png.133842/

 

Updated to GeForce Experience 2.11.2 to GeForce Experience 2.11.2.67 through GFE; I have Beta updates checked for GFE/driver - there is no driver update yet.

Release notes aren't too helpful:

GeForce Experience 2.11.2.67 Release Highlights
• Bug fixes and general improvements.
________________________________________
GeForce Experience 2.11.2 Release Highlights
• Adds VR readiness check for notebooks under "My Rig".
• Adds VR category in GFE feedback.
• Improves pairing and connectivity with Shield devices.
• Fixes audio in remote desktop mode of GameStream.

Still having good performance and no problems with 364.72 on Windows 8.1 MSI GT80 SLI-263 - SLI 980m.

 

I'm the abusee, chiming in.
Just posted on the nvidia forums. From what Ive read (only about 10 pages yet) I havent seen anyone get it quite as seriously as me.
Most people can still access safe mode and try something thru there like reinstalling or removing drives. I cant do any of that. At the time being my system isnt even able to POST 90% of the time....

Some people suggest Logitech Setpoint might be the conflict to blame. So I would advise uninstalling it if you have the newest drivers

 

By the way there's new Vulkan BETA driver 364.91
DriverVer = 04/08/2016, 10.18.13.6491

Updated Vulkan API to 1.0.8
Improve pipeline creation performance and multi-threaded scaling
Increase our maximum bound descriptor sets from 4 to 8
Add support for asynchronous transfer queue
Improve VK_EXT_debug_report messages on incorrect API usage and shader compile failure
Fix VkImageFormatProperties maxMipLevels property
Reduce VkPhysicalDeviceLimits bufferImageGranularity requirement on GM20x GPUs
Improve Vulkan support on Optimus platforms
Fixes for minor driver and SPIR-V compiler bugs

Code:

https://developer.nvidia.com/vulkan-driver

 

Indeed. Warning added.

 

364.72 did some foul witch trickery with the 780M setup in my M18x R1....8 beeps after installing/restarting. I was just tired enough to put the computer aside. Power drained the next day and it POSTed, but my second 780M was giving code 43 in windows. Ran DDU, reflashed VBIOS, everything OK for now. Definitely sick of nVidia, I'm actively pursuing going back to AMD.

 

Well my friend's 680m definitely died off. Can't uninstall/reinstall drivers that work for it, it always crashes now.

We took the oportunity to update his GPU to a 970m so now we have it working again. I also noticed while trying to download the official drivers, I could no longer download 364.72 from their page, sent me an error when I clicked it. So I went to 362 for the time being.

 

Bro with the amount of bad reports I am reading lately on OC Forums as well, this driver should be banned from these forums.......seriously....it is causing people to lose their entire GPU that even if uninstalled the damage is irreversible.......

 

just read your post after posting my last post in this thread, that's exactly what's happening with some people on the OC Forums. I must count my blessings that my 980 GTX (desktop class) is still working as I have used this driver for about a week before reading these warnings........


I wonder why big brother @Mr. Fox has been commenting on the latest nCrapia swiss cheese driver

 

So, is this the next step in nGreedia's "planned obsolescence"?
"Not only do our drivers make your last gen GPUs perform like crap, they also brick them. GeForce Experience (TM)"

 

you got that right, here is what nGreedia is thinking........

Hmmm, AMD has no new good GPUs........we got all the money we can selling our greatest and latest GPUs.......how to make money now? Ok, simply, bring the drivers clowns squad and let them destroy all current GPUs with the latest drivers. This way everyone buys more new GPUs and we get richer. There is no other explanation IMO

 

Employee of the month:

 

seriously brah, when are going to get a new notebook AMD GPU? I don't like to be a slave to nVIDIA anymore and there are no other options at the moment

I am sick of this really, month after month, driver after another, it's a matter of luck if you get a working one. Let alone the risk of rendering your GPU useless if you got a really bad one.

In the past, I always favored nVIDIA GPUs purely because of their excellent drivers back then compared to AMD. They have totally destroyed that image now.

 

It's not like AMD hasn't killed cards though... the Crimson release spilled red all over the floor when the fans stopped turning on...

They both are terrible at drivers and that becomes even more evident when you look at the lackluster performance AMD cards have at launch versus a year or two down the line. I don't have confidence in either of them anymore. With all the failures AMD never bothered to do anything about and the mess Nvidia is making now... it's a bleak picture.

 

I have also used this driver for about a week. What about those who have been forced drivers from Win update? Is this driver also in Win updates database?

 

great, just to make it worse I don't have much experience with AMD Drivers other than the old days when I had Dual 290X Crossfire in my Alienware 18

 

no, windows updates database is a few versions older (luckily)

Like for my Wife's Dell Vostro, Windows updates only offers driver v 353.62 if I remember correctly

 

I think Microsoft backed off of forced video driver updates... I wasn't forced into one. Nvidia shows me when one is available through GFE. Video drivers and sound drivers have always caused the most issues going all the way back to Windows 3.1 and the same applies to Linux as well so forcing video updates is just stupid.

 

I don't know where this AMD driver bashing comes from...seriously. Maybe this was the case 4 years ago, but ever since 2013, their drivers have made incredible gains, and I've certainly never experienced the clockblock, throttlegate, brick-city crap nVidia has been doing this past year. My stock 7970M was performing right on par with a stock 780M before I sold them, which I only did to get larger vRAM cards, and I whole-heartedly regret that decision now with all this crap nGreedia is doing. Actively looking to move from 780M to 8970M.

 

The Crimson release last fall made some cards run with severely reduced fan speed causing heat issues and allegedly caused some failed cards. This is one of the articles:
http://www.anandtech.com/show/9823/amd-releasing-new-crimson-drivers-for-gpu-fan-issue

Stock 7970M performing like stock 780M doesn't sound right as it sometimes struggles to compete with 680M. Unless "them" means you had Crossfire?

 

Listen, I own[ed] BOTH sets, the 7970M crossfire and 780M SLI. And yes, they were trading blows with each other, and the 7970M edged over the 680M in the end as the drivers matured. If I could get my hands on a set of Clevo 8970Ms I would dump the 780M in a heartbeat.

 

one of the best things for me in nVIDIA GPUs was CUDA and now even that is gone

 

CUDA is still provided with the driver package, and it's up to version 8.0, as per 364.72 release notes pdf:
http://us.download.nvidia.com/Windo...-win8-win7-winvista-desktop-release-notes.pdf

What’s New in Version 364.72 WHQL
...
Software Modules (page 3)
• NView - version 147.00
• HD Audio Driver - version 1.3.34.4
• NVIDIA PhysX System Softw
are - version 9.15.0428
• GeForce Experience - version 2.11.2.42
• CUDA - version 8.0

 

so why is it that when I use MPC-HC with the LAV Filters and set it to CUDA, a lot of videos just appear black........

on Windows 7 I never had this problem but on Windows 10 I thought CUDA was not working

 

IDK, I use CUDA a lot, and haven't seen it go missing. Doing computation runs now in SLI, performance is good as are temps:



Likely an app bug with LAV / MPC-HC, go for an update, and/or report the problem.

 

You agree 680M and 7970M are equal but your 7970Ms were equal to 780M SLI? Forgive me but I'm gonna need some proof to digest that.

You shouldn't have any problems getting those 8970Ms, you're probably the only one who wants them.

 

No, I don't agree the 7970M and 680M are equal. Stock for stock, the 7970M (6800) outperforms the 680M (6540) on the 3dmark11 bench when they first came out, neared 7300 single when I sold and is closer to the 780M. If/when I get another set of 8970Ms in, I would be happy to do a stock-stock comparison. They are difficult to find with the crossfire connector, believe me. The clevo 8970Ms are rare, the the Dell 8970Ms have a weird connector, with a incredible difficult to find cable.

 

I might have come off a little snappy. If you get a pair of 8970Ms to beat 780Ms by more than a smidgen that's news to me and I'm genuinely curious.

 

It's all good man, no harm done. I will try to track down a pair and do some comparative testing with 2016 drivers, all the stuff out there is really, really outdated, but AMD was making great updates to the GCN architecture performance with driver updates, while nGreedia has been crippling legacy products. The only thing nGreedia holds over AMD, is physX + CUDA, but I would happily trade that for raw compute performance that AMD has...see how the 7970M will absolutely roast even a 980M for anything remotely compute related. Hairworks can be run on AMD with barely a hitch too. I find it hard to support a company as terribly unethical as nVidia, and to be honest, with all this crap going around, I'm surprised a class action hasn't been leveled at them for this crap.