Bonum Certa Men Certa

Guest Article: Windows NT and the Deepwater Horizon

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



Recent Techrights' Posts

Riot for peace & Love: Catholic Influencers and Digital Missionaries welcome Jubilee of Youth
Reprinted with permission from Daniel Pocock
Google 'Search' is Fast Becoming No Better Than Social Control Media Infested With Bots
Google emerged almost 30 years ago as a company looking to organise the Web and direct people towards informative pages. That Google is dead.
 
How to Report Apple Layoffs Without Saying the "L" Word
don't look for the "L" word
Wall Street Does Not Care About Microsoft's Impending (August) Layoffs, It Believes Lies From Microsoft, Whose Debt Grows Rapidly
If Microsoft is doing so well and swimming in money, why so many cuts (about 29,000 layoffs so far this year)?
Wayland Considered Harmful (to GNU/Linux Adoption)
it's not limited to games
My Experience With Judges Has been Positive, But We Must Still Pursue SLAPP Reform in the United Kingdom
We believe it'll be a "feather in the cap" if we can help change laws in the UK to better protect investigative reporters
Slopwatch Makes the Web Better
Remember what happened to BetaNews?
Slopwatch: Google News is Pumping in Lots of Web Traffic Into Fake Sites That Say "Linux"
somewhere between 30% and 40% of today's "news" about "Linux", as seen by Google News, is LLM slop
Links 30/07/2025: Climate Calamities Highlighted, Kyrgyzstan Crackdown on Expression/Freedoms
Links for the day
Gemini Links 30/07/2025: Watson’s List of Limits, Lysenko 2000
Links for the day
Some People See What Others See... But Only 40 Years Later
When people deviate from "the norm" they typically get ridiculed and dismissed as "crazy"
Links 30/07/2025: Tea Class Action and Google Killing the Web With Slop
Links for the day
Last Month Our IRC Community Turned 17
Funnily enough we never missed a single day when it comes to logging
"The Unix Kernel"
Linux was inspired by MINIX
The Register Relays Microsoft Marketing, Dubs That Marketing "Research"
Hours ago they did a "Microsoft sez" piece
Dealing With Sociopaths, Liars, and Cranks
A dysfunctional society such as this would never develop
Not Owning Mobile Phones
It's not about resistance; it's common sense
PCLinuxOS Had Functional Backups Before the House Fire, the Site Will be Restored in New Webhost
This is the direction we want for GNU/Linux, not some IBM sales strategy
Gemini Links 30/07/2025: Two Sides of Me and "Hooked on Cosmic Voyage"
Links for the day
Microsoft Will Continue Resorting to Crimes in Order to Keep GNU/Linux Usage Down
It is a real problem and we'll revisit it later this week
GAFAM 'Revolving Doors' at The Register and a "Bribe Price List"
"an analyst at Microsoft"
Microsoft Rapidly Shrinking (No, It's Not About Efficiency, It's About Unbearable Debt)
We'll soon see how much debt grew in the past quarter
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, July 29, 2025
IRC logs for Tuesday, July 29, 2025
Corruption is the Standard Operating Procedure at the European Patent Office (EPO)
The EPO is a dictatorship that stains Europe
Local Staff Committee Munich (LSCMN) at the European Patent Office (EPO) Requests an Urgent Meeting to Avoid Abolishing the Office
This is dictatorship led by the most corrupt
Slopwatch: Fake 'Linux' 'Articles' and Spamfarms/Slopfarms
at least 5 fake articles in one day
Gemini Links 29/07/2025: Wayland Unfit for Use and LLM Slop Faking One's Language Skills With Robot Communications
Links for the day
Before the OSI Was Bribed and Hijacked by Microsoft via GitHub and Compromised Management...
The OSI isn't even remotely "woke"
Nailing the "Hey Hi" (AI) Hype Bubble
So-called "hey hi" as they define it now is all about large companies or regimes remotely controlling the processes running on your machine and even your very own behaviour on your machine, which is in effect no longer your machine but some remotely controlled apparatus
The OSI Has Been Silent for Over 3 Weeks, It Has a Severe Trust Issue After Promoting Microsoft and Proprietary GitHub
OSI took a lot of money from Microsoft to become a Microsoft lobbyist
"Four decades; Four freedoms; For all users" Now as a T-shirt
That's shown along the sidebar
Bribery is OK If You Work for Microsoft (No Punishment Expected)
It's very troubling and a symptom of a broken society/system when particular laws or rules are applied and enforced against some people but not against others
Links 29/07/2025: Bad Climate and "Fair Software Licensing" Blasts Microsoft
Links for the day
Links 29/07/2025: Data Brokers Gone Wrong/Rogue and "Copyright Thicket"
Links for the day
Slopwatch: Linuxconfig.org, Linuxsecurity.com, Fagioli, The Register
Today's "Slopwatch" isn't the first article about LLM slop
Someone Should Remind Microsoft Lunduke That Microsoft Hires Many Sexual Criminals and Pedophiles as Well
Microsoft Lunduke on an "expedition" to find one or more perverts, then generalise to everyone in the "community"
Cash Machines (ATMs) Make Mistakes and They're Proprietary Software
Correcting mistakes is a colossal challenge
We Cover Topics Other Sites Are Too Afraid to Cover (Even When They Know the Facts)
It's not that they doubt the truth, they just realise there may be consequences for talking about it
They Try to Tell Us the Free Software Foundation Inc is Dying, But Its Revenue Doubled Since the Dot-Com Bubble Burst
Being in "Activism" is never easy; but it does positive things for society
Yes, Microsoft is the Problem
"I am no MS shill."
It's About the Cost of Workers, Not the Fictional Skills Shortage (That Does Not Exist, the Media Spreads False and Sometimes Self-Fulfilling Narratives)
This issue isn't limited to computing, some dub it "globalism"
Another Failed Use Case for Chatbots (LLM): Legal Advice and Analysis
They're just some self-discrediting toy that costs way too much to operate
Links 29/07/2025: More Pushbacks Against Slop and More Praises of Tom Lehrer
Links for the day
Gemini Links 29/07/2025: Purple Yarrow and Understanding Op Amps
Links for the day
This Monday WebProNews Absolutely Flooded the Web With Fake (LLM Slop) 'Articles' About "Linux", Google News Promoted Them as Legitimate
All of the following are fake articles attributed to pseudonyms or authors that don't exist; the images are also slop. Why does Google promote these?
Linuxiac is Not a Slopfarm, But at Least Some of Its Articles Are Machine-Generated Fakes
what we said about it was correct
Expect More Microsoft Layoffs
"Are more job cuts coming?"
Microsoft Behaving Like It's Running Out of Money to Pay Salaries
Does that seem like the behaviour expected from a company which claims it is "worth" trillions?
LWN Downtime Due to Linode, Not LLM Bots
"I’ve received an email letting me know that there is a potential for data loss."
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, July 28, 2025
IRC logs for Monday, July 28, 2025
Nonfree Software in My Bank, by Richard Stallman
Updated 8 hours ago
Links 28/07/2025: Science, Health, and Conflicts
Links for the day
Gemini Links 28/07/2025: Healthy Self-Image With Autism and a "New Life"
Links for the day
Links 28/07/2025: COVID-19 Sped up Brain Aging, "Circumvention is More Popular Than Compliance"
Links for the day
Richard Stallman is Usually Right Because He Thinks "Outside the Box"
he is able to observe society (mores and norms) as somewhat of an outsider
LWN Has Been Down for a Long Time, Another Casualty of LLM Bots?
Time will tell. How much time though?
Slopfarms Versus 'Linux' (and Against People Who Write Real Articles About GNU/Linux)
LLM slop in slopfarms by Brian Fagioli and Redazione RHC
Gemini Links 28/07/2025: Bila Yarrudhanggalangdhuray and Running pkgsrc in a FreeBSD Jail
Links for the day
Microsoft Turns News Sites Into Spamfarms
Is the site The Register MS the next IDG?
The Register MS/The Register US
On Saturday I contacted them for a comment (before issuing criticism)
Hacking revelations at Vatican Jubilee of Digital Missionaries
Reprinted with permission from Daniel Pocock
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, July 27, 2025
IRC logs for Sunday, July 27, 2025