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 18/12/2014: LinuxQuestions.org Polls, Fedora for POWER

    Links for the day



  2. Links 16/12/2014: Google and ODF, Civilization: Beyond Earth Comes to GNU/Linux

    Links for the day



  3. Bill Gates' Pet Troll Intellectual Ventures is Collapsing as Founder Quits

    Intellectual Ventures founder leaves after an exceptionally large round of layoffs, despite [cref 77299 recent subsidies from Sony and Microsoft]



  4. Keeping Software Patents Out of Europe Following the Demise of Software Patents in the US

    Instability in the EPO seemingly prevents further expansion of patent scope, which is the subject of scrutiny of EPO staff



  5. Links 15/12/2014: OSI 2014 Annual Report, GPLv2 Court Test

    Links for the day



  6. Links 14/12/2014: Calligra 2.9 Beta, Krita 2.9 Beta

    Links for the day



  7. Software Patents Are Dying in the US, But Patent Lawyers Refuse to Admit It

    Patent lawyers continue to distort the reality of software patents' demise in the United States



  8. Links 13/12/2014: Android Wear “Lollipop”, European Commission and FOSS

    Links for the day



  9. Time to Take Microsoft Out of British Aviation Before Planes Crash Into Buildings

    London's mighty Heathrow Airport among those affected by a Microsoft-reliant air traffic control system which is not being able to properly recover from an outage, and not for the first time either



  10. News From France and Germany: Battistelli Under Fire, But Not Fired Yet, Just Firing His Opposition

    The régime headed by Benoît Battistelli and his criminal deputy continues to overthrow or pressure out everyone who is not 'loyal' to the régime



  11. Links 12/12/2014: Linux++, KDE Frameworks 5.5.0, Calligra 2.8.7

    Links for the day



  12. The USPTO is Broken: New Evidence Presented

    The scope of patents, as evidenced by some statistical figures and individual patents, shows that the USPTO is broken and must be reformed or dismantled



  13. US Patent Reform (on Trolls Only) More or Less Buried or Ineffective

    An update on efforts to reform the patent system in the United States, including the possibly imminent appointment of Michelle Lee to USPTO leadership role



  14. Software Patents in Canada Not Dead Yet

    Canada's patent status quo increasingly like that of the United States and Canadian giants like BlackBerry now pose a threat to software developers



  15. Dreaming of a Just Christmas: When a Third of EPO Walks Out to Revolt and European Judges Attack the EPO Over Abuses

    Information about the abuses of Battistelli et al. at the EPO are finally receiving wider coverage and increasing the strain on Battistelli's authoritarian reign



  16. Links 11/12/2014: Red Hat Enterprise Linux 7.1 Beta, Firefox 35 Plans

    Links for the day



  17. Ubuntu Core Announcement is Not About Microsoft and Hosting Ubuntu on Azure is Worse Than Stupid

    The power of media spin makes the idea of hosting Free software under the control of an NSA PRISM and back doors partner seem alluring



  18. France Gets Involved in Battistelli's Abuses in the EPO - Part XII (Updated)

    The EPO scandal has officially spilled over to France, where a French Senator got involved and starts asking serious questions



  19. Rolling of Heads Likely Imminent at EPO

    The European patent system is shaking as management breaks the rules, staff is protesting against the management every week, and charges of corruption resurface



  20. Links 11/12/2014: systemd 218, Empire Total War

    Links for the day



  21. Links 10/12/2014: Fedora 21, Ubuntu Core

    Links for the day



  22. Links 9/12/2014: Fedora 21 and Torture Report Are Out

    Links for the day



  23. Exclusive: The Enlarged Board of Appeal Complains About Battistelli's Corrupt Management to the Administrative Council (Updated)

    Text of the complaint from the Enlarged Board of Appeal (EBoA) reaches Techrights, demonstrating just how rampant the abuse in Battistelli's EPO has become



  24. Protests Against EPO Corruption Approach 1,000 in Attendance

    EPO staff at all levels is revolting against the management of the EPO, whose dismissal seems to be only a matter of time



  25. Links 9/12/2014: Greg Kroah-Hartman Interview, Fedora 21 Imminent

    Links for the day



  26. EPO Staff Protests Today and Protested Last Week, Targeting Corruption in the Institution

    PO staff is demonstrating against abuse by the management of the EPO, today we well as in prior days



  27. Links 7/12/2014: New Linux Release, Marines and Prisoners on GNU/Linux

    Links for the day



  28. EPO Scandal: Benoît Battistelli's Arrogance Recognised by European Delegations

    Battistelli’s Nixon moment and the evasive nature of his approach towards external delegations that are troubled by his behaviour



  29. CBS Brushing Aside and Away Microsoft's History of Blackmail and Bribes Against Linux

    Putting in context some of the poor reporting (or whitewash) regarding Microsoft's bribe (disguised as "partnership") to Barnes & Noble



  30. Links 7/12/2014: Typhoon Hagupit, AURORAGOLD

    Links for the day


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