Intel Core 2 Duo 2200
2GB Crucial Ballistix Tracer 6400 DDR2
320GB Samsung Spinpoint HDD (exact model escapes me at the moment) with two partitions: 80GB Windows partition and a 200+GB data partition
GIGABYTE GA-G31M-S2L LGA 775 Intel G31 Micro ATX Intel Motherboard (F4 bios)
This is as a secondary system primarily for e-mail and word processing and had been working fine for about a month until we started having boot-up problems. After scouring the web chasing down error messages and getting the system back to a usable state, I ended up doing a repair install of XP that worked fine for a day or so until a new round of errors hit. I did a complete XP reinstall and updated everything fine through SP3 and the latest IE updates.
Everything worked perfectly for about 2 days and now Iím getting the following error (had it before latest install, too, I believe): ďThe Windows Logon Process System Process Terminated unexpectedly with a status of 0xc0000135Ē.
Just prior to this error showing up on a BSOD, Iíd seen various taskbar error balloons pop-up telling me certain files were corrupted and to run chkdsk. At least two chkdsk cycles were run with a multitude of errors having been found and corrected. Now, I only get a boot-up BSOD after the Windows green status bar loading graphic.
Having gone through troubleshooting steps to include reinstalling the OS several times over the past week, Iím thinking that I may have a hardware component acting flaky. Iíve run memtest for several hours when the system was working, and no memory errors were reported. Iím wondering if the hard drive is bad and had downloaded some testing utilities, but didnít have a chance to run them before my system went haywire again.
Iím thinking that I need to recover my data and do an install on a new drive to test out a different one if no other gremlins are identified. Something in my system is causing XP to be unstable, and Iím spending too much time on it without making any headway. As soon as I get comfortable that itís working properly after a day or two, some type of system file or other error appears that BSODís my system. Any thoughts?