Nvidia WHQL Driver 355.98

http://www.nvidia.com/download/driverResults.aspx/91808/en-us (Notebook with 7 or 8.1)
http://www.nvidia.com/download/driverResults.aspx/91814/en-us (Notebook with 10)
http://www.nvidia.com/download/driverResults.aspx/91812/en-us (Desktop with 10)
http://www.nvidia.com/download/driverResults.aspx/91806/en-us (Notebook with Vista, 7, or 8.1)
Driver for just announced GTX 980 in laptops and Killing Floor 2.

 

From what I'm reading on the nVIIDA Forums, this seems to break scaling where you turn off scaling. Another driver fail from the nVIDIA Clowns:

https://forums.geforce.com/default/...eady-display-driver-feedback-thread-9-22-15-/

 

https://developer.nvidia.com/gameworks-vr-driver-support

 

This driver is already broken and a hotfix update driver is available:

https://developer.nvidia.com/gameworks-vr-driver-support

This mentions fixes for SLI as well.

@Mr. Fox @Papusan

 

VR SLI, not normal SLI. This is a dev driver mainly intended for VR devs, not a hotfix driver.

 

ohh ok, thanks for the warning, won't install it then. Still disappointed with the initial comments on the GeForce forums thread, doesn't sound promising.

Will test it soon and post my benchmarks.

 

I never read the GeForce Forum driver threads and generally stay off that board altogether. Every single "driver feedback" thread devolves into a flame war and trollfest sooner or later and the moderators there are incompetent dweebs. It's impossible to get a good picture of the status of any driver because the only purpose those threads serve is as a b*tchfest and venting place for angry nerds.

 

I guess you're right, most posts I saw were from muppets that cannot even get it to install. Those n00bs have probably never heard of DDU

 

NVIDIA's drivers have become progressively more screwed up with each release for the past 6 months to an unbelievable extent. I've never seen such a botched up driver mess, literally. They're actually worse now than anything I ever had to deal with from AMD. Throttling, BSOD, temporarily unresponsive desktop icons, intermittent freezing on the desktop, NVIDIA Control Panel crashing/freezing/not responding, browser instability, black screens and LCD damage/EDID corruption. Did I miss anything?

 

Hmm, a new .inf file has appeared, at least to my knowledge of previous drivers and installation of this driver, nv_desktop_refi. It holds the ID 10DE.

 

That INF was included in the last driver, but yes it is new. It's applicable on the Win7/8.1 drivers. I haven't looked at the Win10 driver to see if it also has it.

 

The only driver I think actually got halfway back into a sweet spot has been 355.60, but that still breaks your 780Ms in your Alienwares so it's pointless.

 

I am on 355.84 and it is literally PERFECT for me on my laptop + desktop, even with some undervolting on my laptop GPUs.

 

Clockblocks

 

Good Lord, I swear I need snaps and velcro to hold together my M18xR2 instead of screws ever since Windows 10 ruined my system BIOS with it's EDID-corrupting root kit.

Installed NVIDIA's brand new driver on the M18xR1 (never touched by Windows 10) and the M18xR2 this morning. M18xR1 is working normally. M18xR2 LCD is bricked again. Block 14 was changed from 90 to 00.

 

Is this with write protection done on the panels? Even with physical write protection you can't prevent the bricking?

 

The LVDS cable trick that we thought would write-protect does not. It does not seem to do anything. Everything works exactly the same after I snipped the wire for pin #5, LOL. But, I have not tried the hard mod with the EEPROM leg #7 yet.

 

Well... hopefully we find out soon. Either way we take it, if there's irreparable damage to the system because of Windows 10 and nVidia's drivers, BOTH are to blame. Until intel drivers cause issues, nVidia is part of the problem. We'd need someone to prove it's a repeatable occurrence on both intel and AMD systems before we can write nVidia off as being scot free.

 

it's on 356.04 dev or hotfix (not sure) now. might give it a try.

 

Shot in the air. Have you tried with standard vbios in M18xR2?

 

Nvidia 356.04 is a developer driver its not a hotfix driver. It can be found here:

http://forums.guru3d.com/showthread.php?t=402674

No problems so far. Everything works smoothly. (Can't turn off bold right now)

 

This driver already crashed on me (been a while since a driver crashed), so I'm going back to an older driver.
EDIT: Crashed 3 times on me. Nope, don't like this driver.

 

Did you use DDU to uninstall the previous driver? This drive gave me 0 issues whereas 355.82 used to keep the GPUs always at full speed mode even in Windows 2D environment and if I would touch my graphics card I would literally burn my hand from the heat. Mind you, this is on my desktop, on a laptop it could possible fry the motherboard, the GPU, or any other components due to the constant heat generated because the GPU is @ 100% speed all the time.

 

I usually use DDU to uninstall drivers. Don't remember the last time I didn't use DDU.

 

well if you decide to stay on the previous driver, please monitor your GPU clock speed using GPU-Z and the temps before something bad happens that requires you to change major components.

 

Yes. It made no difference. LCD bricked with stock vBIOS same as modded vBIOS. Also the same with stock system BIOS.

 

My wife's Dell Vostro 5470 has been running Windows 10 for about 2 weeks now with the latest driver. Why hasn't her LCD been fried? or is it an issue pertaining to Alienwares and Samsung/LG laptops only?

 

Because she has Optimus, which means the intel GPU is responsible for the display.

 

edit: nm ↑

 

What @D2 Ultima said is the most logical explanation. From his post, it appears Brother @t456 agrees, too.

At the same time, we don't have a clear understanding of why it affects some Alienware and Clevo laptops and not others. We have zero answers from Micro$loth and NVIDIA. Based on casual observation, there appears to be an unwholesome connection between Windows 10 and Kepler GPUs... in particular, 780M and 880M are very suspicious. I believe there is something in the vBIOS of Kepler (perhaps other) NVIDIA GPUs that searches for a good EDID. If it's not finding something it agrees with after Windows 10 has tinkered with things, it may be trying to help fix it and screwing things up in the process. (Speculation at this point.) Look at GeForce drivers for notebooks and you will find code in the INF relating to EDID.

Open the NV_DISPI.INF (this is for desktops) and search for EDID. Notice where the last entry is, as well as some of the code with references such as "OverrideEDID" and then open a Dell (NVDMI.INF) or Clevo (NVCVI.INF) and you will find additional code that goes beyond that found in the desktop INF file. Using desktop INF mods isn't stopping it (have already tried that after seeing the EDID codes and wondering) but it's still interesting. I need to download an AMD Catalyst driver package and have a look. I suspect I will not find any code in the AMD driver INF files relating to EDID.

Equally important: Why, for the love of Pete, would you have that cancer OS on your precious bride's Vostro?

Side note: You may have noticed that in addition to Micro$lop and Micro$haft, I am using the slur Micro$loth when making reference to the Redmond Mafia.

This is by design: [ Definition: sloth]. Rather fitting, don't you think?

 

Yes.

That, and that all affected displays were non-write-protected (duh ). However, from other reports, that isn't generally so, thereby safeguarding some non-Optimus systems from the same bug (writes do take place, only to no effect).

 

Formatting my computer and my wife's tomorrow. Thank you

 

Oh now that's easy: there are exactly four laptops from Gigabyte, ASUS and MSI COMBINED that use dGPU-only modes: The Gsync G750 line, the Aorus X7, the GT72 and the GT80; all extremely recent and likely already with "win 10 prep". Also, there's been no gsync models with a single fail, which likely means that those models have had some special attention, which isn't easily apparent. Alienware does not use those models and has opted for Optimus-only from what I've heard with their new models, so they wouldn't know anything about that. Since the newer models like the P7xxZM from Clevo generally haven't been killed and the majority of the P37xSM and P37xSM-A models haven't touched Win 10, we can consider it luck of the draw, rather than the ridiculous amount of legacy alienware owners who have a CHOICE to use dGPU-only mode instead of the rest of the world and "optimus".

I can never understand this XD.

I think it's wonderful =D

 

How many 780M and 880M owners got a flag from Micro$loth's Windows 10 Compatibility "Gizzard" that more or less said that your GPU was not compatible with Windows 10 and something to the effect that because your video card is not compatible you needed to wait until the manufacturer fixes that issue? So, you found a way to download an ISO to bypass that notice? Hmm? *raises hand* I know I did and I saw others say they did the same thing. Relevant? I don't know... just another random observation.

Glad you like it. I think it applies to NVIDIA, too. That one part nails it for both of them.

 

testing the 356.04 dev driver.

 

I have not had any issues with 355.98 yet. Works great. Did the same thing I always do, express install over the previous release.

 

Win7. A good choice ...

 

356.04 dev drivers seem to be going ok for me on 8.1....10 needs to be exorcised!

 

Man, 353.62 is still the best driver for me. 355.60 and 355.82 are not stable... sometimes they cause hiccups or freezes, and downright crashes. Not even in gaming, but general usage.

How are 356.04? I don't trust the latest drivers after two continuous botched drivers. Funny enough the issues only seem to be happening very few Titan users. Thought it seems many have general issues with drivers.

 

so far no issues will see after a few days.

 

Really? 355.60 is stable for me. I skipped 353.62 but I know all my friends on desktop (and I do mean all) have had issues with it. I thought 355.60 was the most stable driver in the last few months.

I dunno I've never had nVidia driver problems on this laptop. Maybe it's a sign and I can sell it for a $1000 price markup kekeke... "Guaranteed no problems even with nVidia's most cancerous drivers! M18x R2 throttling at stock clocks with 355.82? FEAR NO MORE! Here's a real time video of Firestrike running with a +157/500 OC with SLI turned on! <insert video>"

*hugs my baby*

 

The thing that makes me skeptical about the whole issue with my nvidia drivers, is that they appeared right after I downgraded from windows 10. Maybe windows is trying to force me into win10 by making my win8 unstable with new drivers!

355.82 for example could be perfectly fine for a day or two, but then it might become unstable and crash. Same with 355.60 and I don't know why. Older drivers seem fine and so far only 353.62 seems to be the last one I ever updated that is problem free.

It's so weird... I just want stable drivers to game!

 

Did you use the built-in downgrade tool or clean install 8.1? Also, the word is "upgraded" from Windows 10. As far as I can see Win 10 is a downgrade to all.

And of course did you try DDU on them?

 

So many shenanigans and varying experiences.
I´m sticking with 8.1 and 347.88 until there´s a general consensus regarding driver.

 

I only moved to 355.60 because BO3 wasn't working well and SLI was not working well (with BO3) either. If it wasn't for that I'd be on 353.06 which was stable still.

 

I've been meaning to change my driver from 347.88 for months now. I want to get rid of all traces of nvidia experience. Doesn't seem to serve any purpose and shadowplay doesn't work in the games I want it to(FFXI).

But every time I check here to see if there's a new stable driver, all I find is complaints that the new drivers just keep getting worse and worse.

Guess I'll just reinstall 347.88 and tick off experience during setup.

Sent from my SM-N910C using Tapatalk

 

I used the built in "RUN AWAY FROM WIN10" button. And yeah, I prefer win 8.1 to 10. Even aesthetically.

I havent tried DDU, I only do clean installs (the built in option in the drivers) and this is the first time in a long while that I have had such issues. I could try DDU and try again the newer drivers but its such a hassle to find problems days later.

 

Clean install Win 8.1 and see how fast the problem goes away.

 

@Mr. Fox @Papusan @TANWare

nVIDIA GeForce 980Ti SLI (x2) 355.98 Driver on Windows 7 VS 10 3DMark

 

Is there a consensus on whether or not this driver is alright for Windows 10? I'm still on 353.54 which isn't a particularly good driver as it is. GPU is a 970M (G751 notebook).