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.
  • 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

What Else is New


  1. Microsoft Financially Backs Patent Trolls That Attack Its Competitors

    Corporate media continues to ignore the elephant in the room, which is Microsoft's deep involvement in arming patent trolls and using them against rivals, including GNU/Linux



  2. PTAB Engages in Patent Justice, But Lobbyists of Patent Trolls Try to Blame PTAB for All the Problems of the US and Then Promote Iancu

    In an effort to curtail quality control at the US patent office, voices of the litigation 'industry' promote the irrational theory that the demise of the US is all just the fault of patent reform



  3. Team UPC Has Been Reduced to Rubble and Misinformation

    A roundup of the latest falsehoods about the Unified Patent Court (UPC) and those who are peddling such falsehoods for personal gain



  4. CRISPR Patent Debacle Demonstrated That Opposition Divisions Do Their Job, But Also Highlighted Serious Deficiency in Patent-Granting Process

    While it is reassuring that EPO staff managed to squash a very controversial patent, it remains to be explained why such patent applications/applicants were even notified of intention to grant (in spite of the EPC, common sense and so on)



  5. Links 23/1/2018: Castle Game Engine 6.4, Qt 5.9.4, SQLite 3.22.0

    Links for the day



  6. Confidence in European Patents (EPs) is Eroding and Stakeholders Are Already Suffering

    The rush to grant lots and lots of patents at the EPO is already taking its toll; quality is declining, decisions to grant are being overturned, and the already-overburdened appeal boards are unable to catch up



  7. Even More Uncertain a Future for the Independence of the EPO Boards of Appeal as Judge Corcoran Too Gets Sent to 'Exile'

    The attack on supposedly independent judges at the EPO escalates further; the judge whom the EPO was ordered to reinstate (by ILO) is being constantly pushed around, not just legally bullied



  8. The Response to Accusations of Censorship by Team UPC? Yet More Censorship to Shield UPC From Criticism

    The Empire of Lies upon which the Unified Patent Court (UPC) was conceived is being exposed for its lies; The Empire Strikes Back with yet more censorship



  9. Links 22/1/2018: Linux 4.15 Delayed Again, Libinput 1.9.901

    Links for the day



  10. Team UPC Calls Critics of the UPC Idiots, Deletes Their Comments, and Blocks Them

    A new low for Team UPC, which is unable to cope with reality and has begun literally mocking and deleting comments of people who speak out truths



  11. How the Opposition to CRISPR Patents at the EPO Sent Shockwaves Through the Industry

    Additional reports/coverage on the EPO (European Patent Office) revoking Broad Institute's CRISPR patent show that the issue at hand isn't just one sole patent but the whole class/family of patents



  12. Unified Patents Says That RPX, Which Might Soon be Owned by Patent Trolls, Paid Patent Trolls Hundreds of Millions of Dollars

    Unified Patents, which helps crush software patents, takes note of RPX’s financial statements, which reveal the great extent to which RPX actually helped trolls rather than stop them



  13. IAM Together With Its Partner, IIPCC, is Lobbying the USPTO to Crush PTAB and Restore Patent Chaos

    Having handled over 8,000 petitions (according to Professor Lemley's Lex Machina), PTAB champions patent quality at the USPTO, so front groups of the litigation 'industry' creep in and attempt to lobby the likely next Director of the USPTO (inciting him against PTAB, as usual)



  14. Software Patents Are Still Dropping Like Flies in 2018, Thanks to Alice v CLS Bank (SCOTUS, 2014) and Section 101 (USPTO)

    Section 101 (§ 101) is thriving in the sense that it belatedly throws thousands of patents -- and frivolous lawsuits that depend on them -- down the chute; the patent trolls and their allies in the patent microcosm are very furious and they blame PTAB for actually doing its job (enforcing Section 101 when petitioned to do so)



  15. Patent Troll Finjan Looks Like It's About to Collapse, But Patent Maximalists Exploit It for Software Patents Promotion

    Patent trolls are struggling in their use of software patents; few (if any) of their patents are upheld as valid and those that miraculously remain in tact become the subject of fascination if not obsession among trolls' advocates



  16. The Attacks on PTAB Are Slowing Down and Attempts to Shield Oneself From Inter Partes Reviews (IPRs) Are Failing

    The Patent Trial and Appeal Board (PTAB) reapplies patent eligibility tests/guidelines in order to squash likely invalid patents; The litigation 'industry' is not happy about it, but its opposition to PTAB is also losing steam



  17. Links 21/1/2018: Wine 3.0 Coverage, KaOS 2018.01, Red Hat Among 'Admired Companies'

    Links for the day



  18. Blockchain Patents Are a Catastrophe in the Making as Trolls and Aggressors Accumulate Them

    As patents pertaining to blockchains continue to be granted -- even in defiance of Alice/Section 101 -- it seems likely that patent wars will sooner or later erupt, involving some large banks, IBM, and patent trolls associated with the notorious Erich Spangenberg



  19. Qualcomm/Broadcom/NXP Combination Would Become a Disastrous Patent Thicket Which Benefits Nobody

    Worried by the prospect of mega-mergers and takeovers which would put far too much market power (and monopoly through patents) in one place, governments and corporations speak out



  20. Patent Litigation in East Asia: Huawei, Samsung, HTC, Nintendo and COLOPL

    A quick look at some high-profile cases in which large Asian firms are embroiled; it seems clear that litigation activities have shifted eastwards (where actual production is done)



  21. Patent Litigation in the US is Down Sharply and Patent Trolls' Demise Has Much to Do With It

    Docket Navigator and Lex Machina both show a significant decline in litigation -- a trend which is likely to carry on now that TC Heartland is in tact (not for just half a year but a whole year) and PTAB completes another record year



  22. Cheating the US Patent System is a Lot Harder After TC Heartland

    Some new examples of tricks (and sometimes cheats) attempted by patent claimants and their representatives; it does not go as well as they hoped



  23. RPX Might Soon be Owned by Patent Troll Erich Spangenberg

    RPX, whose top executives are leaving and business is gradually dying, might end up as another 'asset' of patent trolls



  24. Patent Quality (Not Numbers) as an Asset: Oppositions, Appeals and Rejections at the EPO

    Benoît Battistelli wants a rubber-stamping operation (like INPI) rather than a functional patent office, but oppositions at the Office prove to be fruitful and many erroneously-granted patents are -- by extrapolation -- already being revoked (affecting, in retrospect, Battistelli's so-called 'results')



  25. Links 19/1/2018: Linux Journalism Fund, Grsecurity is SLAPPing Again

    Links for the day



  26. The EPO Ignores This Week's Decision Which Demonstrates Patent Scope Gone Awry; Software Patents Brought Up Again

    The worrisome growth of European Patents (EPs) — a 40% jump in one year in spite of decline in the number of patent applications — is a symptom of the poor judgment, induced largely by bad policies that impede examiners’ activities for the sake of so-called ‘production’; this week's decision regarding CRISPR is another wake-up call and software patents too need to be abolished (as a whole), in lieu with the European Patent Convention (EPC)



  27. WesternGeco v ION Geophysical (at the US Supreme Court) Won't Affect Patent Scope

    As WesternGeco v ION Geophysical is the main if not sole ‘major’ patent case that the US Supreme Court will deal with, it seems safe to say that nothing substantial will change for patent scope in the United States this year



  28. Links 18/1/2018: MenuLibre 2.1.4, Git 2.16 Released

    Links for the day



  29. Microsoft, Masking/Hiding Itself Behind Patent Trolls, is Still Engaging in Patent Extortion

    A review of Microsoft's ugly tactics, which involve coercion and extortion (for businesses to move to Azure and/or for OEMs to preload Microsoft software) while Microsoft-connected patent trolls help hide the "enforcement" element in this whole racket



  30. Patent Prosecution Highway: Low-Quality Patents for High-Frequency Patent Aggressors

    The EPO's race to the bottom of patent quality, combined with a "need for speed", is a recipe for disaster (except for litigation firms, patent bullies, and patent trolls)


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