Just purchased ABIT KR7A-RAID and Athlon XP1800. When I first installed I could not get it to boot. So I refresned the CMOS. It now boots up, and shows CPU as Athlon 1150 MHz and gives error message "CPU is unworkable or has changed". If I go into the BIOS setup, it shows the CPU as Athlon 1500+(133). If I try to save this setting, or if I try to set to 1800+(133), and restart, it will not boot up again, and I have to reset the CMOS again to be able to get it to boot.
First, I don't have this mobo but the problem you describe
sounds alot like what is encountered when the SPEED ERROR
HOLD or something like that is ENABLED in the cmos. If it
IS a option and is enabled, definately disable.
I had this SAME exact problem when I was installing my KR7A- Raid Abit and amd athlon xp 1600+ mobo this morning... At first I would have to clear the CMOS when I changed something in the bios but I'm not sure what I did to get it to work heh sorry =/ Also the Dragon Orb 3 fan I got is very loud hehe
retail or oem chip?
like did it come in a box that was made by AMD, or was it in some sort of plastic case?
because of the similar look of the cpus, it is quite possible that they sent you the wrong chip...but there till is a chance that it is something with the board.
to be sure, take the chip out, and inspect it......check all the markings...
THEY DO PRINT THE PERFORMANCE RATING OF THE CHIP ON THE CORE RIGHT?
or do they just put it in there......?
I have checked the chip itself and it is stamped as an Athlon 1800.It seems that the motherboard BIOS does not recognise it as such, and is recognising it as Athlon 1150. If I keep it at those settings, even though it comes up with message "CPU incorrect..." it still boots, and I can run it, so I dont think the problem is with the chip. If I try to configure it as Athlon 1500 or 1800 and save settings, then it will not boot, and I have to clear the CMOS and start again. Has anyone else experienced this problem?
I have two KT7A-Raid version1.1 and 1.3. 1.1 won't boot. 1.3 boots ok and I set it manually and did the cleared the CMOS. It work ok, but I was getting my butt kick playing UT, so I updated the BIOS and UT screen was acting funning so I cleared the CMOS again and everything is fine and I'm kicking butt again
Your mobo should be ready for XP. They do have a BIOS update, but it doesn't say anything about XP. You might want to update it though.
It doesn't sound good. I know when I updated the BIOS to be XP ready I only had the settings for the 1500-1900. No 900 1200, just for XP CPU, thought that was weird. It's like I have to update my BIOS to go back to a TBird.
If you cleared you CMOS and set to 1800, you should be good to go, but your not. Definitely keep me up to date what you have to do. Since I have the 1800 and the KR7A Board coming in next week. I bought 2400 DDR for it. your ram is 133
By the way even if I set my BIOS to 1900 it still boots.
Good to hear you got your new board, to bad the sound is giving you problems now. I have the none Raid Board and use SB Live X-Gamers 5.1. And I have to Allow LPT Interrupt Sharing. Found in Devise Manager, under Creative SB16 Emulation. With the other Abit bourd w Raid I had to do this before I booted, if not then I would have to disable the 370 chip, raid, or what ever it was called with out looking to get back to windows to Allow LPT Interrupt Sharing. If I just install the drivers, then this Sharing is already check off. Don't know if this will help, since it's the only problem I had with sound. Win98se
About the Audigy problems I've heard something that this card requires Bus Mastering to work properly. Actually, it's not the card that requires it but the Firewire port.
Some PCI slots provide this functionality and others don't, so try to change card's slot. It may help.
I tried unistalling the Audigy sound card, put it in another slot, and XP recognised it OK, and installed the native XP drivers. But when I come to install the Creative programs and drivers from CD, after running setup it still says that it cannot find a soundcard. The card does work however with just the XP native drivers, although with restricted functionality.