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

Traf-O-Data, the Company That Jeffrey Epstein's BFF (Bill Gates) (Co)Founded 53 Years and Went Out of Business Due to Heavy Losses
Who will die first, Bill or Microsoft?
A Note on SimilarWeb
Or why SimilarWeb is meaningless for more than 99% of the sites on the Web
IBM Said to be Shutting Down Offices or Sites in the United States
the press can no longer avoid admitting that IBM moves many jobs to India
LLM Slop as Attack Vector on the Reputation of Linux
The attacks on Linux have escalated to information warfare
 
Techrights Has Dealt With More Potent SLAPPs Than Violent Microsofters Begging to Hide What They Did to Women
I became accustomed to SLAPPs
Links 04/04/2025: Fury in South Korea, Flight MH370 Remains Mystery
Links for the day
Gemini Links 04/04/2025: Anger and Raspberry Pi CM4
Links for the day
Links 04/04/2025: LLM Slop Bubble Bursting and Korea Music Copyright Association Bans Slop 'Music'
Links for the day
Why Microsoft's Shares Sank Almost 20% in Recent Months (the Bubble is Imploding)
verified press reports from the past 24 hours
GNU/Linux Rises to Almost 5% in Algeria While Windows Sinks to All-Time Low
GNU/Linux grew tenfold
Where to Get More Gags
A valued reader recommended that to us
Links 04/04/2025: Tech Stock (Inc. GAFAM) Fall, Google Pretends to Do End-to-End Encrypted Emails (With Google in Control)
Links for the day
To Participate in Fedora Diversity You Must Use Proprietary Software
Not for the first time either
Yandex About to Be Three Times Bigger Than Microsoft (Bing) in Asia
That's about 60% of the world's population
Gemini Links 04/04/2025: Decoupling Updates, Elaho as Gemini Client
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, April 03, 2025
IRC logs for Thursday, April 03, 2025
Microsoft's Trouble in Africa and Asia
A new all-time high for GNU/Linux
Brett Wilson LLP Reported to the Solicitors Regulation Authority (SRA)
The saddest thing in all this is that law firms can maintain high standards shall they wish to
Links 03/04/2025: Tariff Pains and C.D.C. Cuts
Links for the day
StatCounter: Microsoft is Masking a Disaster, It's Way Behind DeepSeek Already and Interest in LLMs Has Waned
it turns out the money "raised" for "Open" "AI" may not even exist at all
Links 03/04/2025: SoftBank Money for Microsoft "Open" "AI" Probably Doesn't Even Exist, Wikimedia Foundation Blasts LLM Nuisance While Microsoft Admits Demand Has Shrunk
Links for the day
Gemini Links 03/04/2025: Patch Panel and Pictures
Links for the day
Islamic Republic of Iran: GNU/Linux at All-time High This Month, Windows Falls to 12%
Vista 10 is up this month despite being "end of life" (EoL) soon
Indonesia: All-Time Highs for GNU/Linux
What's noteworthy right now is the growth of GNU/Linux
statCounter Says GNU/Linux Usage is Up Again (Internationally)
some preliminary April data
Only on April 1st Can the Free Software Foundation Associate With Microsoft's Open Source Initiative (OSI)
We saw some pranks that day linking the FSF to Microsoft (e.g. "endorsing" Windows)
Confirmed in the Mainstream Media: A Lot of Microsoft "Workloads" Were Just LLM Slop (Helping to Fake Growth for Years, as Microsoft Had Paid "Open" "AI" to Become a "Client") and Demand is Rapidly Waning, Datacentres Canceled and/or Shut Down
Anything to facilitate further accounting fraud
Taiwan's Media Covers Closure of Microsoft's "AI" Lab, It's Time to Talk About the Gradual Death of Windows and Implosion of the "AI" Bubble
Earlier this week we showed that mostly Asian media had the 'nerve' to mention Microsoft silently shutting down its 'AI' lab
IBM Gets Rid of Kelly Chambliss as Mass Layoffs Reported in IBM Consulting, IBM Loses Key Contracts/Graft
IBM Consulting has been in disarray lately
More Gains for GNU/Linux, Based on Web Surveys
the Steam site shows rapid growth for "Linux" this month
Slopwatch: Anti-Linux Articles, Not Even Written by Humans
Why aren't Web sites more vocal about this problem?
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, April 02, 2025
IRC logs for Wednesday, April 02, 2025
Links 03/04/2025: Apple Fined Over Secret Surveillance, "Elegant Writer For A More Civilized Age"
Links for the day
Gemini Links 02/04/2025: Books and Cold Tea
Links for the day
Links 02/04/2025: More Layoffs, Nokia Again Takes Advantage of Illegal and Unconstitutional Patent Court With Nokia Staff as 'Judges'
Links for the day
Links 02/04/2025: Seizures and Returns to Windows of 24 Years Ago
Links for the day
LLM Slop Helps Obscure and Distort News About Layoffs (IBM, GAFAM)
It's hard to find accurate information
Links 02/04/2025: Microsoft Developers Are Threatening to Go on Strike, World Backup Day Noted
Links for the day
Gemini Protocol Has Growing Appeal (the Web Got Too Bloated and Full of LLM Slop)
For any "data plan" with bandwidth limits or "tiers" it would be cheaper to use/browse Geminispace
The Web Can Survive LLM Slop, But Only If We Collectively Shun and Discourage Serial Sloppers
Doing nothing ought not be a possibility
Amid Secret Shut-downs and Mass Layoffs at Microsoft (4 Waves of Layoffs in 3 Months of 2025) Some Microsoft Staff Expected to Go On Strike
workers going on strike
Gemini Links 02/04/2025: No more on Mastodon and Gemini Mention Script in Go
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, April 01, 2025
IRC logs for Tuesday, April 01, 2025
My Motion Disbarring or “Striking Off” Brett Wilson LLP for Enabling Violent Americans Who Try to Crush Microsoft Critics in the United Kingdom by Multiple SLAPPs
"Guns for hire" (for Microsoft people who received Microsoft salaries)
The U.S. Patent and Trademark Office Hijacked Again by Patent Litigation Industry, as President Cheeto Prioritises Aggressors
The "mafia" has taken over the "industry" and the Federal system (justice and constitutions trampled upon)
Ubuntu Slop and FUD Manufactured With LLMs and Funded (by Oneself) 'Studies'
Slop and FUD are ruining the Web