As Motorsport.com Italia reports, the FIA has wrapped up its investigation into the wild software gremlins that forced a stoppage during the formation laps ahead of the Bahrain Grand Prix in Malaysia at Sepang. It was a bizarre situation that immediately sparked questions about the reliability of the electronic management systems powering these modern power units and the depth of testing carried out before race day.
The governing body has officially hit back at claims that the software was thrown onto the cars without proper vetting. According to the investigation, the root cause was a very specific cocktail of low internal combustion engine revs and electrical power limitations kicking in across damp sections of the circuit. The system was programmed to slash 250 kW of power in designated zones, but running at exceptionally low speeds on a wet track produced entirely unforeseen consequences. Several cars suffered a drop in power far beyond what was anticipated, with zero chance to claw it back in those sectors.
Faced with criticism over a lack of testing, the FIA pushed back hard by detailing the groundwork done prior to the weekend. Teams and power unit manufacturers had already put the software through simulator drills and track-tested it during FP1 sessions at the Belgian Grand Prix and the Dutch Grand Prix. Nikolas Tombazis, single-seater technical director for the FIA, oversaw a process that proved the issue wasn't a total absence of preparation, but rather the sheer difficulty of catching every single operational variable in testing as electronics grow increasingly complex.
Looking ahead, if similar weather hits the upcoming Singapore Grand Prix, the federation will revert to the exact software configuration used in Malaysia. But a proper, dedicated fix for wet-weather power unit management is on the way for the United States Grand Prix scheduled for 25 October, alongside strengthened verification procedures combining simulations and tighter collaboration between the FIA, teams, power unit manufacturers, and the standard electronic control unit supplier.
The timeline of Sunday's intervention was remarkably fast. The start procedure was halted at 15:45 following two formation laps. By 15:50, just five minutes later, the technical group had already isolated the root cause and distributed an updated configuration.
Extra guidance on how to install and run the new software reached the garages at 16:03. Integration wrapped up at 16:20, the ten-minute warning signal dropped at 16:22, and the cars finally rolled out of the pit lane at 16:33. In under fifty minutes, the technical teams diagnosed an intricate software anomaly, built a patch, and pushed it across multiple different power unit architectures safely.
