Archived from groups: microsoft.public.windowsxp.hardware (More info?)
Hi,
I've got a self-built PC that had an Intel P4 2.00GHz 400FSB 256k cache
processor in a Gigabyte GA-PE667 Ultra 2 motherboard, that works really
well, but the processor belogs to another computer and needs to go back. To
replace it, I purchased an Intel P4 2.66GHz 533FSB 512k cache processor, and
now my system has gone 'tit's up'! I'm running WinXP Pro.
The replacement CPU is identified correctly in the BIOS and during the boot
sequence, and gets as far as the little blue scroller, which stops for a
second, I then get a BSOD which isn't there long enough to read, and the
system reboots. I then get the options menu (previous known good
conguration, windows normally, safe mode, etc) but nothing I do makes any
difference. When I replace the 2GHz processor, WinXP insists on a checking
the disk, and then everything works OK until I replace the CPU again!
I have checked the compatibility list for my mobo, and the CPU is supported.
I am tempted to Ghost my drive (with the first CPU in) and try to repair the
WinXP installation (as this is the second CPU to do this, the other one was
a 2.4GHz 533FSB 512k cache), but am reluctant to if it's more likely for the
CPU to be u/s. It was bought second hand, and I will try it on another PC
before I do.
Any help would be appreciated.
Peter
Hi,
I've got a self-built PC that had an Intel P4 2.00GHz 400FSB 256k cache
processor in a Gigabyte GA-PE667 Ultra 2 motherboard, that works really
well, but the processor belogs to another computer and needs to go back. To
replace it, I purchased an Intel P4 2.66GHz 533FSB 512k cache processor, and
now my system has gone 'tit's up'! I'm running WinXP Pro.
The replacement CPU is identified correctly in the BIOS and during the boot
sequence, and gets as far as the little blue scroller, which stops for a
second, I then get a BSOD which isn't there long enough to read, and the
system reboots. I then get the options menu (previous known good
conguration, windows normally, safe mode, etc) but nothing I do makes any
difference. When I replace the 2GHz processor, WinXP insists on a checking
the disk, and then everything works OK until I replace the CPU again!
I have checked the compatibility list for my mobo, and the CPU is supported.
I am tempted to Ghost my drive (with the first CPU in) and try to repair the
WinXP installation (as this is the second CPU to do this, the other one was
a 2.4GHz 533FSB 512k cache), but am reluctant to if it's more likely for the
CPU to be u/s. It was bought second hand, and I will try it on another PC
before I do.
Any help would be appreciated.
Peter