Thursday, August 30, 2007

WinXP: is it a known bug?

I'm just throwing this out there... maybe someone will read this and it will ring a bell with them. But I for one have never encountered as many problems as my parents have on my own system.

My folks are running WinXP (of questionable origins that neither myself nor WGA will attest to *ahem*). And they are pretty computer illiterate so I can only assume that from time to time they will allow the auto-update to function.

All I know is that at one point, after grabbing a bunch of updates and attempting to reboot, I got a "Windows cannot boot because the following file is missing" (and I'm just paraphrasing because it was at least a few months ago)... and IIRC, the file in question was some DLL or something (a config.-something). Well, anyway, it prompted me at the time to foolishly run out and buy them a new harddrive and in the process accidentally destroying any backups they had of... well, everything... I won't get into that now.

So anyway, the last time I debugged it I got it down as far as a bad PSU (which thanks to a co-worker buddy who had an old derelict lying around, I got to replace for free). And then the following morning I narrowed the problem still further to faulty RAM (at least I suspect it of being faulty because as soon as I pulled it, the system booted without any further problems).

Now we're about a month since the last time I looked at that damn thing... and it's got that "missing file" problem again. And since it's Thursday, I'm assuming that some time earlier today, WinXP attempted to update itself and something (again) corrupted the system files.

And since I'm no tech support specialist, I can't really talk my technically-challenged parents through running the Windows setup... In fact, I'm kind of toying with the idea of buying a new PC (for myself) and giving away the one I'm typing this on right now to them. Because really, in its 7 year history, this PC has never had any of the problems they've had with theirs.

3 comments:

Anonymous said...

Ah... the many things that make you go "hmmm" I never saw this one before so who knows why it is doing it. Could be for any reason. Backup everything, and reformat it. Try slipstreaming the fixes into the main install disc: http://www.ryanvm.net/msfn/updatepack.html
It might help.

Ben-Ohki said...

I dunno know, man, this seems to be a recurring problem, is what I mean. That is, following the previous incident I did a reformat and fresh reinstall already. You think I should redo the slipstream with the latest updates maybe?
And don't forget, as I was saying, the hardware itself is suspect. Oh well... better them than me. :/

Anonymous said...

LOL! Ya, it's so hard to know what the problem is, start be installing the latest drivers, if it's still messed up, you can try to redo the slipstream or wait until the update is out for the slipstream. Maybe run a registry cleaner http://www.wisecleaner.com/