Just thought I would update you on my Pooorly PC

First of all it started out being a faulty graphics card that caused my original problem (it blew up) although it did not fail immediately.
However even after changing the card, formatting the HDD and reinstalling XP, it still would not run properly, although it did seem to settle down "for a short while" (couple of hours)
After suspecting a faulty power supply, which was replaced made no difference, the other option was possibly the main board (which has had a slight problem for the last few years) had finally given up.
Although I changed the PSU it did not make that much difference to the way it "sometimes" starts up. (So probably not that)
But most of the time can't get past the BSOD or it freezes on either the Windows boot screen or Windows startup screen.
Regardless of any of the STOP ERROR messages, windows sometime does boot-up after several hard boots.
I ran a full HDD test with the setting to "Automatically Repair" any bad sectors etc.
Which found one error. (Windows replaced bad clusters in file 3009 of name \windows\system32\config\secEvent.Evt.)
First thought was the error probably occurred from one of the many "hard boots" the PC has suffered over the last few days since the original problem.
But to cut a long story short.
What seemed to have happened was, when the system originally went belly-up it damaged one of the sectors on the HDD (although it was not the OS HDD)
Even after CHKDSK repaired the bad segment it made no difference.
But if you recall I also said earlier that I had also re-installed XP so as to have a nice fresh install with the new graphics card.
Although after the install I had also lost approx 2GB of space compared with what I normally use (and had not even finished loading all of my programs)
The problem was now 2 fold, possibly a faulty re-install, plus re-installing onto a PC with a faulty HDD, that was due to the earlier crash.
So.
Faulty graphics card caused a crash which damaged a HDD.
Faulty XP re-install due to damaged HDD.
Chkdsk resolved the faulty segment with no further damage to the HDD.
But before I actually decided to throw the damn thing out of the window, as I had now spent over a week (10+ hours a day)
I first decided to re-ghost it back from when it "was" actually running properly, (nothing ventured, nothing lost) and yes, you probably guessed it, "IT NOW WORKS FINE"
