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 19/8/2019: Another Linux 5.3 RC, OpenSUSE's Richard Brown Steps Down, Slackware Creates Patreon Page, Qt 6 Initiated

    Links for the day



  2. Speaking Truth to Monopolies (or How to Write Guest Posts in Techrights)

    We need to have more articles tackling the passage of all power — especially when it comes to software — to few large monopolies that disregard human rights or actively participate in their abolishment in the digital realm



  3. Guarding and Rescuing the FSF Titanic: Free as in Speech

    "While a new breed of so-called anarchists campaign against expression that even the state allows, people are also foolishly overplaying the relevance of the state to free speech issues -- as if it's not a freedom issue when a project is increasingly thought-policed, because the thought-policing isn't on a state level."



  4. Toxic Culture at Microsoft

    Racism, intolerance, sexism and bullying are rampant at Microsoft; but Microsoft would rather deflect/divert/sidetrack to Google and so-called 'GAFA'



  5. Guarding and Rescuing the FSF Titanic: Introduction

    "The FSF isn't just threatened, it will hit a large iceberg in the future that changes it permanently."



  6. Linux Journal and Linux.com Should Have Been Kept Going

    There's apparently no good explanation for the effective shutdown of Linux Journal and Linux.com; London Trust Media Holdings (LTMH), owner of Linux Journal, saw numbers improving and the Linux Foundation, steward of Linux.com, is loaded with money



  7. 2019 Microsoft Glossary

    How Microsoft internally interprets words that it is saying to the public and to the press



  8. 2019 Surveillance Glossary

    Distortion of technical and nontechnical terms in this day and age of '1984'



  9. Openwashing Report: It's Getting Worse, Fast. Everything is Apparently 'Open' Now Even Though It's Actually Proprietary.

    The latest examples (this past week's) of openwashing in the media, ranging from 5G to surveillance



  10. GitHub is a Dagger Inside Free/Open Source Software (FOSS); This is Why Microsoft Bought It

    A year later it seems pretty evident that Microsoft doesn’t like FOSS but is merely trying to control it, e.g. by buying millions of FOSS projects/repositories at the platform level (the above is what the Linux Foundation‘s Jim Zemlin said to Microsoft at their event while antitrust regulators were still assessing the proposed takeover)



  11. Microsoft Grows Within and Eats You From the Inside

    Microsoft entryism and other subversive tactics continue to threaten and sometimes successfully undermine the competition; Microsoft is nowadays doing that to core projects in the Free/Open Source software world



  12. Links 18/8/2019: New KNOPPIX and Emmabuntus Released

    Links for the day



  13. Links 17/8/2019: Unigine 2.9 and Git 2.23

    Links for the day



  14. Computer-Generated Patent Applications Show That Patents and Innovations Are Very Different Things

    The 'cheapening' of the concept of 'inventor' (or 'invention') undermines the whole foundation/basis of the patent system and deep inside patent law firms know it



  15. Concerns About IBM's Commitment to OpenSource.com After the Fall of Linux.com and Linux Journal

    The Web site OpenSource.com is over two decades old; in its current form it's about a decade old and it contains plenty of good articles, but will IBM think so too and, if so, will investment in the site carry on?



  16. Electronic Frontier Foundation Makes a Mistake by Giving Award to Microsoft Surveillance Person

    At age 30 (almost) the Electronic Frontier Foundation still campaigns for privacy; so why does it grant awards to enemies of privacy?



  17. Caturdays and Sundays at Techrights Will Get Busier

    Our plan to spend the weekends writing more articles about Software Freedom; it seems like a high-priority issue



  18. Why Techrights Doesn't Do Social Control Media

    Being managed and censored by platform owners (sometimes their shareholders) isn’t an alluring proposition when a site challenges conformist norms and the status quo; Techrights belongs in a platform of its own



  19. Patent Prosecution Highways and Examination Highways Are Dooming the EPO

    Speed is not a measure of quality; but today's EPO is just trying to get as much money as possible, as fast as possible (before the whole thing implodes)



  20. Software Patents Won't Come Back Just Because They're (Re)Framed/Branded as "HEY HI" (AI)

    The pattern we've been observing in recent years is, patent applicants and law firms simply rewrite applications to make these seem patent-eligible on the surface (owing to deliberate deception) and patent offices facilitate these loopholes in order to fake 'growth'



  21. IP Kat Pays the Price for Being a Megaphone of Team UPC

    The typical or the usual suspects speak out about the so-called 'prospects' (with delusions of inevitability) of the Unified Patent Court Agreement, neglecting to account for their own longterm credibility



  22. Links 17/8/2019: Wine 4.14 is Out, Debian Celebrates 26 years

    Links for the day



  23. Nothing Says 'New' Microsoft Like Microsoft Component Firmware Update (More Hardware Lock-in)

    Vicious old Microsoft is still trying to make life very hard for GNU/Linux, especially in the OEM channel/s, but we're somehow supposed to think that "Microsoft loves Linux"



  24. Bill Gates and His Special Relationship With Jeffrey Epstein Still Stirring Speculations

    Love of the "children" has long been a controversial subject for Microsoft; can Bill Gates and his connections to Jeffrey Epstein unearth some unsavoury secrets?



  25. Links 16/8/2019: Kdevops and QEMU 4.1

    Links for the day



  26. The EPO's War on the Convention on the Grant of European Patents 2000 (EPC 2000), Not Just Brexit, Kills the Unitary Patent (UP/UPC) and Dooms Justice

    Team UPC continues to ignore the utter failures that have led to lawlessness at the EPO, attributing the demise of the Unified Patent Court (UPC) to Brexit alone and pretending that it's not even a problem



  27. Links 15/8/2019: GNOME's Birthday, LLVM 9.0 RC2

    Links for the day



  28. 'Foundation' Hype Spreads in China

    Nonprofits seem to have become more of a business loophole than a charitable endeavour; the problem is, this erodes confidence in legitimate Free software and good causes



  29. Links Are Not Endorsements

    If the only alternative is to say nothing and link to nothing, then we have a problem; a lot of people still assume that because someone links to something it therefore implies agreement and consent



  30. The Myth of 'Professionalism'

    Perception of professionalism, a vehicle or a motivation for making Linux more 'corporate-friendly' (i.e. owned by corporations), is a growing threat to Software Freedom inside Linux, as well as freedom of speech and many other things


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