I've come to the conclusion that AOD doesn't play all that well 64 Bit Vista...
Neither does CPU-Z
This may be old news, but if you set CPU Vid to 24 in p-states, it will boot up at 1.25v's everytime
28 = 1.20v
26 = 1.225v
24 = 1.25v
AMD FX-8350 (1237 PGN) | Asus Crosshair V Formula (bios 1703) | G.Skill 2133 CL9 @ 2230 9-11-10 | Sapphire HD 6870 | Samsung 830 128Gb SSD / 2 WD 1Tb Black SATA3 storage | Corsair TX750 PSU
Watercooled ST 120.3 & TC 120.1 / MCP35X XSPC Top / Apogee HD Block | WIN7 64 Bit HP | Corsair 800D Obsidian Case
First Computer: Commodore Vic 20 (circa 1981).
Looking at the MSI/GBT/DFI/ASUS boards, I have mixed opinions.
The MSI CF versions isn't suitable for quads and oc'ing them yet IMO.
The M3A, I'm not sure about yet. Looking at justaposts' progress.
The rest look all fine to me apart from BIOS problems.
We need guys to measure MOSFET temps on their boards under full load at 1.4-ish VCore. That would help.
Measuring Vdroop and Vdrop at the inductor/MOSFET/SUper I/O would also help.
We also need guys to test stability at above 2.4GHz, like folding or a 48 hour stability run. That would also speak volumes.
Usually this is a performance power state thing. If you leave everything on auto and stock, does it still boot 1.20VID?
The HT ref. hasn't actually dropped, that's what I'm saying.
However, what has happened is, the CPU clock has stayed the same, the HT clock has stayed the same, the RAM clock has stayed the same and the NB clock is running at 9x.
This is a known occurrence with Phenom 9500/9600 that I've tested and all ones I've seen from others. Higher than 9x multi is no change although it causes software to start reading as though its downlocked and higher than stock multi is also a no change. That's typically because they are locked.
I always stay clear of Vista 64-bit and 32-bit for testing new boards, new CPUs, new BIOSes, new apps. Because they all have patchy or bad support for it until much later and you never realize where the problem lies then. It's confusing.
Looks correct to me, IF you're in a low performance power state (low NB clock will do this). Experiementation is good, don't ya think?This may be old news, but if you set CPU Vid to 24 in p-states, it will boot up at 1.25v's everytime
28 = 1.20v
26 = 1.225v
24 = 1.25v![]()
Have you tried going lower than 24? Does it boot? What VID does it give you?
So far I've seen it's locked at 1.25VID max.
AoD is hit and miss with Vista x64. Changing voltages seems to be fine if you do them one at a time and altering CPU HT is a crap shoot. Attempting to load a profile via AOD = freeze every time for me. Vista x64 overclocks fine on my two Intel rigs, and I love it's sound stack and other features. I won't be giving it up to make an extra 200MHz on this CPU.
Last edited by Blacklash; 01-06-2008 at 07:54 AM.
Bookmarks