GeForce 320.18 WHQL Driver Download

Cyberdyne

2013-05-23 15:32

Yeah, 320 betas gave me bsod's. I don't think any other driver has ever done that to me. I think I'll sit this one out and watch.

#4602482

Xploder

2013-05-23 15:40

10 minutes in I got my first freeze/full system lockup, just like with 320.14 which froze up 3 times during Metro, surfing the web and idling on the desktop. Back to 314.22 (again)

#4602483

BillieGDJoe

2013-05-23 15:40

Yeah, 320 betas gave me bsod's. I don't think any other driver has ever done that to me. I think I'll sit this one out and watch.

Same here. Hoping for the best!

#4602489

rewt

2013-05-23 15:42

I was getting some strange hang ups with the first two 320 betas I tried, but nothing since. What bugcheck code do you guys get with BSOD?

#4602503

Cyberdyne

2013-05-23 15:46

I forget rewt, one mentioned a driver specifically trying to access a memory space in use or something like that. The other I didn't bother looking up, chalked it up to the same issue since i reverted drivers and no bsods.

#4602507

Xploder

2013-05-23 15:50

I was getting some strange hang ups with the first two 320 betas I tried, but nothing since. What bugcheck code do you guys get with BSOD?

For me there was never a BSOD, just a complete lockup. After a reboot there's usually a nvlddmkm error in the event log (event 14?). Windows seems to unsuccessfully try to reset the driver and the fan spins up to 100% when I wait like 30secs.

#4602509

rewt

2013-05-23 15:51

Okay thanks. If you're interesting in finding the actual bugcheck code/message, you could probably inspect your Windows minidumps if they exist. I just remembered that I converted my USB mouse over to serial trying to avoid that system hang. I wonder if this is why I no longer have a problem.. lol

#4602543

PhazeDelta1

2013-05-23 16:16

So far everything seems to be working fine on W8 Pro 64 bit. If anyone is interested: (branch: r319_00-151)

#4602554

Sergio

2013-05-23 16:21

I forget rewt, one mentioned a driver specifically trying to access a memory space in use or something like that. The other I didn't bother looking up, chalked it up to the same issue since i reverted drivers and no bsods.

i had same problem with 320 drivers, and fixed those BSODs by raising system RAM voltage +0.1v . So seems like this driver sets stressing systems more than previous drivers. For my system i was getting this BSOD always with 320 series , 0x00000109 = Not enough or too Much memory voltage

#4602560

Keesberenburg

2013-05-23 16:25

Wow, good sli scaling in metro last light. http://i41.tinypic.com/309r7lf.png

#4602561

DiceAir

2013-05-23 16:26

anyone that can post some benchmarks. I'm currently at work so can't check.

#4602563

Ancymon

2013-05-23 16:26

World of Tanks still crashing in tech tree: Crashing in the Tech Tree when mousing over tanks/modules (Nvidia users)

#4602573

DiceAir

2013-05-23 16:31

I see in the detailed change log they fixed the 999MHz limit overclock on fermi cards. Good to hear cause I have a GTX 550ti that I want to overclock on a oldish system for my friends to play when they come over.

#4602575

dsbig

2013-05-23 16:32

well I see the the last windows update the updating drivers process now as shorter delays with the black screens in windows 8. edit: what the f**k is this sh*t. I hit clean install and let it install everything. I didnt know it would install the geforce experience app....bleh... no thankyou. rather use my experience. app go bye bye

#4602581

rewt

2013-05-23 16:43

i had same problem with 320 drivers, and fixed those BSODs by raising system RAM voltage +0.1v . 0x00000109 = Not enough or too Much memory voltage

According to Microsoft, bug check 0x109 is CRITICAL_STRUCTURE_CORRUPTION Your solution sounds reasonable, cause number three states: "3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed." http://msdn.microsoft.com/en-us/library/windows/hardware/ff557228%28v=vs.85%29.aspx

#4602588

BenchAndGames

2013-05-23 16:51

Here is performance of SLI GTX 680 with the new 320.18 + PhysX 9.13.0325 !! Everything maxxed out !! ( 1080p + Tesselation Very High + SSAA ON + Physx ON ) http://img43.imageshack.us/img43/3523/sinttulohoj.png

#4602593

alanm

2013-05-23 16:58

Release notes are useless, they are for 320 series vs 314.22. Nvidia has a habit of repeating same release notes vs older series drivers. What are the differences vs 320.14?

#4602596

Xploder

2013-05-23 17:01

i had same problem with 320 drivers, and fixed those BSODs by raising system RAM voltage +0.1v . So seems like this driver sets stressing systems more than previous drivers. For my system i was getting this BSOD always with 320 series , 0x00000109 = Not enough or too Much memory voltage

Yeah... I surely won't overvoltage my otherwise stable RAM just because a new driver f*cks up. Besides - I don't think that's the true culprit here.

#4602601

rewt

2013-05-23 17:05

What are the differences vs 320.14?

I saw two new changes mentioned in the release notes. In reality there may be more than that, since NVIDIA doesn't typically list everything they do. [Fermi-class GPUs]: The maximum GPU clock is limited to 999MHz when overclocked. [1282233] [X-Plane 10]: The game hangs while loading. [1279387]

I don't think that's the true culprit here.

It might be, if you got the same bug check code. Otherwise you're probably right.

#4602614

ESC

2013-05-23 17:15

downloading hope i dont get those BSOD.