Finicky XP install?

  • Thread starter Thread starter Chris Stolworthy
  • Start date Start date
C

Chris Stolworthy

Ok guys, was given a Custom built HP system. The thing crapped out a
month ago and then the warranty guy came out and replaced the MOtherboard,
CPU, and Ram. It has been funny ever since. FOr instance, when I am trying
to install XP it will go through the whole process, then on first "Actual"
boot it pops up and says that the file NTFS.sys is damaged. NExt boot I get
a BSOD and then the boot after it will work intermittently. I checked, the
ram with Memtest and it checks out. SO right now I am low leveling the HDD
to see if that is the problem. Any ideas? Oh BTW I think something might
be wrong with the board. The onboard LAN won't work. I plug cables into
it, and it doesn't show a connection at all. However device shows up in
WIndows XP and installs without a hitch. So I disabled the onboard, and got
a PCI Lan.

-TIA
-Chris
 
Well what are you using to install XP is it oem xp or a custom xp
disk? It sounds like to me your not installing all the nessasary
drivers for the new motherboard and reformmatted and fresh install
should help.
If your using a custom cd to install i would look for an original xp
to install from and find out from hp what other drivers you need to
install after xp is installed for the chipset and etherne...Techman
 
Chris Stolworthy said:
Ok guys, was given a Custom built HP system. The thing crapped out a
month ago and then the warranty guy came out and replaced the MOtherboard,
CPU, and Ram. It has been funny ever since. FOr instance, when I am trying
to install XP it will go through the whole process, then on first "Actual"
boot it pops up and says that the file NTFS.sys is damaged.
Click to expand...

I usually see this kind of thing when PSU isn't working right, memory is
flaky, CPU overheating, etc.

What I'd do:
- Ensure all cables and cards and 100% seated properly.
- Reset the CMOS so you know that the settings are good. (might flash the
BIOS if there is an update available)
- Run with only one memory stick if you have more than one. Swap them and
try again.
- If you have another PSU, swap it out.
- Disconnect everything extra (LAN card, sound card, CD drives, floppy) so
the PC is running as minimal as possible.
- Open the case and blow a large fan into it and run it this way for a
while. (identifies heat problems)
- Pull the guts out and run it on your desk (probably won't help, but I HAVE
had this work) Check for solder hairs, etc. on the mainboard while you have
it out.

Eventually the PC will get stable and then you can slowly work backwards to
find out what is wrong.

And watch out for static. Winter is hell for static!
 
Ok guys, was given a Custom built HP system. The thing crapped out a
month ago and then the warranty guy came out and replaced the MOtherboard,
CPU, and Ram. It has been funny ever since. FOr instance, when I am trying
to install XP it will go through the whole process, then on first "Actual"
boot it pops up and says that the file NTFS.sys is damaged. NExt boot I get
a BSOD and then the boot after it will work intermittently. I checked, the
ram with Memtest and it checks out. SO right now I am low leveling the HDD
to see if that is the problem. Any ideas? Oh BTW I think something might
be wrong with the board. The onboard LAN won't work. I plug cables into
it, and it doesn't show a connection at all. However device shows up in
WIndows XP and installs without a hitch. So I disabled the onboard, and got
a PCI Lan.
Click to expand...

More than likely, the 'warranty guy'...lol...failed to install the
drivers that came with the mainboard CD.


Have a nice week...

Trent

If the cheese isn't yours...its Nacho cheese, man!
 
Well the warranty guy was a dip. I know more about Pc's than he does. He
even installed case fans backwards, lol. I don't know what exactly the
problem was, but finally after the 8th attempt at this thing, it seems to be
running smoothly. No hitches yet.
 
Back
Top