C++ Program physically destroys computer

[bubbleboys]

I've been searching the internet for a while trying to find out how this is possible. My friend was programming in C++ and somehow messed with pointers or something like that.

Some of the stuff that happened after she ran her program (it was a programming project)

All her keys were randomized, some spouted the ABCs, some spouted out the less often used characters

Her computer immediately started overheating. Her computer literally started smoking within 5 minutes i believe.

My question is, how is it possible for a program to physically destroy a computer. Aren't the controls for the cooling fan, etc. protected or just plain simply built right into the motherboard or BIOS?

Thanks

P.S. I never managed to get a copy of the program from my friend seeing as how they're computer got destroyed.

[Jayzee]

I suppose that software was not run under WinXP or any kind of protected environment... I've done same kind of software once in C++ in DOS environment.

What I did was basicly send random data to random ports (outp function).. Screen started flickering, then eventually blanked and computer shutted down.. When I started it BIOS was totaly ****ed up, password was gone, settings were all wrong and computer worked at 70% of it's previous speed. Lucky for me it was school computer... :p

Function which you ask about (fan speed etc.) I think are not protected in any matter by OS, but rather controlled by some registers in CPU.

[ThunderRiver]

Interesting. So far, I haven't managed to use C++ for any real damages yet.

I didn't think it was possible because it is quite a high level language anyway. Who could have thought a high level language could do so much damages?

[tx83]

Look, your friend lies. It is impossible our days to destroy physically a computer with a C++ software (in the way you describe it). However, it was possible long ago (before 1992), when a virus spreaded and destroyed some bioses that weren't protected at this time.

Our days, it is absolutely impossible. The motherboard controls how much power is sent on every parts of the machine (the miracle of ATX). The mother board even controls when the power supply powers on or off. Even Windows can't bypass this protection.

There are some motherboards manufacturers that distributes overclocking softwares. These, often, can control how much voltage is given to the CPU or the Memory. The way they do this is by using assembly call to the

bios with a key to unprotect. The protection is different for every type of motherboard, and is closed source

most of the time. When it is released publicly, you must know, that the BIOS makes a validation everytime you

adjust the voltage, so you can't give more then 10 % to 20 % more power to a part (depending on the manufacturer), the bios will not accept it and the change will not occur if it is not in this range.

So, is a C++ program able to destroy one piece of hardware ? I would say it is possible if you play too much with the voltages. BUT, it is absolutely impossible to make it explode or even make it smoke. The BIOS protection prevents going over a certain temperature (it would power off the computer). If the computer started smoking, the problem comes from elsewhere. Maybe the motherboard was directly screwed on the case (you must always use little pins that prevent the motherboard from touching directly to the case).

[THE BAT]

I suppose that software was not run under WinXP or any kind of protected environment... I've done same kind of software once in C++ in DOS environment.

What I did was basicly send random data to random ports (outp function).. Screen started flickering, then eventually blanked and computer shutted down.. When I started it BIOS was totaly ****ed up, password was gone, settings were all wrong and computer worked at 70% of it's previous speed. Lucky for me it was school computer...  :p

Function which you ask about (fan speed etc.) I think are not protected in any matter by OS, but rather controlled by some registers in CPU.

585972690[/snapback]

yes, i think that too

in the past, i saw some program do this

but it can't do anything on Windows XP and other

[GreenMartian]

Found these simple for-printf code that can give you a nice blue screen of dread a few years back. Used to work in Win95, and surprisingly enough - XP. Works for most (if not all) 32-bit compilers in windows (tried on borland, ms, and gcc)

Yeah, i bsod-ed my own comp a few times... just for the sake of curiosity. :unsure: I've yet to see code that could affect hardware functions directly lately (At least not since my assembly days in DOS). But i remember a friend had a toshiba laptop a couple years ago that had this software to change the bios password, and some other bios stuff...

#include <stdio.h>
int main(void) {
  for (;;) {
  printf(" \t\b\b\b\b\b\b");
  }
  return 0;
}

PS: Seems harmless enough? Go ahead. You've been warned. :devil:

[Malisk]

SpeedFan is an example of a software where you can directly manipulate fan speeds, or turn them off if you wish, and it runs just fine under Windows XP. So if you support the motherboards you can clearly turn off all/most fans in the computer automatically without the user having to know anything. However, as others have said, your BIOS should kick in later, or even the CPU shutting down itself if it gets bad enough and you haven't configured CPU throttling/warnings in the BIOS (this isn't something that's always done).

I didn't think it was possible because it is quite a high level language anyway. Who could have thought a high level language could do so much damages?

C++ isn't that high level, and you can even program assembler in it with asm {} clauses. But even without doing that, C++ is fully usable to write e.g. device drivers with and in these cases bad pointers or other things can really mess things up. :)

Edited May 26, 2005 by Jugalator

[bubbleboys]

Look, your friend lies. It is impossible our days to destroy physically a computer with a C++ software (in the way you describe it). However, it was possible long ago (before 1992), when a virus spreaded and destroyed some bioses that weren't protected at this time.

Our days, it is absolutely impossible. The motherboard controls how much power is sent on every parts of the machine (the miracle of ATX). The mother board even controls when the power supply powers on or off. Even Windows can't bypass this protection.

There are some motherboards manufacturers that distributes overclocking softwares. These, often, can control how much voltage is given to the CPU or the Memory. The way they do this is by using assembly call to the

bios with a key to unprotect. The protection is different for every type of motherboard, and is closed source

most of the time. When it is released publicly, you must know, that the BIOS makes a validation everytime you

adjust the voltage, so you can't give more then 10 % to 20 % more power to a part (depending on the manufacturer), the bios will not accept it and the change will not occur if it is not in this range.

So, is a C++ program able to destroy one piece of hardware ? I would say it is possible if you play too much with the voltages. BUT, it is absolutely impossible to make it explode or even make it smoke. The BIOS protection prevents going over a certain temperature (it would power off the computer). If the computer started smoking, the problem comes from elsewhere. Maybe the motherboard was directly screwed on the case (you must always use little pins that prevent the motherboard from touching directly to the case).

585972735[/snapback]

my friend wasn't lying. I saw the computer after it was destroyed. Plus they have no reason whatsoever to lie. Lie for an interesting story, no, she had more than enough interesting stories. She ran the program on Windows XP, by the way. The maker of the computer was Sony, it was a laptop.

Like I said before, this is what really baffles me. How does a computer overheat from a program? (And don't try to work off the lieing angle) My friend still has the destroyed computer. One of these days, I'm going to get that hard drive and get the contents off it. In the mean time, I'm hoping some of you could provide a definitive answer.

Perhaps there is a problem with the BIOS on that particular motherboard that Sony failed to detect and she accidentally stumbled across it.

[bubbleboys]

Now that I think about it, BIOSs can be updated to a certain extent, right? I'm not sure how far you're allowed to edit the BIOS before you need to send it to a manufacturer to update. Maybe her program edited the BIOS but still stayed in the bounds.

Just a theory.

Just to answer any extra questions. The computer merely smoked, it didn't explode. She never tampered with the hardware of the computer. I mean it's a laptop, you can't really do all that much if you open it up.

[shihchiun]

If the computer was destroyed from heat, it probably had a heat problem to begin with. The program or wahtever it was just caused high CPU usage, which in turn caused more heat, and if the heatsink was unable to cope with the heat the computer either shut off or died.

[ShmengeTravel]

Some motherboards allow you to overclock from within windows. It could've been one of two things. Either the program she was making caused her laptop to just overheat at stock temps, or the program could've somehow actually overclocked the CPU to the point of no return. I'm not sure what intel boards can do this, I am familiar with nvidia-based chipsets having such features.

[bkellner]

I'd say yes it is possible. But the program most likely ran commands to the hardware to cause it to overheat. Stop fans and overclock, or whatever.

[Kestrel]

Total BS.

[Andareed]

You can write a kernel driver to do anything windows does. So the question should be if the processor allows such action.

[nomis_nehc]

heh, i think your friend is bs'ing too. from what i know of c++, it doesn't seem possible today.

[azcodemonkey]

It's coincidence.

[bubbleboys]

heh, i think your friend is bs'ing too. from what i know of c++, it doesn't seem possible today.

585974791[/snapback]

may seem impossible but think about computers. The stupidest retard (no offense to them) is still smarter than the world's smartest computer, even that Honda robot. Do you know why? Because a computer lacks any common sense and doesn't assume what you want. It's quite possible that in programming the BIOS, the programmers overlooked a special case scenario which normally doesn't happen.

Before we start saying that all these programmers have master's in yada yada, they're still human and by nature, they will naturally assume the computer knows what they want and will do that.

When I go off to college, my friend will be relatively close so I'll see if I can grab the laptop's hard drive supposing it wasn't damaged too badly. But rest assured, my friend is no BSing and neither am I.

[Kestrel]

may seem impossible but think about computers.  The stupidest retard (no offense to them) is still smarter than the world's smartest computer, even that Honda robot.  Do you know why?  Because a computer lacks any common sense and doesn't assume what you want.  It's quite possible that in programming the BIOS, the programmers overlooked a special case scenario which normally doesn't happen.

Before we start saying that all these programmers have master's in yada yada, they're still human and by nature, they will naturally assume the computer knows what they want and will do that.

When I go off to college, my friend will be relatively close so I'll see if I can grab the laptop's hard drive supposing it wasn't damaged too badly.  But rest assured, my friend is no BSing and neither am I.

585975135[/snapback]

You have a somewhat simplistic view of modern day computers. In the past there have been design flaws (or simply insufficient safeguards) that allowed physical damage (prime example.... setting the refresh rate of a monitor too high) but those days are long past unless you're talking about some very old or some very esoteric computer equipment.

In this case, either your friend is BS'ing YOU, YOU are BS'ing US or, as Weenur pointed out, it's coincidence.

[neowin_hipster]

Well it's entirely possible to access registers on your chipset (and just about any other device). For example, on VIA KT266A and KT333 systems you can enable two flip-flops that enable the "halt" instruction for the CPU. This is disabled by the bios on boot probably because this feature wasn't bug-free. Depending on the quality of the hardware it could be possible to make things burn and fry. For example, if two pins are connected and they both try to drive a signal (let's say pin a is a 1 and pin b is a 0) then we could have some problems.

It is highly unlikely though. Safeguards are built into standards and other safeguards are are put in place without even thinking any more. Engineers do get lazy though especially when managers are bitching about product releases.

[Ultra Frosty]

You can write a kernel driver to do anything windows does. So the question should be if the processor allows such action.

585974781[/snapback]

You can only write a kernel mode application by getting a special SDK from microsoft, which you have to sign a license agreement in writing, in Redmond. The DDK that you can get for free can only make device drivers, in which case still cannot damage the system even if malprogramed because Windows still has total control over the system.

In NT (NT, 2000, XP, 2003, Longhorn), you cannot do such, as the OS is in protected mode which means that you cannot access physical memory thru your apps, and there is not bug in this. You cannot access any of the stuff that the OS can (BIOS, chipset, raw hardware access), unless you have a kernel mode application. It is much more complicated than I can explain to someone who thinks C++ on WinXP can destroy a computer, so I will leave it at that.

[MrA]

You can only write a kernel mode application by getting a special SDK from microsoft, which you have to sign a license agreement in writing, in Redmond. The DDK that you can get for free can only make device drivers, in which case still cannot damage the system even if malprogramed because Windows still has total control over the system.

In NT (NT, 2000, XP, 2003, Longhorn), you cannot do such, as the OS is in protected mode which means that you cannot access physical memory thru your apps, and there is not bug in this. You cannot access any of the stuff that the OS can (BIOS, chipset, raw hardware access), unless you have a kernel mode application. It is much more complicated than I can explain to someone who thinks C++ on WinXP can destroy a computer, so I will leave it at that.

585981996[/snapback]

But AFAIK, windows device drivers (made using the DDK) run in ring 0, just like the kernel and so you can do many stupid things like change the PDBR or IDT entries.

[UnnamedStone]

lol hardware is not designed to do anything you want

Bios programming is possible if you allow it

This is a sample of bios programming.

http://www.symantec.com/avcenter/venc/data/cih.html

[jokeripa]

may seem impossible but think about computers.  The stupidest retard (no offense to them) is still smarter than the world's smartest computer, even that Honda robot.  Do you know why?  Because a computer lacks any common sense and doesn't assume what you want.

retards have common sense?