After flashing the BIOS my CPU has gone from a 3000+ to a 1700+ and I'm trying to recover the original settings.
Mobo MS6712 (KT4V)
CPU AMD Athlon XP 3000+ (@2172) not o/c'd
My original BIOS was dated 01/02/2001 and I figured was very old for the system so I had a look at the MSI site for an update. The original version was 1.1 and the most recent was 5.4. To make sure I got the right one I downloaded and ran the MSI Live Monitor and let it auto update to look for the most recent files. I followed all the instructions, created a recovery disk and let it flash the BIOS.
When I reset the computer it didn't display anything, not even the POST. No beeps nothing. I reset and used the recovery disk, then tried the update again. This time after restarting it worked and got into Windows. I ran Aida32 and cpu-z to see if everything looked OK and found to my horror that my CPU, previously recognised by both as an AMD Athlon XP 3000+ (@2172MHz) is now a Athlon 1700+ running at 1300MHz.
I had previously looked at the BIOS and noted down the settings in case I had to manually reset them - good thing I did. Comparing the current settings with the old ones the FSB and "current host clock" is now 100 instead of 166, and the multiplier is still 13. (13x100 = 1300 which is now, and 13*166=2158 roughly what it used to be).
I reset again entered the BIOS and tried to manually change this setting, checking also that everything else was the same. With the new BIOS some of the available settings were different, but the options selected all agreed with the old ones. I changed the FSB back to 166, checked the multiplier on 13 saved and exited. It tried to restart and this time nothing on screen, again no beeps, but this time it wouldn't recover with the disk made earlier.
To get it to start again I had to move the CMOS jumper, and now I am back in the same situation, with the CPU reporting as a 1700+ instead of a 3000+. I tried using the rollback drivers feature of XP on the BIOS but it threw up a couple of error messages, stopped responding and reset the computer.
If anyone has ideas on how I can try to fix this they would be greatly appreciated.
Mobo MS6712 (KT4V)
CPU AMD Athlon XP 3000+ (@2172) not o/c'd
My original BIOS was dated 01/02/2001 and I figured was very old for the system so I had a look at the MSI site for an update. The original version was 1.1 and the most recent was 5.4. To make sure I got the right one I downloaded and ran the MSI Live Monitor and let it auto update to look for the most recent files. I followed all the instructions, created a recovery disk and let it flash the BIOS.
When I reset the computer it didn't display anything, not even the POST. No beeps nothing. I reset and used the recovery disk, then tried the update again. This time after restarting it worked and got into Windows. I ran Aida32 and cpu-z to see if everything looked OK and found to my horror that my CPU, previously recognised by both as an AMD Athlon XP 3000+ (@2172MHz) is now a Athlon 1700+ running at 1300MHz.
I had previously looked at the BIOS and noted down the settings in case I had to manually reset them - good thing I did. Comparing the current settings with the old ones the FSB and "current host clock" is now 100 instead of 166, and the multiplier is still 13. (13x100 = 1300 which is now, and 13*166=2158 roughly what it used to be).
I reset again entered the BIOS and tried to manually change this setting, checking also that everything else was the same. With the new BIOS some of the available settings were different, but the options selected all agreed with the old ones. I changed the FSB back to 166, checked the multiplier on 13 saved and exited. It tried to restart and this time nothing on screen, again no beeps, but this time it wouldn't recover with the disk made earlier.
To get it to start again I had to move the CMOS jumper, and now I am back in the same situation, with the CPU reporting as a 1700+ instead of a 3000+. I tried using the rollback drivers feature of XP on the BIOS but it threw up a couple of error messages, stopped responding and reset the computer.
If anyone has ideas on how I can try to fix this they would be greatly appreciated.
Phew!