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/4/2014: Slow Easter News Day

    Links for the day



  2. Links 18/4/2014: New KDE, Kubuntu, and More

    Links for the day



  3. Some Perspective on Heartbleed®

    Our views on the whole Heartbleed® bonanza, which seems like partly a PR stunt (for multiple stakeholders)



  4. Microsoft is Leaving Windows -- Including Vista 8.1 -- Vulnerable to Non-Government Crackers, Not Only to NSA

    Microsoft makes it ever more evident that securing users of Windows is not at all a priority, and perhaps not even a desire



  5. Links 17/4/2014: Android RDP, New Ubuntu, RHEL 7 Milestone

    Links for the day



  6. Racing to 1984: Mass Surveillance, Cracking, 'Targeted' Assassinations, and Illegal Torture

    Links for the day



  7. More Microsoft Subsidies to Patent Troll Intellectual Ventures

    Microsoft hands money to Bill Gates' close friend who is the world's largest patent troll



  8. Aiding Microsoft Under the Disguise of 'Pro-FOSS'

    Not everything which is FOSS necessary becomes, by virtue of existence, a positive contribution, as we are constantly reminded by projects that help proprietary software and/or restrictions get a strong grip on FOSS



  9. Links 16/4/2014: Red Hat PR, Ubuntu LTS Imminent

    Links for the day



  10. Links 15/4/2014: Lots of PCLinuxOS Releases, Ukraine Updates

    Links for the day



  11. Apple and Microsoft Actively Lobbying Against Patent Reform in the US

    Apple and Microsoft are reportedly intervening/interfering with US law in order to ensure that the law is Free/libre software-hostile



  12. Lawsuit by Microsoft Shareholder Targets Fine for Crimes Rather Than the Crimes Themselves

    A new lawsuit by a Microsoft shareholder shows everything that's wrong with today's model of accountability, where those who are responsible for crimes are accused of not avoiding fines rather than committing the crimes



  13. Public Institutions Must Dump PRISM-Associated Software

    Another reminder that taxpayers-subsidised services should refuse, as a matter of principle, to pay anything for -- let alone deploy -- proprietary software with back doors



  14. GNU/Linux News: The Opportunities Amid XP EOL

    Links for the day



  15. Microsoft Gets Its Money's Worth From Xamarin: PlayStation 4 Now Polluted by Microsoft

    The Trojan horse of Microsoft, Xamarin, is pushing .NET into Microsoft's console competitor



  16. After Brendan Eich Comes Chris Beard

    Having removed Brendan Eich using bullying and blackmail tactics, his foes inside Mozilla achieved too little as we have yet another man (coming from inside Mozilla) acting as CEO



  17. Healthcare News: Free Software in Health, Humanitarian Causes

    Links for the day



  18. Links 14/4/2014: MakuluLinux, Many Games, More Privacy News and Pulitzer Prize for NSA Revelations

    Links for the day



  19. TechBytes Episode 87: Catching up With Surveillance (NSA, GCHQ et al.)

    The first audio episode in a very long time covers some of the latest happenings when it comes to privacy and, contrariwise, mass surveillance



  20. Server News: KVM, ElasticHosts, Other GNU/Linux Items, and Open Network Linux

    Links for the day



  21. Hardware News: Freedom, Modding, Hackability on the Rise

    Links for the day



  22. Distributions News: GNU/Linux Distros

    Links for the day



  23. GNOME News: Financial Issues, Mutter-Wayland, West Coast Summit, Community Participation

    Links for the day



  24. KDE News: Kubuntu at the Centre Again KDE Applications Updated

    Links for the day



  25. Techrights Rising

    Effective immediately, Techrights will do what it takes to bring back old volume and pace of publishing



  26. Links: Surveillance, Intervention, Torture and Drones

    Links for the day



  27. Mobile Linux Not Just Android: Jolla, WebOS, and Firefox OS News

    Links for the day



  28. Google's Linux Revolution: New Gains for Android, Chrome OS (GNU/Linux)

    Links for the day



  29. Free/Libre Databases News: MongoDB, NoSQL, and MySQL Branches/Forks

    Links for the day



  30. Open Access on the Rise: Textbooks, Journals, Etc.

    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