I recently bought an Athlon 1800+ with Abit's KG7-RAID and 512 MB Infineon DDR-RAM (2100, one stick).
Now I'm facing an interesting problem. If I configure the BIOS for an XP 1800+ (got the BIOS Update) the system will freeze either before the operating system is about to be loaded OR around the windows xp login screen. If I change the settings for 100 MHz FSB and the same multiplier (11.5 -> 1150 Mhz) the system runs properly. I tried all updates and newest drivers (VIA, ABIT, AMD) but the problem stays...!
I've tried to replace the RAM with one 256 MB stick (which I borrowed from my local computer store...) but the problem stays the same! So I dont think it's the RAM... Is it possible that simply the BIOS isnt ready yet (wait for another update) or is my Enermax 431W power supply to weak?
Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
I am in the same boat as you except I am running a 1.4 on an abit KG7, here's my story:
Im excited to finally find a forum outside of the abit site.
I just put together a new system with the following:
Athlon 1.4 (266)
Viper II Ultra (AGP 32 megs similiar to TNT2 Card)
350 Power Supply from Ethermax
I put together the bare basics as recommended. My hardrive, video card, and cd are from my previous system.
Anyways after booting up i left everything at defaults and reinstalled windows 2000 into the drive. Somethign was wrong and it couldnt boot. After I did the reinstall the machine booted fine.
Then after that I restarted and went into the bios so I could change the default speed that was selected to its correct speed which is 1400 (133). It is the last speed option on the list. After selecting that I rebooted and nothing. My monitor would even turn on. The computer was on but I did not see anything on the monitor...no memory count nothing.
I have spent the whole day printing and combing for info at abit and amd but have found nothing. I am not sure as to why the system will not operate at its correct speed. Its very puzzzling to me.
Now when I get home I will have to take the battery out the board and turn the power off in order for it to go back to its default values so that I may boot. I am not sure what the problem could be...I don' think its hardware at this point...But I could be wrong...
I spoke with AMD and A-bit today. AMD said its either the board or the ram (Which is what i thought) A-bit said it was probably the ram. They said use Crucial, Corsair, and or Kingston.
I just tried a lower 1000(133) and rebooted and my system hung. Apparently its choking on the 133 settings (not sure why). It boots fine when I select 1050(100) in addition when I select 1400(100) its turns it back down to 1050(100) where as if I had selected 1400(133) it completely freezes.
Things seem to be pointing to faulty memory.
I just ordered a Kingston memory piece again today and it will be here monday. Orignally I ordered akingston but the company tried to be funny and ended up sedning me transcend memory. Eventhough I had confirmed with them that they had kingston memory.
I will keep everyone posted, thanks for the help Justin!!
I think there is more to this then bad ram. I had a 1.3 t-bird in my system with a front side bus of 137 and a mulitplier of 11. It ran great untill I installed the XP processor. Theres too many people having this problem for it to be bad hardware in all of their machines. I've been looking all over the net tonight trying to find an answer to this problem. Here's other people with the same thing happening,
It works! It worked for Vincent, and for Evil Matt, and it worked for me. I've rerun several benchmarks that consistently hung before, and so everything looks great!
If your box crashes using 133 but is stable under 100, try these two changes and see if it helps. I'm planning on sending a writeup to the Abit technical support people letting them know what's going on. Hopefully some clever person at Abit will be able to find and fix whatever bug apparently crept into the 5w BIOS.
Well I had my share of problems with the KG7 as well, only my problems were beyond repair and the board had to be replaced with some nice Asus A7V266e. Here it goes. I ordered presumably a nice system, Athlon 1800 512mb of Crucial DDR, enermax 350w power, and the board of death. I hooked everything up nicely and the first thing I noticed was that there was no setting for the athlon XP chip. Bios update, no problem. I prefer not to format my HD if possible, so I started up the beast and winXP Pro would not load.... Great. So, i found a beat HD, formatted it, then loaded XP Pro again, this time it starts. Seems fast enough, winamp opens up quick, ATOMIX works great, then we get to the semi-demanding stuff. Audiograbber, Unreal Tournament, Quake 3. First to do some CD Ripping i open audiograbber. Nice it's working 2x as fast as my PIII 866. All of a sudden track 3 comes along, the system freezes. Hard shutdown. I said well what can it be come to find out soundblaster live = death with athlons. SO i put in my Philips 5.1 which is nicer anyway, and try it again. Great track 4 rolls around same thing. I move on to another app. UT to be exact. SICK! graphics are mint everything is mad smooth, 2 minutes into the game... Frozen. Im p**sed. I take out 1 dimm of ram since i have 2x 256 and leave just one in slot 4. It works for a bit longer now but same thing. I do every update that everyone recommended and still nothing. I called the place i ordered it from and got a rma # just 1 day after installation. Ordered the ASUS and all i have to say, newer board, less problems, STABLE! Not to knock the ABIT, but i have fried abit boards in the past and that whole quality speed reliability thing.... think again ~~~~~ JRS
Hi, Last night I put together my brand new KG7 and 1600XP to my suprise everything worked. The proper CPU setting for the XP 1600 are a 10.5 Multiplier and 133 CPU FSB Clock.. according to ABIT's FAQ. I have not tried this.. I came up with 1500x100. I think people are overclocking these AMD processor accidentially since the XP1600+ runs at 1.4 MHZ and XP1800+ at 1.6 . Also you multiply the numbers.. you don't just set it to the 133 FSB clock because you have a 266 board.
1500*100 = 1.5 GHZ (close enough to 1.4)
1600*133= 2.13 GHZ (way too fast!)
10.5*133 = 1.397 GHZ (about 1.4, recommended by ABIT)
Well you may have your processor running up to speed, but your front side bus is under clocked. The board has DDR (double data rate) memory which is 133 X 2 = 266.
I finally got mine to work by starting at a 100 fsb and raising it 5mhz at a time and letting windows boot fully each time, untill I reached 133 fsb. In fact I have it slightly overclocked no at a 137fsb.
I did this as per Abit's instructions, while I was on the phone with an Abit technician. He stated "the bios may be a little buggy".
I have the 1800 which runs at 1.53MHz. That's a multipler of 11.5 and a fsb of 133.
>Also you multiply the numbers.. you don't just set it to the 133 FSB >clock because you have a 266 board.
>1500*100 = 1.5 GHZ (close enough to 1.4)
>1600*133= 2.13 GHZ (way too fast!)
>10.5*133 = 1.397 GHZ (about 1.4, recommended by ABIT)
Mmm, not sure if I'm missing something here, but this sounds incorrect. If you have an Athlon XP, of any rating, you actually do just set the FSB to 133 (assuming you've paired it with DDR2100/PC133). The 1600*133 calculation above isn't correct, 1500+/1600+/1700+ etc.. are nothing more than AMD's arbitrary performance ratings, they have nothing to do with the multiplier*FSB calculation for clock speed. 1600x133 would in fact be a 212.8 GHz. You are however correct in saying that would be way too fast but you won't find a mobo with a multiplier setting of 1600 anyway.
I think what you're doing is 15x100, which would be 1.5GHz, but is still not correct, and unless you've unlocked your Athlon XP, a rather tricky process, just changing your multiplier setting in either the BIOS or with jumpers won't have any affect anyway.
What does this button do?
After reading many forums it appears to be a board, bios, processor or ram problem. I am able to boot WinXP fine with the following BIOS configuration:
My problem is that I can boot up fine, but several minutes after boot, my computer will freeze randomly. It will freeze after several instances of opening and closing Internet Explorer or clicking on msn messenger. Regardless... booting with those values is unacceptable as I am underclocking the FSB therefore getting a total overall speed of 1050Mhz from the processor.
However when I change the FSB to 133 (to get 1200mhz), the OS fails to boot and reports a STOP error message. Relating STOP error codes to faulty memory I then swapped DDR sticks, but still no go... no boot up.
Any other ideas before I send this board back and get another brand?
Ok, here it goes. The problem lies in the cpu temperature, not the drivers. You see, as the multiplier settings are higher, the cpu temp rises in a parallel fashion. That is why you can run your system at lower FSB & Multiplier settings.
The solution is to either get an AMD approved fan, or add thermal paste between the CPU and the Fan. If one way doesn't work, try the other. I had exactly the same problem, and I fixed it like that.
Also use the MOBO monitor, supplied with the Abit CD. That way, you can monitor the temperature. It should be anywhere between 45 and 55. But not more. Ideally, less then 50.
The solution you had posted still does not address the problem that the processor can not be run at the FSB of 133.
Yes the system can be run at the FSB of 100 but the multiplier set to a higher amount therefore increasing the CPU temperature.
However, this is not how the processor should be run.
I have finally given up and I shall return by motherboard for something else. None of my inquiries to ABIT has been answered and I have lost respect for a company I had once thought was the best motherboard manufacturer.
By putting the FSB at 133, you are asking for the cpu to go at a higher temperature. Trust me, go with the temperature, make it go lower. The FSB is still part of the equation:
FSB x Multiplier = CPU speed
So this solution does address the FSB problem.
I had exactly the same problem as you did, and I resolved it by addressing the temperature.
PS At this point in life, i am resolving another instability issue. I get random freezes every now and then, after the system runs fine. So I reverted it to Bios 5W, and until now, it has shown to be a succesfull solution.