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. How OSI Co-Founder Got Banned From the OSI's Mailing Lists (a Month After the Other Co-Founder Resigned in Protest in Those Mailing Lists, Bemoaning Attacks on Software Freedom)

    This post is not an endorsement of the message; its purpose is to show what was censored and let people decide for themselves if that merited a ban



  2. IRC Proceedings: Friday, February 28, 2020

    IRC logs for Friday, February 28, 2020



  3. Alexandre Oliva Against Bullying and Violence

    I was ready to come to a close of this series, but an urgent request I got takes priority over the last planned post in the series, now postponed



  4. Links 28/2/2020: Qt 5.15 Beta, UBports/Unity8 Now Lomiri, GCC 8.4 Release Candidate

    Links for the day



  5. Richard Stallman is Now Eligible for the FSF's Award

    To counter the impression that FSF leadership distances itself from the FSF's founder it can publicly display a healthy and cordial relationship with GNU's chief



  6. People Who Oppose Stallman Can be Rude and They Pick on People Who Merely Defend Stallman's Role at FSF

    Earlier this week I wrote about aggressive reactions I receive for my articles; here's one of them (minutes old)



  7. 3 Founders Out in 5 Months

    With OSI's co-founders both out (not long after the start of this year), as well as the founder of the FSF, one must ask who's left to lead the fight against proprietary software injustices



  8. Inside the Free Software Foundation (FSF) - Part II: The Majority of the Board Supports Richard Stallman

    It seems to have become somewhat fashionable separating high-profile projects and institutions from their founders; at the FSF, thankfully (at least for now), the founder still has a foothold



  9. IRC Proceedings: Thursday, February 27, 2020

    IRC logs for Thursday, February 27, 2020



  10. EUIPO and EPO Celebrate Corruption in Croatia

    The EPO returns to its corrupt roots of the Battistelli era even in the form of photo ops



  11. Death of the UPC (Unitary Patent) Confirmed by the British Government

    The lies about the UPC are repeatedly being called out as UPC disarray is confirmed by the spokesperson of Prime Minister Boris Johnson



  12. A Month After One OSI Co-Founder Resigns in the Mailing Lists Over OSI's Attacks on Software Freedom the Other OSI Co-Founder Gets Kicked Out for Speaking About It

    The 'cancel culture' seems to be canceling people who speak about software freedom, under the guise of the real motivation being manners (when one lashes out at those who attack Free software and free speech)



  13. Links 27/2/2020: LibreOffice 6.4.1, Collabora Office for Phones and Latte Dock 0.9.9

    Links for the day



  14. The Linux Foundation is Deeply Committed to Diversity and Inclusiveness (as Long as You Have Perfect Vision and Use 'Big Browsers' That Spy)

    The Linux Foundation's message of inclusiveness refers only to a particular kind of inclusiveness



  15. Inside the Free Software Foundation (FSF) - Part I: Year Zero

    People behind the ousting of Richard Stallman (or 'leaders of the coup' as some call them) want a fresh start; but they aren't starting what most FSF supporters have been led to believe



  16. Alexandre Oliva on Diversity Hypocrites

    "Some of them purport to be for inclusion and diversity, but won't hesitate to make fun of someone's poorly-disguised handicap."



  17. IRC Proceedings: Wednesday, February 26, 2020

    IRC logs for Wednesday, February 26, 2020



  18. Alexandre Oliva: Courage is Contagious

    Having a proposal rejected at a conference is nothing unusual, but the surrounding circumstances and the conflicting versions are.



  19. Links 26/2/2020: Cosmo Communicator 2-in-1, FSF Outlines Plans for Code Hosting

    Links for the day



  20. Reminder: At Linux Foundation in 2020 Three Board Members, Including the Vice Chair and Director at Large, Are Current or Past Microsoft Employees

    Sometimes the facts speak for themselves (or pictures speak louder than words)



  21. IRC Proceedings: Tuesday, February 25, 2020

    IRC logs for Tuesday, February 25, 2020



  22. Links 25/2/2020: MakuluLinux LinDoz and Manjaro 19.0 Released

    Links for the day



  23. FSF's Interim Co-President Alexandre Oliva on FSF Communication Policies

    Surely I, being acting president and then half-acting president, must suck as a manager. I probably do indeed, but it's not so simple.



  24. The EU's EUIPO Will Later Today Help the EPO (Run by EUIPO's Former Chief) Promote Illegal Software Patents

    Propaganda terms such as "intellectual property rights" and meaningless concepts like "technical effect" are being used to promote so-called 'computer-implemented inventions' (software patents by another name)



  25. Growing Acceptance That There's No Future to the UPC System and the Unitary Patent

    There are growing pains and more signs that even key elements of Team UPC move on, accepting the demise of the UPC



  26. Emulating the Linux Foundation's Business Model (Selling Influence)

    LibrePlanet sponsors are presented with benefits of offering money to the event (or to the FSF)



  27. Guest Article: LibrePlanet Attendees Should Demand a Partial Refund

    What we do know is — that the FSF is no longer “Free as in Speech!”



  28. IRC Proceedings: Monday, February 24, 2020

    IRC logs for Monday, February 24, 2020



  29. An FSF That Rejects Its Founder Would Not Remain FSF As We Once Knew It

    It's important to keep the FSF focused on its goals; that won't be achieved by expelling those who insist on these goals



  30. Links 24/2/2020: Linux 5.6 RC3, Netrunner 20.01, Google Summer of Code 2020 Mentoring Organisations Announced

    Links for the day


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

Recent Posts