i just downloaded the nvidia 280.26 drivers and i raised my overclocking to 825 and guess what, it overclocked perfectly and it is verystable runnning furmark without a problembefore i couldnt overclock more than 814 but now i can till 825
....
just wanted to share my experiance ....
-
Was just about to post this
I updated my Drivers page with the link
-
is this the beta one or the full fledged version?
-
its the latest WQHL drivers
-
sweet.. ima get this when i get home
-
Kingpinzero ROUND ONE,FIGHT! You Win!
Nothing to report here, my benchmarks actually lost some points, but so far the same happened to everyone over guru3d as well.
Still I'm not able to stay stable above 814/1628/1600, at least in benchmarks.
Didn't gamed on them yet so I didnt tested anything. -
-
Gonna download this after i go home
-
its terrific! I am able to push my card to 825-1650-1600 without any problem! Been playing an hour or two of TF2 without any hiccup
-
Kingpinzero ROUND ONE,FIGHT! You Win!
Oh well that sucks, im not able to push my card further. I wonder if others g53sw users can experience the same issue; first gen g53 are another thing really.
-
Are you using MSI or Inspector? Why not try 823/1646 shader and just start at 1500 memory. This will still have same FPS outcome as 800-815 core (with locked shader). Once you reach 1560 memory (still at 823/1646 shader) you'll get 1 FPS extra as using The Witcher 2 as guide.
With the Inspector you'll see how the core reacts once the loaded values are applied. It overshoots at 820 core, and does 823. So it's only between 815 and 823 which is the logical choice.
I noticed some sort of break-in period with my 460M card. It needs some getting used to, like playing your games at lower OC settings then working your way up.
At 823/1646 shader and 1560 memory, the FPS count is the same as with 1700 memory. To get to the next extra FPS, the core has to be at 839 with locked shader and 1697 memory, ..this is hard to achieve at this point.
So FPS-wise 823/1646/ 1560 memory is the lowest OC with the same FPS outcome as those 825/1650/1600 (1640).
Some lesser graphic options could still cut .5 to 2 FPS, and having the slight core and memory added helps stabilize the FPS count. -
Kingpinzero ROUND ONE,FIGHT! You Win!
At this point is just the VRMs or the gpu itself which cant reach some clock speeds.
As an example i can go up to 820/1640 but having the ram at default. As long as i go above 1300 over ram, gpu downclocks and the driver crashes. I need to reboot to gain again p2 clocks.
Ive tried anything i could do, anything above 820 while having memory above 1500 is instant crash. -
I'm not trying to offend you, ..
I was just saying that you cannot use values like 816-822 core clock, because in the Inspector when the values are applied you will see that it will overshoot the clock in mhz to 823 core and 1643 shader as max values even from 816 core and 1633 shader.
Basically you can only use 815 or 823/824/825.. You could always still use lower memory like 1400+ and break-in from there, but the inspector shows the values when the apply button is pressed. Goodluck with the OC'ing. -
Kingpinzero ROUND ONE,FIGHT! You Win!
As i said i appreciate the input and the insights, im using both inspector and afterburner tbh.
So far i didnt focused so much on it, maybe ill try something else, but im pretty sure i tried every possible combo. -
i got odd 390 more 3dmark 06 with these, did not test if i can oc more yet
-
Just got a 3dmark11 score of 2546 with settings 905/1810/1401. temp seemed to average in the mid 40's with a high of 57 degrees C. This is with the 560m on a g74. I'm thinking of running withcher 2 on these settings, do you think that would be safe?
i'm concerned about pushing it more as I was having issues with the driver stopping on me, some kinda kernel error. any suggestions? -
ok i recently decided to push the memory from 1600 to 1625 with the core/shader clocks are on 825-1650 but after a while i got ''driver has recovered from .......'' thing so i guess when i pushed the memory to 1625 it caused the driver to crash but when i used it on 1600 it didnt crash
-
Kingpinzero ROUND ONE,FIGHT! You Win!
I thought you'd be interested in my last findings.
Basically I'm able to complete a 3dmark06 run at 823/1450 but not 3dmark11.
Now if I do my math correctly the fps is the same so the score, which is unchanged (15,925) compared to 814/1628/1600.
Also temps stays the same. Anything higher (825,826) crashes and downclock, unless I lower the VRAM speed to 1400.
So I think that the real culprit here is the VRAM clock in conjunction with core and shaders.
Now I can think of a better psu, maybe 180w would help, but also it doesn't mean anything as my p2 state pushes the voltage to 0,912v and it's not editable in nibitor. -
I've fiddled with the OC again. I was able to reach a very stable gaming clocks of 827 / 1654 shader/ 1716 memory. Boy I totally abused my laptop when testing it with TW2, Metro 2033 and Fallout 3. I did all sorts of boss fights, jerking the mouse very quick trying for the game to crash or freeze. One game after another..
I did all 3 bench with it. Vantage improved a bit, but I don't really rely on these anymore. All I care about is highest FPS at 1080p in an acceptable eye candy level. Anyways, Vantage was 10,188, Mark11 is 2393, and a low Mark06 of 16,146 (I was expecting 16,360).
These benchmark scores doesn't reflect the real FPS on games.. Anyways 1400+ worked.. I do believe these cards just needs a little encouragement. Maybe a better, stable power supply.. ok. -
Would this 280.26 driver update be good for someone who isnt looking to overclock the gpu but rather just leave it alone. Or is it going to drop performance.
-
its somewhat more optimized for recent games...
-
So for older games like Assassins Creed or world of warcraft it will perform poorly?
-
Should play those games just fine.
-
well for me a have a rule, any newer drivers are better ( i know it is not necesserly), but i think the newer drivers have the same things that the old driver had but with either new features or improvments, nothing bad could be added to new drivers unless there is a bug which rarly happen especially in official drivers, but in the beta you could find some
-
3dmark11 / reset to performance level " 1280*720 " I got 2438 max with 280.26, there is another thing now I m using physx9.11.0621 it is more stable but in some benchmark fps drops, game run perfect.
I m still testing and I couldt decide yet which I have to continue 275.33 or 280.26. -
Hey guys, I've been trying to figure out how to install the latest nvidia driver on my asus g53sw. I basically get a pop up that says my card is not supported. How do you get it to install? Thanks in advance.
-
G73/74/53 Series Driver and Application Reference -
I like the 280.26 for it added 1 FPS on The Witcher 2 on a higher graphical setting. If in lower graphical set it might be at 1.5 FPS. It might even be 2-3 FPS on older games like DX9. Though I haven't dealt with that thoroughly..
I've had my OC'ed at 828/1657 shader/ 1728 memory since yesterday and it's totaly stable with Metro 2033 and The Witcher 2 with 76*C max GPU temp. I usually do boss fights to test the OC and do benchmarks just to test for stability. As for bench, the gaming OC did 10202 on Vantage, 2399 Mark11 and 16250 Mark 06. I've used 828/1657/1753 also which could run all benchmarks, and did 16325 Mark 06 and was stable with TW2. But right now I'll stay with the stable, cool temp OC of 828/1657/1728 mem.
Every new driver just makes fps better.. I have no voltage mods and I only use those free benchmark software (vant, mark11, mark 06). Lastly, I only play games and test OC at 1080p nothing less and don't need external monitor, ..DX11 (for Metro 2033). -
Nvidia 280.26 drivers are AWESOME !
Discussion in 'ASUS Gaming Notebook Forum' started by eXpert, Aug 10, 2011.