• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

XP1600+ unlocking

alexXx

Senior member
I have an Xp1600+ and an asus a7v333 mobo. I tryed to unlock it, but, when i change the mutliplier to anything other than the default 10.5x, when i reboot, the system will say that it failed to boot do to overclocking. Does this mean that the chip is still locked? I can choose any mutliplier setting i want, but it will fail to boot on anything otehr than the default 10.5. Is there a setting in this bios that will halt when a speed setting is altered?
thx
 
Yes, i tryed to unlokc it with the tom's hardware guide. i think i did it correctly, but it says that the system failed due to cpu overclocking. (even when i lower the multiplier)

 
Originally posted by: alexXx
Yes, i tryed to unlokc it with the tom's hardware guide. i think i did it correctly, but it says that the system failed due to cpu overclocking. (even when i lower the multiplier)

Sounds like it isn't properly unlocked. Can you test the bridges with a multimeter?

jaybee
 
hmm should i test accross each l1 bridge? if so, what should i get?
Is is possible there is some setting on my mobo, that won't allow me to o/c it? cause the voice program that comes with the a7v333 says that it can't boot due to cpu overclocking.
 
Yeah, test the L1's. Wrap wire or even a paper clip around the multimeter leads if you have to -- it's a pretty small area. Use the wire instead of the lead as the probe of course. Test to make sure each bridge is connected (close to 0 resistance), and make sure the adjacent aren't connected. But first I would try a separate post in motherboards to see if there is a setting you're missing. It sounds like the cpu isn't properly unlocked, but I'm not familiar with your board.

jaybee
 
Back
Top