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 20/7/2019: Weston 7.0 Alpha, Nageru 1.9.0

    Links for the day



  2. Companies That Collapse Because the European Patent Office (EPO) Gave Them Fake Patents in a Hurry

    False hopes and false promises won’t do any favours to European Patents, whose legal certainty suffers because Campinos and Battistelli measure nothing but ‘production’ (quantity) rather than quality of patents



  3. Slack Committed a Very Major Crime That Can Cost Many Billions If Not Trillions in Damages for Years to Come

    The inevitable has happened to Slack, which no longer deserves to exist as a company; moreover, the people who ran the company must be held criminally accountable



  4. Demand for European Patents Will Continue to Decrease If a Lot of European Patents Turn Out to be Invalid, Worthless

    The EPO's abandonment of patent justice and quality (in pursuit of so-called 'production' targets) is likely to doom the Office as the whole or render it vastly less relevant to the rest of the world



  5. 35 U.S.C. § 101 Still in Tact in the United States and Software Patents Rot Away

    The United States, where the number of granted patents decreased last year, becomes more productive; there are more signs that patent maximalism (patent litigation, patent scope etc.) has receded



  6. Links 19/7/2019: Deepin 15.11 and GNU/Linux Back on GPD MicroPC

    Links for the day



  7. Violence is Not Free Speech and Laws Exist Against Violence

    Free speech is certainly under attack and the debate is being framed within the context of Nazism; but this overlooks the fact that there are actual death threats and calls for genocide in the mix



  8. Links 19/7/2019: Oracle Linux 8.0, Latte Dock 0.9 Beta and PCLinuxOS KDE Darkstar 2019.07

    Links for the day



  9. Why Does Jim Zemlin Publicly Congratulate Microsoft?

    The signs aren't particularly encouraging when one considers that the leadership of the Linux Foundation is a fan of Microsoft and sometimes connected to Microsoft



  10. 2 Days Later (Case in Progress) and Still Media Silence About G 2/19

    The very legitimacy of years' worth of rulings and the EPO's abusive attacks on judges are under the microscope; but the media isn't paying any attention, perhaps deliberately



  11. The 'Linux' Foundation is Acting Like a Microsoft ISV Now, Commitment to Linux and FOSS Deteriorates Even Further

    The Linux Foundation has just announced a new Microsoft-funded initiative that's pushing GitHub and CLAs (passing copyrights on code to corporations)



  12. Links 18/7/2019: OPNsense 19.7, Krita 4.2.3 and KDevelop 5.3.3 Released

    Links for the day



  13. Index: G 2/19 (Enlarged Board of Appeal, EPO)

    G 2/19 (Enlarged Board of Appeal, EPO)



  14. EPO Looney Tunes – Part 4: G 2/19 - Faites Vos Jeux…

    "Josefsson needs to bring in the “desired result” for his political masters in the Administrative Council if he wants to be in with a chance of reappointment."



  15. Media Not Interested in G 2/19, Which Demonstrates Patent Justice is Nowadays Impossible at the EPO

    The EPO spreads patent injustices to other countries and courts; the media is miraculously enough not interested, almost as though there's a coordinated blackout



  16. Librethreat Database Updated

    Database which keeps track of variants of attack vectors on Free/libre software now includes two more forms of threat



  17. A Look Back (and Forward) at Friendly Programming

    Historical perspective on computer languages and how to do better



  18. Red Hat's Freedom Reduced to Just Online Partner Enablement Network (OPEN) and Microsoft as a Close Partner; Canonical's Ubuntu Just an 'App' for Windows?

    Free software is being snapped up by proprietary software giants and patent bullies that treat it as little more than an 'add-on' for their proprietary offerings



  19. Linux Foundation Apparently Celebrates Sysadmin Day With a Microsoft Windows Site!

    The Linux Foundation shows ‘love’ to actual GNU/Linux (the real thing) by apparently rejecting it and badmouthing it



  20. EPO Looney Tunes – Part 3: The Legal Line-up for G 2/19

    The deck appears to have already been stacked for G 2/19, a decision on EPO judges' exile to Haar (veiled disciplinary action/collective punishment by those whom the judges are supposed to 'oversee')



  21. Links 17/7/2019: VirtualBox 6.0.10 and Mageia 7.1 Releases, Mint Betas

    Links for the day



  22. Links 16/7/2019: Btrfs Gets 'Cleaned Up', Clonezilla Live 2.6.2-15

    Links for the day



  23. EPO Looney Tunes - Part 2: The “Difficult Legacy” and Its Dark Historical Shadow

    Assuming that he was informed, then it seems fair to say that Battistell’s little “joke” at the expense of the Boards was in very bad taste



  24. EPO Noise Machine Turned On as Haar Hearing Kicks Off, Patrick Corcoran Defamed Again

    The EPO does not want people to hear about Haar; it just wants people to hear about how wonderful the EPO is and there are some who have just decided to slander Patrick Corcoran again



  25. Microsoft is 'Doing Kamikaze' (神風) on Linux

    An analogy for what the Linux (only in name!) Foundation and Microsoft mean to Linux — or by extension to GNU/Linux and Free software whose largest repository Microsoft took control of



  26. The 'New' Linux.com Sometimes Feels Like a Microsoft Promotion Site

    Anything that the ‘Linux’ Foundation touches seems to turn into its proprietors’ agenda; one of those proprietors is Microsoft, which has a "Jihad" against Linux



  27. IBM is a Threat to the Internet, Not Just to Software Development (Due to Software Patents Aggression)

    IBM continues its aggression against technology — a fact that’s even more distressing now that IBM calls the shots at Red Hat



  28. EPO Looney Tunes - Part 1: Is D-Day Approaching for Battistelli’s “Difficult Legacy”?

    European patent justice isn’t working within the premises of EPOnia; a bunch of ‘show trials’ may in fact turn out to be just that — a show



  29. Links 16/7/2019: LXD 3.15, Q4OS 3.8 and D9VK 0.13f

    Links for the day



  30. Links 15/7/2019: Vulkan 1.1.115 and Facebook Openwashing

    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