Anyone using/OC'ing a NON 64 mobile Athlon 3000?

[Pohemi]

I bought an AMD Athlon XP mobile 3000+ DTR processor to try building a gaming rig that I could overclock. Here's the system:<p>
<p>
AMD Athlon XP mobile 3000+(DTR)
Asus A7N8X-E deluxe bios 1012
Corsair TwinX1024-3200XL OR Kingston KHX1024-4000K2
WD Raptor 74gb sata drive
Maxtor 250gb sata drive
BFG GeForce6800 Ultra OC
Ultra X-Connect 500W PSU
Thermaltake Xaser III case
Thermaltake Volcano 12 HSF
Windows XP Pro SP2<p>
<p>
Now I know the multiplier on this CPU is unlocked, but the FSB just does NOT want to go any higher(stock 133). This thing seems rediculous. I've tried raising the Vcore voltage. I've tried relaxing the latency even though I shouldn't have to(the memory is underclocking now anyway). The farthest I've gotten was dropping the multiplier from stock setting of 14 to 13, and raising the FSB from 133 to 142. I thought I finally figured it out, when it crashed again after raising the FSB to 145. I've tried every combination of variables I can think of between the Vcore, FSB, multiplier, etc... and still can't seem to overclock this bitch at all. If anyone out there has a system built on one of these chips that is overclocked, please let me know. Thanks. :frown:

 

[imported_whatever]

try doing the l12 mod ... google it for details. i know my xp-m oc's much better with it.

 

[Pohemi]

My only problem with that is...if the processor needs to be RMA'd(as in if it IS faulty) then I'm screwed and I'll have payed X amount of dollars to hard mod a chip that's STILL going to be shot anyway! I'd just like to know if anyone else using this chip has experienced this or if I just have a bad chip or something else is conflicting. Thanks for the suggestion though whatever!

 

[Pohemi]

Any other help, comments, or thoughts from anyone? Any idea why I can't raise the FSB?

 

[TheStu]

It could be the board... my roomie is using thae same board and he and I had a hell of a time maneuvering through the BIOS
Have you tried dropping the multi to like 5 and then running the 200 FSB?
have you looked to see if you are using a FSB/CPU Ratio?
is it PCI/AGP locked?

that's all I can think of off hand... et back to me on this though it sounds interesting

 

[Pohemi]

I have not tried dropping the multiplier down to less than 10. As for the ratio, do you mean the FSB/memory ratio? If that is what you are refering to, I have kept it at a 1:1 ratio. I have left the memory speed at auto, which I'm PRETTY sure keeps the memory sync'd with whatever the FSB speed is. I'm not sure if this board has a PCI/AGP lock, but I can't see how that would keep me from raising the FSB speed. I know quite a few friends using this same board to OC an AMD mobile Athlon XP chip, and I've also done it myself in the past. I just can't figure out why I can't do it with THIS processor.

I will continue to try lower multipliers(whatever options are available in the bios) and will keep you updated.
:disgust:



Asus A7N8X-E deluxe, rev. 2(bios 1012)
AMD Ahlon XP mobile 3000+
Corsair TwinX1024-3200XL OR Kingston KHX1024-4000K2
WD Raptor 74gb sata drive
Maxtor 250gb sata drive
BFG GeForce6800 Ultra OC
Ultra X-connect 500W PSU
Thermaltake Volcano 12 HSF
Thermaltake Xaser III
Windows XP Pro SP2

 

[imported_whatever]

instead of doing the cpu l12 mod, you can just insert the wires into the socket. does the exact same thing, and there is no problem with RMA.
however, make sure that you remember it is there if you ever take out the processor - i didnt (bought the board/cpu from a friend) and am now working on getting the motherboard working again.

 

[Pohemi]

Well...nothing else has worked so far. I'm pretty well convinced that it is a bad chip. I've gone back to a 35w XP mobile 2400+ for the time being, and I'm RMA'ing the mobile 3000+. When I receive the replacement processor, I'll throw it back in to test it and I'll keep you updated. BTW this mobile 2400+ ROCKS!!(215 FSB 12 multiplier 1.675 Vcore= 2.58 gHz)

 

[OSL]

Hi Pohemi,

I have an AOpen MK89-L desktop mobo and plan to buy a Athlon 64 mobile 3400+ (62W, 1.5V) for this.
I am not planning to OC, but reduce power and heat. Do you think it will just work ?

I also have an Athlon XP mobile 2400+ (35W, 1.3V). What mobo do you use for this, and how have you overclocked it ?

OSL

 

[Pohemi]

You're a little off the subject here...but I'll entertain you as well as I can. As far as the system you're planning on building, I really can't say for sure. I would imagine it should work fine, but it MAY depend on the type of memory you are using also. Make sure that you consult AMD's website for a list of compatible memory modules for this mobile 64 3400+. I built a system with a socket 939 Athlon 64 3500+, and had tons of problems due to the on-die memory controller not liking my Cosair 2-2-2-5 sticks. The system would run fine at DDR333 in dual channel, but not DDR400. I don't know anything about the Abit board, or even what socket the board and chip is(754?). Abit may also have a list of compatible memory modules that you may want to check.

As for my mobile 2400+ system...the system build is listed above but here it is again:

AMD AthlonXP mobile 2400+ (Thermaltake Volcano 12 HSF)
Asus A7N8X-E Deluxe (bios 1012)
Corsair TwinX1024-3200XL (2-2-2-5 latency)
WD Raptor 74 gb sata drive
Maxtor 250gb sata drive
BFG GeForce6800 Ultra OC
Ultra X-Connect 500W PSU
Thermaltake Xaser III
Windows XP Pro SP2

This had to be one of the easiest OC's I've ever done. I simply went into the bios and changed the following settings:
1) CPU external clock speed (FSB) from 133 to 215
2) CPU Multiplier from 14 to 12
3) Vcore(cpu voltage) from 1.35 to 1.675

You have to keep in mind that every chip is different and even if they are the same model, series, and even stepping, two seemingly identical chips will not neccesarily OC the same. I also did not simply make these changes all at once. These settings were reached through the painstakingly slow process of raising the FSB 5 mhz at a time, and then raising the Vcore only when the system was no longer stable. OC'ing is quite a process(albeit fun for some, including me) and should not be attempted until you have enough knowledge to know what you are doing and understand the risks to your hardware.

For future reference: Don't take this personally, but if you have questions, look for a thread related to your specific question or problem instead of posting off-subject on someone elses thread. If you can't find one, start your own! This helps the forum stay as organized as possible. Thanks and good luck.

 

[Pohemi]

OK peeps...if anyone still gave a crap- my RMA replacement chip should be coming from Newegg tomorrow. I'm going to install the new mobile 3000+ after I get it, and I'll be sure to post any updates on here. If there is no change, then the mobile 3000's just suck and whaddya gonna do? :disgust:

 

[TheStu]

I notcied you are running an Ultra X-Connect.... are those any good? I've been looking at reviews of them and they look ok, but I would like a user's opinion.... specifically an OCer's

 

[Pohemi]

I have not had any problems with mine. I consider my system a pretty full load on the PSU, and it has performed beautifully so far. Besides everything listed in my system build, I also have the typical floppy and two different DVD-RW drives connected as well(not to mention the fan controller and 7 case fans in my case). I use ALL the PSU cables so it doesn't really save any space, but they do look more organized and it definitely helped when I was building/wiring my system together. I would recommend it.

 

[Pohemi]

OK. I got my RMA replacement processor back from Newegg today. Like I figured, the first one WAS a faulty chip. Unfortunately, so far I have not been able to push the mobile 3000 past what my mobile 2400 can OC to. I attribute this to the fact that the mobile 3000+ chips are DTR(desktop replacement) processors, and have a stock Vcore of 1.65. I'm going to test out the 3000 tomorrow with my Kingston PC4000 ram, just to make sure it's not the memory limiting the overclock.

 

[TheStu]

well good luck with all that... why exactly did you get the Mobile 3000 again?

 

[Fern]

Originally posted by: Pohemi420
OK. I got my RMA replacement processor back from Newegg today. Like I figured, the first one WAS a faulty chip. Unfortunately, so far I have not been able to push the mobile 3000 past what my mobile 2400 can OC to. I attribute this to the fact that the mobile 3000+ chips are DTR(desktop replacement) processors, and have a stock Vcore of 1.65. I'm going to test out the 3000 tomorrow with my Kingston PC4000 ram, just to make sure it's not the memory limiting the overclock.

So, what are the results?

Fern

 

[Pohemi]

Originally posted by: TheStu
well good luck with all that... why exactly did you get the Mobile 3000 again?

Ummmm...for the hell of it Just wanted to see if I could push it farther(faster) than what I already had with a 2400 and 2600. I knew that the 24, 25, and 2600's were pretty similar in their OC'ing abilities, and I just had to find out if the 3000 for some reason could be pushed higher. Apparently it was somewhat of a waste of $xxx. Oh well.

I'm about to try pairing it with my Kingston ram to see how it does. As soon as I can use my comp again I'll let y'all know what happened.

 

[Pohemi]

Originally posted by: Fern

Originally posted by: Pohemi420
OK. I got my RMA replacement processor back from Newegg today. Like I figured, the first one WAS a faulty chip. Unfortunately, so far I have not been able to push the mobile 3000 past what my mobile 2400 can OC to. I attribute this to the fact that the mobile 3000+ chips are DTR(desktop replacement) processors, and have a stock Vcore of 1.65. I'm going to test out the 3000 tomorrow with my Kingston PC4000 ram, just to make sure it's not the memory limiting the overclock.

So, what are the results?

Fern

The Kingston ram didn't make a whole lot of difference. I was able to get it stable at 220 FSB, while the highest stable setting with the Corsair ram was 215-218. But I also had to raise the Vcore to 1.75, while I can run it at 1.7 with the Corsair ram. Based on the idea that it'll run hotter and not much faster, I think I'm going to stick with the Corsair. In summary, don't bother spending the extra $50 for the mobile 3000 processor. The lower wattage 2400, 2500, and 2600 chips OC just as well. Lesson learned, I'm storing this one in my hard drive.

 

[Fern]

From what I hear, FSB 220 on that Asus mobo is pretty good. Also I have heard pc4000 doesn't always work well with the NF2 mobo's. Doesn't seem to have been a prob for you though.

What did you end up OCing the mobile 3000+ to? FSB @ 220, but with what multi?

Fern

 

[Pohemi]

Ahhh...sorry I forgot to mention that. The multiplier was 11.5 (220*11.5=2530 mhz). I tried using a multiplier of 12, but couldn't keep it stable above a FSB of 210.

 

[Fern]

2530mhz, not too bad. Sounds like what the mobile 2600+ are capable of. Maybe AMD is selecting some of those (2600+) rebadging them as 3000+ and making a little extra $ from them.

 

[Pohemi]

Yeah...that sounds likely. It seems that a lot of the mobiles come off of the same production line and are just badged differently. I've heard that this in fact true: AMD produces a mass line of chips in the same production line, and badges them after they have been individually tested. It would explain why so many different model chips are capable of about the same max speed whether it's a 2400, 2500, 2600, or 3000; it seems that it would take a lot of time and money to do it that way though.