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. The EFF Back to Tackling Software Patents, Not Just Patent Trolls

    Electronic Frontier Foundation lawyers start targeting large companies that exploit patents for intimidation and extortion, not just patent trolling



  2. Microsoft Wants to Devour the Competition (Linux), Devour People's Data

    Refuting the "new Microsoft" propaganda and some ludicrous concept that Microsoft is now "playing nice"



  3. Benoît Battistelli Thinks 'President' is Above the Law, Decides to Ignore the Court's Ruling

    Staff of the EPO is given yet more reasons to protest tomorrow at the British Consulate, for the so-called 'President' of the EPO reminds everyone of the very raison d'être for the protest -- a vain disregard for the rule of law



  4. Links 24/2/2015: Xfce 4.12 a Week Away, GNOME 3.16 Previewed

    Links for the day



  5. Links 23/2/2015: Ubuntu Kylin 14.04.2 LTS, Cinnamon 2.6 Previews

    Links for the day



  6. IRC Proceedings: February 8th - February 21st, 2015





  7. The EPO's Sham 'Internal Investigation' of EPO Vice-President Željko Topić's Affairs

    The EPO never investigated the Željko Topić affair, it only pretends to have investigated (one small aspect, i.e. cherry-picking) using a Benoît Battistelli-controlled group



  8. Links 21/2/2015: GNOME 3.15.90, Google Wins Android Lawsuit

    Links for the day



  9. Microsoft AstroTurfing War on GNU/Linux is Still Going On, But Hidden Better, Uses API as Instrument of Lock-in

    The corruptible press continues to describe blatant attacks (Embrace, Extend, Extinguish) against GNU/Linux and Free software as Microsoft 'embracing' Open Source



  10. Lenovo's Superfish Scandal is Spyware on Top of Spyware (Microsoft Windows), the Problem is Inherently Proprietary Software

    Shifting focus to the root problem, which is neither Lenovo nor its laptops but the non-free programs installed on hardware



  11. Benoît Battistelli Once Again Threatens EPO Staff That 'Dares' to Protest, Battistelli Exploits Terror Attacks to Pretend to Respect Free Speech

    The European Patent Office (EPO) President, Benoît Battistelli, reportedly started threatening -- as before -- staff that decides to exercise the right to assemble and protest against abuses, including the abuses of President Battistelli himself



  12. Links 20/2/2015: Android Studio v1.1, GDB 7.9

    Links for the day



  13. Links 20/2/2015: Bloomberg Joins Linux Foundation, ClearOS Community 6.6.0

    Links for the day



  14. The Chartered Institute of Patent Attorneys Slams the European Patent Office for Structural Failings

    An important letter which we overlooked while writing yesterday's 4 articles about the European Patent Office (EPO); yet another key stakeholder complains



  15. Links 19/2/2015: Hewlett-Packard on Cumulus Linux, Previews of GNOME 3.16 Beta

    Links for the day



  16. Techrights Under Attack Again, Shortly After Important EPO Articles

    Techrights highlights a pattern that is months old; Site faces availability issues shortly after reports about the European Patent Office and its abuses



  17. EPO Staff Protests Against Benoît Battistelli’s Lowering of Patents Quality (Scope Expansion and Software Patents for Profit)

    A protest in Munich in less than 6 days will target Mr. Sean Dennehey, who has helped Battistelli cover up his abuses and crush legitimate critics, whom he deemed illegal opposition as if the EPO is an authoritarian regime as opposed to a public service which taxpayers are reluctantly (but forcibly) funding



  18. Breaking: European Patent Office Sued by Its Own Staff in The Hague, Must Unblock Staff's Voices

    The crooked management of the European Patent Office (EPO) gets in legal trouble after repeated attempts to cover up abuses and suppress criticism



  19. Željko Topić's History in SIPO Leaves a Legacy of Alleged DZIV Vehicles (Bribes), Authorship Abuses, and Intimidation Against Reporters

    Another deep look at Željko Topić's background in Croatia, preceding his very notorious appointment to the EPO where he now serves as Benoît Battistelli's most controversial attack dog



  20. The Old Obsession With Patent Trolls Continues to Distract From Debate About Software Patenting

    A roundup of recent coverage about monopolies on algorithms in the United States



  21. Links 19/2/2015: 64-bit ARM Linux, Chinese New Year

    Links for the day



  22. Links 18/2/2015: Linux Report, FlightGear 3.4

    Links for the day



  23. EPO Scandals: The Story So Far

    An overview of articles about mischief, misconduct and breach of laws at the EPO



  24. Links 17/2/2015: TripleO, Pivotal

    Links for the day



  25. Links 17/2/2015: SystemD 219, Frugalware 2.0 (Rigel) Released

    Links for the day



  26. Željko Peratović Slammed for Whitewashing Željko Topić After Publishing Important Piece on Behalf of Key Sources

    Response from Ivan Kabalin to Zeljko Peratovic's so-called "apology" which is both mysterious and seemingly inadequate as it does nothing to actually explain what was wrong (if anything)



  27. Benoît Battistelli Has Made Oversight of European Patent Office Absolutely Impossible





  28. Microsoft Already Killed Nokia, Don't Let It Kill Android Players Too

    Microsoft's strategy against Android mirrors the company's evil strategy that derailed MeeGo and Nokia



  29. Intel Continues to Attack Software Freedom Through UEFI

    The Trojan horse that Microsoft uses to cement its monopoly on desktops and laptops (making it hard or impossible to install and run GNU/Linux) is also being misused to block Coreboot



  30. Links 16/2/2015: Netrunner 15, Bridge Linux

    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