Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

salvorhardin

(9,995 posts)
Sun Sep 2, 2012, 09:01 AM Sep 2012

Your PC Just Crashed? Don’t Blame Microsoft

When computers crash, buggy software usually gets the blame. But over the past few years, computer scientists have started taking a hard look at hardware failures, and they’re learning that another type of problem pops up more often than many people realize. That’s right: hardware bugs.

Chipmakers work hard to make sure their products are tested and working properly before they ship, but they don’t like to talk about the fact that it can be a struggle to keep the chips working accurately over time. Since the late 1970s, the industry has known that obscure hardware problems could cause bits to flip inside microprocessor transistors. As transistors have shrunk in size, it’s become even easier for stray particles to bash into them and flip their state. Industry insiders call this the “soft error” problem, and it’s something that’s going to become more pronounced as we move to smaller and smaller transistors where even a single particle can do much more damage.

But these “soft errors” are only part of the problem. Over the past five years, a handful of researchers have taken a long hard look at some very large computing systems, and they’ve realized that in many cases, the computer hardware we use is just plain broken. Heat or manufacturing defects can cause components to wear out over time, leaving electrons leaking from one transistor to another, or channels on the chip that are designed to transmit current simply break down. These are the “hard errors.”

Full article: http://www.wired.com/wiredenterprise/2012/08/chip_errors/all
17 replies = new reply since forum marked as read
Highlight: NoneDon't highlight anything 5 newestHighlight 5 most recent replies
Your PC Just Crashed? Don’t Blame Microsoft (Original Post) salvorhardin Sep 2012 OP
Oh yes, it's not just Micro$oft, not by any means. bemildred Sep 2012 #1
Number 3 is incorrect.... whistler162 Sep 2012 #14
Bollocks. bemildred Sep 2012 #15
Do yourself a favor and get Sophos whistler162 Sep 2012 #16
I don't run Apple. bemildred Sep 2012 #17
a clean computer is a happy computer! madrchsod Sep 2012 #2
Yes, that's true salvorhardin Sep 2012 #5
Funny thing, you can leave Linux running for months without a reboot, add software, take 2on2u Sep 2012 #3
I have to reboot mine about twice a year (Ubuntu). bemildred Sep 2012 #6
Same thing with my iMac... awoke_in_2003 Sep 2012 #11
Sounds like propaganda designed to sell new hardware.... Scuba Sep 2012 #4
This isn't news Moral Compass Sep 2012 #7
To you and me maybe salvorhardin Sep 2012 #8
Yeah, people do not realize that "hardware" has lots of software in it. bemildred Sep 2012 #9
I agree, but let's get real here. longship Sep 2012 #10
I have to deal with XP at work... awoke_in_2003 Sep 2012 #12
It's the whole sloppy, sleazy culture surrounding Microsoft - not JUST Microsoft. kenny blankenship Sep 2012 #13

bemildred

(90,061 posts)
1. Oh yes, it's not just Micro$oft, not by any means.
Sun Sep 2, 2012, 09:22 AM
Sep 2012

They (M$) have a big problem with their open hardware platform, because they do not control everything in the box, so some 3rd party vendor can crash the box and you have no clue why. I used to spend days chasing down patches and fixing bugs getting homebrew Windoze boxes to run with cheap hardware.

With open source, you can throw all that free communal labor at it and keep the problem under control, but in a for profit environment, the labor costs will kill you.

So you have three choices:

1.) Expensive, unreliable, insecure, buggy, labor intensive, and useful at the cost of lots of wasted time (M$/open hardware).

2.) Free, reliable, pretty secure, a little buggy, and generic: open source U*ix based systems/open hardware (some assembly may be required).

3.) Very expensive, pretty secure, very reliable, and very proprietary (Apple and lots of dead or obscure companies.)

 

whistler162

(11,155 posts)
14. Number 3 is incorrect....
Mon Sep 3, 2012, 09:34 AM
Sep 2012

Apple is insecure, INSTALL SOPHOS - http://www.sophos.com/en-us/products/free-tools/sophos-antivirus-for-mac-home-edition/reviews.aspx , unless you are talking about accessing the hardware for replacement then it is very secure. As for very reliable, its a intel based PC no more no less.

bemildred

(90,061 posts)
15. Bollocks.
Mon Sep 3, 2012, 10:39 AM
Sep 2012

Please see post #10 for a discussion of why Apple (OSX) is more "secure" than Windoze at the kernel level, and also the design flaws that will make it (Windoze) forever inferior until they are corrected, wihich Microsoft does seem to be working on, but it seems to be a two steps forward one step back sort of thing. The war between marketing and engineering continues, you might say.

You are talking about a different issue: network security, where the situation is more similar across platforms, and much depends on the net applications in use, over which there is poorer control.

The issue under discussion was not hardware, but control of the hardware. Apple is a closed hardware platform. You buy Apples from Apple. You can buy PCs from anybody or make your own, and then try to run Windoze on it.

 

whistler162

(11,155 posts)
16. Do yourself a favor and get Sophos
Mon Sep 3, 2012, 11:24 AM
Sep 2012

or any other free anti-virus for OSX. Your misbelief that it is more secure is one of the biggest security flaws in OSX.

bemildred

(90,061 posts)
17. I don't run Apple.
Mon Sep 3, 2012, 12:23 PM
Sep 2012

I run PCs with FreeBSD, Ubuntu, Windoze, depending on the need. Used to work with all sorts of shit.

OSX is based on one of the old BSDs, and I am not giving any 3rd party software root privileges on a Unix box unless I know a hell of a lot about it, preferably with source code.

madrchsod

(58,162 posts)
2. a clean computer is a happy computer!
Sun Sep 2, 2012, 09:23 AM
Sep 2012

people do not realize who much dust is inside thier computer. heat sinks do not work if they are covered with dust

salvorhardin

(9,995 posts)
5. Yes, that's true
Sun Sep 2, 2012, 09:35 AM
Sep 2012

However, even perfectly maintained computers are experiencing hardware errors. It's a side effect of taking chip dies ever smaller such that even a stray cosmic ray can flip bits.

 

2on2u

(1,843 posts)
3. Funny thing, you can leave Linux running for months without a reboot, add software, take
Sun Sep 2, 2012, 09:27 AM
Sep 2012

software out, tweak, untweak blah blah and NEVER see it hiccup.

bemildred

(90,061 posts)
6. I have to reboot mine about twice a year (Ubuntu).
Sun Sep 2, 2012, 09:40 AM
Sep 2012

Sometimes more when patches are applied that require it.

Occasionally I have to restart Firefox or what have you. FreeBSD was better, or the propietary Unix boxes, which was why they were/are so popular as net servers.

 

Scuba

(53,475 posts)
4. Sounds like propaganda designed to sell new hardware....
Sun Sep 2, 2012, 09:34 AM
Sep 2012

... I've seen a few computers for over 20 years without problems.

Moral Compass

(1,524 posts)
7. This isn't news
Sun Sep 2, 2012, 09:46 AM
Sep 2012

Anyone that has spent any time around computing/networking hardware of any kind knows that often it is the hardware not the software that causes crashes and instability. Nothing new about this.

salvorhardin

(9,995 posts)
8. To you and me maybe
Sun Sep 2, 2012, 10:43 AM
Sep 2012

I think most people though think of hardware as pure and inviolate. There is the question too of whether this is becoming more common as chip dies continue to shrink.

bemildred

(90,061 posts)
9. Yeah, people do not realize that "hardware" has lots of software in it.
Sun Sep 2, 2012, 10:53 AM
Sep 2012

The think of it as being mechanical.

longship

(40,416 posts)
10. I agree, but let's get real here.
Sun Sep 2, 2012, 11:11 AM
Sep 2012

The Microsoft problem is how it handles hardware failures, or program failures. Even many simple software upgrades on M$ requires a complete reboot. That is because a huge amount of the user interface is intertwined with the Windows kernel.

This is a huge engineering mistake which makes Windows operations susceptible to failure at the kernel level due to bugs in user level software. That's the origin of the cursed BSOD that plagued Windows for years. I understand this is now better than it was, and that's good for Windows users everywhere. Unix (and OS X, AFAIK) separate the UI and kernel, so when a program fails, it almost never takes down the kernel. In my experience, it has never happened after over 15 years of Linux use.

Every crash I have experienced on Linux was a direct cause of a hardware failure, usually a hard drive, so that is an issue that any OS has. Maybe the PC platform is part of the issue here, but I have had many PC's over the years and find them to be stable, even when I run them as servers running 24/7, even for years, rebooting only for kernel upgrades.

These are my experiences. I understand Windows advocates arguments. Some of them are valid, but as a geek I still don't want a proprietary OS on my machines. Windows makes it extraordinarily difficult to change things M$ doesn't want you to change. And Windows has a history of forcing you to upgrade hardware when new releases come out, and upgrade expensive software when new releases come out. That's not nice.

 

awoke_in_2003

(34,582 posts)
12. I have to deal with XP at work...
Sun Sep 2, 2012, 04:08 PM
Sep 2012

I hate it when a program locks up the computer, you open task manager to kill the program, and Windows tells you it can't stop the program. Why the hell can an operating system not kill a program? Guess I am spoiled from my Unix, Linux, and Apple time.

kenny blankenship

(15,689 posts)
13. It's the whole sloppy, sleazy culture surrounding Microsoft - not JUST Microsoft.
Sun Sep 2, 2012, 07:18 PM
Sep 2012

The culture wherein users are treated like cattle and prodded to click-through licensing agreements on their way through the front gates of the abbatoir, and where you can't tell where the kernel ends and userland crap begins, and the line separating "essential apps" from spyware and even straight up trojan horses is never fixed, and the natives have lived with this nightmare so long they think it's a natural and invevitable situation, which they mutely accept just like their Windows PCs slowing to a useless crawl within a couple of years of purchase from all the accumulated shitware clogging their systems. But that's the culture which they've created and encouraged. So yeah, I will blame Microsoft. I will also blame Republican and Democratic Administrations for not enforcing antitrust laws. But they do what they're paid to do, and the source of that bribe money is ultimately the same fountain of shit on a silicon chip from Seattle.

Latest Discussions»Issue Forums»Editorials & Other Articles»Your PC Just Crashed? Don...