GeForce 326.29 BETA Driver Download
Click here to post a comment for GeForce 326.29 BETA Driver Download on our message forum
m2896
With 326.29 GPU temp is 80 deg in BF3. It is too hot(noisy). With 314.22 BF3 temp was 75-76 and noise was acceptable. Else is good.
jogogold
DeadLight crashes on startup. Going back to 314.22 :bang:
jogogold
I just remembered that I can't install 314.22 on my 760!! any one got a modified inf??
m2896
DoW2 texture flickering not fixed.
ShadowDuke
Startup crash here, too.
m2896
I've returned on 314.22 and GPU temp droped from 80 to 77 (in the same conditions). Summer makes itself felt.
Darren Hodgson
I've just reverted back to the 320.49 drivers and can confirm that Deadlight now works fine so if you're having problems playing that game (or Remember Me as mentioned by SSJBillClinton) with the 326.19 or 326.29 drivers then that is your solution until NVIDIA release more mature drivers. I decided to go back to the older driver simply because if two Unreal Engine 3 games have issues then it is more than likely that there will be others. At the moment, there is no real need to use the 326.01 drivers anyway as I did not have issues (that I can recall, anyway) with the 320.49 drivers. NVIDIA usually break at least one game when they switch driver branches from past experience.
PurSpyk!!
Borderlands 2 also crashed with an ntdll.dll. Game also uses the Unreal engine, but other games that use the same engine, all the Bioshock games, Dishonoured and a few others have no issues. 302.49 have no issues at all with these games.
Darren Hodgson
@ PurSpyk!! - I own Borderlands 2 but have not played it in a while and thus never got to test it with the 326.29 drivers but I've no doubt I would have had the same Ntdll.dll crash as yourself. Clearly NVIDIA have broken something between the r319 and r325 driver branches and if I had to hazard a guess then I'd say it is connected with the PhysX libraries or the build of Unreal Engine 3 the games use otherwise you'd expect every UE3 game to have the same Ntdll.dll crash.
Personally, I would suggest reinstalling the 320.49 drivers until NVIDIA fix this issue (which is likely to be several weeks away at least). I reported the issue with Deadlight directly to NVIDIA a few days ago so hopefully they are looking into this but if anyone has Ntdll.dll crashes with UE3 games using these r325 drivers then please tell NVIDIA about it using *this* link, as the more people that do then the more likely it is to be flagged a high priority fix.
Spets
I just tried BL2 and it hasn't crashed for me, any certain areas?
Darren Hodgson
I can't answer that as I never played the game with the 326.xx drivers. Are you using hardware PhysX at all as the issue could be caused by that?
Spets
Yes, using hardware PhysX with 09.13.0604 + legacy. I ran around Thousand Cuts with a caustic smg as well as dragons lair. Not sure when they did it but Thousand Cuts isn't as bad as it used to be with dips, still get the drops in the area though.
SSJBillClinton
Had the infamous monitors not waking up from sleep today. Eugh.
Darren Hodgson
Do you have either Deadlight or Remember Me to test as both games have Ntdll.dll crashes for a number of people, the former for myself, and they both use UE3?
Spets
I can try Deadlight a little later on 🙂
Snorgrind
try changing ForceFakeVideocard=false from false to true in enbseries.ini
usualy fixes it 🙂
Spets
Seems to be working (click to enlarge):
http://i.imgur.com/Lsi4mifl.jpg
I'll play through it and see if anything happens.
fernake
From where come all these drivers, this is not the official website of Nvidia.
SaiBork
This one is actually from the nvidia website. It's a developer driver for the implementation of the new OpenGL version.
More details, see here
Darren Hodgson
Thanks for the confirmation.
It could a Kepler issue. It wouldn't be the first time as there was a bug that occurred on both the Titan and GTX 780 with the r319 drivers which caused Sniper Elite V2, Sniper Elite: NZA and Aliens vs. Predator (2010) to freeze when Advanced Shadows were enabled. That was fixed in one of the later 320.xx drivers as far as I've been able to confirm with my own testing (the 320.49 drivers seemed OK).
