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. Boycotting Micro Focus International

    Microsoft's "Partner of the Year" is taking over the patron of SUSE and all of Novell's remains, except the patents (Microsoft has already grabbed those)



  2. Vesna Stilin's Remarks on Željko Topić: Part XI

    Vesna Stilin speaks about her confrontation with EPO Vice-President Željko Topić, who has criminal lawsuits against him in Croatia



  3. Links 22/11/2014: Linux Mint 17.1, Ubuntu MATE

    Links for the day



  4. Links 21/11/2014: Problems at Debian, Jolla Tablet

    Links for the day



  5. Links 18/11/2014: Linux 3.18 RC 5, New DigiKam

    Links for the day



  6. Special Report: Many Criminal Charges Against EPO Vice-President Željko Topić

    The abuses of Željko Topić, who has gained notoriety in his home country, are rapidly becoming public knowledge across all of Europe



  7. Links 16/11/2014: Xfdesktop 4.10.3, GNU Hello 2.10

    Links for the day



  8. Microsoft is Going Into the Anti-Whistleblowing Business, Dodges Criticism Over 19-Year Bug Door in Windows

    With Aorato acquisition Microsoft helps protect the criminals (from whistleblowers) and with lies about .NET Microsoft distracts from a bug that has facilitated remote access into Windows (by those in the know) for nearly two decades



  9. Reaffirming Microsoft's Long-Known Hostility Towards Net Neutrality, Microsoft Crashed Juniper

    Steve Ballmer is ranting against net neutrality and Juniper's business is in trouble after a lot of executives from Microsoft took over most top positions there



  10. Another Massive Step Towards Elimination of Software Patents as Even CAFC Rules Against Them

    After SCOTUS gets involved in the Ultramercial case, the CAFC finally decides to actually serve justice rather than dogma



  11. The GOP's Patent Reform Plan Not Effective Enough to Stop Massive Patent Trolls Like Microsoft/Nokia

    The corporations-serving GOP says that it wants a patent reform, but another reminder is needed of the futility of the suggested changes



  12. How the EPO's Executive Branch (Battistelli and Topić) Banned Scrutiny and Created Authoritarian Model of Control: Part X

    A look at highly dubious moves by EPO President Battistelli and his right-hand man Topić, whose abuses are becoming hard to oversee or even report



  13. Links 15/11/2014: Linux Mint 17.1 Release Candidate, Popcorn Time 0.3.5

    Links for the day



  14. IRC Proceedings: October 26th, 2014 – November 8th, 2014

    Many IRC logs



  15. The Terrible Joke Which is Microsoft 'Loving' Linux: Nightmares With UEFI 'Secure' Boot (i.e. Windows Monopoly Imposed) Continue to Affect GNU/Linux Users

    A reminder of Microsoft's sheer hostility towards GNU/Linux and long-reaching sabotage of GNU/Linux installations



  16. Patent Lawyers Worry About Section 101 in 'Alice' (and Other Patent News)

    A quick roundup of news of interest regarding software patents



  17. Will Write for FUD (Against FOSS)

    Black Duck rears its ugly head again, serving to show that it is in the business of changing perceptions and not in the information or analysis business



  18. Debunking Several Days of Never-Ending Lies About Microsoft and .NET

    .NET is not "Open Source", it cannot be forked (there remains patent threat), Visual Studio is still completely proprietary and it is expected to come to other platforms only because Windows has lost its dominance and Microsoft wants to perpetually control APIs (with software patents) and hence reign over developers



  19. Links 14/11/2014: LibreOffice 4.3.4, Ads Now in Firefox

    Links for the day



  20. Links 14/11/2014: GNOME 3.14.2, PulseAudio 6.0

    Links for the day



  21. Microsoft Windows is Still Designed as a Paradise of Back Doors, Intrusion, Wiretaps, and Interception

    At many levels -- from communication to storage and encryption -- Windows is designed for the very opposite of security



  22. Forget the FUD About Bash and OpenSSL, Microsoft Windows Blamed for Massive Credit Cards Heist

    Home Depot learns its lesson from a Microsoft Windows disaster, but it stays with proprietary software rather than move to software that is actively audited by many people and is inherently better maintained (Free/libre software)



  23. Windows 'Update' and NSA Back Doors, Including a 19-Year Bug Door in Microsoft Windows

    The back doors-enabled Microsoft Windows is being revealed and portrayed as the Swiss cheese that it really is after massive holes are discovered (mostly to be buried by a .NET propaganda blitz)



  24. Revealed: Microsoft is Trying to Corrupt the UK in Order to Eliminate Its OpenDocument Format-Oriented Standards Policy

    Microsoft interference with Britain's preference for ODF is now confirmed, thanks to a valuable news report from Computer Weekly; OOXML lock-in is being unleashed by Microsoft on Android users



  25. Links 13/11/2014: Ubuntu MATE 14.04.1 LTS, New KDE Plasma

    Links for the day



  26. .NET is NOT "Open Source", But Microsoft's Minions Shamelessly Openwash It Right Now

    The openwashing of .NET continues with yet another publicity stunt that is intended to lock in developers



  27. Links 11/11/2014: GNOME Trademark Dispute Settled, Mozilla Embraces Tor

    Links for the day



  28. Patent Reform Subversion After Republican (GOP) 'Win' in US Senate

    The Grand Corporations Party, or the political party which serves large businesses that are funding it, continues to just focus on a mirage of a 'reform' rather than tackle the real issues where culprits include very large businesses such as Microsoft and Apple



  29. Microsoft-Armed Patent Troll MOSAID (Now Conversant) Wants to Sweep up More Patents for Litigation

    Reports about patent trolls and scope of patents serve to show what the foes of Free software are up to right now



  30. When Courts in the US Attack the Right to Reuse APIs

    Challenging the clueless ruling from the Court of Appeals for the Federal Circuit in the United States (very pro-software patents and anti-computer science), notable programmers write to the highest court


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