P
Per-Olof Litby
Greetings,
I've encountered a really strange problem. Recently I had a
motherboard fail (blown capacitors) so I went out and got a
new one. I moved the CPU (1.1GHz Athlon) to the new
motherboard, which has new memory on it, empty of any PCI
or AGP cards (the board has built in video), connected the
disk, set up the BIOS and booted Windows in the belief that
XP would recognize the new hardware. I've done this type of
motherboard replacement before without any problems.
But then the problems started. XP booted a couple of
seconds into the splash screen with the blue progress bar,
and then crashed. There was a hint of a blue screen but
only for a fraction of a second so impossible to see any
error message. This was 100% repeatable.
I figured it had to do with the new motherboard, and that I
needed to reinstall XP. So I tried two different solutions:
1) Boot Win XP CD, do a "Repair" install on C:\WINDOWS
2) Create a new partition on the disk (D
and try a fresh
install of XP there
Both methods fail with exactly the same symptom: The
installation program copies all the files and performs the
first reboot. The first graphical install screen comes up,
says "Installing Windows" and quotes 39 minutes to
completion. It shows the first page of informational text
about new XP features, and then fails. An error window
comes up saying that there were CRC errors (!) Clicking on
the single "OK" button produces the install error log which
quotes CRC errors on files (some of them with .MAN
extensions) in the /i386 directory. I don't have the exact
error text because I can't print it (no running OS) and I
don't want to try the install any more times for fear of
wrecking the disk which has important data on it.
The strange thing is that I've tried this several times,
both for Home and Pro editions (I'm installing from an MSDN
CD) and it complains about the exact same files every time.
I've also tried the exact same CD in two other systems
without any problems. I even moved the CD drive from the
troublesome machine to another one just in case the drive
was faulty. So I know for a fact that the CD and the CD
drive both are OK.
CHKDSK /R on C: from the Recovery Console shows the disk is
OK too.
I'm starting to wonder if it could be the CPU, because that
is the only component remaining from the "old" system that
I can't test. Could some functionality in the CPU have been
damaged when the motherboard blew its capacitors, but still
allow the CPU to partly function?
Appreciate e-mail copies of any replies since I don't read
this newsgroup regularly.
thanks ahead,
P O Litby
Stockholm, Sweden
I've encountered a really strange problem. Recently I had a
motherboard fail (blown capacitors) so I went out and got a
new one. I moved the CPU (1.1GHz Athlon) to the new
motherboard, which has new memory on it, empty of any PCI
or AGP cards (the board has built in video), connected the
disk, set up the BIOS and booted Windows in the belief that
XP would recognize the new hardware. I've done this type of
motherboard replacement before without any problems.
But then the problems started. XP booted a couple of
seconds into the splash screen with the blue progress bar,
and then crashed. There was a hint of a blue screen but
only for a fraction of a second so impossible to see any
error message. This was 100% repeatable.
I figured it had to do with the new motherboard, and that I
needed to reinstall XP. So I tried two different solutions:
1) Boot Win XP CD, do a "Repair" install on C:\WINDOWS
2) Create a new partition on the disk (D
and try a freshinstall of XP there
Both methods fail with exactly the same symptom: The
installation program copies all the files and performs the
first reboot. The first graphical install screen comes up,
says "Installing Windows" and quotes 39 minutes to
completion. It shows the first page of informational text
about new XP features, and then fails. An error window
comes up saying that there were CRC errors (!) Clicking on
the single "OK" button produces the install error log which
quotes CRC errors on files (some of them with .MAN
extensions) in the /i386 directory. I don't have the exact
error text because I can't print it (no running OS) and I
don't want to try the install any more times for fear of
wrecking the disk which has important data on it.
The strange thing is that I've tried this several times,
both for Home and Pro editions (I'm installing from an MSDN
CD) and it complains about the exact same files every time.
I've also tried the exact same CD in two other systems
without any problems. I even moved the CD drive from the
troublesome machine to another one just in case the drive
was faulty. So I know for a fact that the CD and the CD
drive both are OK.
CHKDSK /R on C: from the Recovery Console shows the disk is
OK too.
I'm starting to wonder if it could be the CPU, because that
is the only component remaining from the "old" system that
I can't test. Could some functionality in the CPU have been
damaged when the motherboard blew its capacitors, but still
allow the CPU to partly function?
Appreciate e-mail copies of any replies since I don't read
this newsgroup regularly.
thanks ahead,
P O Litby
Stockholm, Sweden