It's a limitation of all voltage reading software. HWMonitor, CPU-Z, etc all do the same thing.Originally Posted by LowRun
Seriously their software is not making their hardware look good
It's a limitation of all voltage reading software. HWMonitor, CPU-Z, etc all do the same thing.Seriously their software is not making their hardware look good
Smile
Of course it's a software limitation, been known for ages, what i'm getting at is that PC Probe is even more inaccurate (way more i should add) despite the fact that it is an Asus software.
You can't really blame asus for there software, I doubt they will pay someone to re-make it and doit right.
Heck man, I never did get the x-fi software working :\.
Says I got an unsupported sound card lol.
I'm not sure why they even put the x-fi sticker on that via chip in the 1st place...
Must work somehow lmao.
Hwinfo32 and everest are the way to go.
Or hwmonitor if you don't need some of the extra sensor stuff.
Speedfan, well, best of luck to you on that one.
In the past that has had buggy smbus scanning code.
I would stay away from that one..., but whatever floats your boat.
hey asus's turbo-v is 9999999999999999999999999x better than amd overdrive at changing stuff
Polling rates, yeah ... I like them fast.
I thaught it was an issue with the fsb/etc readings in everest, to fast and mucked it up... (could of been fast and not muck it up)
I didn't notice the prob in cpu-z.
Didn't show up in thg clock.
I haven't tried amd's program in a long time, last time I knew it was kinda decent.
I only know that turbo mode is effected.
I don't think it's software, cpu-z, everest, whatever it shows up in.
In my install of win2k3, with turbo enabled, no fluctuation (stuck in turbo right now though).
In win7, up to 400mhz fluctuation on my ht/cpu-nb at 275mhz fsb, with turbo (yeppers.. freaking huge..).
In win7, no turbo mode, no fluctuation.
I still have the other pwr states active, it still uses 4x, 8x and so on, just that the last pwr state, turbo, is disabled :|.
I put win7 into permament turbo mode (turbo enabled with everything else, but turbo enforced at all times), just like my win2k3 install, but still had the fluctuation ^^.
I have no clue what's going on.
Possible to fix in windows somehow maybe, but maybe it's turbo I dn.
One thing, I haven't ran the cmd line ver for the pwr profile manager thingy in win7 to make sure the config was the exact same as my win2k3's setup to test with.
I can't remember the name of it off hand.
I dn, that's all I've found out so far about this fsb(everything mhz related kinda) fluctuation thing on my board.
Oh and one other thing, I've personally only noticed the odd readings in everest and aida64, but only in win7 so far.
Same programs though with turbo off and no probs.
Also that if I match the multiplier I used to use while in turbomode, say 4.125ghz, no fluctation.
What the heck right ?
No turbo for me until the next bios probably lol, or whatever.
I'm just gonna keep it off for now.
For some reason I'm able to up my pcie speed back to 150mhz again with my 240gt, and without increasing my pcie voltage at all so far :\.
Related, I dn :\.
That and my mem latency benchmark results in everest are a tiny bit more reliable, lower on avg then before.
Just wierdness.
Last edited by NEOAethyr; 10-23-2010 at 11:34 PM.
Reply With Quote
Bookmarks