New Nvidia Driver - 344.60 - Poss bug/issue

[Dancamvet]

Hey guys,

Just a heads up on these drivers. I have a gaming laptop with a GeForce GTX 765M and when trying to install these drivers twice it has failed and caused the system to stop recognising my Nvidia graphics card. Fortunately my system runs the onboard motherboard graphics when not in heavy contact so i've been able to sort it just doing a system restore.

They're only a "booster" for CoD: Advanced Warfare and I've read that they're not all that good. If you've managed to get em working, mucho gusto. If not I'd make sure you have a system restore point before you have a go and be aware of that this bug is out there.

Dan

[N5XTR]

I haven't had any issues with 344.60 on my GTX-660.
Release Notes for it says it is specifically an update for CoD.

The new GeForce Game Ready driver, release 344.60 WHQL, includes improvements which allows GeForce owners to continue to have the ultimate gaming platform. In addition, this Game Ready WHQL driver ensures you'll have the best possible gaming experience for Call of Duty: Advanced Warfare

[Dancamvet]

I haven't had any issues with 344.60 on my GTX-660.
Release Notes for it says it is specifically an update for CoD.

The new GeForce Game Ready driver, release 344.60 WHQL, includes improvements which allows GeForce owners to continue to have the ultimate gaming platform. In addition, this Game Ready WHQL driver ensures you'll have the best possible gaming experience for Call of Duty: Advanced Warfare

Yeah, I tried it again and got the same issue. It might be because of the dual setup of my laptop with the Nvidia card only coming active for heavier gaming activity. I've decided to do without.

[Kahn]

I updated to this release on my gtx760 and didn't have any issues. Everything seems to be running as normal for me.

I have the desktop version though.

[Merlin]

I have an internal Intel and dedicated nvidia 760 on my laptop and no issues so far. Will check today and make sure I'm actually running on the nvidia though in case it reset anything that it shouldn't have.

[Dancamvet]

Maybe i'm just lucky then. Only other thing i can think of is last couple of times i've been using Nvidia card to game just before running update. Might try it from a clean start so it's not in use.

[Dancamvet]

Welp - little update, I've tried most things apart from running a clean install from custom install (partly because my setup is working fine as is) and I still get the same driver install fail with 344.65 as well. Tried through GeForce experience, tried from down load exe., tried from update driver in device manager. All the same end result.

Basically the driver install fails early on and in device manager the nVidia displayer adapter disappears (likely due to the mess of the driver). Have had to do a couple of system restores to get things back on track.

There is a support page on install failure - Driver Installation Failure and I suppose I'd need to parse a failed install to know more but i'm not sure it's worth the hassle atm as everything is working fine on 344.48.

Any sage advice from the technically minded out there?

Dan

[Gabriel Lyons]

yup I haven't bothered to upgrade yet either

[Merlin]

I'll check today bit I thought I saw a newer driver out very shortly after that one. ccleaner does a really good registry cleaning, and can back up its changes.

Which OS version are you running. If 7 try safe mode to do an uninstall. And after the uninstall and reboot, delete the driver that Windows trieds to install until all you get is a basic vga adapter listed. Then reboot and try the install again.

[Dancamvet]

THREAD RESURRECTION!

An addendum to this, have managed to sort it with latest released version of Nvidia drivers.

Not sure whether this Windows 7 update issue was a factor but useful to know about.

In the end a clean install removing the previous software in safe mode did the job. The GeForce management software (GeForce Experience) was also updated, wonder whether this was a factor but I guess I'll never know exactly what was causing the issue.