Recalls: BMW F80 M3 Sedan
Overview
Manufacturers, or importers, issue recalls for defects or faults which have the potential to cause injury. Generally, manufacturers will inform the original buyers if their vehicle is subject to a recall and of the steps required to remedy the defect or fault. Please note that the recalls below (if any) are for Australian-delivered vehicles only. Furthermore, the number of recalls should not be taken as an indication of a model’s reliability or its safety more generally.
Recalls: BMW F80 M3 Sedan
2014-17 BMW F80 M3 Sedan: Takata airbag recall
In December 2018, a staged recall campaign was initiated for BMW ‘F Series’ models – this included 2014-17 BMW F80 M3 Sedan vehicles. These vehicles had Takata driver’s airbags and the propellant wafers in these airbags could absorb moisture over time. In the event of airbag deployment, excessive internal pressure could cause the metal inflator housing to rupture and metallic fragments could be projected through the airbag cushion towards vehicle occupants – these fragments posed a risk of serious injury and fatality. For the VINs of the recalled vehicles, please see PRA 2018/17191.
2016 model year BMW F80 M3 Sedan: loss of drive
In January 2019, recall campaign 00 26 4001 00 was issued for 2016 model year BMW F80 M3 Sedans that were available for sale in Australia from 1 March 2016 to 31 August 2016. In these vehicles, the carbon fibre (CFK) driveshaft contained a three-hole flange with a pushing piece which was not produced with sufficient long-term drivability. If the pushing piece was pulled out of the three-hole flange, then drive torque may no longer be transmitted to the rear wheels, resulting in a loss of drive – this could cause a critical driving situation which increased the risk of a collision and injury to vehicle occupants and other road users. For the VINs of the recalled vehicles, please see PRA 2019/17309.
Problems and faults: BMW F80 M3 Sedan
Overview
This section identifies potential problems, causes and fixes based on the experiences of owners and repairers, online sources and technical service bulletins. This information is provided solely for reference purposes and AustralianCar.Reviews recommends that only properly qualified persons carry out repairs or modifications. Furthermore, the number of items below should not be taken as an indicator of a model’s reliability or the frequency with which they may occur.
To report a problem or fault to the AustralianCar.Reviews team, please use the Contact Us form. Note that AustralianCar.Reviews does not offer advice on automotive problems or disputes; such enquiries will not receive a reply. For vehicles purchased from dealers after 1 January 2011, please see our Australian Consumer Law fact sheet.
2014 BMW F80 M3: ‘Service Engine Soon’, ‘Drivetrain Malfunction’ and VANOS faults
In September 2014, BMW North America issued Service Bulletin SI B12 26 14 for BMW F80 M3 Sedans that were manufactured prior to July 2014. These vehicles may exhibit the following symptoms:
- Illumination of the ‘Service Engine Soon’ warning (Malfunction Indicator Light);
- The engine may enter a reduced power mode with the ‘Drivetrain Malfunction’ message displayed; and,
- One or more VANOS faults may be stored in the DME, even though the engine is mechanically sound and no unusual noises can be heard from the VANOS area. These VANOS faults related to implausible camshaft position (intake or exhaust), the camshaft stuck situation, or the camshaft angle offset relative to the crankshaft being outside the tolerance range.
According to the service bulletin, these symptoms could be due to unfavourable Engine Position Management (EPM) parameters in the DME software. The service bulletin recommended test plans be performed using BMW’s ISTA/D diagnostics system and any VANOS hardware issues were to be corrected. After performing repairs, or if the ISTA test plan was inconclusive, the vehicle’s DME software was to be re-programmed with the latest version of ISTA/P. If further VANOS control faults occurred after the DME software was updated, further diagnosis would be required to identify its cause.
