GeForce 326.29 BETA Driver Download

-Tj-

2013-07-22 23:49

Thanks i just checked guru3d news about openGL 4.4, baam 326.29 driver! 😀

for issue 1328621 - Win7x64, GK104: Black edges in Battlefield 3 when SLI and MSAA 4x is enabled Latest version of "nvidia inspector" has a fix implemented: "-added FERMI_SETREDUCECOLORTHRESHOLDSENABLE as "Antialiasing fix" to avoid black edges in some games while using MSAA (R320.14+)"

It doesnt work (only dx9), also it happens on GF110 chip and no SLI.

#4624528

-Tj-

2013-07-23 00:00

Speaking of RememberMe, its ok here. Im at normal geforce 326.19 atm and it started fine, im still at the beginning though, somewhere in sewers. But the only thing that's BAD is this U3E streaming micro loading stutter by new scenes, same like Bioshock Infinite. I mean common how messed up is this U3E streaming system?? or driver streaming code cant handle it. :S

#4624534

Bhudda

2013-07-23 00:11

for issue 1328621 - Win7x64, GK104: Black edges in Battlefield 3 when SLI and MSAA 4x is enabled Latest version of "nvidia inspector" has a fix implemented: "-added FERMI_SETREDUCECOLORTHRESHOLDSENABLE as "Antialiasing fix" to avoid black edges in some games while using MSAA (R320.14+)"

that fix doesn't work, people already reported it in the nv inspector thread.

#4624536

Bhudda

2013-07-23 00:17

the weird temp readouts people are having do you use precision x? because I had the same and false 2d speeds. When I installed msi ab instead all was okay.

#4624539

Bhudda

2013-07-23 00:18

it works for many games jsut not battlefield. :wanker:

I wish nvidia would fix it, it's gone on for long enough. :bang:

#4624546

SSJBillClinton

2013-07-23 00:29

Speaking of RememberMe, its ok here. Im at normal geforce 326.19 atm and it started fine, im still at the beginning though, somewhere in sewers.

That's really odd! It crashes just after the Capcom splash screen here, about 5 secs after launching the game. Maybe it's a 600-700 series problem?

#4624574

DJ_Casper

2013-07-23 01:15

Remember Me is the name of the game, just fyi Casper.

Man don't need to learn me. Not the first time in Gaming world TY!

#4624579

DJ_Casper

2013-07-23 01:21

I havent seen you post any, so please stop spamming here...

Na hui poslan olen' >>>

#4624583

Cyberdyne

2013-07-23 01:25

Then I guess if you knew that he was talking about a game, you're just digging your hole deeper, eh? Have fun with that.

#4624585

GeniusPr0

2013-07-23 01:26

Haven't had issues with any of the drivers. I'll try these out I guess.

#4624602

GhostXL

2013-07-23 02:04

Does it use the Unreal Engine 3 because Deadlight, which is UE3, crashes with the 326.19 drivers?

I played TERA Rising, UE3 Black, Dishonored, and a host of other UE3 engine games, but Deadlight is the only one that crashes. It happens only on 326.xx drivers. Deadlight crashes only when I transition into a new area, any new area from any point in the game. Files are fine as I verified them on steam. I have no issues with Borderlands 2 as others seem to be mentioning problems.

#4624621

Cyberdyne

2013-07-23 02:40

system.exe ram problemmmmmmmm nvidia :S

You keep posting about this, but it doesn't make any sense. For one, there is no such thing as system.exe, from the taskmanager it's just called system. It's not an executable. It's where the windows kernel lives. No one else reports having this problem, if you ask me it sounds like a virus. And yes, it is possible that the problem goes away when you install an older driver, obviously your system is unstable in the first place. Do a clean install of windows (don't install whatever you think you need), I bet you the problem goes away.

#4624662

MrBonk

2013-07-23 07:24

This driver seems not to crash and freeze the System with 460 cards. Testing please

I would also confirm this but I have not gotten my 460 back from Nvidia yet.

#4624706

Darren Hodgson

2013-07-23 09:19

Deadlight still crashes to the desktop on resuming a savegame with these drivers so other than having OpenGL 4.4, which no game currently uses anyway, these do not seem any better or any worse than the previous 326.19 drivers I was using. There doesn't seem to be any obvious improvements, additions or fixes that I can see. To all intents and purposes these appear to be the 326.19 drivers with OpenGL 4.3 replaced by OpenGL 4.4 and nothing else.

#4624800

LesserHellspawn

2013-07-23 13:39

While not being listed in the list of supported cards, this driver runs with my two 660ti just fine.

#4624803

Darren Hodgson

2013-07-23 13:48

That's really odd! It crashes just after the Capcom splash screen here, about 5 secs after launching the game. Maybe it's a 600-700 series problem?

Check the event log to see what the error is. If it's a problem with Kernelbase.dll then a revalidate usually fixes that as I found out with Aliens: Colonial Marines this morning when I had the same crash upon resuming my save game. After revalidating the game I was able to continue the campaign without any problems, although it is a rather joyless experience, I must say! If it's a Ntdll.dll crash then it is probably the same issue as Deadlight (also an Unreal Engine 3 title) and will require a fix from NVIDIA. Alternatively, you could go back to the 320.49 drivers, which is what I may do if I have any more games other than Deadlight crashing with these drivers.

#4624804

alanm

2013-07-23 13:49

eh...I asked only because the last few since 320.18 gave me nothing but problems, black screens, games crashing, desktop hanging, weird temperatures etc. I dont want to risk any problems again, yet I would love to update my drivers since, Sniper Elite V2 crashes every once in a while with 314.22... That's why I asked for opinions and experience first.

With drivers, anyones opinions on them are useless. I've had solid experiences with all 320.xx drivers incl 320.18 while I know others had a miserable time with them. Everyones hardware, software configs are different and may give different results. So you can only test yourself and see.

#4624807

Darren Hodgson

2013-07-23 13:52

I played TERA Rising, UE3 Black, Dishonored, and a host of other UE3 engine games, but Deadlight is the only one that crashes. It happens only on 326.xx drivers. Deadlight crashes only when I transition into a new area, any new area from any point in the game. Files are fine as I verified them on steam. I have no issues with Borderlands 2 as others seem to be mentioning problems.

The Deadlight issue may be to do with a specific version of Unreal Engine 3 or even PhysX. I downloaded and tried Chivalry: Medieval Warfare last night with these drivers and it also ran fine despite being a UE3 title. Aliens: Colonial Marines, also UE3, works fine as well, although I did have to revalidate the game cache.

#4624809

SSJBillClinton

2013-07-23 13:58

Check the event log to see what the error is. If it's a problem with Kernelbase.dll then a revalidate usually fixes that as I found out with Aliens: Colonial Marines this morning when I had the same crash upon resuming my save game. After revalidating the game I was able to continue the campaign without any problems, although it is a rather joyless experience, I must say! If it's a Ntdll.dll crash then it is probably the same issue as Deadlight (also an Unreal Engine 3 title) and will require a fix from NVIDIA. Alternatively, you could go back to the 320.49 drivers, which is what I may do if I have any more games other than Deadlight crashing with these drivers.

Yeah, it's Ntdll.dll.

Faulting application name: RememberMe.exe, version: 1.0.2056.0, time stamp: 0x5193979d Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: Faulting module path: C:\Windows\SysWOW64\ntdll.dll

I honestly didn't mind what I played of that game too much, it looked nice and had an interesting setting. Unfortunately it was the actual game part that brought it down...

#4624822

Darren Hodgson

2013-07-23 14:15

@ SSJBillClinton - Deadlight works fine with the 320.49 drivers apparently so I suspect they may work for Remember Me too. Whatever is causing the Ntdll.dll crash is very probably the same one for both games, seeing as they both use Unreal Engine 3. It may be a specific build or the version of PhysX they use, which might explain why other UE3 games run fine, e.g. Chivalry: Medieval Warfare and Aliens: Colonial Marines. I would report the issue directly to NVIDIA and then revert back to the 320.49 drivers. I think I'm going to do that tonight and wait for more mature r325 drivers, though knowing NVIDIA they'll jump to a new driver branch and a fresh set of problems by that point!!! There only seems to be minor improvements and fixes between the r319 and r325 branches anyway so I don't think I'd lose much going back to the older driver and I'll likely gain stability with more games.