Athlon XP unlocking?

Dom

Well, I can't seen to overclock my 2200+ (T-Bred) at all. I've tried raising the multiplier, which did raise the clock speed a little. I also tried raising the FSB, but, altough the BIOS says it was raise it really wasn't. So, is my only option to unlock the CPU? If so could someone please provide a detailed unlocking guide for the Athlon XP's?

Thanks, Dom.

VW_Factor

So true about nForce2 mobos.. No need to unlock.. The mobo does it for you.. Very easy..

Crash Override

make sure you have agp/pci lock enabled and then move your multiplier down to 12 and your FSB up to 167

that should give you a 2400+ right there

VW_Factor

I own an 1800+.. Running 166FSB with a multplier of 12.. Mobo recognizes it as a 2400+.. Although I have some temp issues to take care of.. It runs really well..

shuki

unlocking it gives you the option or ability to change the multi. If you can already do that, then it is unlocked already.

When you say you raise fsb in BIOS but it really wasn't raised, how do you know it was not raised? If you set it in BIOS and save and reboot and come back up into windows, it should really be raised. Raise it again and boot up. Rt. click my computer and properties and see what speed you're at under general tab.

and for much more help, we'll need to know which mobo and BIOS youre using too.

Dom

That worked, it POSTed as a 2400+, however Windows would not boot. I tried to raise the core voltage but it didn't work.

Dom

When I said it really wasn't, I ment I did check the My Computer> general tab. I also used WCPUID.

BTW, I have an A7N8X Dlx, full systems specs can be seen by clicking my sig image.

shuki

Lets go for a 166 fsb.

OK not sure about asus BIOS settings but make sure your cpu and ram are in synch mode (3/3, 4/4, 5/5, 6/6) are options with abit I believe. Anyhow you just want a snyched rate. If you have 6/6 option got with it. Lock off pci and agp at stock speed if that option is available. pci 33 and agp 66. Then set volts for vcore and vmem. vcore I would set at 1.8 and vmem at 2.75. I would also set full aggressive timings in ram (as low as numbers as possible in all the CAS RAS CMD rate stuff. Then set fsb to 166 and multi to 11. That is really close to default speed on the cpu so you probably would not even need the increase vcore but we'll start high and come down.

also DOM, before doing any of this I would make sure you have all data backed up!!! When OCing hosed OS's are a regularity untli you find your comfort zone..... I would go in expecting to do a complete OS reinstall and then if you dont' have to you can then be pleasantly surprised

Dom

Well, I skiped ahead a little, and tried a 166FSB, 11.5Multi, 66AGP and default vcore, and that gave me 1913Mhz! CPU is running at 40*C idle.

I wanted to hit 2Ghz, but iunno, should I go higher?

shuki

if you're prepared to reinstall everything push on man! Did you up any volts? vcore or vmem?

And with your setup, I'd say your goal of 2G is well within spec. Next step is 174x11.5 or 166x12 your choice. The higer fsb will push your mem a bit more and give you better performance. And it looks like you've got some good stuff in there. the higher multi will push cpu more but either way they'll both put you at 2G Just give it enough juice and it'll do it

But again, be prepared to clear CMOS at best and reinstall windows at worst...

edit - first you should really check your stability at 166x11.5. Run 3dmark2k1 and 2k3 through. and then run sandra mem bench. Post up some scores while you're at it

VW_Factor

Your T-Bred should easily hit the 2G mark.. You may have to keep it a bit cooler, but mine does it.. I dont see why your 2200+ shouldnt do it.. I'd say give a hack at it..

DriveEuro

If you take it in small increments then I suggest going higher. But eventually it gets too fast and causes hard drive corruption.

Dom

SiSoft Sandra 2003 Memory Bandwith




3DM2K1SE score

3DM2K3 score

Dom

Everything seems completely stable @1914 11.5x166.

WyreTheWolf

Good job Dom are you going to keep pushing for a higher overclock?

Dom

Well I just tried what shuki suggested, 174x11.5 or 166x12. I tried each with 1.8vcore, 174x11.5 POSTed @ 1990Mhz and 166x12 POSTed @ 2400+ (2Ghz I assume). However Windows would not boot either time. I'm back running @ 1914Mhz 11.5x166 w/ 1.75vcore and eveything is working again. Since I really don't feeling like reinstalling Windows because I have a lot of stuff installed, I think I'll hold off pushing it any further, perhaps when I recive my 9700Pro I will try again.

Thank you to everybody for their help! It is most appreciated by this AMD n00b.

NewsFactory

Here's two Mods for AMD's Athlon™ XP processors! the first Mod will set your Athlon™ XP 2000+ 2200+ or 2400+ to a XP2800 (166x13.5) defaulting to a 166 FSB.

and the second mod will help you hit 200's MHz FSB with your Athlon™ XP 2600+ 2700+ or 2800+ that's like running a Barton CPU.....Hehe and as they say TRY @ Your own Risk

Thanks to Praetereo , Aceman and Nohto ! for the Mods

Here's a snip from both mods! just click on the links for more Info! Please also see the second mod to set your Athlon™ XP 2000+ 2200+ or 2400+ to a XP2800 (166x13.5) defaulting to a 166 FSB.

Modifying A 133 Fsb T-bred B Into 166 Fsb

We mentioned earlier that there differences between Barton and TBred-B in terms of their L12 bridges. The difference can also be seen with the Athlon XP 2700+ and 2800+, which share a 166MHz FSB. Would it be possible to go straight to a 166MHz FSB by changing the L12 bridges? We decided to test this with a TBred-B Athlon XP 2200+:

To reconnect the two severed L12 bridges, we will use the same method used to unlock the multiplier. Apply correction fluid to the gap in the second bridge from the right (the bridge we will attempt to connect), then tape the adjacent bridges to prevent short-circuiting. Then connect the bridges using a conductive silver pen.

PC booted and the BIOS quite clearly shows a 166MHz FSB. A simple L12 connection to unlock 166MHz FSB speeds seems to be well worth the effort – if you choose to unlock the multiplier, unlock this higher FSB setting as well to give a significant performance boost.

http://www.xtremesystems.org/forums/...&threadid=6930


Possible Solution for Running High FSB

On my 2700 and other new chips, they ran cut-connected-connected-connected. These bridges set the default FSB, with the former being 133, and the latter being 166. To test whether this affected the chip being able to run a high FSB in this board, I connected the third L12 bridge (one away from the "L12") on Aceman's 2200 - This would in effect make it look like a new XP2800 (166x13.5). We began testing and the chip was defaulting to a 166 FSB. We then procedded to make small increases in FSB in BIOS. We were hoping we would run into the problems that my 2700 was having. Sure enough, his chip could no longer run high FSB speeds. It started producing the exact same error screens and messages that my 2700 was, and at nearly identical FSB speeds. To further test, we pulled the 2200 out, and I broke the connection I had made on the third L12 bridge. We then immediately put the chip back in without changing anything else. The chip was instantly able to run 220+ FSB speeds again just like before. This really seemed like conclusive evidence that these bridges affected if a chip could run high FSB in this board. I then took a model knife (x-acto knife) and cut the third L12 bridge on my 2700. This made it match the factory setup of Aceman's 2200, and when we booted up, the chip did indeed default to a 133 MHz FSB. We started increasing the FSB with our fingers crossed, and I was amazed to see the chip booting perfectly fine as we started running all the way into the 200's! We tested what we could in the limited time we had, and the chip breezed through 3DMark at 220 MHz FSB. We did not have time to accomplish any in depth testing, but running Prime and Sandra at high FSB speeds was perfectly fine.

http://www.xtremesystems.org/forums/...?threadid=6934

Dom

Links are dead.

shuki

DOM, you said you set the vcore up but did you also max the vmem?? I would say its the voltage to your ddr holding you back there not the volts to the cpu. But, once again, be prepared to reinstall due to a corrupt OS crash.... And IMO, skip that mod on the cpu. You saw how simple it was to run it at 166 in BIOS with no mods at all. but again, just my opinion...

Dom

I don't plan to mod the CPU, I just would like to see them. As for the vmem, what would it look like in the BIOS?

shuki

ummm. if you'll be up a few minutes I'll DL your mobo manual and tell ya. brb

edit - also, what BIOS are you using? stock or have you flashed to latest?

oh, another thing to remember... the blasted nforce chipset BIOS lockup/freeze bug..... could just say saving settings do not power off and be the last message you see without a new BIOS chip or a hotflash from a working BIOS chip... Just want you to be aware of the risks involved...

an check your PM

Dom

Yeah, I'll be up, sleep is unimportant anyhow.

shuki

OK on page 2-18 of your manual. DDR reference voltage. By default it is at 2.6 but up it to 2.8.

also, you can really increase your memory bandwidth and performance by setting your memory settings to full aggressive. Since you got some good stuff there, why not take advantage of it

Crash Override

hey dom have you checked out your code to see what your 2200+ was marked down from if at all?

do you know what stepping yours is by chance?

Dom

No, I don't know. Too lazy to take the HSF off.

Crash Override

i only found out mine since i had to take off the HSF anyways to put my V9 on so i cant blame ya

if you ever do though youll know more about your cpu and what it was originally designed for

my last 2200+ wouldnt do anything over 1914 very stable either. It would sometimes for a few week run at 1.94 but then id have to back it back down to 1914.

This new one though is really amazing me.......with almost no effort its hitting 2.05 (171*12) with the fastest memory timings without a single hitch.

so maybe you have one thats of a lower quality which would suck

Dom

I've been meaning to take off the HSF, just to find what CPU I have exactly. I would do it know but I don't have any more thermal compound left.

Dom

On another note I just had to clock my CPU back down to default speeds. My computer wouldn't boot for some reason so I clocked the CPU back down to default speeds and it booted right up.