what the hell? 1.33 Bird won't take above 11 mulitplyer?

[fluxcapacitor]

I just got my A7V133 and 1.33 Bird today. I love this proc, I can run it stable at 1.333 at 1.49 V Core! Right now I'm running at 1466 at 1.64v. It's set on 11x133 via Jumpers. When I set the dip switches to 11.5 multiplyer, it still posts at 1466!!?? Why would it do that? I tried upping the V Core to 1.75, but continually ran into OCing errors [Win protect faults, 'run setup prog to fix this problem', etc.]. So if it's factory unlocked [taken a 10, 10.5, and 11 multi], does anyone have a clue why it would not except that multiplyer? The chip is an AXIA0112. Its' got a MC462 on it w/ Artic Silver, and as I type this its running at 32c w/ the one case side off, so temp is a non-issue. Any input appreciated here...

[hunter]

Well my Axia will run great at a 10 multiplier all the way to 10x150 (1500) just fine, but will lockup at the desktop at 10.5 X 136(1428) or 11x136 (1496) or 11x133 (1463). It is like the CPU doent like any multiplier other than 10. And it runs perfect at 10x150 in Cas 2, fast CPU command, Cpu drive strength 3, at 1.75 core, 3.5 I/O, idle 31C ,load 43-45C. So I wanna know also. Are these faulty CPU's?

[fallout55]

Hmm..mine is a week 5 1.33 Bird and in my first testing it did 12x133 for 1596mhz, but locked in Q3. Was fine at 11.5x133,,1533mhz. I am perfect right now with 10x155, 1.85 vcore. This is with an Iwill KK266, I did have multiplier troubles with the KT7A before I traded it in.

[Hoot]

That's really peculiar. Start from the point of view that your CPU is spec'd for 12.5x106=1333. To the delight of overclocking enthusiasts, that is usually not the end of the journey. You can increase FSB to yield more total speed, but typically you have to drop the multiplier after increasing the Vcore does not accomplish any more improvement. Every CPU has a maximum speed limit, a maximum multiplier limit and a maximum FSB limit, for a given range of Vcore and Vi/o. Plain and simple. Finding the limits of the latter two usually involves backing off on one or the other. Typically, the FSB limit is more influenced by the other components in your system and the Multiplier limit by the CPU/Vcore combination within the limits of your PSU.
When I got my 1.0G/266 Tbird, I spent an evening recording the different settings of multiplier and fsb for a given Vcore and Vi/o that ran stable. Now, I have a chart of my "Sweet Zone". By stable, I mean not only posts, not only gets me to the Windows desktop, but runs Prime95 and 3D Mark 2001 successfully. Anything less is no accomplishment due to it not being reliable. Sure, you have to put in some time on the "learning curve", but then you have a reference document to consult before trying something new.

Hoot