Basically what this thread is about: I'm overclocking and performance is either staying the same or going down
I finally got the overclock window to show up in my nVidia Control panel.
Here's the issue. I overclock to 650/900/1600, but I end up getting a thousand less on 3DMark06.
Why is that?
EDIT: using Dox 180.44 (think that might be the culprit)
Edit2: Switched to XFastest latest and found no significant difference even though i was OCed up to 692/988/1813
Edit3: These are the benchmarks from page 2
![]()
Overclock of: 700/999/1800 (XFastest latest)
![]()
stock (Dox 180.44) shocker... (ran this a 2nd time and got 8635)
![]()
700/800/1800 (Dox 180.44)
-
-
ur power options set to performance? your 3D setting (forget which exactly, its at the top of advanced control in nvidia control panel) set to performance, NOT quality? you going off battery or you plugged in?
did you apply the setting and save them to a profile properly and load that profile? -
* Running "High Performance" on Vista 'battery icon'
* Not sure what 3D Setting you're talking about but under "Multi-display/mix-GPU Acceleration it says "Single display performance mode", under "Texture filtering - quality" it says "Quality".
* I'm running off plug
* I click "custom" then change my clocks and hit "save". To make sure it was taking I set it up to a high core clock and it froze up my machine so I think I can assume that it is taking the settings.
Not sure what's going on. I'm happy that the overclock window shows up (which I've had issues with before this reformat and version 6.03 of nTune) -
Also, Start CPUID's HWMonitor. see what your max temps are. -
I hit apply too and on the "view system information" tab it has the core/memory/shader that I set too..
-
make a profile setting. its the last option in the performance tab. DO NOT OVERCLOCK the way you are doing now. Make a overclocking profile and use that so it oveclocks only when you open a certain game.
Thats the way i overclock and it always works for me. -
Yeah change "quality" to "performance" where it has the spinning Nvidia logo...
-
Got it. Thanks. Going to give it another shot now.
edit: Gave it another shot, got only 100+ points from going to (690/925/1610) that seems a bit low for that much of an up from (600/799/1500)
I overclocked it more and it went back down another 100 points, that's quite odd. -
Hrmm, still nothing after overclocking several times and nVidia panel even says it is changing the clocks. ****.
-
I tried the latest XFastest drivers and didn't get more than 3% change. Even with overclocking. So I'm not sure what's going on.
What I'm doing.
nTune - change the clocks, hit "apply" I've had my clocks up to 725/900/1675 and only 3% change, no difference when I lower the clocks, if I higher them to high I do crash out of the app and the driver resets. -
Start the nvidia system monitor (It gets installed with ntune) and make sure you select the core, memory and shader clocks (after you start it a little green nvidia icon shows up in your taskbar. If you don't see the monitors you want, rightclick the icon and select "Select Monitors", then select the monitors you want. That way, you can see if your clocks really are what you want them to be. Also bring up CPUID's HWMonitor. Does TZS0 ever hit 98C?
What scores are you seeing in 3dMark06? Not just the overall score, but the individual SM2, SM3 and CPU scores. -
My temps are fine. I'll recheck my 3DMarks at different overclocks .
I also turned on the monitor and its picking up the right clocks, just doesn't seem to make a bloody difference. I know on my E1705 I was able to almost double my 3DMark. I was just hoping for 10-20% -
Overclock of: 700/999/1800 (XFastest latest)
stock (Dox 180.44) shocker... (ran this a 2nd time and got 8635)
700/800/1800 (Dox 180.44) -
it looks like you clocks just arent holding the OC. it took me a couple times of applying saving and loading for me to figure out how to get the clocks to stick. it think you just gotta tinker some more. have you been able to verify your clocks are actually OC'd with nvidia system monitor?
-
-
You are pushing the shaders too hard. Try 650/850/1550 first and see what that gets you. Start small and work your way up so you can see where the cutoff is for your gpu. Push all the clocks 25 or 50 Mhz at a time. Once things go backwards, back off by 25 or 50 and just try pushing the shader. In my experience pushing the memory clock past 900 buys you nothing. Pushing core gives you the most gain, but I can't get it much past 700 without TZS0 spiking. But I can push my shader clock farther than the other two clocks and see some small benefit when I do.
You don't try to qualify a Formula One car the very first time you get in it. You take it slow the first couple of laps and improve your times incrimentally. If you go all out on the first lap, you will crash. Same thing applies to overclocking. -
Alright that's good. I'll check it out.
-
Alright well here's what's up. I can run it two different times and get 500 points less. I ran at 700/850/1600 and got my highest 9010. Then ran a few others and came back to 700/850/1600 and got 8500.
I noticed that on the 2nd test it dropped way lower the 2nd time I ran the same settings. Which is really odd. not sure what's wrong. Anyone ever experience this? -
If you run HWMonitor, you may see TZS0 hit 98C. You might also try rebooting in between benchmark runs. I usually get the best score after a reboot and then letting all the background stuff settle down for a few minutes. I got 9326 at 700/900/1600.
-
I think something else is wrong, not sure. Cause I'll run the darn thing and sometimes it just slows way down. I think i realize it when I'm playing games too. it'll just kind of hickup and for a bit it'll go really slow.
-
yeah, it it is hitting 98c on TZS0, guess it's time to look into that.
-
storm, you running the 9c.08 BIOS? If so, and if you're not running RAID.. flash back to the 9c.05 BIOS. See if that fixes it. I had better luck with the .05 BIOS not tripping TZS0.
-
I am using RAID
Running 9C.12.00
Just tried RM Clock, it for some reason isn't actually lowering the voltage (according to CPU-Z at least)
RMClock reports it's working, I still spiked to 98, but I was able to run a test without it dropping to below 20 FPS (Firefly on 3DMark06 seems to wreck havok on my computer so I use it to test) -
Just run perf. on demand..
EDIT: Oh, or..just down your clocks a touch on the GPU. Hows the other temps looking? -
Everything is actually starting to make sense now. Been running "Orthos" it's a CPU primer, got it down to where it won't go past 44c on both cores. Then also TZS0 has kept quite and never going above 61c.
Also seems that my graphics hickups have gone on vacation. So we'll see.
So far good stuff. Glad I thought to check my TZS0 temps. thing was raining on my parade all along.
EDIT: played about 20 or so minutes of COD5 and it kicked up to 98c, but didn't notice to much loss of performance. Not as much as usual. Hrmm, wonder if I can completely stomp out this TZS0 issue. -
The short answer, no. Otherwise I would have a long time ago. Hence the BIOSes, etc. RMClock stops it. TZS0 still shows 98c with RMClock, but it doesnt allow for the downclocking of your CPU when RMClock is activated.
-
Yeah I think the undervolting really helps.
-
It is a life saver. RMClock interupts the Vista power management, therefore it won't allow the false 98c temp to trip Vista to downclock the CPU. So, you could run stock voltages and it still wouldn't trip. But, you may as well get some extra benefit and consume less power too
-
I'm getting 9050 - 690/980/1790
A few of my other scores
9008 - 700/975/1750
8975 - 689/875/1750
8879 - 675/900/1650 -
I hate to tell you this, it's the BIOS.
Give the .10 or .08 a try.. will quite possibly help having a different ACPI table. otherwise, your temps are beautiful! Run the .10 BIOS first and see if it helps.
-
Hey guys, while we're on the topic of temps, feel free to check out the nifty gadget in my thread here: http://forum.notebookreview.com/showthread.php?t=324705
-
Nifty lil thing you found there
-
While we are on the topic of RMClock (or were a few posts back), when I click on the "Use P-State Transitions" box in any profile, RMClock locks up. Anyone seen this? (Vista 64 with the "signed" .dll, P8400, P7811FX)
-
.10 still does RAID right?
-
-
what is the timing between your transitions? time up and time down? should be towards the bottom of your profiles screen, and if I recall default is like 50/200ms.
-
I just went to v10 of bios. Timing transitions? hrmm...
On RMClock's profile screen?
Been bleeding my computer both GPU and CPU and i'm at 86 on TZS0 -
so, no more tzs0 issues?
-
Yeah..I dont have rmclock installed..but towards the bottom of the profiles screen, there is an Up-transition and Down-transition in milliseconds(ms) - that may be whats giving fiz the problems.
-
-
-
Yeah I can. Things seem better. I'd say 9c.10 is better for sure. I'm going to do some more OC on my video card and see what happens
-
http://forum.notebookreview.com/showthread.php?t=311919
This was a single stock 7811FX run, on 3dmark with 9c.05.00 BIOS, GPU OCd only. No RAID installed though. CPU didnt downclock, and TZS0 didn't trip. So, jsut showing ya..this system is your system. You can get here, just gonna take some trial and error. Quadzilla, and I believe Jakamo both use the .10 BIOS if I remember correctly. And, neither have had issues with the TZS0 and they OCd their cards. See Jak's signature. This should help you a ton. Good luck, and if all else fails.. kick RAID and go .05
Overclocking 7811-fx
Discussion in 'Gateway and eMachines' started by stormlifter, Nov 18, 2008.