Scientists develop computer that never crashes

Define "never crashes"... We have had the ability to create systems free of deadlock for a long time. Do you think a space agency would send anything into space that has the ability to deadlock and freeze up? I mean, the London guys took a slightly different approach but this article needs to take into account the current state of art.
 
Yes, *nix computers crash. But at least I know why they crash - me. Both my Windows and Linux experiences are frought with deadlocks that require the use of the Big Shiny Button to recover, but the Linux crashes usually immediately follow my entering a wonky command or trying something outside the box. Windows, on the same hardware, explodes randomly and gives me nothing human-readable to troubleshoot the issue.

For reference, I've locked up a Ti-83 Plus to the point that the batteries had to come out.
 
Never say never! I dare them to give that computer to my sister. It will crash in seconds!
 
Bethesda develops an open world game for the uncrashable computer. Game CTDs within an hour.

In all seriousness though, I find it hard to believe, regardless of whatever methodology they have behind it, there's no way there's a system to ensure a computer will never crash. To say otherwise is to grossly underestimate the capabilities of human stupidity.

What is so hard to believe? Unless something goes wrong with the rom. Maybe servers would be really interested in this.

Because no matter how flawless hardware may be, software will always have bugs
 
In order for this computer to never crash, it should never be powered on, or never connected to the internet, infected by installing windows, and remain free of human interaction.
 
I guess the best verbage that you could use is "that it has never crashed since powering it up". That would be a more accurate statement for them. Its just sad that all the ney sayers are jumping on them for ONE WORD!! Provided that it hasnt crashed since powering on, it stands to reason that with regular use that it prolly wouldnt crash NORMALLY. That in and of itself is pretty impresive.
 
If a computer crashes, most of the time it is because it was badly programmed.
If you let 2 computers calculate the same instructions they'll both crash.

If you want to avoid crashes due to hardware faults, you can allready implement VMware Vmotion stuff or Oracle RAC, etc...

Could have missed the point here
My thoughts too... how many crashes are *not* from bad hardware/bad writes to memory? I would think *most*? Sounds like a load of crap to me...
 
Oh come on...! My comp never crashes. I DON'T USE M$OFT WINDOWS!!!

Mine never crashes either! Haven't had a crash in the last few years that I even remember when it was. I use Windows 7/8. :)

Same here. I have never had a single crash on my Windows 7 and 8. Methinks Guest must be using old Windows versions (I.e. Windows 95/98/ME).

Same again. Since XP, Windows has been very stable.
 
This solution is both a hardware and a software solution. It is an alternate scheduling methodology: http://en.wikipedia.org/wiki/Scheduling_(computing

For reference, servers are slower than desktop computers, which are slower than for example a PS3. However, the accuracy of the CPU's is the other way around.

This proposed solution increases the 'accuracy', hence slowing it down.
 
None of my Windows 7 PCs have ever crashed.

I can't even recall the last time I saw a PC crash that wasn't caused by illegal software.
 
Back