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
  • StumbleUpon
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Propeller
  • Slashdot
  • 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. Divide and Conquer: How Microsoft Fractures Free and Open Source Software, GNU/Linux

    Latest examples of Microsoft's strategy, wherein it sends out affiliates to pretend to be FOSS people and then promote software patent deals, separation between Open Source and Free software, departure from the GPL, promotion of 'open' core (proprietary) as "Open Source", and demotion of free/libre platforms like GNU/Linux along with free suites/formats like ODF



  2. GNU/Linux Users in Techrights

    We deal with the old question, how many people who read Techrights use GNU/Linux?



  3. “Only Idiots Want to Pay for Novell” (Corrected)

    Strong words from Rui Seabra to Red Hat's Wildeboer, who criticises people's willingness to pay Microsoft for GNU/Linux



  4. GNU/Linux Keeps Gaining Market, Microsoft-Funded Net Applications Keeps Lying

    GNU/Linux market share on the desktop approaching 5% in W3Schools.com



  5. The Truth About Thomas Edison and New Species of Patent Trolls

    A look back at very abusive behaviour from a patent office icon; new critique of the patent process



  6. AOL Escapes Microsoft

    AOL turns to Google, despite rumours that Microsoft wanted to buy AOL



  7. Eye on Security: Windows Ransomware, DLL Hole, Malware, and More

    Menaces and unpleasant 'niceties' that only affect users of Windows this week



  8. Links 3/9/2010: GNOME 2.32 Beta 2, Android Tablets

    Links for the day



  9. IRC Proceedings: September 2nd, 2010

    IRC logs for September 2nd, 2010



  10. Links 2/9/2010: New Survey Shows Red Hat GNU/Linux Increasingly Replacing Windows

    Links for the day



  11. Links 2/9/2010: Red Hat at Year Highs, Fake 'Open Source' Called Out

    Links for the day



  12. Microsoft Saved the Bush Family From Embarrassment

    A migration to Microsoft Exchange in the White House led to loss of crucial data which could help show how the United States entered wars and why



  13. Insanity of Microsoft Patents and the Insanity of 'Green' Patents

    Microsoft earns a patent monopoly on "[o]perating system shut down"; Patent monopolies prey on ideas that help preserve the planet



  14. Microsoft Looks to Communism for Answers

    Microsoft turns to China, hoping that therein exists some way to rescue Xbox 360; instead, China brings competition to Xbox 360, whose price is going up, not down



  15. "Novell Laboratories" and Patent Extortion Against Generic Drugs

    Notorious "death patents" are being used against Novell



  16. It's True, Android is Not Free (Because of Microsoft Patent Extortion)

    New FUD from Microsoft staff and a reminder of what it is that really puts a price tag on Android (and it's not Google)



  17. Bloomberg Gets the Facts Wrong (About SCO and Novell)

    Another example of Bloomberg publishing misinformation, which in this case serves SCO and thus harms Linux



  18. Red Hat Now Worth Almost 3.5 Times What Novell is Worth

    A look at Novell's decreasing relevance wrt to Red Hat and other companies that actually produce and distribute Free software, not proprietary software



  19. “Novell Inc (NOVL) Received an Offer in Early March and Has Yet to Announce a Deal.”

    Novell is still up for sale and the financial market expects some announcement to come sooner or later



  20. Microsoft Says Choose Microsoft to Avoid Lock-in

    Microsoft warns about VMware lock-in as it attempts to sell proprietary hype [sic] V



  21. IRC Proceedings: September 1st, 2010

    IRC logs for September 1st, 2010



  22. Links 1/9/2010: Linux in Ukraine, 'Green Party' of Belgium Moves to GNU/Linux Desktops

    Links for the day



  23. Microsoft Boosters of Software Patents in Linux/UNIX Sued for Patent Violation

    Centrify and Likewise get sued, having attempted to outdo Free software by faking it and adding software patents to it



  24. Microsoft Lobbyists Continue to Push for Software Patents in Europe (Transforming Government) to Tax Linux

    Microsoft wants European GNU/Linux users to pay through the nose, but first it needs to use lobbyists like Zuck to change the law in Europe, by pretending to speak for small businesses



  25. Microsoft Uses Linux to 'Succeed'

    Microsoft uses Linux-powered phones not just to make income (patent tax) but also to spread Microsoft propaganda, which includes Linux insults



  26. Links 1/9/2010: Chakra 0.2.0, Ksplice Free for Fedora

    Links for the day



  27. Apple's Co-founder Steve Wozniak a Patent Trolls' Apologist, Apple is Patenting DRM Ideas

    Wozniak helps prove that also departing co-establishers of proprietary predators defend patent trolling



  28. Microsoft is Said to Have Had an Anti-OpenOffice.org Seminar on Monday (Updated)

    The Microsoft camp is attacking Oracle's OpenOffice.org (OOOo) while pretending that Oracle is an "evil empire" (whereas Microsoft "loves" open source)



  29. Software Patents and Microsoft Hurt Korea as Country Tries to Escape Microsoft Monopoly and Market Abuses

    Microsoft dependencies, Ballnux in Korea, and the ill effects of software patents there



  30. Correcting Common Case of Misreporting: Novell is Not an Open Source Company

    Novell is a semi-shut (or "mixed source") company, not "Open Source" as some Web sites falsely report


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

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts