GeForce 304.48 Beta Driver

Had weird problem last night... BF3 exited (I was forced to kill it) to the desktop. The BF3 icon was still running, however if I clicked on the BF3 icon nothing was happening (I was actually losing mouse cursor). I checked AB log and it looks like the power % spiked to 388...hmmm... i checked event viewer and I've only notice 1 warning (display driver restart)... no critical or error events... I will try BF3 tonight at stock speeds... Not sure what it is... I'm using adaptive vsync on... Problem is I played for 10-20 hours last week without any issues... After the crash I did change nvidia power management to performance. Perhaps I should lower power in AB from 122% to 117% or something... I don't think it is PSU... fun fun fun... ;)

I had this problem when I initially installed the Windforce. I wasn't sure if the problem was with my CPU O/C or the GPU O/C. I've since modified both and that problem never came back again. I haven't tried the new beta drivers yet, as I don't have any issues with my current driver.
 
For some reason I'm getting slight micro stutter with BF3 with these drivers...Anyone the same??
 
I had this problem when I initially installed the Windforce. I wasn't sure if the problem was with my CPU O/C or the GPU O/C. I've since modified both and that problem never came back again. I haven't tried the new beta drivers yet, as I don't have any issues with my current driver.

Thanks for your feedback... I ran heaven for few hours and it crashed, so it looks like unstable GPU clocks... I lowered core by 5Mhz, and I will re-run heaven before going to bed. Unless I will lower core by another 5Mhz if it crash again playing BF3 tonight...
 
For some reason I'm getting slight micro stutter with BF3 with these drivers...Anyone the same??

I'm experiencing the same thing. I checked my GPU usage in MSI Afterburner and it wasn't staying ~99%, instead hovered between 95-98% every few seconds and had several points where it dropped near 25%.

Going to back to 301.42 and see if this solves the issue.

Edit: I think the issue is the server lag. Hopefully that'll fix the micro-stuttering that we're feeling.
 
Last edited:
Yep, it's a server lag issue. Don't start freaking out and troubleshooting it... liek I almost did, rofl. Thankfully I was playing with a friend over Skype and he noticed it too, because I was about to start messing with drivers etc.
 
Yep, it's a server lag issue. Don't start freaking out and troubleshooting it... liek I almost did, rofl. Thankfully I was playing with a friend over Skype and he noticed it too, because I was about to start messing with drivers etc.

This freaked me out because I just got my new 680 lightning and I was thinking I had a bum card. So glad thats not the case.
 
Yep, it's a server lag issue. Don't start freaking out and troubleshooting it... liek I almost did, rofl. Thankfully I was playing with a friend over Skype and he noticed it too, because I was about to start messing with drivers etc.

+1,
I played on 2 different servers and it was bad last night and everybody was complaining about it...

What gives? EA/Origin servers? I hope they can fix this...

BTW... I did lower my core by 5Mhz and after 3hrs of gameplay, there were no crashes to report.
 
+1,
I played on 2 different servers and it was bad last night and everybody was complaining about it...

What gives? EA/Origin servers? I hope they can fix this...

BTW... I did lower my core by 5Mhz and after 3hrs of gameplay, there were no crashes to report.

Hah, had the same issue myself playing on the new NCIX Metro server (helping admins test it). I thought it might have been because I had a 9 day uptime without reboot but that wasn't it. Weird because I ping 10-15ms to the server, so it must be an infrastructure problem (maybe stats reporting polling or something).

Didn't get a chance to play last night, still lag issues?
 
Hah, had the same issue myself playing on the new NCIX Metro server (helping admins test it). I thought it might have been because I had a 9 day uptime without reboot but that wasn't it. Weird because I ping 10-15ms to the server, so it must be an infrastructure problem (maybe stats reporting polling or something).

Didn't get a chance to play last night, still lag issues?

These drivers suck for bf3. I used them before the PB issues and they did this. Roll back and wait on the next set.
 
These drivers have been working great for me, save for one minor issue in D3: Whenever I zone from one area to the next, the game visuals freeze, but the game itself continues to run just fine. A quick alt-tab fixes it, but both my mini comp with a 690 and my big comp with tri-sli 580s have this problem.
 
Been using these for awhile now and I can't say I've seen any issues with them yet.
 
only issue I've seen with this set is w/ DE:HR, breaks something in the menus so you have to fun the game in full-screen windowed mode. this isn't an isolated incident as it's been reported by others.
 
only issue I've seen with this set is w/ DE:HR, breaks something in the menus so you have to fun the game in full-screen windowed mode. this isn't an isolated incident as it's been reported by others.
just change the max pre rendered frames to 3 and DE will work fine.
 
thanks for the share, worked great...

what the heck does that setting do anyways?

If you set it higher, you get more mouse input lag but smoother gameplay; if you set it lower, you get less mouse input lag but your game play may get more jittery.

In most cases, the default setting of 3 is a happy medium. Some game engines may not behave properly with an MPRF setting that is not 3, as you have discovered. Also, if you use Nvidia Inspector to set MPRF to 0, it will instead use the default application setting of 3:

http://forums.laptopvideo2go.com/topic/29333-max-pre-rendered-frames-benchmarks/
 
If you set it higher, you get more mouse input lag but smoother gameplay; if you set it lower, you get less mouse input lag but your game play may get more jittery.

In most cases, the default setting of 3 is a happy medium. Some game engines may not behave properly with an MPRF setting that is not 3, as you have discovered. Also, if you use Nvidia Inspector to set MPRF to 0, it will instead use the default application setting of 3:

http://forums.laptopvideo2go.com/topic/29333-max-pre-rendered-frames-benchmarks/
the default setting for the last year or so has been "application controlled". this is only the second game ever where I had to mess with that setting in the cp. the previous game was Bioshock which required the setting to placed on "0" for several driver revisions or it would hitch badly. but yeah the "0" setting is gone and default is no longer "3".
 
This freaked me out because I just got my new 680 lightning and I was thinking I had a bum card. So glad thats not the case.

Yeah, slight microstutter with vsync off is happening with 304.48, a lot of people at the nvidia forums are reporting it (ie the nvidia(dot)com forum). Reverting to 301.48 removes the MS.
 
Last edited:
Yeah, I rolled back due to a few other issues. Sadly, its going to be another month before we see another driver update. I'm totally unimpressed with Kepler drivers.
 
Yeah, I rolled back due to a few other issues. Sadly, its going to be another month before we see another driver update. I'm totally unimpressed with Kepler drivers.
yeah same here and its one of the reasons I sent my 670 back for a full refund.
 
Back
Top