Can an illegal copy of windows XP damage a computer?

[Foz2001]

Here's my situation.

I'm trying to help a family with 2 computers. They had a legitimate copy of windows xp running since the computers were built, but about 3 months ago they had a friend come in and put a "windows xp performance edition" copy on both machines because both computers needed a format and they no longer had the original xp discs. Anyways, both machines ran fine for about a month or so. Now all of a sudden they both wont work. I havnt physically looked at them, because i'm an hour away and want to get as much knowledge as I can before I get there.

Specs:

Both Socket A 2400+'s
512MB in one, 1GB in other
Abit mobos I believe.

First computers problem:
Computer will not turn on. The lights flash, fans twitch, and thats it.

My guess - PSU

Second computers problem:
Computer turns on, it will not post.

My guess - mobo/vid card


They are convinced that the illegal copy of windows has caused this because both computers failed within about 2 weeks of each other. I'm quite convinced its a coincidence. However the First computer has a fairly new PSU, because I put it in, so it is very strange for it to not power up.


So is it possible for software to cause hardware to fail?


Any info would be great on this situation. Also a legitimate copy of windows will be installed once I get the computers working again.


Foz

[bbz_Ghost]

Aside from the question itself, the issues you just described sound more like hardware issues to me. The only thing I could fathom would be caused by the bogus XP edition would possibly be some kind of CMOS virus (unlikely in this day and age), so I'd start suspecting the hardware going bad. Seems a bit odd that two machines would drop at roughly the same time, especially using the same OS, but even so...

They're not even POSTing so that's all hardware. After POST is when the handoff from BIOS control to software control (aka the OS on the drive) happens, and they're not getting anywhere near that point.

One thing to try as it's been useful to me over the decades:

Take all the hardware out of each machine, literally, and rebuild it. Reseat the CPU if possible in the socket, reseat the RAM in their sockets, even switching them around a bit, and reseat any PCI/AGP/PCI-E cards they have also. Believe it or not, sometimes this fixes a shitload of weird random screwball issues that just appear outta nowhere.

[Foz2001]

Yah ill definetely have to do that if its not something simple such as a loose card, thanks for the tip.

[leSLIe]

software cannot cause hardware damage, in your case it´s just an ugly coincidence. there are a LOT of variables that have to converge in order for a "bios virus" to work.

[Foz2001]

ok so after being on the phone trying to diagnose it ive come to this...

the second computer which powered on - the heatsink for the motherboard was laying at the bottom of the computer, so my guess is the mobo overheated, and is shot. How vital are those little heatsinks ?


edit- MODS - feel free to move this thread at this point if you want.

[bbz_Ghost]

hehe

It's pretty important if one was attached by default. It could be a situation where the thermal compound just gave out due to age and the heatsink fell off. If that's the case, and the heatsink was off for a good length of time, yes it's possible the chipset could have burned itself out. :(

[Slade]

if the northbridge toasted, it's done.

software doesn't destroy hardware

[leSLIe]

software doesn't destroy hardware

unless it´s an illegal copy of Windows ME :D

[GORANKAR]

unless it´s an illegal copy of Windows ME :D

Or even a legal copy of WinME for that matter.
Though only indirectly. Me taking the hammer to the computer in a fit of homicidal rage is directly what destroyed the hardware. Win ME just caused the homicidal rage. :p

There were some viruses that can kill your bios, or flash the firmware of a hard/cd/dvd drive,(rendering them useless). Have not seen an example of those in a long time though.

[Whatsisname]

generally speaking yes http://en.wikipedia.org/wiki/Halt_and_Catch_Fire

if the northbridge toasted, it's done.

software doesn't destroy hardware

[Finn]

The windows could have damaged hardware if the 'performance edition' meant whoever installed it also overclocked the computers without sufficient cooling and/or subquality parts.

[leSLIe]

Or even a legal copy of WinME for that matter.
Though only indirectly. Me taking the hammer to the computer in a fit of homicidal rage is directly what destroyed the hardware. Win ME just caused the homicidal rage. :p


oh yes!! :D

[eeyrjmr]

software cannot cause hardware damage, in your case it´s just an ugly coincidence. there are a LOT of variables that have to converge in order for a "bios virus" to work.

software CAN damage hardware. IF drivers are very bad they will damage the hardware they are driving

the hacked display drivers can put a monitor out of its operating range and not only burn out the monitor BUT take out the GFX card. Likewise bad drivers can stop fans in a system and cause the system to burn itself out

The most well know is that copy-protection for games that damaged optical drives

please don't spread FUD, or in this case false-optimism

[leSLIe]

The most well know is that copy-protection for games that damaged optical drives


what? i've heard starforce was really nasty, but to the point that it actually causes harm to your drives? i don't see how :confused:

[Slade]

as I recall if you try to force a monitor OUT of it's operating range, the monitor kinda says "Monitor out of range". Most simply refuse to display anything if the signal is incorrect.

as far as software really messing it up, nothing that serious is out there for some poor joe to get on their system and mess it up. You'd have to WILLFULLY want to mess your hardware to get it wrecked that bad.

In theory with the nvidia boards in particular, if one were to write software to tap into the clockgen of chipsets and say spike the voltage (if that's even directly accessible), that could happen. The problem is getting the program to continue running to cause the damage, most systems would just lock and do nothing.