caton_phil
Mar 6 2005, 04:03 AM
Help!
I have an Asrock K7VM2 mobo running with Amd Athlon XP 1700 cpu. I recently bought an AMD Athlon XP 2400 cpu, number AXDC2400DKV3C, which I am pretty sure is compatible with this board but it won't run. There doesn't seem to be much I can change in the way of clock multipliers etc on the board/bios so I assume it should just run. I have tried clearing CMOS but NO. The board powers up, fans etc, but no OS and no beeping. Can anyone shed some light on this or does it seem I ahve bought a bad CPU???
Thanks.
Phil
rigel
Mar 6 2005, 04:30 PM
From ASRock.com
http://www.asrock.com/product/product_k7vm2.htmThey state that the processor should work.... Athlon XP, so the processor seems to fit.
In the cmos setup, does it recognize the 2400 processor at all?
Will it still work with the 1700 reinstalled?
May want to zip them an e-mail, just to make sure all is well with processor and system board.
Good Luck,
Rigel
caton_phil
Mar 6 2005, 04:43 PM
Yeah, I looked there an it appeared to me that it should work. I wasn't sure if I had overlooked something. Trouble is the board has nothing to set the cpu aprt from FSB which is at 133 and not 100. So I assumed it should do it automatically. My 1700 runs fine again in there. That runs on multiplier of 11. The 2400 should run at multiplier of 15. But as there are no jumpers to set (and nothing to set in BIOS) I assumed it must do it automatically.
I have tried clearing CMOS but with that CPU in it doesn't even get to a stage where you can go into bios. As I say, the board powers, fans etc, but screen stays black and no beeping.
I am sending CPU back as I am fairly sure now it must be duff.
Phil
rigel
Mar 6 2005, 05:54 PM
I looked at the manual, and saw that for the most part, everything is automatic. But, just for grins, plug the 1700 back in and make sure that you don't have your board hard set to run the 1700. It should be under the advanced tab. look at the cpu host freq and make sure it says auto.
The givens are the board works... and everything else associated with it. You have proven that with the 1700 working.
Worth a shot....
If that doesn't do it, my best guess would be a bad out of box cpu. As always, use static handling precautions when working with ESD sensitive devices.
Rigel
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.