Boot up stalls at "Checking NVRAM.."

[BrownsDawg]

I need some help here. I recently bought an XP 2500+ to replace my current XP 1900+ which I am putting into another computer. I put in the new processor and switched out a stick of 256mb PC2700 for a 512mb stick.

When I tried to start my computer, I got the message "Checking NVRAM.." and it just stopped there. I have an MSI KT3 Ultra motherboard that does support 333mhz fsb. However before the 1900+ was in with its 266mhz fsb.

I can't even enter my BIOS by hitting delete, and I tried resetting the CMOS using the jumper twice (the first time i had the power cable plugged in and thought that might affect it).

The first time i tried it said I have an XP 1700+, and after the resetting the BIOS it said it was an AMD 1100 mhz (above where it says "Checking NVRAM..")

So does anyone have any suggestions as to what I should do? My roommate thinks I might need to upgrade the BIOS on my mobo, and says I should try putting the XP 1900+ back in my system and doing that, although thats a time consuming process. I might try that later today.

Thanks for the help.

 

[MacaroneePenguin]

Well first, I would check for BIOS update, while having your 1900+ installed. After you've updated, replace the CPU and try going into BIOS.

IF that does not work:

Try this. Stick your 1900+ in there. If it boots, normally, go into BIOS and change the settings accordingly as if you had the 2500 installed. Right after you click on Save and Exit and it reboots, turn off the computer and put your 2500 in.

Do the 2nd alternative at your own risk...

PS: dont forget to check your RAM speed settings.

 

[ShOcKwAvE827]

Good question, someone should answer it.

 

[BrownsDawg]

Well just an update...

I tried putting the 2500+ into another computer and the same thing happened. And this was a brand new computer I just put together that was running perfectly on the 1900+.

So I guess newegg sent me a bad processor. :|

 

[Nitemare]

I encountered the same thing with a new 9100 video card. Weird thing is I read somewhere that some monitors caused this. I switched monitors and flashed the bios and it worked fine. I was able to switch back after I flashed the bios