• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New cpu in XP

C

chess9

Elite member
I added a new 3.2 cpu to a winxp rig that had a 2.4 previously installed. It doesn't find the hard drive and gives me the "NO BOOT DEVICE" error message. Is this a cpu id issue under WinXP or a bios issue, or a bad cpu?
Thanks,
Robert
 
You might want to check that your hard drive connections and IDE cables are secure before you check anything else.
 
Installing only a new CPU in an existing system shouldn't require anything special to get it to work. Like Andy mentioned, check your cable connections before you waste the time on somthing unrelated.

You might check to see if your BIOS settings have changed. I know that installing a new chip may reset the BIOS defaults and this could affect the drive settings or boot order.
 
BlueWeasel:

For some reason the 3.2 cpu is checking for the Intel boot loader and when it does't find it it gives me the "No boot device" error message. I'm wondering if there is a switch in the bios that is mis-set. 🙁

Also, since the cpu boots through the POST, I'm assuming the cpu is probably ok.

Thanks, guys!
-Robert
 
Sounds like a BIOS bug. Is your motherboard rated to handle the fast CPU?

Maybe check the manufacturer's website for BIOS update... (look thru and see if you can find something about "no boot loader" in the revision history)
 
Drag:

Yes, this is a brand new mb with the 875 chipset. It will go to 3.2. It goes past the POST, so I'm assuming it's either an XP cpu id problem, or a bios switch that isn't set properly. I'm using a sata (raptor) boot drive and the switch settings in the bios are not very clear.

Thanks!
Robert
 
Throwing this 1 in from way out in left field, but quite awhile back, I had a P3 that did just this, and after doing extensive searching, I concluded that it was a "Frequency" problem with the actual chip, I rma'd the cpu, got another back and all was well. This may not pertain to your situation, but it does sound like what happened to me.
 
i agree with flashing your bios to the newest.... if that doesn't help, try that cpu in another machine and see what happens. You can also try leaving that cpu in there and booting into knoppix or something.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top