Latest Nvidia Driver 355.60 (August 13th) Fails

Don't know why it keeps failing to install. Never had this problem before.

 

To protect LCD's from burning out? LOL


Sent from my iPhone using Tapatalk

 

And now the older driver is failing to install too. What the hell?

 

Maybe NVIDIA removed Alienware hardware IDs (probably a really smart move if they did) until they can figure out what is killing so many LCD panels. There are enough examples of it happening now that they need to be concerned and pay attention.

 

Nah, the IDs are there. I checked myself.
Since Saint Satan said older drivers have failed, then the problem lies elsewhere.

 

maybe their hardware or config is causing it. i am curious if this does "fix" the LCD failure issue.

 

That is what I always get when I try to install driver in a normal manner. I have to use I have disk method to get drivers to install. I got this driver to install by the usual modded method.

 

busted installer?

 

That would mean every driver I've tried to install that way was busted. Somewhere along the line it just happened where that damn thing would pop up. Even after I've modded the driver if I click the setup icon inside the folder it still failed. I just gave up trying to get this way to work.

 

I didn't know about LCD panel problem. This morning my Aw17 said there are a Nvidia update, but i've read the changelog and i decide to not install it.

 

If you haven't already, just for kicks look at your GPU hardware ID in Device Manager to see if it changed. My Panther is now 13D7.0270 instead of 13D7.0376 and I cannot install NVIDIA drivers unless I mod the INF and disable Driver Signature Enforcement. Before that I was able to install unmodded drivers on this machine..

 

I don't have a basis for comparing what the old one was to what the new one, if any, is. Besides, this problem started when I had the original 880s in the pc, it just started to happen. I understand it happens now because of the after market upgrade to the 980s.

 

Unless something changed, the Alienware 18 hardware ID is (was) 05AB regardless of the GPU installed. My Clevo P570WM/Eurocom Panther used to be 0376, now it is 0270. What I was explaining is to check the hardware ID properties in Device Manager for the GPUs and see if it still shows 05AB. That part of the hardware ID refers to the motherboard/model and not the GPU.

Below is a screen shot from my Clevo P570WM. Perhaps it will make more sense looking at that. Compare the content of the INF (13D7.0376) against the properties of the HWID in Device Manager (0270 used to be 0376). This causes my driver installation to fail unless I mod the INF and disable Driver Signature Enforcement before booting Windows 10. This is likely related to a BIOS update I installed for Windows 10 on my P570WM, but out of curiosity, I am wondering if that somehow changed on your Alienware 18. If it did, then it is something with Windows 10 or GeForce drivers that changed the HWID and not my Panther BIOS update.

 

Mine is, %NVIDIA_DEV.13D7.05AB.1028% = Section105, PCI\VEN_10DE&DEV_13D7&SUBSYS_05AB1028. This has been the string I've used since I inserted the 980s, and learned to do it myself (THANKS @j95). The thing I have noticed in win10 drivers is that I have had to change the Section#___. When I'm on win8.1, the section # I've always used was Section 146. For the win10 driver I changed it to a lower number, otherwise it would not work. The one I listed above is what I'm using for the Dell win10 driver.

 

this is what it says for me in 8.1

PCI\VEN_10DE&DEV_13D7&SUBSYS_05AD1028&REV_A1
PCI\VEN_10DE&DEV_13D7&SUBSYS_05AD1028
PCI\VEN_10DE&DEV_13D7&CC_030000
PCI\VEN_10DE&DEV_13D7&CC_0300

 

Question to the one with the failed driver... are you on Windows 10?

If so, look around for a setting that allows drivers to install for your GPUs without being through Windows Update only. That is a problem going on; the manual installer will fail because Windows thinks only Windows Update is allowed to install drivers for you. I don't remember where the option is as I'm not on Win 10 myself, but someone else (who is currently asleep) told me about it. I couldn't find it with a google search just now either, so good luck.

 

It turns out my change in hardware ID was caused by a test BIOS I was checking out and giving feedback for. I'm using a new one now and the hardware ID is back to what it is supposed to be. Sorry for the false alarm. Nobody else would have been affected because it has not been released to the public. I was not aware of that when I posted. I found out I was a guinea pig after the fact, LOL. Everything is peachy now.

 

kinda confused now.

 

Why? I explained why I asked people to check their hardware ID. There was no reason for anyone to check, but I did not know that when I posted the question. I'm just mentioning it now so that nobody else thinks there is a reason to check and report on it. My bad.

This problem was induced by the test BIOS I was using that I thought was a production release. I thought Windows 10 had changed the hardware ID somehow because I flashed it before installing Windows 10 and did not connect the dots until after I posted the observation.

 

so it was a experimental BIOS for the eurocom/clevo that caused the hardware ID change?

 

Yes. I did not know it was experimental and I wasn't actually supposed to have that older test version. I ended up with that one because they gave me a link to the wrong file by mistake, but it's all good now. I would have gladly tested it anyway, so no harm/no foul.

 

ok, so i guess the issue is still unresolved for the alienwares

 

The new one that came out today fails as well.

Any easy way to fix?

And then when I try to install the old Nvidia driver that worked it will now fail so I have to do a system restore to get my GPU working again...wtf? Why would the old one suddenly start failing now?

 

For the sheer hell of it, and for plain 'fun' (and because I'm bored this evening), I've just updated to 355.82 on W10 via an express install - installed fine just now. No doubt my 'puter will soon blow up....................

 

Well, maybe Windows 10 buggered up something in your system BIOS. I'm not joking, either. Have a look at this info and the links provided. Nasty stuff happening to more and more people at every turn. This is not good.

 

Not even the official AW driver will install. I uninstalled the driver and tried to install a fresh driver and it says it can't find compatible hardware.

 

Have you already tried to go back to Windows 8.1 or Windows 7 to see if the problem goes away? It may be something caused by Windows 10 simply being an extremely screwed up piece of trash. Looking on the positive side, maybe they did something on purpose to block you from installing GeForce drivers under Windows 10 to keep your LCD from getting fried by Windows 10.

 

I just rolled back to Windows 7. Let's see what happens...

 

It works fine on Windows 7 now. Must be a bug with Windows 10.

My 3D Mark score dropped from 8,600 to 8,300 though. Windows 10 is better for gaming it seems.

 

Glad it's working now.

Windows 10 does do some things better that W7 or W8.1 and it all depends on the game or the benchmark. In my extensive testing it did a few things a tiny bit better and more things not as well as W7 or W8.1 did them, and nothing remarkably better. Exhaustive testing results are provided in this post. It's really terribly unfortunate that the product launch was so poorly executed, and with some truly disastrous (and very costly) results for some customers.

 

Figured I'd post an update in case anyone else is having issues...

I found a way to install drivers that fail without doing any weird BS. Just boot into safe mode and install them.