EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

10.12.10

Guest Article: Windows NT and the Deepwater Horizon

Posted in Microsoft, Windows at 2:48 am by Dr. Roy Schestowitz

Microsoft blue ribbon

Summary: An analysis of the causes that led to the Deepwater Horizon blowup (or what failed to prevent it), based on the long inquiry

THE previous post spoke about Stuxnet, which endangers many people whose company/authority/personal computer runs Microsoft Windows. Another recent disaster where Windows got some blame was the Deepwater Horizon blowup [1, 2, 3, 4]. An anonymous Techrights contributor wrote an update on the topic — one which we publish below.

“Here’s an update on the Deepwater Horizon story, “he writes, “New testimony spurred me to look up transcripts that had not been published at the time. There were several bombshells worth sharing and thinking about. For example, Windows NT is named and shamed by the expert witness. Windows was not mentioned in most press coverage but it seems to have played a more central roll than even I expected.”

Here is the report in question PDF and corresponding interpretation:


Windows NT and the Deepwater Horizon

A buggy control system left drillers and the rig blind and might even have damaged a critical safety system on the sea floor.

Microsoft Windows may have been directly responsible for Deepwater Horizon catastrophe. Previously, Techrights showed that Microsoft Windows played a crucial role. A 824 page transcript from the July 23 Deepwater Horizon investigation has been posted and we can see that things were as Techrights guessed. Mr. Williams describes Windows NT, “a very unstable platform” as the root cause of most problems. This buggy Windows based control system left drillers blind when it crashed daily was responsible for safety system bypasses and may have destroyed the annular seal. New testimony from Andrea Fleytas, who operated the alarm panels on the doomed bridge and jumped from the flaming deck with Mr. Williams, shows that the drilling team may have had time to escape if the alarms were not inhibited. This interpretation of her testimony, with some quotes, was published by the Times Picayune. The consequences of this disaster and ongoing cover up are well reported in the Florida Oil Spill Law blog.

Mr. Williams describes typical Windows problems in three identical, malfunctioning control systems, A Chair, B Chair and C Chair, on pages 42 and 101. There’s incompatibility, instability, harmful bugs and worries about viruses. On page 42, Mr. Williams talks about the systems, their importance and how broken they were.

The A-chair is located in the dog house. That is the main operating point for the driller to control all drilling functions. It controls everything from mud pumps to top drive, hydraulics. It controls everything.

For three to four months we’ve had problems with this computer simply locking up. [sometimes it was a blue screen, sometimes a frozen display] … We had ordered replacement hard drives from the manufacturer. We had actually ordered an entire new system, new computers, new servers, new everything to upgrade it from the very obsolete operating system that it was using. Those computers were actually using Windows NT, which is a very unstable platform to begin with.

Between the manufacturer and the rig, they could not get the bugs worked out of the new operating system. They couldn’t get the old software to run correctly on the new operating system. Our sister rig, the NAUTILUS, was going through those growing pains kind of for us. We had already ordered all the equipment. We were just waiting on them to figure it all out so that we could copy their learnings and make it work on our rig.

Meanwhile, we were limping along with what we had. We had ordered new hard drives. They came in. We replaced the images on the hard drives for the software imaging, got them back running, the chair would run for two, three days, and they would crash again. … I can’t tell you how many hours or days he [electrical supervisor, Tommy Daniels] spent focused entirely on getting these chairs resolved. … He was still working towards that up until the time of the explosion. It had not been resolved.

In the same discussion, Mr. Williams attributes the blowout to the failure of this system by referencing a previous incident.

[in another accident] It was internally discussed that the chair crashing caused the kick, because they lost all — They lost all communications to the drill package. They had no way to monitor anything for several seconds, and before they could get the B Chair up, they had taken a kick.

On pages 103 and 104, he also describes how a “blue screen of death” could lead to a “kick” while waiting for the backup system to boot and be informed by “servers”. Operators complained about this loss of control every day and it happened at all hours of the day and night.

It should be noted that the problem with the alarms was not the sensors but it could have been viruses. Mr. Williams describes how he made sure all of those were working properly on pages 66 and 68 to 70. On page 77, Williams says, “The chairs themselves were completely independent and isolated from the entire rig network, so there was no chance of infection, virus, hacking, there was no opportunity for that.” This tells us that the rest of the network had problems that might have been carried to the control system via physical media, like USB drives or floppies.

Non free software left BP engineers in the field divided and helpless. On page 102, Mr. Williams tells us, “There was no fixing bad software. We could simply manage it, try to keep it running.” So, BP’s management was told that all they could do was as the vendor says. Money and resources were being spent to fix the problems but they were wasted. When the vendor’s software failed, BP was stuck begging for more from a system that had to be bypassed.

Mr. Williams describes the general alarm, its inhibition and consequences starting on page 30. The whole rig was blind to real danger.

.

You have four states of alarms. You have a normal operating condition, you have an inhibited condition, which simply means that the sensory is active, it is sensing, and it will alarm and it will give the information to the computer but the computer will not trigger an alarm for it. It will give you the indication, but it won’t trigger the actual alarm. [other states described] …

there are several toxic and combustible gas sensors located in key areas, mainly around the drilling package. … When you get two detectors to go into a high state in one zone, what is supposed to happen is the ESD for that zone should trip, which is your emergency shutdowns [designed to prevent explosions], and you should also sound the generator alarm.

The general alarm is set up to inform the entire rig of any of three conditions. … Each one of those conditions has a distinct tone and a distinct visual light. We have light columns throughout the rig. One red — Within the column there’s a red, a yellow, and a blue, with the red being fire, yellow being toxic, blue being combustible. So you get an audio tone and a visual tone with every general alarm. [none of these were used in the accident because the computer was set so general alarms had to be triggered manually. As we will see, they failed to do this.]

… When I discovered it was inhibited about a year ago, I inquired as to why it was inhibited, and the explanation I got was that they — from the OIM down, they did not want people woke up at 3:00 o’clock in the morning due to false alarms.

On pages 40 and 41 we see that Emergency Shut Downs had been set to bypass because the system shut panels down frequently over false alarms. This left everyone at risk of explosion.

On page 37, Mr. Williams drops another bombshell, that the same system may have destroyed the blow out preventer without human input. A reasonable system would inhibit motion, even human directed motion, that would destroy itself. What they had left them wondering about everything.

it took me a few days to understand or to formulate why we were getting chunks of [annular] rubber back. There was an incident prior to that where we were in testing mode and the annular was closed around the drill pipe. I got a call from the night-time toolpusher to come investigate whether or not there was an input to the stick to hoist the block while the annular was closed, and I inquired as to why he needed to know that. He said, “Well, the block moved about 15 or 20 feet. We need to know why. We need to know if it was inadvertent stick movement or if it went up by itself.” [an informal investigation] got into the chair log data and dissected the data. What we determined was one of the sticks was moved in the positive direction. What we could not definitively determine was which stick. The tag system inside the log was not accurate enough. It simply said, “Joystick A, Joystick B,” …

All the logs prove to me is that the computer thought someone pushed the joystick. The signal was erroneous and might also have been spurious.

The most dreadful immediate consequence of all of this was that eleven men died in an explosion and fire. New testimony shows a situation that a more reasonable system should have been able to react to and save the day. The blow out preventer should never have been damaged. Alarms should have sounded, so people could escape. Panels and generator should have been shut down to prevent an explosion. What actually happened? David Hammer of the Times Picayune tells us.

Andrea Fleytas said she felt the rig jolt that evening and saw more than 10 magenta lights flash on her screen notifying her that the highest level of combustible gas had entered the rig’s shaker house and drill shack, critical areas where the rig’s drilling team was at work. … she was trained to sound a general alarm any time more than one indicator light flashed, but didn’t do so immediately in this case because she had never been trained to deal with such an overwhelming number of warnings. … she eventually “went over and hit the alarms” after the first or two large explosions.

[before pushing the alarms] Fleytas received a telephone call from crew members on the drill floor who said they were fighting a kick of gas and oil in the well; she took another call from the engine control room asking what was happening and she told them they were having a well control problem; and she continued to hit buttons on her console acknowledging the multiple gas alarms popping up in various sectors of the rig. … A few seconds after she got off the telephone with the engine room, there was a blackout on the rig. A few seconds after that, the first explosion rang out, Fleytas testified. It was then that she sounded the general alarm.

Keplinger said in his own testimony that it was after the explosion when he first “noticed a lot of gas in there and called” the shaker house to try to get whoever may have been there out, but nobody answered the phone.

Fleytas said she knew of no protocols for activating the emergency shutdown and no one activated it. Gas likely ignited in the drilling area, killing everyone there, and also caused the two active engines to rev so high that all power on the rig was lost, preventing fire pumps from working and keeping the rig from moving away from the spewing well.

Microsoft failure did not end when the rig sank. Those trying to fix things were also burdened with second rate software.

Since then, people from Texas to Florida have been sickened and harmed by the spill. Toxic levels of dispersant have shown up in people’s private pools, the beaches are contaminated with about 200 ppm of oil, oysters, crabs and shrimp have even more. The oil made its way into people’s blood. If the big spill in Mexico is a guide, the spill will linger for decades [2].

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email
  • Google Bookmarks

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

What Else is New


  1. [Humour] COVID-19 is Very, Very Afraid of Human Beings Making More Monopolies Instead of Fighting Together

    The European Patent Office (EPO) to the rescue! Fighting a dangerous pandemic one profitable monopoly at a time!



  2. The News is Never 'Slow', It's Just Journalism That's Slowing Down (and Investigative Journalism Coming Under Attack)

    A mix of censorship and subtle mind control contribute to misinformed societies that shape their perception or misunderstanding of the world based on false measures of authority (where money can determine what is true and what is untrue); many topics remain completely untouched, leading to apathy in a vacuum; it's very much applicable to international organisations, which are presumed benign by virtue of being multi-national or supranational



  3. Social Control Media is About Social Control and If It Doesn't Ban You It'll Shut Down Everyone's Account (One Day)

    It’s time to leave the ‘Internet rot’ which is social control media well behind us; blogging and RSS/XML may seem like a thing of the past, but they may as well become the future (again; if we make the correct and informed choices)



  4. Microsoft's Fingers in Every Pie: The Cult Mentality That Society Needs to Become Wary of

    Microsoft and its co-founder (pretending to do his for-profit 'charity' via the Gates Foundation) are trying to control the world; in the process they've moved to control even their most potent competitor, according to Gates himself, which is GNU/Linux



  5. Links 9/7/2020: Google’s Open Usage Commons, GNOME 3.36.4, Neptune 6.5

    Links for the day



  6. IRC Proceedings: Wednesday, July 08, 2020

    IRC logs for Wednesday, July 08, 2020



  7. Links 8/7/2020: SUSE to Acquire Rancher Labs, Btrfs as Default in Fedora, Qt Creator 4.12.4

    Links for the day



  8. Yes, Master

    When the Linux Foundation tells us to tone down our language we ought to remember what kind of hypocritical stance these people have (note: the above have nothing to do with slavery, either)



  9. Fraunhofer is Again Evergreening Software Patents to Maintain Its Codecs Cartel, Forcing Everyone to Pay to View/Stream Multimedia Files

    The roller-coaster of software patents on multimedia isn't stopping; we know the culprits who can be named for perpetuating this injustice



  10. [Humour/Meme] Focusing on the Bombings and Who's Included in the Bombings

    Supremacist agenda disguised as "tolerant and inclusive" is still objectionable supremacist agenda



  11. Manners Are a Good Thing. The Yardstick or the Standard of Manners Changes Over Time.

    Entirely legitimate grievances of African-Americans are being exploited by people who aren’t even African-American (and usually don’t speak for African-Americans) to warp the debate from one about software ethics and technical issues, not to mention war crimes of companies that employ many programmers, to something which is unlikely to really help African-Americans (also, they don't employ any African-Americans)



  12. IRC Proceedings: Tuesday, July 07, 2020

    IRC logs for Tuesday, July 07, 2020



  13. Links 8/7/2020: Huawei’s GNU/Linux PC, Sparky 5.12, and Endless OS 3.8.4 Released

    Links for the day



  14. [Humour] Television Channels That Don't Speak of Real Looting But Participate in Looting

    People may need to look beyond (or outside) the television screen to grasp what's going on



  15. (Software) Freedom is Elusive Without the Ability to Concentrate

    Software is consuming people's minds; to make matters worse, people have become so attached to such software that they're unable to see it and get away from it (they associate that software with "social life")



  16. Monopolies Erode Freedom, Freedom Erodes Monopolies

    "There are so many reasons that GitHub makes projects less free."



  17. Links 7/7/2020: NomadBSD 1.3.2, Clonezilla Live 2.6.7 and DRM Comes to Cars

    Links for the day



  18. [Humour] IAM Ranked Top for Quality of EPO Propaganda

    Contrary to what the European Patent Office (EPO) keeps saying, patent quality is slipping very fast in Europe (based on the EPO's own analysis!) but patent trolls-funded publishers deny that



  19. When They're Done With Patents on Foods and Recipes They'll Have Patents on Fashion, Taste and Smell

    The mental dysfunction — an infectious condition — that says everything in the world must be patented should be resisted; it overlooks the fact that patents were introduced to protect/promote actual invention, not thoughts, feelings, nature and art



  20. [Humour/Meme] IBM's Money is Unhealthy to the Free Software Foundation (FSF)

    IBM will never be happy as long as RMS (Richard Stallman) has a say in the FSF — directly or indirectly — or even in the GNU Project, both of which he himself created back when IBM was the biggest monopolist



  21. IRC Proceedings: Monday, July 06, 2020

    IRC logs for Monday, July 06, 2020



  22. Never Let IBM/Red Hat Lecture Us on Morality

    Ethics and morality should not be taught by those who themselves need a lesson; in the meantime we're losing the courage to speak freely and those who commit atrocious acts like it a lot better that way



  23. [Humour/Meme] Wear the Red Hat as the Open Org Becomes Openwash

    IBM is changing Red Hat and not for the better; sooner or later IBM will become another Microsoft and changing from one to the other will be like swapping 'masters'



  24. IBM is Imposing Non-Free, Privacy-Infringing Tools and Patent Tolls on Red Hat Staff

    There are signs that Red Hat under IBM will be more like assimilation to IBM, not IBM assimilating to the 'Red Hat way' or the so-called 'open org'



  25. They Tell the Free Software Community That It is Racist While Saying Nothing at All About Trump's Racism (Because He Gives Them Government and Military Contracts)

    While their president compares 'foreign' people to a virus (using innuendo, dog whistles and racist rhetoric reminiscent of the Nazi era) the big US corporations (American surveillance giants) turn their attention to rather innocuous words inside people's code (which almost nobody sees anyway)



  26. LibreOffice 'Personal Edition' Seems Like a Marketing and Communication Fluke

    Had LibreOffice developers (and the Document Foundation) communicated these changes more openly, they would have averted/avoided some of the FUD



  27. It Almost Feels Like Microsoft Has Already 'Bought' Canonical

    Canonical's disturbing trajectory and betrayal of the community continue unabated; one can easily get the impression that Ubuntu exists to help Microsoft at some level



  28. Update to GNU Project Bleeding into Microsoft

    Update



  29. Microsoft is Going to Get Tired of Whining About “GAFA” and Accept That It's Just as Bad If Not a Lot Worse at Privacy

    Microsoft is being treated by the US government as if it's not abusing anything, let alone people's privacy; if anything, this demonstrates the degree to which Microsoft infiltrated or 'vendor-captured' regulatory branches



  30. Links 6/7/2020: LibreOffice 7.0 RC1, MX-19.2 KDE Beta 1, Linux 5.8 RC4

    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