Sgian

Distinguished
Apr 10, 2004
6
0
18,510
Wonder if anyone could help me with a prob?

I have a AMD 3000 CPU on a Jetway V600DAP Mainboard. Prob is, i can only get the CPU to run as 1800+ @ 1.40 GHz. This is with jumpers set to 133 MHz. Whenever I try to step up the jumpers to 200MHz, which would allow the CPU to run as 3000+, it locks up on me randomly between 10 secs and 20 mins or so.

I have tried all the usual things...running it barebones, etc, but no joy. I don't think it's overheating, but I can't see any other possibility. I have been trying to solve this for over a week now and I am worn out with it. Any tips, questions or advice would be appreciated.

Sgian
 

karamazov

Distinguished
Mar 6, 2004
257
0
18,780
You board could just plain not support a CPU like that..

As I sit up in my bed looking at all the stars, I begin to wonder... WHERE THE HECK IS MY ROOF!?
 

Sgian

Distinguished
Apr 10, 2004
6
0
18,510
I have tried a single 512MB DDR400 RAM and also 2X 256 DDR266 RAM. No problem with either when jumpers are set to 133MHz, but lockup on setting jumpers to 200MHz.

PSU just been upgraded to twin fan 550W as I thought that my lowly 300W PSU may have been the problem.
 

Sgian

Distinguished
Apr 10, 2004
6
0
18,510
Board and CPU were sold to me at the same time by a very good local family store. The Tech in the store attached the CPU and fan to the mainboard in front of me while we chatted.

According to SiSoft Sandra, the board is capable of running this CPU.

Please keep advice coming as I can use the process of elimination to hopefully solve my problem.

Sgian
 

endyen

Splendid
Yes it is a kt600 mobo so it should support the chip. Check the bios revision, as an older date may not recognize the 200 fsb xp3000+.
Try the fsb at 166 and see how that goes. Then pretend you are ocing and bump the fsb a little at a time, to see how high it will go.mbm5 is a good idea, to keep an eye on temps.
 

Sgian

Distinguished
Apr 10, 2004
6
0
18,510
FSB at 166MHz reports AMD1750.

Think prob may be solved now though...on re-reading the board manual, there is an AUTO setting for the multiplier. Tried that with FSB set at 200MHZ and returns AMD3000+. Has been stable for 2 hours now, so fingers crossed.
 

pat

Expert
The A3000+ is not supposed to be a 166MHz bus speed? I though that only the the 3200+ is a 200MHz buz CPU.If it it, then maybe you are overclockins your CPU by running it at 200MHz. Sure, the multiplier might be lowered by the BIOS, but FSB overclocking cause more heat. IT it is stable and the temp are good, the you should be ok. To know, download prime95 and run a torture test.

-Always put the blame on you first, then on the hardware !!!
 

Sgian

Distinguished
Apr 10, 2004
6
0
18,510
Ok Pat, I have been stable at 200MHz for the full day, but I'll jumper to 166 and use AUTO multipliers just to see what it reports back.

Sgian
 

endyen

Splendid
The xp3000+ comes in 2 flavours, one with a 166 fsb, and the newer one with a 200 fsb. You probably have the newer one, as at auto on the multi, and 200 fsb, the 166 fsb version would be at 2.5 gigs, and would not even post.
 

oolceeoo

Distinguished
Jan 25, 2004
57
0
18,630
Check the chip itself to see that you indeed do have a athlon 3000+. I ordered a few years ago from Tiger Direct(don't order from them) a AMD k6 rated at 500mhz. Well, they sent me the wrong cpu, sending me 200mhz rated k6. When I tried to set the jumpers to 500mhz it wouldn't post, so i kept trying different settings and boom, it posted at 200mhz. I forget what I set the bus frequency at i think it was 66mhz with a 3x multiplier. I looked on the chip and indeed it was rated at 200mhz. So check the CPU itself to make sure that you indeed have the correct cpu that you purchased. Your local family shop may have just put the wrong cpu into your socket.

P4C 3.0ghz
Asus P4C800E-D
GeForceFX 5900 Ultra 256MB
2x512 MB corsair dual channel pc3200
200GB WDJB HDD
Nothing OC'd
 

Sgian

Distinguished
Apr 10, 2004
6
0
18,510
Checked CPU, it is indeed a 3000 (well, if the print on the chip is to be believed anyway!)

Everything running fine on Auto, fsb set to 200, so it must be a newer CPU right enough.