Alright, so the computer just went out on its own at a certain point in time. I came across it, moved the mouse, and it just restarted on its own.
However, when turning back on, it took an oddly long amount of time, and instead of automatically logging onto windows as it usually does, it gave me a blank error message (red x, "yes" or "no", but no text or label, and clicking either does nothing)... Tried a few more times, same issue... figured windows installation corrupted...
So I reinstalled a new version of windows onto the same paritition and overwrote the old one. Didn't reformat since I wanted to keep the files and had no spare HD's or partition to play with, but it overwrote the windows folder and such...
Anyway, now it logs onto windows, however stalls far more often than it should. It also takes much longer to load windows as well... like well over than triple time, upto 5 minutes... And when using windows, well, I really can't describe it any better than it just often "stalls", most basic operations take a good 20 seconds to register, while the program doesn't respond in the meanwhile... we're talking about simplistic things like deleting favorites from the IE list (didnt bother installing firefox yet heh), clicking on some links, right clicking on various things such as folders or desktop, etc...
Ran MemTest86 for the better part of 24 hours, and not a single error popped up, so the RAM looks ok... Ran DiskCheck (or whatever they call ScanDisk on XP), and it got through with no errors, although I never really got a 'report' of any sort other than a popup stating "scandisk is complete"... Does the XP version provide any such report if there are no issues?
Anyway, I guess apart from HD and Memory, the potential culprits could be the motherboard or CPU... or perhaps PSU?
I still have an inkling that its the HD, as this kind of behaviour would make sense if there was an issue with it, but scandisk seems ok... (I'm defragging now, even though it might not be necessary, if it bugs up that should tell me something...)
What else could cause this kind of issue that I should be testing for? I don't have many spare parts to swap out, unfortunately...
Could the CPU or Motherboard cause these kinds of effects if they malfunctioned? I'm relatively sure vid-card wouldn't...
And there's always the PSU, but that's relatively new, maybe 2 or 3 months old after my old one fried...
Bah, it's so much easier when the unit just doesnt turn on and theres a wierd odour coming from one specific part hah... anyway, ideas? ^^
However, when turning back on, it took an oddly long amount of time, and instead of automatically logging onto windows as it usually does, it gave me a blank error message (red x, "yes" or "no", but no text or label, and clicking either does nothing)... Tried a few more times, same issue... figured windows installation corrupted...
So I reinstalled a new version of windows onto the same paritition and overwrote the old one. Didn't reformat since I wanted to keep the files and had no spare HD's or partition to play with, but it overwrote the windows folder and such...
Anyway, now it logs onto windows, however stalls far more often than it should. It also takes much longer to load windows as well... like well over than triple time, upto 5 minutes... And when using windows, well, I really can't describe it any better than it just often "stalls", most basic operations take a good 20 seconds to register, while the program doesn't respond in the meanwhile... we're talking about simplistic things like deleting favorites from the IE list (didnt bother installing firefox yet heh), clicking on some links, right clicking on various things such as folders or desktop, etc...
Ran MemTest86 for the better part of 24 hours, and not a single error popped up, so the RAM looks ok... Ran DiskCheck (or whatever they call ScanDisk on XP), and it got through with no errors, although I never really got a 'report' of any sort other than a popup stating "scandisk is complete"... Does the XP version provide any such report if there are no issues?
Anyway, I guess apart from HD and Memory, the potential culprits could be the motherboard or CPU... or perhaps PSU?
I still have an inkling that its the HD, as this kind of behaviour would make sense if there was an issue with it, but scandisk seems ok... (I'm defragging now, even though it might not be necessary, if it bugs up that should tell me something...)
What else could cause this kind of issue that I should be testing for? I don't have many spare parts to swap out, unfortunately...
Could the CPU or Motherboard cause these kinds of effects if they malfunctioned? I'm relatively sure vid-card wouldn't...
And there's always the PSU, but that's relatively new, maybe 2 or 3 months old after my old one fried...
Bah, it's so much easier when the unit just doesnt turn on and theres a wierd odour coming from one specific part hah... anyway, ideas? ^^