6625wd: CPU Frequency has increased suddenly, and doesn't lower

Evening!

Though I doubt there's much I can do at this point, before contacting Zepto
I'd thought I'd pick you alls brains.

While editing photographs (Adobe Lightroom), the laptop seemed to blank
out for a brief moment and since will not 'cycle down' or reduce frequency
despite various attempts to do so. The fan is now on all the time at high
speed irregardless of what's happening on the computer. The Frequency is
pegged at 2.4ghz 99% of time, occasionally dips, then shoots right back up.

After 4 or 5 hours of various solutions, I finally bit the bullet and reinstalled
Vista fresh. Despite this, the problem still remains, even on a fresh install.

I was using bios 008, but tried updating to 011, no luck. I'm using Windows
Vista 32bit, with all the basic updates and Zeptos ftp drivers installed. The
system currently is completely fresh, nothing installed but windows itself.

Any thoughts?

UPDATE: For some reason the clock is now showing 1197/1197, which is better
but seems wrong. This occured after I undocked, re-docked, and rebooted
the laptop. No other changes. It sticks to this clock for 30+minutes.

QUESTION: What is the normal idle clock of a 6625wd with 2.4ghz duo?

 

The normal idle clock for a 2.4 GHz duo is 800MHz. But you can only get that if you have bios 011, which adds support for SLFM (Super Low Frequency Mode)

 

The 2.4ghz version defaults to 1200mhz in lfm, but in slfm it clocks to 800mhz.

 

Is that both cores or one? After sometime and various reboots I've got
one core at 1473 and the other at 798... it seems to have relaxed there
over the past hour with no change. Nothing running, still clean install.

 

Well it depends on what program you use to read the speeds. The Intel TAT shows the 100% correct speed. I know RMClock has been known to show incorrect readings.

 

Thanks, I was using RMClock, I'll go get Intel TAT and see if things haven't
actually cleared up on their own. Perhaps it's a case of mountains out of
mole-hills!

UPDATE: Things look normal now, though it doesn't explain why the clocks
kept locking on high (2.4ghz) in the beginning.

 

If you use the newest beta ver. of RmClock it will show correct clock. Note that CPU-Z does not report correct MHz in the last few builds

 

Helpful, thanks all! However at this point there seems to be many related
and unrelated issues causing a variety of problems within the laptop. I'm
headed over to Zepto customer service to see if I can get to the root of
these issues.

Thanks for the help though, much appreciated!