EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

07.23.10

Microsoft Windows BSOD Caused Deepwater Horizon Disaster

Posted in Microsoft, Windows at 1:17 pm by Dr. Roy Schestowitz

Deepwater Horizon oil spill

Summary: Blue Screen of Death caused a crucial computer system not to prevent the biggest disaster of the 21st century

Who ever said that use of Microsoft products does not cause death? We last heard it hours ago in response to our latest post about Russia. According to this new report from the New York Times:

The emergency alarm on the Deepwater Horizon was not fully activated on the day the oil rig caught fire and exploded, triggering the massive spill in the Gulf of Mexico, a rig worker on Friday told a government panel investigating the accident.

[...]

Problems existed from the beginning of drilling the well, Mr. Williams said. For months, the computer system had been locking up, producing what the crew deemed the “blue screen of death.”

“For those not familiar with the term, BSOD stands for the Blue Screen of Death, made famous by Bill Gates,” wrote our reader. Bill Gates is also a BP investor [1, 2, 3].

Sarcastically our reader adds: “I wonder will a future inquiry find UNIX was at fault.”

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

9 Comments

  1. satipera said,

    July 23, 2010 at 4:18 pm

    Gravatar

    Using Microsoft software for safety critical applications is criminal negligence.

    Dr. Roy Schestowitz Reply:

    I know someone who suggests criminal prosecution either for those who choose Windows or those who make/sell Windows, but I don’t agree. Either way, I wrote about Microsoft’s deliberate/willful negligence in [1, 2, 3].

  2. twitter said,

    July 23, 2010 at 5:01 pm

    Gravatar

    This should be a special occasion to Call Out Windows. I’ve read several headlines about “bypassed safety systems” but did not realize that the system in question was bypassed because it was Windows and suffered from the usual Microsoft problems. As a Gulf Coast resident, I’m personally offended by this but not particularly surprised. Many in the press might not think it significant because there were so many bad decisions that BP made, but things might have been different if the alarm system had been working. Thanks for documenting it.

  3. twitter said,

    July 25, 2010 at 11:38 am

    Gravatar

    It turns out that the unreliable system is directly responsible for the most of the Deepwater Horizon deaths and could have prevented the accident if it had worked properly. The New York Times article requires a login, and transcripts won’t be available for three weeks. The New Orleans Times Picayune has this article describing the deaths caused by the alarm bypass. The relevant opinion and expert quotes are worth documenting here. The problem is not particular to the Deepwater Horizon, all of Transocean’s rigs have the same system and, of course, anywhere people use Windows for mission critical work they wastefully risk worker’s lives, public health and their own business.

    With the general alarm set to bypass, the rig’s one danger alarm never sounded, Transocean chief electronics technician Mike Williams testified. If it had, he said workers in the drilling area — the shaker room, the mud room, the pit and pump room — would have immediately evacuated. Several of the 11 workers killed in the explosion worked in those areas. [no one from these areas survived]

    … drilling area is extremely susceptible to fire if gas kicks up from the well, so the rooms are air tight, and control panels can be set to shut down if gas seeps in, but Williams testified that one such panel in the drilling shack was set to bypass.

    About five weeks before the accident, Williams was called to check on a computer system in the drill shack that was constantly on the fritz. Williams said the software was chronically bad, leaving a “blue screen of death” on the driller’s interface and often causing the driller to lose crucial data about what was going on in the well. Once, when the Deepwater Horizon was drilling a different well, the computer froze up and the rig took a kick of natural gas while the driller was looking at “erroneous data,” Williams said.

    the rig’s general alarm and indicator lights were set to “inhibited,” meaning they would record high gas levels or fire in a computer, but wouldn’t trigger any warning signals. “When I discovered they were inhibited a year ago I inquired why, and the explanation I got was that from the OIM (the top Transocean official on the rig) on down, they did not want people woken up at 3 a.m. due to false alarms,” said Williams … Williams said an emergency shutdown system, which was supposed to shut off the engines, didn’t trip, either. The engines ended up overspeeding by drawing power off the gas and Engine No. 3 exploded … Mark Hay, the Transocean senior subsea supervisor, set the control panel system to bypass its gas shutdown function, and when Williams questioned him, Hay said there was no point in Williams fixing it because none of the Transocean rigs use the safety system. … “Damn thing’s been in bypass for five years. Matter of fact, the entire (Transocean) fleet runs them in bypass”

    It is clear from Williams testimony that Windows was not up to the task and that this directly lead to the accident. The first warning workers got of gas in the drilling room was a generator overspeed and explosion, when a properly functioning system would have activated a warning alarm and shut equipment down. The system was bypassed because it was not reliable. Transocean issued a lame excuse for this negligence, calling the bypass standard industry practice. It may be true that other drillers take similar risks but that does not make it a good practice. There were many other mistakes made as documented by this overlapping article that documents damage to underwater equipment and four failed safety tests, but the explosion and fire itself may have been prevented if the alarm and shutdown system had worked reliably.

    Industry should purge itself of this unreliable and costly software.

    Dr. Roy Schestowitz Reply:

    A long thread that I saw earlier (initiated in a newsgroup in response to one article I wrote) noted that the software runs on Windows only. They run it on a flaky foundation.

    BP still has many platforms that run the same software, i.e. they can suffer BSODs that would multiply the scale of the existing disaster.

    BP must look at the platform it uses (you can read that in more than one way).

  4. FactBknown said,

    July 28, 2010 at 3:43 pm

    Gravatar

    First, I am not a big Microsoft lover. I have worked in the IT field for over 12 years and over that time, with 4 companies. Each company was predominantly Windows based. Grant you, none of them were in such an industry that could cause death if a system failed. However the fact is that Microsoft did not turn the Alarms off. They did not bypass the safety systems. Their software is dominated by errors, BSOD, hardware incompatibilities and etc… The fact is that though Microsoft is not the best and we would likely still have the issues if it had been a different OS. The fact is that someone at BP wanted the alarms off due to false alarms. That is when they need to have a strict on-call rotation that only one person is woke up and they can physically check the alarm. If it is needed then the others can be awaken. If it is in fact a false alarm, then reset it and go back to bed. Also, if they are getting BSODs, why is there not a backup alarm system or operating system? And why was the systems bypassed instead of being looked at by a tech or by Microsoft? It would be real sad if the BSOD was caused by a simple driver issue that could have been resolved easily. BSOD happens to everyone, but if it is a vital system then have a backup system. Sounds like someone took Out of Sight, Out of mind literally.

    Dr. Roy Schestowitz Reply:

    Based on some research I saw, the software in question only runs under Windows. It’s irresponsible to run such crucial systems on an operating system that’s largely rejected by stock exchanges/markets.

    I hope that lessons will be learned and weak links will be removed.

    twitter Reply:

    I like what Richard Stallman had to say about it,

    Managers careful about safety would have had the cause of the false alarms fixed. But that would have cost money, and they probably gave cost savings higher priority than safety.

    It is too bad that managers don’t understand that free software is cheaper from start to finish and start the migration efforts sooner than later. People making these systems must understand things by now but that won’t replace old systems that are still in the field. The cost of not replacing the system in this case was obviously higher.

    Dr. Roy Schestowitz Reply:

    I guess the question is, what did he call “BP” this time? “Big Polluter” is his most common joke, but there are variations.

What Else is New


  1. Links 22/7/2014: Linux 3.16 RC 6, New UberStudent

    Links for the day



  2. Links 20/7/2014: Jolla in India, Mega Censored in Italy

    Links for the day



  3. Longtime Mono Booster Joins Microsoft-linked Xamarin

    Jo Shields almost joins Microsoft, settling instead for its proxy, Xamarin



  4. Linux Foundation Welcomes Patent Aggressor Red Bend Software

    The Linux Foundation's AllSeen Alliance welcomes as a member a company that uses software patents to sue Free/Open Source software



  5. Matt Levy From Patent Progress (and CCIA) Does Not Really Want Patent Progress

    Matthew ('Matt') Levy moved into a foe of patent progress last year, but he still runs a site calls Patent Progress, in which he diverts all attention to patent trolls (as large corporations such as Microsoft like to do)



  6. Attacking FOSS by Ignoring/Overlooking Issues With Proprietary Software

    The biasing strategy which continues to be used to demonise Free/Open Source software (FOSS) along with some new examples



  7. Links 19/7/2014: CRUX 3.1 is Out, CyanogenMod Competes With Google Now

    Links for the day



  8. Microsoft's Massive Layoffs Go Far Beyond Nokia; Nokia's Android Phones Axed by Microsoft's Elop

    Microsoft's rapid demise and permanent exit from Nokia's last remaining Linux platform (after Microsoft had killed two more)



  9. Patents on Software Already Being Invalidated in Courts Owing to SCOTUS Ruling on 'Abstract' Patents

    The Federal Circuit Appeals Court has just "invalidated a software patent for being overly abstract," says a patents expert



  10. OpenSUSE 'Community' is Crumbling, AttachMSFT Killed SUSE's Potential (Except as Microsoft Tax)

    Not much too see in the land of SUSE and Attachmate, or formerly the company known as Novell



  11. Links 18/7/2014: Slackware Turns 21, Spotify Switches to Ubuntu

    Links for the day



  12. Links 16/7/2014: Manjaro 0.8.10 Third Update, SIA Migrates to Red Hat

    Links for the day



  13. Microsoft's Latest Round of Massive/Bulk/Large-scale Layoffs

    Microsoft boosters are preparing 'damage control' pieces ahead of massive layoffs at Microsoft



  14. Secrecy Allows British Government to be Manipulated by Microsoft for Spyware Behind Closed Doors

    Dependence on malicious software from NSA ally Microsoft is highly dependent, at least in Britain, on government secrecy and vain refusal to comply with Freedom of Information (FOI) requests



  15. Software Patent Applications Already Being Rejected in the US Owing to SCOTUS Ruling, Some Patent Lawyers Are Fuming

    Good news on the software patents front as the USPTO starts rejecting software patent applications, based on patent lawyers' words



  16. Links 15/7/2014: New Plasma, Google Announces Project Zero

    Links for the day



  17. Interest in Free Software Coverage and 9 Months With Tux Machines

    Thoughts about the level of interest in Free/Open Source software (FOSS) and growth of at least some sites that focus on GNU/Linux



  18. White House Backs Away From Appointing Patents Zealot to Top USPTO Position

    Philip Johnson is no longer poised to become the Director of the USPTO, which is basically an establishment that provides protectionism to primarily US-based corporations



  19. Professor James Bessen Presents the Case Against Software Patents After Important SCOTUS Ruling

    The debate about software patents in the Unites States continues, with academia on one side and greedy patent lawyers on the other



  20. Software Patents Demising in the US as Microsoft Patent Attacks on Android/Linux Suffer a Huge Setback

    M-Cam's assessment of Microsoft's bundle of extortion (using software patents) shows toothlessness, irrespective of the SCOTUS decision to effectively annul "abstract" software patents



  21. Links 13/7/2014: KDE Activity Surge

    Links for the day



  22. Pro-Microsoft Spin in Microsoft-Funded News Networks

    The rogue media (misinformation) campaign of Microsoft benefits from networks which have been paid by Microsoft over the years



  23. Cronyism at Play: European Hostility Towards Free/Libre Software Despite Espionage and Moles

    Europe continues to be held hostage with back doors, lock-in, and massive payments to foreign powers, despite evidence that these powers are destructive and hostile



  24. Wirelessly-Controlled Contraceptives and Other Villainous Bill Gates Initiatives

    Remote controls for people's reproductive systems are now in the making and Bill Gates is a prominent investor in the technology



  25. Links 12/7/2014: CrossOver, New Wine

    Links for the day



  26. Links 10/7/2014: LXLE 14.04 in Headlines, Plasma 5

    Links for the day



  27. OpenDocument Format (ODF) Still Alive and Kicking

    Caligra, WebODF and various influential nations' departure from Microsoft Office will help famous projects such as OpenOffice.org and LibreOffice make ODF the only international standard for editable documents exchange



  28. The Effect of Corporate Media Bias: FOSS Demonisation and Microsoft Openwashing

    A set of very recent examples where the corporate press produces FOSS-hostile articles (or pro-Microsoft articles) by citing biased sources of convenience



  29. The NSA's Top (and First) PRISM Partner, Microsoft, Lies to Governments and Businesses as Office Gets Banned in China

    Developments in China reveal that security and privacy threats posed by reliance on Microsoft are so great that a ban becomes inevitable and continues to expand (Microsoft put on more and more block lists and blacklists)



  30. Microsoft's Propaganda Machine Tries to Shift Security Debate Amid Serious Catastrophes

    Observations and analysis of some recent deception in corporate news sites (like Condé Nasty), trying to pretend that Microsoft is secure, that Microsoft is pursuing security, and that FOSS and Android security or privacy are inherently poor


CoPilotCo

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

CoPilotCo

Recent Posts