Dell 14z undervolting

I have a P8600 and got BSOD at 0.875/0.875/0.875/0.925. Testing out higher multipliers now (I know - I was supposed to start high and work down, but I'm doing it in reverse because I'm foolish).

 

It's okay, I have a P8600 and I can't get it as low as that either. My undervolting came out to be 0.8750V, 0.8750V, 0.8875V, 0.9500V.

 

I tested my 7x/8x and they both went down to 0.875V, so my settings are now at 0.875/0.875/0.875/0.925.

 

You seem to be the only one with a t6500 who managed to get below 1V. Mind posting some screens? I think that would help the rest of us figure out why it's restricting us.

 

Sure, just ask if you need any other screens/info.

 

thanks for the screenshots...but I still dont get it how u managed getting it below 1v...maybe my specific CPU has a lock...

 

+1 Nilo, will compare when I get home and get a chance to mess around with the lappy.

 

Here's where I ended up at with my P8600:

6x .8750
7x .8875
8x .8875
9x .9375

Max Core temp dropped from 70 to 60. Still stable after 7 hour stress test. Just running Google Chrome right now doing some internet surfing and my temp is 38. I might be able to get the middle multipliers down to .8750 but I had to call it at 2am and figured the benefits of dropping the middle multipliers down .0125 would be negligible anyway.

The only thing I didn't try was enabling S-LFM, which based on other reports is causing system freeze. If anyone has gotten S-LFM to work, please report and I'll give it a try.

 

SLFM does not cause me any trouble.

 

So I just tried turning it on. Instant freeze, just as others have reported. I see from your sig that you're running a 1555. Same processor so it's obviously not purely a processor issue, but something about the 14z P8600 config must be causing S-LFM to hang up. Anyone else have any luck with S-LFM?

 

p8600, 14z + SLFM = instant freeze for me also

 

It could be that those who can't go lower than 1V do not experience that freezing when enabling the Super LFM. Mine is lower than 1V and freezes too, just like others reported.

Another thing: I disabled all intermediate multipliers -- they are useless. I only have the 6x and 9x (min and max) multipliers enabled, others are unchecked.

 

no luck - everything matches up except for where you've undervolted to .9250 volts. I'm wondering what 's going on here.

 

Hey how much diff in temp has undervolting made for ur T6500 like on full load and Idle??..and also battery life?

 

I dropped from 87/99 (core 0/core 1) while running orthos to 69/74, so it's quite the drop in temp. I haven't been able to check them at idle, and I haven't concerned myself too deeply with battery life, though I suppose I should check that out as well.

 

Are ur temp's in C or F??

 

Celsius. Is that too high?

 

Post overload, lol. 99 Celsius is very hot for a CPU; what are you using to measure the temps?

 

lol yeah - my bad. Forum kept conking out, so I accidentally submitted the same post multiple times. Went back and deleted them.

I was using the program in the undervolting guide - HWMonitor, for 64 bit. I should note that RMClock noted lower temps across the board - didn't show the core temp going higher than 54 C when I was just running the Orthos stress test this recent time.

I'll probably run it again with different temp software. Any recommendations besides HWMonitor?

On a totally unrelated note/rant, i didn't really need Orthos to stress test as Nokia PC suite uses up 100% of the CPU on a regular basis, stupid software.

 

Which version of HW Monitor; that sounds really out. Normally you might get maybe 5C difference using different software, but not 40C + difference.

 

yeah man!!..thts pretty high...mine shows a max of 71-72C before undervolting under full load...and around 65-66 after UV,,,thts using HWMonior,,
As per the RM clock CPU reading goes...before UV it went to around 55-56C but after doing it goes to 48-49C max..
urs is the T6500 CPU isnt it?
the funny thing is tht my CPU goes up to 63-64C while general usage as per HWM but never has crossed 66-67C after UV even on full load,,,

 

Hmmm. I will have to recheck/reinstall/redo something with regard to HWMonitor. @fragile, it wasn't a 40+ difference, it was 54 on RMClock while HWMonitor indicated 65 - this was the last time I checked with undervolting.

 

Can anyone advise as to what the optimal thermal protection and enhanced low power state settings are, and why? Here's a screenshot of my settings which I haven't changed at all.

Thanks

 

I am unable to get my t9550 to go below 1.000v on any multiplier. I do not know why Anybody have any ideas? I am able to select a lower voltage in RMClock, but it does not show up as lower than 1.000v in any monitoring software.

 

Upon further investigation, I realize I am not the only one. Apologies.

 

Same happens to me. My P8600 is set to 0.875v at the lowest multiplier, 0.925v at the highest, but according to RMClock, Everest and CPU-Z, it never actually goes below 1.000v.

 

Some of you guys thought my temps were too high and were wondering about what version of HW Monitor I was using, so an update on that: I was using HW Monitor version 1.14, 64 Bit, and I was running it on a flash drive. does that make a difference at all? Also, if I use some alternative to RMClock, is it possible for me to go past the 1 V limit? Or is there any override that I can find for that?

 

Mine got really hot before undervolting to 1v across the board. It ran at [email protected] and [email protected] beforehand so this is still a substantial improvement.

Here is a picture of a hwmonitor before undervolting:



You can see the "CPU" column says it got up to 95, but the "core" temperatures only got up to 81 and 82. I stopped orthos when I saw 95 as I felt that may be risky depending on where that temperature reading is coming from... does anybody know where this thermometer is located?

After 1.000v across all multipliers and a 30 minute stress test:



Wayyy lower That's a average of 10 degrees Celsius on almost all temperatures!

 

Do you have DFFS enabled? I had the same problem with mine not going below 1.000v until I enabled DFFS. After I enabled DFFS, everything was fine.

 

I'm still stuck behind the 1V barrier like karan1003. The only options I see now is to either find an alternative to RMClock (maybe CPUGenie which actually isn't free ) or to find a way to enable DFFS.

@krick what processor are you running on and if you don't mind could you psot up some screen shots of your RMClock? I an unable to turn on DFFS because it is grayed out. I was hoping I could find out how I could enable it or if it might be restricted depending on your processor.

 

Even though I could go lower than 1V on my P8600, and both RMClock and CpuZ show 0.875V on the 6x multiplier, everytime when I look at the voltage in those programs, it jumps from 0.875 to 1V and back. For example, open CpuZ and while the computer is idling, look at the voltage that it's reporting. You'll notice that the multiplier value constantly stays at "6.0x", however the voltage shows as "0.875V" and then jumps to "1V" for a second or two, and then back to "0.875V". Happens all the time. Anyone is seeing the same or knows why?

 

Interesting. I'll be sure to check that out, and I'll let you know what I find.

 

You're probably seeing bug iii, #3: VID/FID jumps

http://forum.notebookreview.com/showthread.php?t=276661

I have the OS power plans set to Dell Recommended for every profile and the min/max processor states set to 100%, no more VID/FID spikes.

 

So.. after a ridiculous number of crashes (I finally learned) I figured out that dfs doesn't work with slfm ><. For battery, I've turned off my 9x multiplier, and have the 6x at min voltage, and 8x at min voltage (disabled the rest) and on ac, I have 6x at min and 9x at .925.

 

Dropped all my multipliers to the minimum 0.925, stressed for 10hrs, no issues.

edit: forgot to mention, the temps went from 72 to about 64

 

SLFM configuration values won't do anything until you turn on DFFS. The Intel specs say that SLFM is done though internal dividers in the CPU and the northbridge (does not change the external bus). There is a handshake with the northbridge to synchronize the divider, but we don't have an Intel chipset on the 14z. The chipset needs to support it and I suspect the Nvidia MCP79 doesn't.

 

Well.. That was a waste of like 15 freezes . Anyways, I'm happy with my new setup. Minimum voltage on battery, and dropped like .11v.

Thanks for your help!

 

Hi guys. I got mine down to minimum voltage rmclock would allow which is 1.1 for all multipliers. is there a way to set rmclock to startup in performance on demand mode instead of resetting to no management everytime? i looked through the settings and the program even says it's saving settings before i shut down the computer, but i can't get it to start up in performance on demand mode

 

do you think this cpgenie program might work on my older (2005) dimension 4700 or is there no way to manually customize the voltage on that one (Pentium 4)? or is there a totally different procedure and set of programs for desktops or P4 processors? i have rmclock working on the optiplex 320 (P4, circa 2007) at work, but it doesn't allow me to change the p values on my dimension at home

 

You're settings will stay, but I believe you need to buy it to set up a profile, which I assume saves your settings. When you reopen rmclock, i'll show no management, but that is because you havent saved a profile. In management you can choose something like reset settings when rmclock closes etc, and I unchecked them. I only use rmclock when I need to change something.

 

Interestingly, I was unable to get below 1V beforehand with Vista (although I was able to select lower voltages).

I am now able to go below 1.000V without issue [after installing Win 7 RC & checking the DFFS box]. The only multiplier I have tried it with is the lowest... but 1.66GHz runs flawlessly @ .825V. Will be testing the other multipliers and will keep you guys posted.

 

I believe I've been able to get all multipliers down to .825 except the highest (9x), so I'm only using that one when on ac

 

Hey, checking that DFFS option is working nicely. The CPU used to bottom out at idle at 1.60GHz and 1.000v. Now it's down to 800MHz, at the proper voltage setting. Awesome! As soon as I hit Apply, the CPU temperature dropped like a rock from 42C to 35C, like less than a minute. I have yet to test battery life.

 

Out of curiosity... has anybody actually gotten a BSOD AFTER the first 5 minutes of stress testing with orthos? After doing this a few times I'm getting to the point where I run orthos for 5 minutes, and if I'm still running, that's good enough for me. I haven't had any issues.

Got my T9550 down to .95v (this being 2 steps up above BSOD) @ 2.66ghz and the minimum .825v @ 1.66ghz with RMClock's auto-fill filling in the rest of the voltages. I did test all the multipliers by themselves for 5 minutes, but I'm an impatient person. Temperatures went down from the stock 95+ (stopped the test after hitting 95 centigrade on one of the thermometers) under load to a meager 76 max under load. Very impressed with the huge temperature drop. Pull from battery at idle went down from 20.5W to 13W. I don't honestly have an idea on how much battery life this saves me, but it has to be substantial.

 

It likely is, but I'd run it for ten minutes at the least under load to test for stability. That's the bare minimum. I haven't gotten any BSOD's after testing for five minutes, but then again, I haven't been able to get past the 1 V minimum RMClock seems to be limiting me to, so I can't comment.

 

I'd actually recommend running for a lot longer than 10 minutes. When I undervolted, .96 was fine until about 40 minutes into the stress test.

Ideally you'd run it for 45 minutes to an hour, or even longer if you could, just to make sure.

It's not going to hurt if it does blue screen, but it would be damned annoying if you were in the middle of something.

BSOD after 5 minutes is absolutely fine, it just means you definitely can't go that low. I think I have got BSOD after 2 minutes before on one setting.

 

I'm not entirely convinced that orthos is a good representation of overall cpu stability, possibly due to using a limited set of cpu instructions? It certainly does generate the heat if you want to look at max temps though. I've had to bump my 9x to 0.950v even though orthos ran for 10 hours at 0.925v without any issue.

The problem was getting BSODs within 20m playing HL2e2 with CPU locked at 9x. Locking the CPU to 8x, I was able to play the entire game without issue. Then going back to complete some achievements, I set it back to 9x and BSODs again. Bump the voltage to 0.9375 and BSOD again within 30m. Bump to 0.950v and I was able to complete 21/22 achievements and gave up on the last cause it's impossible.

I'm almost tempted to disable 9x altogether since 8x is stable at a far lower voltage, or just leave 9x enabled on AC power.

 

Well, personally, I don't think I could see the difference between 2.13 and 2.4 ghz, especially since the most i'll be doing on battery is surfing or using a word processor. The .27 ghz might make a difference if I'm doing something like photoshop, rendering, editing video or doing one of those cad like programs.

 

Battery life please!


YARR!
}:^)~
CorruptHertz

 

I think the estimate is a little over 4 hours without wireless, backlight on lowest etc etc. I haven't timed it yet though, this is just the windows estimate.