The ThrottleStop Guide

On battery power if you are just doing light weight stuff like email and taking notes then your CPU should be spending the majority of its time at a VID voltage lower than you can set with any software so there won't be much battery life to be gained. Here are the VID specs for a P8600 when in sleep mode.

0.650 - 0.850 V - C4
0.600 - 0.850 V - DC4
0.350 - 0.700 V - C6

Obviously letting your CPU spend as much time as possible in one of these deeper sleep states is the best way to save power. That's why running a high multiplier at idle isn't such a bad thing. It allows the CPU to operate quickly, get its work done processing background tasks, and then re-enter one of these sleep states for maximum power savings.

Lowering your max voltage like you have done should help for other tasks like watching a movie or where there is a more consistent load on the CPU.

Once I have some time, I'm going to do some more testing and compare power consumption to different VID and FID settings. I added power consumption reporting in mW to the log file yesterday so it will be easier to gather some data and put that into Excel for analysis. I think there are a few power consumption myths that don't apply to some of Intel's newer processors that do a great job reducing power all by themselves.

 

unclewebb,

I have tried your ThrottleStop program several times and can only manage to freeze Win7x64 with a BSOD thrown in occasionally too.

I don't want to do anything else except have the VAIO with a 2.26GHz P8400 run cooler (faster would be a bonus, but I don't really expect that).

Could you give me a very noobish way to do this using ThrottleStop?

Thanking you in advance.

 

Most of the time, you will only see a BSOD if you have lowered the VID voltage too low. With ThrottleStop in monitoring mode, what is the VID range for your CPU? Have you done any stability testing with Prime95 or similar? You can also post a screen shot of HWiNFO32 which will show the default VID for each frequency mode.

The TS noob guide is download TS, enable it by clicking on Turn On, check the Set Multiplier box, adjust the VID voltage lower one step at a time until you lose Prime95 stability. Some laptops aren't 100% Prime95 stable even at default settings so testing this way lets you find out how stable your laptop is before you start trying to lower the voltage. Post some screen shots so I can have a look at what you are doing.

 

unclewebb,

lol... okay thanks! (I was lowering the VID voltage to 0.975 from 1.2 (I think)).

I guess you don't need screen shots for how duh I was.

Is there any way to increase performance on my P8400?

 

A VID setting of 0.975 might have something to do with a BSOD.

The P8400 has a locked multiplier so the only way to increase its speed is to use a program like SetFSB to increase the bus speed. Many laptops are not supported by SetFSB.

Many of the Dell laptops let you unlock EIST in the bios so you can trick a Core 2 CPU so both cores run at the highest possible IDA multiplier but most other laptop models don't support this. Even if this worked on your laptop, the performance increase on a P8400 is negligible.

 

Okay, I'll forget about overclocking and see how low (VID) I can have a stable system at.

Thanks!

 

Thank you again, you confirmed what i thought.
NO way to lower the SLFM= NO gain in battery life under light usage.
However under full load i have rather lower temps, so that's already a good result!!

Do you want an advice?
I have expoited another program to do this dirty work...
It's called Cpugenie and it have an automatic voltage optimization tool that finds out the best voltage for your processor.
I've done it and then, after i uninstalled cpugenie (it's not freeware), applied the voltage in ThrottleStop , and it worked.
Now i have a maximum voltage of 1.000 and the pc is stable al 100%.

 

The autotune isn't that good, sometimes it stops too high and other times it passes VIDs that fail Prime in less than an hour. If you care about your machine, it should never be a race. Live testing is the way to go.

 

MarkraM and JohnnyFlash, thanks to both of you - for the well balanced advice!

 

I don't have the knowledge to say if it's a good program or not, but i can say that in my case it worked as it should.
The voltages it reported as the "optimal" are good, cause i've tried to lower it a bit more and i had a crash

 

Since ThrottleStop doesn't use the intermediate multipliers, there's no need to get too complicated with auto tune. Just run Prime95 and drop the VID down one notch at a time in ThrottleStop until you get an error. I'd only test for about 5 minutes at each step until you got the stable VID range narrowed down and then I'd test for longer after that. Some short Linpack - LinX testing isn't such a bad idea either. That program creates more heat than any real world application I run so I tend not to run it very long when laptop testing.

LinX - A simple Linpack interface - XtremeSystems Forums

 

So there is no way to get past 1.73ghz@4cores on a 720QM?

 

Not with ThrottleStop. You'll need SetFSB to do that, and it may or may not support your laptop's motherboard.

 

On the 720QM, by the time all 4 cores are active, you'll be lucky if you are getting any turbo boost and will probably be running mostly with the default 12 multiplier at 1.6 GHz. If your motherboard supports it, the best thing you can do is get a 920XM ES CPU off of Ebay and sell your 720QM to recoup some of that cost. The 920XM ES are currently selling for about $470 including shipping. I think they were under $400 for a while but it must be Christmas pricing at the moment.

When fully loaded, if your power supply is capable, the 920XM can be adjusted to run over 100% faster than a 720QM. These are Intel's first Extreme CPUs that are in a whole different league when it comes to performance compared to the non-Extreme Quad Core CPUs. The 720QM has the multiplier and turbo TDP/TDC locked so there is nothing ThrottleStop can do. SetFSB, if it works, might get you a 10% performance boost. When you start to increase the BCLK, you will end up hitting the turbo TDP/TDC limits sooner so the BCLK goes up but the multiplier will start to throttle sooner. The overall performance gain might not be as much as a BLCK increase leads you to believe.

I'd much rather have a 100% performance boost by switching to an XM CPU.

 

I was messing around with the rt msr tool to find how the i7 sets up processor speeds and voltages. If it can change clock speeds, control itself at idle, etc,
it must have some way of doing it. So I took the whole msr table, took everything important from it and included it here . It might help figure out how to modify the i7s. I know that use different architecture,(they use uncore clock etc like amd chips), but it still might be doable. This might include other stuff like harddrives,etc so if you need that information then i could also provide that.

processor: i7 q740

key
passive read: done without reading the current msr state(not always needed)
msr read: reading the current msr state 0x10(the edx changes from reading the msr)
standard boilerplate msr reading that shows up through most of the table(0x02)
unique registry: means a different reading than the standard boilerplate(eax)
unique edx registry: means a different reading on just the edx
dual unique registry: means different readings on both the eax and edx
completely unique registry: there are different readings on each core
in either the eax or edx so a picture is included.
non unique registry: been previously used may use a word to identify it.

 

ThrottleStop 2.90 beta 8
http://www.mediafire.com/?p0psm43trbkj5su

Edit: I broke the Power Saver feature during the recent beta 7 update but it's all better in beta 8.

I added Atom support to this version. I changed the timers that ThrottleStop uses to accomplish this so if ThrottleStop used to work for you and now it doesn't, let me know. I haven't seen any problems on the Core 2 and Core i and Atom testing so far.

I also included initial Sandy Bridge support. I have no hardware and last time I checked, Intel had not released their updated documentation so this is my best wild guess. Some key registers have changed in Sandy Bridge so I'll have to wait for some feedback.

I also added in a few safety features so if you change your CPU, ThrottleStop will not try to use your previous settings and will try to start up safely so you can make some adjustments.

lenovoy560acpi: The Core i7-740QM has a locked maximum multiplier and the turbo TDP/TDC values are also locked by Intel so there isn't too much any software can do with one. If anyone finds a magic register that controls core voltage, they'll be a hero. Intel moved this register or it doesn't exist any more when they switched from Core 2 to Core i.

About the only way to make a 740QM run faster is with SetFSB but not all motherboards are supported. The performance improvement won't be huge because the turbo TDP/TDC values are still locked so when loaded, you will hit those limits sooner which reduces the turbo multiplier so overall MHz might not increase as much as you would think it should.

Here is where the Intel documentation can be found.

Intel® 64 and IA-32 Architectures Software Developer's Manuals

The Appendix in Volume 3B is where all the MSR registers are listed. This will help you to make a lot more sense out of what you've found. Unfortunately, this is the public documentation and some of the important stuff is hidden. You have to have some connections and sign an NDA to get the good stuff from Intel. You usually have to work for a company to get this. Individual programmers like myself are at a disadvantage when they have to waste a lot of time playing this guessing game of what is hiding in what register. I've been very lucky and have had some help from testers like rge and somebody over on XtremeSystems and TPU.

The MSR Tool is only designed to read the first 4 threads of a Core i7 Quad. I've been thinking of updating that program to read all 8 threads and fix a bug or two. Maybe someday.

 

Most motherboards don't support extreme versions because it's 55W part.
Which is ridiculous in any 15" notebook less than 2".
$450+ is much considering even the slowest sandy bridge mobile will crush the 920XM ...
With 450$ you have already paid 1/3 of your new notebook

 

Don't count on it. Might be a touch better at stock, but not overclocked it won't.

 

ThrottleStop 2.90 beta 8
http://www.mediafire.com/?p0psm43trbkj5su

All the above fixes and I turned Power Saver mode back on.
----------------------------------------------------------
Retail 720QM CPUs sell for $230 on Ebay. That reduces your cost of upgrading to the 920XM. The 55W Max TDP is a specification. Actual power consumption can vary significantly depending on how you have your 920XM set up.

Can you post some tests of that? The tests I've seen so far comparing a Sandy Bridge CPU to a Core i7-875 does not show a performance improvement that is going to crush a 920XM. Intel has made some changes to Sandy Bridge including Turbo Boost 2.0. If you can't adjust the turbo TDP/TDC settings like you can do with a 920XM then the new Sandy Bridge doesn't have a hope of competing with a fully overclocked 920XM or 940XM. It might be 12 to 18 months before Intel releases a second gen Sandy Bridge CPU that can compete, let alone beat, a 920XM or 940XM.

 

ThrottleStop 2.90 beta 8

Bugs spotted, Am using M15X, 920XM.

Having Clock Modulation and Chipset Clock Mod Tick at 100%. Randomly the Chipset Clock Mod will throttle and behave as untick, what i did was untick and tick chipset clock mod again to resolve. Is it possible for the programme to refresh and remember the settings every 1hr or somehow?

 

I can't reset the speed of the system from the old ini file..........

 

I'm not sure if that is an M15x issue or a ThrottleStop issue. Some M15x laptops, especially with the 260M and 920XM, have chipset clock modulation issues because there is not enough power available to power everything that needs to be powered at full speed.

The M115x doesn't use regular Clock Modulation so don't check that one.

If you have the time to do some testing, can you check the log file option and the more data option and then go play a game until you start having some throttling problems. Play for a minute or two or as long as you can stomach the slow and sluggish play and then exit the game and go back to the desktop and give ThrottleStop a chance to return everything to normal. Exit ThrottleStop after that so the log file gets written to the ThrottleStop folder.

Post or send me a screen shot of ThrottleStop about a minute after the game has ended. Don't bother checking and unchecking anything. Just send me a screen shot of exactly how TS was setup while gaming.

Have the Set Multiplier checked and set to the highest possible value and check the chipset clock modulation box and have that set to 100%.

There can be issues that what the bios wants runs at a higher priority level than ThrottleStop does so ThrottleStop is not able to compete and what the bios wants wins out. Once you show me some data, I'll show you how you can adjust ThrottleStop with an INI option to see if it will make any difference.

 

Ok, I had to turn it on, hadn't had to do that before. All setings were at the max 3.990 and multiplier was not selected as default so it would not change the settings. I am getting there..................

Edit; OK I'm back but the original ini file had all the profile names but not the selection for muliplier etc. I reset everything and saved it and am all good now. Again I had to turn it back on too. I hadn't had that issue migrating before.

 

I had to build in some safety features into beta 8 so when you first download it, you will have to do a Turn On when you first run it and do a Save and set the Do Not Reset FID/VID on Exit option to whatever you like. This will help prevent BSODs when a user swaps a CPU. After it is set up, it should work the same as before. I just did a reset CPU on my QX9650 and it still works OK.

 

Hi there, so I just installed TStop yesterday and had success in OCing my 940xm chip. Today I did a stability test on my machine and everything was looking perfect. I restarted my computer and just as it was starting i heard 2 beeps and the screen never turned on. I tried multiple times to reboot and i get the same 2 beeps and nothing.

My computer is a Clevo x8100, 940xm with dual ati 5870 cards. I hope I didn't burn my chip. Any reports of this happening to anyone else?

 

I should mention that the set multiplier was 17. However under load it would go up to 24. So 24 times 133 = 3192. The 940xm chip is 2.13 turbo to 3.33, so the 24 multiplier is within acceptable range. The hottest I saw the chip was 62 degrees celcius.

 

I forgot to mention that I forgot that I was watching a movie wirelessly on my tv from my laptop. When I tried to restart my computer the movie froze on my tv and as my laptop started to power up I heard 2 beeps and nothing.

 

A 940XM has a maximum turbo multiplier of 25 and 62C is well within normal so I'm not sure what happened. A ThrottleStop Set Multiplier setting of 17 tells the 940XM to use as much turbo boost as possible so that was OK.

How high did you increase the turbo TDP/TDC setting in ThrottleStop? I don't think your CPU has been damaged. Try contacting Clevo and ask them what two bios beeps mean.

The Alienware M17x-R2 users have not had any problems, even when pushing things far harder than you were. Here's an example of 5150Joker's 940XM running fully loaded and stable with the multiplier at 26.00 on all 8 threads.



Edit: Watching a movie isn't a significant load for a Core i7-940XM.

 

I left the TPD/TPC settings the same 55/47. I am sure glad to hear that I wasn't pushing the chip too hard. I will call "Prostar Computers" tomorrow to ask them some questions. Thanks for your quick response.

 

Pushing the chip too hard? It doesn't sound like you were pushing the chip at all. When benching, some users have had the TDP/TDC up to around 100 and a few have gone a little beyond for a quick test or two. For comparison, a desktop Core i7-920 uses a TDP/TDC setting of 130W/110A so the basic Intel design has a lot of head room as long as you keep them cool and you were certainly doing that.

Did you use ThrottleStop to increase your turbo multipliers. I believe the most recent bios for the Alienware M17x-R2 sets all 4 turbo multipliers at 25. Let me know what you figure out.

 

Well, I have been able to restart it after several tries. I put the multiplier to its lowest setting I could get it to which is 9. Before I started playing with the multiplier it was at 4 which is the highest internal multiplier cmos let you set to. I restarted and 2 beeps with a blank screen showed up again. So I reboot 4 or 5 times until it starts properly. At least I know the cpu is fine and my graphics cards are good. I wonder if rebooting while watching a movie caused some kind of corruption somewhere. I wonder if this problem is coincidental. So as it stands I am going to take off all the overclocking stuff off of this computer and try to put everything back to they way it was before, in case I have to send it back for warranty issues. ThrottleStop is working great on my other computer. I will just have to give it another try when I get my Clevo running properly.

 

The lowest multiplier physically possible in a 940XM is 9. If ThrottleStop is only reporting 4, that's usually a sign that something else is slowing your CPU down internally like Clock Modulation or Chipset Clock modulation. The bios might be turning these on by mistake or for some other reason.

Can you post some screen shots of ThrottleStop? That makes it a lot easier to see the problems you are having so I can troubleshoot and fix ThrottleStop if it needs it.

It sounds like something got screwed up in the ThrottleStop settings file. If this ever happens again, exit ThrottleStop, delete the ThrottleStop.ini configuration file and then restart ThrottleStop so it can create a new INI file with new settings. If this doesn't work, delete the INI file and then reboot to make sure your CPU gets reset to its default values before starting ThrottleStop again.

I'm not sure if there is a problem with your bios or maybe when it locked up during your movie, some random data got written into the configuration file and now that's causing some of your problems.

 

[/URL][/IMG]

This first picture was taken before I deleted the TStop.ini file

 

[/URL][/IMG]

This picture was taken after I deleted everything TStop off of my computer. I rebooted and then unrared TStop and ran it again. Picture taken moments after TStop was running.

 

I'm glad your 18748 multiplier went away. Not sure where that came from or why but I'll definitely look into it to make sure it doesn't happen again.

As for the TDP/TDC numbers, I'm not sure about them either. I've been mostly helping the Alienware M15x and M17x users and they haven't shown me any problems with sky high TDP/TDC like your CPU is showing. Some desktop motherboards set these two values really high so they don't interfere with you getting maximum turbo boost. That might be what's going on. Did the TDP ever show a more normal looking value like about 55?

You can try deleting the ThrottleStop.ini file again and instead of rebooting, completely power down. When you restart your laptop, start up ThrottleStop and see if it is showing the same TDP/TDC settings. Rebooting should have been good enough to reset your CPU to its default settings.

 

Just tried it again and TDP/TDC settings are 2019/2659. Same as before. I am using the TStop zip file I downloaded so that I use a fresh TStop every time. The ini file I deleted was sitting is the TStop folder. I just delete the whole folder and power down, then power up. Sometimes it takes 3 or 4 times to start.

Edit

For maybe the first 5 times I ran TStop my TDP/TDC values were 55/47

 

Have you updated your bios since you originally were getting 55/47?

If you set TDP/TDC to 55/47 and then exit ThrottleStop and restart it, are those settings still there or does it go back to the 2019/2659 settings?

 

Goes back to 2019/2659. No I haven't updated the bios. Prostar doesn't have a bios download, however Sager has one. The I have currently is 10.00.11PR and the Sager has is 10.00.11OC. It comes as an iso file. I am a little nervous about updating the bios. How often do people brick their computers doing this?

 

BIOS updates are pretty much foolproof nowadays provided you don't loose power during the process. Typically only take a few minutes at most.

 

One bricked computer is one too many. I wouldn't update your bios. No use changing something if maybe the problem is with ThrottleStop or who knows.

I'll send you a PM with some more tests you can do to see if we can figure out what's going on.

 

Are there any plans on integrating some kind of fan control on the software? That would be nice, we are lacking a good fan control software for laptops.

 

Installed a Qx9650 into my D901C, and then tried out ThrottleStop. By letting the CPU idle, and having the voltage set to cap at 1.200, the Laptop is cooler while running at the 3.2 speed. Important to me, as I was concerned about heat as this Laptop has 8800M GTX SLI installed.

Have run for about a week now with no downside to date. Smooth and cool is a good thing. Next week i will move up a 0.5 step on the multiplier and see how that goes.

Thanks for allowing me to jump past the faster [and much more expensive] Xeon processor!

 

ClevoX8100, try removing the battery from your laptop and unplug it from the AC adapter. Wait a short time and then plug back in. De-energize all the circuits.

I had to do the same thing when my Asus G50VT wouldn't boot because of halting during the Power On Self Test.

 

I haven't read all the way through this thread, sorry, but is there a way to use Throttlestop to undervolt my Core 2 Duo without fixing the multiplier?

 

Yes, you can do that using ThrottleStop but during my testing, based on power consumption, there was no reason not to fix the multiplier at the highest possible value.

At idle, whether the multiplier or VID are high or low on a 45nm Core 2 CPU makes virtually zero difference to power consumption as shown here.

http://forum.notebookreview.com/6369641-post5060.html

It used to make a difference on the previous 65nm Core 2 CPUs but the 45nm CPUs are very power efficient at idle regardless of what you set them to. They are designed to automatically go into the deeper C3/C4/C6 sleep states where the VID used is lower than RM Clock or ThrottleStop let you control.

If you want a low multiplier at idle, click on the Set Multiplier button and maximize that and then reduce your maximum core voltage. If you lose full load stability then you have reduced your core voltage too far and will need to increase it. I use Prime95 Small FFTs for testing which is a good enough real world test for my purposes. Some users prefer LinX, IBT, Linpack testing.

After that, click on the Power Saver feature. You can fine tune this feature by going into the Options window and increasing or decreasing the Power Saver C0% number. This feature will lower your multiplier at idle and make your computer slower but on the 45nm CPUs, it really doesn't save you much power. You can also use the SLFM feature if your CPU supports it but same thing, it changes the reported speed but doesn't do much to save power.

 

Ok, thanks! My max temperature using small FTT's on Orthos went from 76 to 67, thats a rather marked improvement, and my processor works fine on the lowest voltage on the highest multiplier.

 

I tried that a few times without any success. But thanks for the help.

 

Quick question, with version 2.90b8 what does 'PWR_mW' mean? In the logfile this is empty.

 

The new column, PWR_mw in the log file will show the battery charge or discharge rate. If you don't have a battery or you are plugged in and fully charged then this column will show 0. This number is in milliwatts so divide by 1000 to get watts. This is a reading from a Windows function that only updates about every 15 or 20 seconds. Here's an example log file and an explanation of what the log file PWR_mw column is showing.

Code:

  DATE     TIME    MULTI   C0%   CKMOD  CHIPM  PWR_mW  TEMP
01/06/11 19:19:22  11.50    2.7  100.0  100.0  -18426   43  Battery discharge rate is about
01/06/11 19:19:23  11.50    3.4  100.0  100.0  -18426   43  -18.4 Watts  (-18426/1000)
01/06/11 19:19:24  11.50    3.2  100.0  100.0  -18426   43
01/06/11 19:19:25  11.50    3.2  100.0  100.0  -18426   42
01/06/11 19:19:26  11.50    3.2  100.0  100.0  -18426   43
01/06/11 19:19:27  11.50    3.9  100.0  100.0  -18426   43
01/06/11 19:19:28  11.50    3.3  100.0  100.0  -18426   42
01/06/11 19:19:29  11.50    3.1  100.0  100.0  -18426   43
01/06/11 19:19:30  11.50    4.5  100.0  100.0  -18426   43
01/06/11 19:19:31  11.50    7.9  100.0  100.0  -18426   43
01/06/11 19:19:32  11.50    6.7  100.0  100.0  -18470   42
01/06/11 19:19:34  11.50    3.6  100.0  100.0  -18470   42
01/06/11 19:19:35  11.50    8.8  100.0  100.0  -18470   43
01/06/11 19:19:36  11.50    5.8  100.0  100.0  -18470   43
01/06/11 19:19:37  11.50   12.3  100.0  100.0  -18470   45
01/06/11 19:19:38  11.50    2.8  100.0  100.0  -18470   42
01/06/11 19:19:39  11.50    5.0  100.0  100.0  -18470   42
01/06/11 19:19:40  11.50    2.7  100.0  100.0  -18470   43
01/06/11 19:19:41  11.50    5.8  100.0  100.0  -18470   44
01/06/11 19:19:42  11.50   12.8  100.0  100.0  -18470   43
01/06/11 19:19:43  11.50   15.3  100.0  100.0  -18470   43
01/06/11 19:19:44  11.50    4.1  100.0  100.0  -18470   43
01/06/11 19:19:45  11.50    7.4  100.0  100.0  -18470   43
01/06/11 19:19:46  11.50    3.1  100.0  100.0  -18470   44
01/06/11 19:19:47  11.50    6.5  100.0  100.0  -18470   43
01/06/11 19:19:48  11.50    5.3  100.0  100.0  -18470   43
01/06/11 19:19:49  11.50    3.3  100.0  100.0  -18470   43
01/06/11 19:19:50  11.50    3.5  100.0  100.0  -18470   43
01/06/11 19:19:51  11.50    3.9  100.0  100.0  -18992   43  Power consumption increases slightly
01/06/11 19:19:52  11.50    3.9  100.0  100.0  -18992   43  to almost -19.0 Watts as I get ready
01/06/11 19:19:53  11.50    2.4  100.0  100.0  -18992   43  to run Prime95 Small FFTs.
01/06/11 19:19:54  11.50    2.4  100.0  100.0  -18992   43
01/06/11 19:19:55  11.50    2.4  100.0  100.0  -18992   43
01/06/11 19:19:56  11.50    2.3  100.0  100.0  -18992   42
01/06/11 19:19:57  11.50    2.3  100.0  100.0  -18992   43
01/06/11 19:19:58  11.50    2.3  100.0  100.0  -18992   43
01/06/11 19:19:59  11.50    2.4  100.0  100.0  -18992   43
01/06/11 19:20:00  11.50    6.3  100.0  100.0  -18992   43
01/06/11 19:20:01  11.50    2.6  100.0  100.0  -18992   43
01/06/11 19:20:02  11.50    4.3  100.0  100.0  -18992   43
01/06/11 19:20:03  11.50    2.3  100.0  100.0  -17971   43
01/06/11 19:20:04  11.50   41.3  100.0  100.0  -17971   51  Start Prime95 Small FFTs.
01/06/11 19:20:05  11.50  100.0  100.0  100.0  -17971   53
01/06/11 19:20:06  11.50  100.0  100.0  100.0  -17971   54
01/06/11 19:20:07  11.50  100.0  100.0  100.0  -17971   54
01/06/11 19:20:08  11.50  100.0  100.0  100.0  -17971   54
01/06/11 19:20:09  11.50  100.0  100.0  100.0  -17971   55
01/06/11 19:20:10  11.50  100.0  100.0  100.0  -17971   54
01/06/11 19:20:11  11.50  100.0  100.0  100.0  -17971   56
01/06/11 19:20:12  11.50  100.0  100.0  100.0  -17971   56
01/06/11 19:20:13  11.50  100.0  100.0  100.0  -17971   56
01/06/11 19:20:14  11.50  100.0  100.0  100.0  -17971   56
01/06/11 19:20:15  11.50  100.0  100.0  100.0  -17971   57
01/06/11 19:20:16  11.50  100.0  100.0  100.0  -17971   57
01/06/11 19:20:17  11.50  100.0  100.0  100.0  -17971   57
01/06/11 19:20:18  11.50  100.0  100.0  100.0  -17971   58
01/06/11 19:20:19  11.50  100.0  100.0  100.0  -17971   58
01/06/11 19:20:20  11.50  100.0  100.0  100.0  -17971   58
01/06/11 19:20:21  11.50  100.0  100.0  100.0  -36397   58  Reported power consumption finally
01/06/11 19:20:22  11.50  100.0  100.0  100.0  -36397   59  increases to about -36.4 Watts.
01/06/11 19:20:23  11.50  100.0  100.0  100.0  -36397   59
01/06/11 19:20:24  11.50  100.0  100.0  100.0  -36397   59
01/06/11 19:20:25  11.50  100.0  100.0  100.0  -36397   59
01/06/11 19:20:26  11.50  100.0  100.0  100.0  -36397   59
01/06/11 19:20:27  11.50  100.0  100.0  100.0  -36397   60
01/06/11 19:20:28  11.50  100.0  100.0  100.0  -36397   60
01/06/11 19:20:29  11.50  100.0  100.0  100.0  -36397   60
01/06/11 19:20:30  11.50  100.0  100.0  100.0  -36397   60
01/06/11 19:20:31  11.50  100.0  100.0  100.0  -36397   61
01/06/11 19:20:32  11.50  100.0  100.0  100.0  -36397   61
01/06/11 19:20:33  11.50  100.0  100.0  100.0  -36630   61
01/06/11 19:20:34  11.50  100.0  100.0  100.0  -36630   62
01/06/11 19:20:35  11.50  100.0  100.0  100.0  -36630   61
01/06/11 19:20:36  11.50  100.0  100.0  100.0  -36630   62
01/06/11 19:20:37  11.50  100.0  100.0  100.0  -36630   62
01/06/11 19:20:38  11.50  100.0  100.0  100.0  -36630   62
01/06/11 19:20:39  11.50  100.0  100.0  100.0  -36630   62
01/06/11 19:20:40  11.50  100.0  100.0  100.0  -36630   62
01/06/11 19:20:41  11.50  100.0  100.0  100.0  -36630   63
01/06/11 19:20:42  11.50  100.0  100.0  100.0  -36630   62
01/06/11 19:20:43  11.50  100.0  100.0  100.0  -36630   63
01/06/11 19:20:45  11.50  100.0  100.0  100.0  -36630   63
01/06/11 19:20:46  11.50  100.0  100.0  100.0  -36630   63
01/06/11 19:20:47  11.50  100.0  100.0  100.0  -36630   64
01/06/11 19:20:48  11.50  100.0  100.0  100.0  -36630   64
01/06/11 19:20:49  11.50  100.0  100.0  100.0  -36630   63
01/06/11 19:20:50  11.50  100.0  100.0  100.0  -36630   64
01/06/11 19:20:51  11.50  100.0  100.0  100.0  -36630   64
01/06/11 19:20:52  11.50  100.0  100.0  100.0  -36797   64
01/06/11 19:20:53  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:20:54  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:20:55  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:20:56  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:20:57  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:20:58  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:20:59  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:21:00  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:21:01  11.50  100.0  100.0  100.0  -36797   66
01/06/11 19:21:02  11.50  100.0  100.0  100.0  -36797   65
01/06/11 19:21:03  11.50  100.0  100.0  100.0  -36797   66
01/06/11 19:21:04  11.50  100.0  100.0  100.0  -36963   66
01/06/11 19:21:05  11.50  100.0  100.0  100.0  -36963   66
01/06/11 19:21:06  11.50  100.0  100.0  100.0  -36963   67
01/06/11 19:21:07  11.50  100.0  100.0  100.0  -36963   67
01/06/11 19:21:08  11.50  100.0  100.0  100.0  -36963   67
01/06/11 19:21:09  11.50  100.0  100.0  100.0  -36963   67
01/06/11 19:21:10  11.50  100.0  100.0  100.0  -36963   67
01/06/11 19:21:11  11.50  100.0  100.0  100.0  -36963   67
01/06/11 19:21:12  11.50  100.0  100.0  100.0  -36963   67
01/06/11 19:21:13  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:14  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:15  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:16  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:17  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:18  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:19  11.50  100.0  100.0  100.0  -36963   69
01/06/11 19:21:20  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:21  11.50  100.0  100.0  100.0  -36963   68
01/06/11 19:21:22  11.50  100.0  100.0  100.0  -37107   68  As a CPU heats up, it is common for
01/06/11 19:21:23  11.50  100.0  100.0  100.0  -37107   69  power consumption to increase a
01/06/11 19:21:24  11.50   20.4  100.0  100.0  -37107   60  little as shown here.  -37.1 Watts
01/06/11 19:21:25  11.50    3.4  100.0  100.0  -37107   58  Prime95 ends and back to idle CPU.
01/06/11 19:21:26  11.50    2.4  100.0  100.0  -37107   58
01/06/11 19:21:27  11.50    2.6  100.0  100.0  -37107   57
01/06/11 19:21:28  11.50    2.4  100.0  100.0  -37107   56
01/06/11 19:21:29  11.50    2.5  100.0  100.0  -37107   56
01/06/11 19:21:30  11.50    2.5  100.0  100.0  -37107   55
01/06/11 19:21:31  11.50    3.4  100.0  100.0  -37107   55
01/06/11 19:21:32  11.50    2.3  100.0  100.0  -37107   55
01/06/11 19:21:33  11.50    2.3  100.0  100.0  -37107   54
01/06/11 19:21:34  11.50    2.3  100.0  100.0  -37107   54
01/06/11 19:21:35  11.50    2.5  100.0  100.0  -37107   53
01/06/11 19:21:36  11.50    2.4  100.0  100.0  -37107   52
01/06/11 19:21:37  11.50    2.3  100.0  100.0  -37107   52
01/06/11 19:21:38  11.50    2.3  100.0  100.0  -37107   52
01/06/11 19:21:39  11.50    2.3  100.0  100.0  -37107   52
01/06/11 19:21:40  11.50    2.2  100.0  100.0  -37107   51
01/06/11 19:21:41  11.50    2.3  100.0  100.0  -37107   51
01/06/11 19:21:42  11.50    2.3  100.0  100.0  -37107   51
01/06/11 19:21:43  11.50    3.0  100.0  100.0  -37107   51
01/06/11 19:21:44  11.50    2.3  100.0  100.0  -37107   51
01/06/11 19:21:45  11.50    3.9  100.0  100.0  -37107   50
01/06/11 19:21:46  11.50    3.3  100.0  100.0  -18515   50  The power consumption number has
01/06/11 19:21:47  11.50    2.3  100.0  100.0  -18515   49  finally caught up.  Windows battery
01/06/11 19:21:48  11.50   21.7  100.0  100.0  -18515   54  monitoring is only update about
01/06/11 19:21:49  11.50   20.3  100.0  100.0  -18515   49  every 15 to 20 seconds.
01/06/11 19:21:50  11.50    3.6  100.0  100.0  -18515   49
01/06/11 19:21:51  11.50    3.0  100.0  100.0  -18515   49
01/06/11 19:21:52  11.50    2.6  100.0  100.0  -18515   49
01/06/11 19:21:53  11.50    2.6  100.0  100.0  -18515   48
01/06/11 19:21:54  11.50    2.4  100.0  100.0  -18515   48
01/06/11 19:21:55  11.50    2.4  100.0  100.0  -18515   48
01/06/11 19:21:56  11.50    2.4  100.0  100.0  -18515   48
01/06/11 19:21:57  11.50    2.3  100.0  100.0  -18515   47
01/06/11 19:21:59  11.50    2.4  100.0  100.0  -18515   47
01/06/11 19:22:00  11.50    6.3  100.0  100.0  -18515   50
01/06/11 19:22:01  11.50    2.8  100.0  100.0  -18515   47
01/06/11 19:22:02  11.50    3.2  100.0  100.0  -18515   47
01/06/11 19:22:03  11.50    2.3  100.0  100.0  -18515   46
01/06/11 19:22:04  11.50    2.3  100.0  100.0  -18515   47
01/06/11 19:22:05  11.50    2.4  100.0  100.0  -18837   46
01/06/11 19:22:06  11.50    2.3  100.0  100.0  -18837   46
01/06/11 19:22:07  11.50    2.4  100.0  100.0  -18837   46
01/06/11 19:22:08  11.50    2.3  100.0  100.0  -18837   46
01/06/11 19:22:09  11.50    2.3  100.0  100.0  -18837   46
01/06/11 19:22:10  11.50    2.3  100.0  100.0  -18837   46
01/06/11 19:22:11  11.50    2.5  100.0  100.0  -18837   46
01/06/11 19:22:12  11.50    2.3  100.0  100.0  -18837   45
01/06/11 19:22:13  11.50    2.3  100.0  100.0  -18837   46
01/06/11 19:22:14  11.50    2.4  100.0  100.0  -18837   45
01/06/11 19:22:15  11.50    2.4  100.0  100.0  -18837   46
01/06/11 19:22:16  11.50    2.3  100.0  100.0  -18837   45
01/06/11 19:22:17  11.50    4.1  100.0  100.0  -18593   45
01/06/11 19:22:18  11.50    2.6  100.0  100.0  -18593   45
01/06/11 19:22:19  11.50    2.4  100.0  100.0  -18593   45
01/06/11 19:22:20  11.50    2.3  100.0  100.0  -18593   44
01/06/11 19:22:21  11.50    2.4  100.0  100.0  -18593   45
01/06/11 19:22:22  11.50    2.9  100.0  100.0  -18593   45
01/06/11 19:22:23  11.50    2.3  100.0  100.0  -18593   44
01/06/11 19:22:24  11.50    2.6  100.0  100.0  -18593   45
01/06/11 19:22:25  11.50    2.4  100.0  100.0  -18593   45
01/06/11 19:22:26  11.50    2.3  100.0  100.0  -18593   44
01/06/11 19:22:27  11.50    2.4  100.0  100.0  -18593   44
01/06/11 19:22:28  11.50    2.3  100.0  100.0  -18593   44
01/06/11 19:22:29  11.50    2.3  100.0  100.0  -18593   44
01/06/11 19:22:30  11.50    2.4  100.0  100.0  -18593   43
01/06/11 19:22:31  11.50    2.5  100.0  100.0  -18593   44
01/06/11 19:22:32  11.50    3.2  100.0  100.0  -18593   44
01/06/11 19:22:33  11.50    2.2  100.0  100.0  -18593   44
01/06/11 19:22:34  11.50    2.6  100.0  100.0  -18593   44
01/06/11 19:22:35  11.50    2.4  100.0  100.0  -18448   44
01/06/11 19:22:36  11.50    2.3  100.0  100.0  -18448   43
01/06/11 19:22:37  11.50    2.3  100.0  100.0  -18448   43
01/06/11 19:22:38  11.50    2.4  100.0  100.0  -18448   43
01/06/11 19:22:39  11.50    2.8  100.0  100.0  -18448   43
01/06/11 19:22:40  11.50    2.9  100.0  100.0  -18448   43
01/06/11 19:22:41  11.50    7.8  100.0  100.0       0   42  Plugged laptop back in.
01/06/11 19:22:42  11.50    3.2  100.0  100.0       0   42
01/06/11 19:22:43  11.50    2.3  100.0  100.0       0   42
01/06/11 19:22:44  11.50    2.3  100.0  100.0       0   43
01/06/11 19:22:45  11.50    4.9  100.0  100.0      11   42
01/06/11 19:22:46  11.50    2.7  100.0  100.0      11   42
01/06/11 19:22:47  11.50    2.6  100.0  100.0      11   42
01/06/11 19:22:48  11.50    3.0  100.0  100.0      11   41
01/06/11 19:22:49  11.50    2.7  100.0  100.0      11   41
01/06/11 19:22:50  11.50    2.7  100.0  100.0      11   42
01/06/11 19:22:51  11.50    3.3  100.0  100.0      11   41
01/06/11 19:22:52  11.50    2.6  100.0  100.0      11   41
01/06/11 19:22:53  11.50    2.7  100.0  100.0      11   41
01/06/11 19:22:54  11.50    2.6  100.0  100.0      11   41
01/06/11 19:22:55  11.50    2.8  100.0  100.0      11   40
01/06/11 19:22:56  11.50    4.1  100.0  100.0      11   41
01/06/11 19:22:57  11.50    2.6  100.0  100.0      11   40
01/06/11 19:22:58  11.50    2.7  100.0  100.0      11   41
01/06/11 19:22:59  11.50    2.7  100.0  100.0      11   40
01/06/11 19:23:00  11.50    2.7  100.0  100.0      11   40
01/06/11 19:23:01  11.50    3.2  100.0  100.0      11   40
01/06/11 19:23:02  11.50    2.6  100.0  100.0      11   41
01/06/11 19:23:03  11.50    2.8  100.0  100.0      11   40
01/06/11 19:23:04  11.50    2.6  100.0  100.0      11   40
01/06/11 19:23:05  11.50    2.7  100.0  100.0   42047   40  Laptop is now charging at the rate
01/06/11 19:23:06  11.50    2.6  100.0  100.0   42047   40  of 42.0 Watts.  Positive number is
01/06/11 19:23:07  11.50    2.6  100.0  100.0   42047   40  charging, negative is discharging.
01/06/11 19:23:08  11.50    2.5  100.0  100.0   42047   40
01/06/11 19:23:09  11.50    2.3  100.0  100.0   42047   39
01/06/11 19:23:11  11.50    2.3  100.0  100.0   42047   39
01/06/11 19:23:12  11.50    2.4  100.0  100.0   42047   40
01/06/11 19:23:13  11.50    2.3  100.0  100.0   42047   39
01/06/11 19:23:14  11.50    2.4  100.0  100.0   42047   40
01/06/11 19:23:15  11.50    2.4  100.0  100.0   42047   40
01/06/11 19:23:16  11.50    2.3  100.0  100.0   42047   39
01/06/11 19:23:17  11.50    2.6  100.0  100.0   42047   38
01/06/11 19:23:18  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:19  11.50    2.4  100.0  100.0   42069   38
01/06/11 19:23:20  11.50    2.4  100.0  100.0   42069   39
01/06/11 19:23:21  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:22  11.50    3.0  100.0  100.0   42069   39
01/06/11 19:23:23  11.50    2.3  100.0  100.0   42069   39
01/06/11 19:23:24  11.50    2.4  100.0  100.0   42069   38
01/06/11 19:23:25  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:26  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:27  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:28  11.50    2.4  100.0  100.0   42069   38
01/06/11 19:23:29  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:30  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:31  11.50    2.3  100.0  100.0   42069   38
01/06/11 19:23:32  11.50    3.6  100.0  100.0   42069   38
01/06/11 19:23:33  11.50    2.3  100.0  100.0   42069   37
01/06/11 19:23:34  11.50    2.4  100.0  100.0   42069   37
01/06/11 19:23:35  11.50    2.3  100.0  100.0   42069   37
01/06/11 19:23:36  11.50    2.3  100.0  100.0   42102   38
01/06/11 19:23:37  11.50    2.3  100.0  100.0   42102   38
01/06/11 19:23:38  11.50    2.4  100.0  100.0   42102   37
01/06/11 19:23:39  11.50    2.6  100.0  100.0   42102   38
01/06/11 19:23:40  11.50    2.4  100.0  100.0   42102   37
01/06/11 19:23:41  11.50    2.3  100.0  100.0   42102   38
01/06/11 19:23:42  11.50    2.4  100.0  100.0   42102   37
01/06/11 19:23:43  11.50    2.3  100.0  100.0   42102   37
01/06/11 19:23:44  11.50    2.4  100.0  100.0   42102   38
01/06/11 19:23:45  11.50    2.3  100.0  100.0   42102   37
01/06/11 19:23:46  11.50    2.3  100.0  100.0   42102   37
01/06/11 19:23:47  11.50    2.8  100.0  100.0   42102   37
01/06/11 19:23:48  11.50    3.9  100.0  100.0   42125   37
01/06/11 19:23:49  11.50    2.3  100.0  100.0   42125   37
01/06/11 19:23:50  11.50    2.4  100.0  100.0   42125   37
01/06/11 19:23:51  11.50    2.6  100.0  100.0   42125   37
01/06/11 19:23:52  11.50    2.9  100.0  100.0   42125   37
01/06/11 19:23:53  11.50    2.3  100.0  100.0   42125   37
01/06/11 19:23:54  11.50    2.4  100.0  100.0   42125   36
01/06/11 19:23:55  11.50    2.6  100.0  100.0   42125   36
01/06/11 19:23:56  11.50    2.3  100.0  100.0   42125   36
01/06/11 19:23:57  11.50    2.3  100.0  100.0   42125   36
01/06/11 19:23:58  11.50    2.3  100.0  100.0   42125   36
01/06/11 19:23:59  11.50    2.4  100.0  100.0   42125   36
01/06/11 19:24:00  11.50    2.3  100.0  100.0   42125   37
01/06/11 19:24:01  11.50    3.0  100.0  100.0   42125   36
01/06/11 19:24:02  11.50    2.3  100.0  100.0   42125   37
01/06/11 19:24:03  11.50    2.4  100.0  100.0   42125   36
01/06/11 19:24:04  11.50    8.0  100.0  100.0   42125   37
01/06/11 19:24:05  11.50    5.3  100.0  100.0   42125   39
01/06/11 19:24:06  11.50    7.2  100.0  100.0   41003   36
01/06/11 19:24:07  11.50   17.0  100.0  100.0   41003   38
01/06/11 19:24:08  11.50    6.3  100.0  100.0   41003   36
01/06/11 19:24:09  11.50    2.8  100.0  100.0   41003   36
01/06/11 19:24:10  11.50    3.7  100.0  100.0   41003   36
01/06/11 19:24:11  11.50    5.2  100.0  100.0   41003   36
01/06/11 19:24:12  11.50    5.1  100.0  100.0   41003   36
01/06/11 19:24:13  11.50    3.2  100.0  100.0   41003   35
01/06/11 19:24:14  11.50    2.6  100.0  100.0   41003   35
01/06/11 19:24:15  11.50   36.7  100.0  100.0   41003   44
01/06/11 19:24:16  11.50  100.0  100.0  100.0   41003   46  Restart Prime95 Small FFTs.
01/06/11 19:24:17  11.50  100.0  100.0  100.0   41003   47
01/06/11 19:24:18  11.50  100.0  100.0  100.0   39616   47
01/06/11 19:24:19  11.50  100.0  100.0  100.0   39616   47
01/06/11 19:24:20  11.50  100.0  100.0  100.0   39616   48
01/06/11 19:24:22  11.50  100.0  100.0  100.0   39616   48
01/06/11 19:24:23  11.50  100.0  100.0  100.0   39616   48
01/06/11 19:24:24  11.50  100.0  100.0  100.0   39616   49
01/06/11 19:24:25  11.50  100.0  100.0  100.0   39616   49
01/06/11 19:24:26  11.50  100.0  100.0  100.0   39616   49
01/06/11 19:24:27  11.50  100.0  100.0  100.0   39616   49
01/06/11 19:24:28  11.50  100.0  100.0  100.0   39616   50
01/06/11 19:24:29  11.50  100.0  100.0  100.0   39616   49
01/06/11 19:24:30  11.50  100.0  100.0  100.0   39616   50
01/06/11 19:24:31  11.50  100.0  100.0  100.0   39616   51
01/06/11 19:24:32  11.50  100.0  100.0  100.0   39616   51
01/06/11 19:24:33  11.50  100.0  100.0  100.0   39616   51
01/06/11 19:24:34  11.50  100.0  100.0  100.0   39616   52
01/06/11 19:24:35  11.50  100.0  100.0  100.0   39616   52
01/06/11 19:24:36  11.50  100.0  100.0  100.0   39616   53
01/06/11 19:24:37  11.50  100.0  100.0  100.0   34288   52  My 90 watt charger is not adequate
01/06/11 19:24:38  11.50  100.0  100.0  100.0   34288   53  to fully power the CPU and fully
01/06/11 19:24:39  11.50  100.0  100.0  100.0   34288   53  charge the battery at the same time
01/06/11 19:24:40  11.50  100.0  100.0  100.0   34288   54  so the charge rate decreases.
01/06/11 19:24:41  11.50  100.0  100.0  100.0   34288   54
01/06/11 19:24:42  11.50  100.0  100.0  100.0   34288   55
01/06/11 19:24:43  11.50  100.0  100.0  100.0   34288   55
01/06/11 19:24:44  11.50  100.0  100.0  100.0   34288   54
01/06/11 19:24:45  11.50  100.0  100.0  100.0   34288   55
01/06/11 19:24:46  11.50  100.0  100.0  100.0   34288   56
01/06/11 19:24:47  11.50  100.0  100.0  100.0   34288   56
01/06/11 19:24:48  11.50  100.0  100.0  100.0   34288   56
01/06/11 19:24:49  11.50  100.0  100.0  100.0   34477   56
01/06/11 19:24:50  11.50  100.0  100.0  100.0   34477   56
01/06/11 19:24:51  11.50  100.0  100.0  100.0   34477   57
01/06/11 19:24:52  11.50  100.0  100.0  100.0   34477   57
01/06/11 19:24:53  11.50  100.0  100.0  100.0   34477   58
01/06/11 19:24:54  11.50  100.0  100.0  100.0   34477   57
01/06/11 19:24:55  11.50  100.0  100.0  100.0   34477   58
01/06/11 19:24:56  11.50  100.0  100.0  100.0   34477   58
01/06/11 19:24:57  11.50   26.5  100.0  100.0   34477   48  Exit Prime95.
01/06/11 19:24:58  11.50    4.8  100.0  100.0   34477   48
01/06/11 19:24:59  11.50    4.7  100.0  100.0   34477   48
01/06/11 19:25:00  11.50    3.6  100.0  100.0   34477   48
01/06/11 19:25:01  11.50    4.4  100.0  100.0   37629   48  and charge rate increases again.
01/06/11 19:25:02  11.50    3.3  100.0  100.0   37629   47
01/06/11 19:25:03  11.50    3.2  100.0  100.0   37629   47
01/06/11 19:25:04  11.50    3.6  100.0  100.0   37629   46
01/06/11 19:25:05  11.50    3.1  100.0  100.0   37629   47
01/06/11 19:25:06  11.50    3.2  100.0  100.0   37629   47
01/06/11 19:25:07  11.50    3.3  100.0  100.0   37629   47
01/06/11 19:25:08  11.50    3.2  100.0  100.0   37629   47
01/06/11 19:25:09  11.50    4.6  100.0  100.0   37629   46
01/06/11 19:25:10  11.50    3.2  100.0  100.0   37629   46
01/06/11 19:25:11  11.50    3.3  100.0  100.0   37629   46
01/06/11 19:25:12  11.50    3.2  100.0  100.0   37629   46
01/06/11 19:25:13  11.50    3.1  100.0  100.0   37629   46
01/06/11 19:25:14  11.50    3.3  100.0  100.0   37629   46
01/06/11 19:25:15  11.50    3.2  100.0  100.0   37629   46
01/06/11 19:25:16  11.50    3.5  100.0  100.0   37629   46
01/06/11 19:25:17  11.50    3.2  100.0  100.0   37629   46
01/06/11 19:25:18  11.50    3.2  100.0  100.0   37629   46
01/06/11 19:25:19  11.50    3.1  100.0  100.0   36674   46
01/06/11 19:25:20  11.50    3.2  100.0  100.0   36674   46
01/06/11 19:25:21  11.50    3.8  100.0  100.0   36674   46
01/06/11 19:25:22  11.50    3.3  100.0  100.0   36674   46
01/06/11 19:25:23  11.50    3.2  100.0  100.0   36674   46
01/06/11 19:25:24  11.50    3.2  100.0  100.0   36674   46
01/06/11 19:25:25  11.50    3.2  100.0  100.0   36674   46
01/06/11 19:25:26  11.50    3.2  100.0  100.0   36674   46
01/06/11 19:25:27  11.50    3.1  100.0  100.0   36674   46
01/06/11 19:25:28  11.50    3.5  100.0  100.0   36674   46
01/06/11 19:25:29  11.50    3.2  100.0  100.0   36674   46
01/06/11 19:25:30  11.50    3.2  100.0  100.0   36674   46
01/06/11 19:25:31  11.50    3.5  100.0  100.0   35953   46
01/06/11 19:25:32  11.50    3.0  100.0  100.0   35953   46
01/06/11 19:25:33  11.50    3.2  100.0  100.0   35953   46
01/06/11 19:25:34  11.50    3.1  100.0  100.0   35953   46
01/06/11 19:25:36  11.50    3.2  100.0  100.0   35953   45
01/06/11 19:25:37  11.50    3.2  100.0  100.0   35953   45
01/06/11 19:25:38  11.50    3.3  100.0  100.0   35953   45
01/06/11 19:25:39  11.50    3.3  100.0  100.0   35953   45
01/06/11 19:25:40  11.50    3.1  100.0  100.0   35953   45
01/06/11 19:25:41  11.50    3.2  100.0  100.0   35953   46
01/06/11 19:25:42  11.50    3.3  100.0  100.0   35953   45
01/06/11 19:25:43  11.50    3.2  100.0  100.0   35953   45
01/06/11 19:25:44  11.50    3.2  100.0  100.0   35953   46
01/06/11 19:25:45  11.50    3.2  100.0  100.0   35953   45
01/06/11 19:25:46  11.50    3.1  100.0  100.0   35953   45
01/06/11 19:25:47  11.50    3.5  100.0  100.0   35953   46
01/06/11 19:25:48  11.50    3.2  100.0  100.0   35953   45
01/06/11 19:25:49  11.50    3.4  100.0  100.0   35953   45
01/06/11 19:25:50  11.50    3.2  100.0  100.0   35309   46
01/06/11 19:25:51  11.50    3.2  100.0  100.0   35309   45
01/06/11 19:25:52  11.50    3.7  100.0  100.0   35309   45
01/06/11 19:25:53  11.50    3.2  100.0  100.0   35309   46
01/06/11 19:25:54  11.50    3.3  100.0  100.0   35309   46
01/06/11 19:25:55  11.50    3.1  100.0  100.0   35309   46
01/06/11 19:25:56  11.50    4.8  100.0  100.0   35309   45
01/06/11 19:25:57  11.50    3.2  100.0  100.0   35309   45
01/06/11 19:25:58  11.50    3.2  100.0  100.0   35309   46
01/06/11 19:25:59  11.50    4.4  100.0  100.0   35309   46
01/06/11 19:26:00  11.50    5.5  100.0  100.0   35309   46
01/06/11 19:26:01  11.50    3.2  100.0  100.0   35309   46
01/06/11 19:26:02  11.50    3.2  100.0  100.0   35309   45
01/06/11 19:26:03  11.50    2.7  100.0  100.0   35309   46
01/06/11 19:26:04  11.50    2.9  100.0  100.0   35309   46
01/06/11 19:26:05  11.50    4.2  100.0  100.0   35309   45
01/06/11 19:26:06  11.50    3.9  100.0  100.0   35309   45
01/06/11 19:26:07  11.50    3.7  100.0  100.0   35309   45  As a battery nears its full charge
01/06/11 19:26:08  11.50    3.2  100.0  100.0   35309   45  level, the rate of charge decreases.
01/06/11 19:26:09  11.50    3.5  100.0  100.0   35309   45  When fully charged and plugged in,
01/06/11 19:26:10  11.50    4.1  100.0  100.0   35309   45  this column will be steady at zero.

 

Thanks, but it seems there's something wrong at least at my end - I just gave it a go by removing the adapter plug from the laptop and it's still showing zero (power settings etc are all maxed).