I recently replaced the Duron 800 (running @ 1007) on my IWILL KK266-R with an Athlon XP 1700+. As part of this upgrade I had to change the FSB setting on the KK266-R to 133MHz from the previous setting of 100MHz. However, with this setting my PC is locking up everytime within a few minutes of logging into Win2k (or Win98SE).
Any solutions to this, or any idea as to why this might be happening ?
More details below ...
Here is a short spec of my PC --
- IWILL KK266-R with October 22, 2001 BIOS update
- Athlon XP 1700+ Retail boxed version with sufficient cooling
- 3 x 256MB PC133 SDRAM (SimpleTech)
- VisionTek XTASY 6564 Ti200 (GeForce3) w/ 64MB DDR
- Adaptec USB 2.0 Card
- No other cards in other expansion slots
- 2 7200RPM HDDs on normal IDE (NOT RAID)
- DVD/CD-RW/Floppy etc.
I was using a Duron 800 @ 1007 till now and everything was rock stable (well, more or less). I have both Win2K and Win98SE, installed on two different drives, and I used both from time to time without any problem. Since my Duron had a 100MHz FSB, I had set the 100/133 FSB jumper on my IWILL KK266-R to the 100MHz side.
Today I replaced the Duron 800 with an Athlon XP 1700+, and initially forgot to put the FSB jumper on the 133MHz side. So on bootup the BIOS detected my CPU to be an Athlon XP 1331+ and upon logging into Win2K the system reported the processor speed to be only 1100MHz. I immediately realized that I need to switch the FSB jumper on the MB, and hence shutdown the system, put the jumper to the 133MHz side and rebooted the system. This time the BIOS correctly detected the processor as an Athlon XP 1700+ and Win2K booted up just fine. However, within a few minutes after I logged in, the PC locked up. I had to hard boot it and again Win2K started up fine ... but locked up within a few minutes after I logged in. This kept on happening for a number of times ..
At this point I thought may be something is wrong with my Win2K installation ... so I booted the Win98SE drive instead. This time also the system booted up just fine and kept running fine for a while even after logging in ... so I thought "okay at least the hardware is fine ... may be I'll have to reinstall Win2k". However, within 10 minutes or so the system again locked up
I have no clue as to what might be wrong ! The SDRAM is PC133, so it shouldn't have any problem running @ 133MHz ... the video card and USB cards are both fairly new, so I wouldn't expect any problem from them either.
ANY IDEA WHAT MIGHT BE WRONG HERE ? Am I missing some important step here ? Do I have to change anything else in the BIOS ?
After MANY attempts I finally gave up for the time being and set the FSB jumper on the 100MHz side and increased the CPU clock from 100 to 128. This is probably keeping the FSB speed to 100MHz, but the BIOS is detecting the CPU as XP 1640+ ... which is good for me for now.
So after a lot of trial and error, the system is running more or less stable now with 100MHz FSB speed, 128MHz CPU clock and showing the CPU speed at 1411 MHz. It is okay for now ... but surely I would like to get better results.
I am still puzzled though why my system is locking up @ 133MHz FSB ... so if ANY of you have any suggestions, I am all ears !!
BTW, I have increased the I/O voltage by 10% as well and that hasn't improved the situation.
Please, someone tell me that I am missing something
Any solutions to this, or any idea as to why this might be happening ?
More details below ...
Here is a short spec of my PC --
- IWILL KK266-R with October 22, 2001 BIOS update
- Athlon XP 1700+ Retail boxed version with sufficient cooling
- 3 x 256MB PC133 SDRAM (SimpleTech)
- VisionTek XTASY 6564 Ti200 (GeForce3) w/ 64MB DDR
- Adaptec USB 2.0 Card
- No other cards in other expansion slots
- 2 7200RPM HDDs on normal IDE (NOT RAID)
- DVD/CD-RW/Floppy etc.
I was using a Duron 800 @ 1007 till now and everything was rock stable (well, more or less). I have both Win2K and Win98SE, installed on two different drives, and I used both from time to time without any problem. Since my Duron had a 100MHz FSB, I had set the 100/133 FSB jumper on my IWILL KK266-R to the 100MHz side.
Today I replaced the Duron 800 with an Athlon XP 1700+, and initially forgot to put the FSB jumper on the 133MHz side. So on bootup the BIOS detected my CPU to be an Athlon XP 1331+ and upon logging into Win2K the system reported the processor speed to be only 1100MHz. I immediately realized that I need to switch the FSB jumper on the MB, and hence shutdown the system, put the jumper to the 133MHz side and rebooted the system. This time the BIOS correctly detected the processor as an Athlon XP 1700+ and Win2K booted up just fine. However, within a few minutes after I logged in, the PC locked up. I had to hard boot it and again Win2K started up fine ... but locked up within a few minutes after I logged in. This kept on happening for a number of times ..
At this point I thought may be something is wrong with my Win2K installation ... so I booted the Win98SE drive instead. This time also the system booted up just fine and kept running fine for a while even after logging in ... so I thought "okay at least the hardware is fine ... may be I'll have to reinstall Win2k". However, within 10 minutes or so the system again locked up
I have no clue as to what might be wrong ! The SDRAM is PC133, so it shouldn't have any problem running @ 133MHz ... the video card and USB cards are both fairly new, so I wouldn't expect any problem from them either.
ANY IDEA WHAT MIGHT BE WRONG HERE ? Am I missing some important step here ? Do I have to change anything else in the BIOS ?
After MANY attempts I finally gave up for the time being and set the FSB jumper on the 100MHz side and increased the CPU clock from 100 to 128. This is probably keeping the FSB speed to 100MHz, but the BIOS is detecting the CPU as XP 1640+ ... which is good for me for now.
So after a lot of trial and error, the system is running more or less stable now with 100MHz FSB speed, 128MHz CPU clock and showing the CPU speed at 1411 MHz. It is okay for now ... but surely I would like to get better results.
I am still puzzled though why my system is locking up @ 133MHz FSB ... so if ANY of you have any suggestions, I am all ears !!
BTW, I have increased the I/O voltage by 10% as well and that hasn't improved the situation.
Please, someone tell me that I am missing something