Nvidia 320.18 driver warning

And here we go again...
All was working just fine until I just booted up now: blank screen. Turned laptop off and on, and all is working fine again.

------------------------------------------------------------------------------------------------------------------------------------------------------
Details from Event Viewer:

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
CMDre 00000001 00000080 00000000 00000005 0000000d
---------------------------------------------------------------------------------------------------------------------------------------------------------

I'm going back to 314.22. This is just playing Russian Roulette...

 

Yeah, although a couple of people seem to be fine on the 680/120hz the fact that a vbios mod is needed says it's a pretty critical change they made!

Basic advice to any 680m/120hz users is to wait it out on 314.22 - the few extra FPS are not worth the chase . And hassle dell, I know others have, and it's the only way to raise the priority with them. Seems that our friendly AW reps have taken a page out of NV's book (in the last two weeks at least), unless you have good news say nothing

 

I know some people don't like it but I use ccleaner every now and then, after new installs, software updates or uninstalls, and make a backup of registry as a precaution.

 

I also have always done this but with such good drivers in recent times I got used to just upgrading. No more putting back my global settings every time I update the driver (or have to go through the 3D wizard).

Back to the bad old days it seems.....

 

I think 320.18 killed my 580m. I tried every fix and today I clean re-installed Windows 7. I've tried older drivers and new 320.49 but to no avail. My laptop still randomly crashes. I've never did OC but my VDDC is stuck at .92v. Is my 580m permanantly damaged? How do I change the voltage back to stock configuration? MSI Afterburner and ASUS GPU tweak did not work.

 

That sounds like you're right as long as you have not changed the vbios? .0.92v has burned 580m's for overclockers. This is the first that I have seen that is always at that voltage without a vbios mod to deliberately select this voltage. The usual symptom is .92v at game start for 5-10 seconds and then occasionally after that on the 580m, and not at all after that on mine.

One thing you could try is a very old driver. from 3xx onwards the voltage boost started happening on pre-fermi cards so if you go back to the last pre version, 296.10 WHQL to see if the driver can be eliminated but it does sound like it's somehow got stuck and fried

 

Just another thought....you are using gpu-z to monitor, right? - I've known it to not read voltages correctly in the past. Maybe try HWiNFO64 or another program that will show you a different voltage reading. I seem to recall something similar with my 580m's and gpu-z....

 

Good info man. @desertburst: only have afterburner loaded and use the OSD part to set up on-screen voltage and clocks. You then get to see it in real-time while gaming

 

Yeah, i think gpu z tells you the voltage which has been set in the vbois for various p states
but not the actual voltage

maybe hwinfo or some other tool could help you out

 

I use hwinfo64 and nvidiainspector. It's still .92v. Maybe flashing it with different vbios will help?

 

That is weird. I'd still say check it in real time with only afterburner just to rule out some hwinfo interaction. If you have never flashed the vbios then it makes no sense that a reflash will work but as long as you get the original (or use the one dell publish) it can't hurt to try

In nvidiainspector, what voltage does it show as P0 and P1 default setting voltage?

 

0.920V. 0.870V is maximum voltage in overclocking menu, but the monitor on left shows 0.920V.

 

Is this the P0 and P1 voltages (should be 0.87v and 0.80v). If you are seeing this high voltage in windows then the driver is unlikely; that .92v has to be coming from somewhere??

I'm still a bit confused, any chance you can post a screen shot (use snipping tool) like this:

 

Right, that shows that the vbios is at default so something else is causing that overvolt, unless the driver boost to .92v somehow burned the card to leave it permanently at that setting.

No hwinfo or any other monitoring loaded? You may have to disable the hwinfo service if you have it set to autoload.

That P1 voltage should be only 0.80v.

 

nvidia inspector was the only thing loaded at the time. Is there any way I can manually set voltage limit?

 

No that is why it always needs a modded vbios. Time to try the flash I think. The dell one I originally used took you through creating a bootable CD which flashed the vbios with.

Edit: hold on! What is schenker in the subvemdor? I've only ever seen dell or clevo in that field, looks like an aftermarket vbios...

 

Google says 1558 is a code for CLEVO/KAPOK. I have no idea what schenker is. sounds german. My 580m is a replacement for 485m which I originally had so maybe that's why.

 

Yup, I'd say that it came with a vbios mod to 0.92v. Flash the dell one ASAP and hope the damage was not permanent.

Driver Details | Dell UK

Listed by dell as 'urgent'.

Expand all the information fields below the driver link to see all the info you need

 

So this is where that card came from originally: mySN.co.uk | XMG | Schenker Technologies

Actually I'm liking the look of them and they are now on my list of options for my next purchase. Almost 1/2 the price of an SLi 18x and FULLY configurable. with AW no longer having the wow factor that I liked I've held off on spending my 'toy' money

 

I flashed my 580m with vbios you linked, then noticed that the vbios was already 70.24.2b.00.06. After flashing the voltage briefly returned to stock(.8/.8/.85/.87) then went back to .92V. what is this sorcery? and how did it flew across the pond and end up here?
My 580m worked fine over a year, so I am 100% sure 320.18 did something with it. Flashing vbios was much easier than I imagined so I will try few other vbios roms. If that doensn't fix it the 580m goes into the oven.

edit: the vendor name/code did not change.

 

It seems that the 320.49 is out. Please apologise as I was in the other part of the world. Coming to the point, is it worth it?
The last time I checked 320.18 was a complete wreck to my Alienware m17x w/680m. I am also waiting for the vBIOS update from Dell's site.
Is it okay to update to this driver?

 

All I can think of is that you have always had .92v but the latest driver (which has crippled others) pushed it too far, bang, screwed card! As for how it got there ebay is the usual culprit for the 'grey' market.

I would just try as a last resort a pre3xx driver but don't hold out much hope: NVIDIA DRIVERS 296.10WHQL

The oven may fix it but only after you get the voltage down...

 

That's possible. I got my wisdom tooth pulled out today so I am still under influence of painkillers and my head is still fuzzy..I can't remember if they had .92 from the beggining. I'll give 296.10 a shot.

 

I don't think it's worth it - too much work for so little return. There seem to be very few claims of burned cards with this driver (the previous one did a good job of that) but there are a lot of reports of graphical issues in games. Wait it out a little longer, a good one HAS to come along soon along with the vbios update you need.

 

So it seems, AMD must be having a hell of laugh somewhere! I'm gonna stick with the 314.22 version. So far so good for me. Thanks!

 

Installed 296.10 driver and this situation got a bit more interesting. hwinfo and gpu-z shows the votage is back to normal(0.87V), but nvidia inspector still shows 0.92V when P0&P1. I wonder which value is correct...
Unfortunately the random crash problem did not go away. I think the damage is permanent. It seems that 3D/120hz variants of alienware and clevo got hit the hardest. Thanks NVIDIA!

 

I.m wondering if the vbios flash you did to dell original actually worked? You said the vendor ID did not change and I would expect to see dell in that field same as mine. When it asked something about a mismatched ID and do you want to continue you pressed Y to continue?

 

Getting all sorts of problems with 320.49 on my desktop rig. Upgraded from 324.22, which worked great. Crysis 3 can't run for more than a few minutes without crashing. My overclocks tested very stable with OCCT and Furmark previously, haven't tried either since I've updated the drivers. Will have to check that in a bit.

 

Yes I did press Y. So far I've tried a few different vbios including dell, clevo, and msi but none of them fixed the issue.

 

It does sound like the card is bad now

 

326.10 beta has just been released. In tests I have not seen a voltage boost at ALL! Looks like NV have fixed the non-existent overvolt.

Quick BMAC benchmark:

stock clock no change (45fps)

700mhz overclock +3fps(53fps)

At least they didn't seem to cripple it to lower the stress

 

Anyone already tested this driver version on a 680M with 120Hz screen? Though I doubt the blank/black screen bug will be fixed with this one.
By the way, still no new vbios version available. I do hope it will come soon, otherwise we seem to be "stuck" with an old driver.

 

I have the old vbios in my 680m I doubt they will release a new one anytime soon, there are 680m with the newer vbios (UEFI compatible) released before, I saw them on techinferno if your desperate for them.

The latest driver with my 680m seem fine, but I havent had a chance to stress it yet.

 

I was referring to the new vbios update NVIDIA mentioned, I allready have the newest (UEFI compatible) one, as found on techinferno.

From a NVIDIA thread: "This is a VBIOS issue. We fixed it in VBIOS but will require an update from Alienware. It was just fixed and verified a couple of days ago."

Will try to test this new driver this weekend as well.

 

yeah, the 326.19 is working just fine
no blank screen

also fixed my 3d issues after flashing my stock rom and then flashing the non-OV, unlocked rom

 

After using this new 326.19 Beta driver I'm happy to report I haven't encountered any issues yet. No black/blank screen during boot-up, even after a few days. Makes you wonder if that vbios update NVIDIA mentioned, wasn't just a placeholder...

 

happy to hear that everything worked out fine now!
probably just nvidia was doing the blame game and wanted some more time

 

I just had to roll back . The latest beta started to crash the whole machine. Screen goes blank, fans step up a notch and nothing responds except a hard reset. It even happened on a restart as soon as the driver loaded in windows so had to use safe mode. Very annoying, I was seeing much lower temps with the latest one and I'd tested it with most of my games.

Why this suddenly started happening when in firefox and clicking a link is weird!

 

DIsabled hardware acceleration? Tried chrome or IE? Or opera even?

 

Yeah on the acceleration. I've had to do that one on every release after 314.22.

It is random but once it starts it happens every few minutes and then can't get into windows. Weird thing is I rolled back one release (can't remember the .V) and it happened again and I'd been using that driver without issue for a while and never saw anything like this.

I didn't want to mess with other browsers since I seem to have a working driver version right now - fingers crossed

 

Your version is soo old though haha... it'll be fine I hope. Tbh I have issues when I plug something into the display port and run chrome, it will display only black until I restart chrome, I guess since everything is prompted to run on the dGPU when through the displayport, but its not the end of the world for me anyways.

Good luck for whenever the next driver vesion comes, the 3D screen better be worth it!

I've had no major issues with the latest release, havent done any heavy gaming or benchmarks though yet.

 

Thanks, If I didn't like it so much I'd have already got an AMD card. If I wanted all these problems then I might as well give them another try but I'm not loosing the 3D while it still works so well

The Nvidia thread on the latest beta, 326.19 is still getting a lot of bad reports and the thread has descended into a troll circus with threats of violence due to it all being a 'Zionist plot'! The moderator clearly does not understand his job....

 

I read here that the new Beta was working fine , so i decided to be brave this morning and updated. It din't go well the machine started to crash, screens went blank. did a restart had the same problems.

rolled back to 314, have not seen the problems resurface.

 

Today a new Beta driver was released by NVIDIA, version 326.41. Still testing it, but so far working without any problems.

 

You having any issues with the screen waking up from sleep? I had a ton with 326.19.

 

All the known problems everybody was talking about went away when I went to version 326.19 (at least on my laptop). Everything is working as it should work.
Makes you really wonder what the difference on our machines really is. It just does not make sense the same driver behaves different on the same laptops, or almost the same...

 

You're right, it does not make sense, except that all the 3xx series drivers have been messing with overvolting, even on cards that should not get 'boost'. That in conjunction with the drivers pushing the hardware harder with each release has ended up with the hardware starting to fail (any driver post 314.22) so it is sporadic in what it causes and on what config of machine.

Technically the 680m and 780m (not sure about the cards in-between, some are not keppler but just rebadges of earlier cards) should not be having this problem but NV seem to have introduced a lot more problems that may be related as they have tried to build the 'killer' driver. The only thing being killed up to the last WHQL is the cards themselves

Bump, see initial post

 

Micky this thread makes life so easy for me ! thank you

 

Bump, update in opening post