After checking I have more space than I thought I did on the C: partition.
50,606,419,968 bytes free to be exact.
I was doing the repair because after the login screen but before the system tray finished populating with icons, Windows Explorer would always crash a few times. The crashes would typically unhook PeerGuardian2 by giving it an icon in the system tray but not allowing it to have a right click menu or a window of any kind to manipulate or bring to the foreground. If I killed PeerGuardian2, I would have to unload its drivers with a special program before I could restart it. Restarting it would crash windows Explorer and the whole fiasco would start all over again.
I was able to prove that PG2 was not the problem by completely uninstalling it and watching Windows Explorer crash a few times after a reboot. In other words Windows Explorer would crash regardless of PG2's presents however, starting PG2's seemed to aggravate the issue but having it seemed more fun than not having it. I reinstalled PG2 and left its window open before shutting the computer down as a work around that would allow me to interface with PG2's settings after the next reboot when windows explorer would crash.
The problem with Windows Explorer crashing began when I made an embarrassingly newbie mistake when installing Asian language support files on my computer. I installed the files, but then on step2 I was possessed by Murphy's law and decided to greedily select not just the Asian languages from the list but every language. I learned my lesson. This caused WinXP to throw a temper tantrum and intermittently show me a blue screen of death. So I uninstalled all the language support completely, rebooted and tried again. This time however I only selected the languages from the list that I would be needing or using. After that windows seemed to be working except for the fact that Windows Explorer would crash a few times after every login.
I troubleshot the problem on a few different tech support forums; but after shooting down all the things that might be causing such a strange symptom, each technician I worked with came to the same conclusion: I would need to do a repair or a complete reformat and fresh install. For a while we thought it might be a bad memory issue, but I ran extensive memory tests for 3 days straight and no problems were reported. I also ran virus, rootkit, spyware, spamware, malware, etc. scans in both safemode, normal mode, and online (Panda, Kaspersky, McAfee etc.) with no signs of any infections.
I was happy using my computer in its somewhat unstable state because I could work around the problem. Then I read that a WinXP repair could sometimes fix difficult or annoying issues without compromising software that was already installed and rooted in the system registry. I decided to give it a shot, and this is where we are today.
Sorry for such a long post. I wanted to be thorough in my answer for the sake of clarity.
Questions: Are we at a point where we should try a Parallel install? Should I try disabling the embedded network support on the BIOS first?
It's getting late here on the west coast so I might have to bail out until after school tomorrow.
Thanks for helping.
Edited by geekstogouser, 26 November 2007 - 10:12 PM.