Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Is Windows XP too old for my computer?

Oct 20, 2013 9:33AM PDT

I was one of the number of users who stuck with Windows XP when Windows Vista came out, and I still run that Operating System on my PC today.

But some time ago (a little less than 2 years ago) I gave my PC a near-complete hardware upgrade (about 90%, I replaced everything but the secondary hard drive), New Ram, New Motherboard, Processor, Power Supply and when I did that, the Technician who put the hardware in, got the drivers and Operating System set up, told me that I should refrain from further hardware upgrades, as it's getting to a point where Windows XP will not be able to run the hardware, even with the drivers, and also advised against unlocking all four of the processing cores, so for a long time, I ran on two processing cores instead of all fours, but not too long ago, it came to be that my PC had to be wiped, and being a 2D Artist and Graphic Designer who had obligations to meet, it had to be done quickly. When I powered on the computer the next time, it showed me all four cores were unlocked, I was still able to get into Windows and use the programs I often used before, but stability problems soon started arising, Programs would freeze, Windows wouldn't always read input such as mouse clicks, small to medium inconveniences. When my PC developed display problems, and I brought my tower into the shop, everything checked out physically, my two hard drives were given the all clear; my RAM, Motherboard and Power supply were not mentioned as factors, the problem was discovered to be unrelated to the tower, as I no longer have display issues after replacing the monitor.

But the stability problems remain, even after a wipe and a fresh install of Windows XP. We're all aware of people who get an Operating System that's too old for the hardware they run, but is it possible for the reverse to occur? That the Operating System I'm using is too old for the hardware I run and that an upgrade to Windows 7 will resolve this, or was the technician who installed my hardware out to lunch when he suggested this as a factor?

Hoping for a conclusive opinion

-Hannah

Discussion is locked

- Collapse -
Answer
Yes and no
Oct 20, 2013 10:09AM PDT

Yes and no. Essentially, the technician you're talking to is full of crap and you should take your business elsewhere.

If there is driver support for a given bit of hardware for an OS, that's the end of the story. I'm not sure where they were coming up with this nonsense about limiting the number of CPU cores and all of that either. There are a few, very specific, instances where you may want to do that, but not as a general rule certainly.

The stability problems you're encountering could be the result of any number of things, but not because of any particular age of the OS. As I said, as long as there are drivers for the hardware for that specific OS, that's all the more you need. It can certainly happen that you'll find hardware being made these days in which the manufacturer never bothered to make XP drivers. So in that case, XP would indeed be too old for the hardware. There's nothing really stopping them from making XP drivers if they wanted, but the XP market share is basically stagnant or declining and Microsoft is trying to push people off of that platform as fast as possible, so it doesn't make a lot of sense to spend a lot of resources developing XP drivers for newer hardware.

If the same technician who has been feeding you all of this utter nonsense is the same one who built your PC, I'd be inclined to think they just picked cheap/shoddy parts because they didn't know what they were doing. It's entirely possible they screwed something else up. If you've been taking this PC to the same person every time it's had an issue, I'd say it's time to get a second opinion. Until you know for sure what you have is fundamentally a software issue, upgrading to Windows 7 could just make matters even worse. Take the unit somewhere else to get a fresh set of eyes on it and see what that turns up because to put it rather bluntly, the one technician has been blowing a whole lot of smoke up your ****.

- Collapse -
You could be right, but...
Oct 20, 2013 5:19PM PDT

I think it's possible the guy (or myself) could be mistaken, but he doesn't intentionally mean to mislead me, I've known him for quite some time, he's not the lying type.

As for taking it to him each time there's an issue, I haven't done that the past two times, I went to someone else(Circumstances beyond my control), and they didn't do nearly as good a job as he did, he's at least three times the technicians they are.

As for the parts, I picked those out myself, I know they're compatible with each other, but hopefully they aren't shoddy >////>

- Collapse -
Regardless
Oct 20, 2013 11:23PM PDT

Regardless of whether he's deliberately lying to you or not, what cannot be denied is that he's one of those type who fancies they know a whole lot more than they actually do. Like the person who thinks they're some kind of master auto-mechanic because they could follow the instructions in a repair manual for changing the oil. These people are probably more dangerous than the average idiot who really doesn't know anything, but at least admits they don't know anything.

But with so little detail to work off of regarding what the one guy usually does that the others didn't, it's difficult to say for sure. We'd need more details on what the various places actually did. Someone like the guy you describe might think that registry cleaning programs are some great and glorious tool, never once stopping to ponder why Microsoft hasn't bothered to include such functionality into the OS for all these years. Not doing a little research to find out that Microsoft actually made the first registry cleaner, then quickly pulled it because they found it was causing problems. Not taking the time to put those two pieces together and draw the rather obvious conclusion.

Since this is a custom machine, that means most diagnostic tools won't really work and it's down to the drawn out and tedious method of testing everything one at a time.

So since you say you recently reinstalled the OS, that's where I'd start. Reinstall it again, making sure to format the drive along the way. Install only the bare minimum of programs. Get it up to SP3 and then all the updates after that, but install only the drivers and then the absolute bare minimum number of programs you need to be able to get by for about the next week. If the problems persist, you've narrowed it down to either hardware or some kind of issue with those specific programs you've installed. So assuming for example you usually use the full Adobe Creative Suite, but this week you could get away with only installing Photoshop, only install Photoshop. If you can go for long periods of time without issue, where you normally would have had issues, add one additional program and start the testing over again. Rinse and repeat until either everything is installed or you start having problems. If you're still getting issues, you're PROBABLY looking at a defective bit of hardware. So get yourself a copy of memtext86+ and let that run overnight. Even a single error is too much for RAM, so if you get any errors at all during your testing you'll need to test each memory module individually by physically removing the rest. If you find a defective one, send it in for a warranty replacement.

If the RAM checks out fine and you're still getting issues, you should remove any hardware from the system you don't absolutely need. Run like that for a week, see how things go. If they work well, add ONE piece of hardware back about every week and test in between. Same as with the software, rinse and repeat until you've either got every bit of hardware back into the unit and it works great or you isolate the problem component.

It's boring, it's tedious, but it's also the only way you're going to not just be fumbling around in the dark hoping you stumble across the solution by dumb luck. It's also ultimately less painful than dealing with the current crop of issues ad infinitum.

- Collapse -
Answer
Sure.
Oct 20, 2013 12:54PM PDT

I find USB 3.0 drivers to be rare to missing. Also, I can't count how many times folk ask why they can't install XP on a SATA HDD.

Maybe it's time has come when folk can't figure that out?
Bob

- Collapse -
*nod*
Oct 20, 2013 5:20PM PDT

I do pretty much plan to do just that, when I'm able.