BMW 29F4: Catalytic-converter conversion efficiency below threshold, bank 1 — Diagnosis and Repair

29F4 is a BMW-specific DTC stored by the DME for the exhaust treatment and catalyst efficiency. Verify the complete module text because details can vary by chassis and software level. What Does 29F4 Mean? This record reports Catalytic-converter conversion efficiency below threshold, bank 1. It does not identify a failed part by itself; assess status, frequency, companion codes and freeze frame together. Code: 29F4 Definition: Catalytic-converter conversion efficiency below threshold, bank 1 Module: DME System: exhaust treatment and catalyst efficiency Key data: status, frequency, freeze frame and companion DTCs Typical cause: an exhaust leak before the catalyst or a connector problem Severity: medium Note: verify for VIN, engine and software level The fastest OBDThink split is to see whether the code is currently active and which module records appeared at the same time. Symptoms • A warning or temporary loss of the related function may occur. • The fault can be intermittent, and some vehicles show no obvious driver symptom. • Companion DTCs may identify the root cause more clearly than this record. Possible Causes Work from inexpensive, easy checks toward complex causes; do not replace a part without evidence. • an exhaust leak before the catalyst or a connector problem • a biased lambda signal, mixture fault or misfire • an aged catalyst contaminated by oil or coolant Diagnostic Steps with OBDThink OBDThink is an independent BMW coding and diagnostic mobile app and is not affiliated with BMW AG. On supported vehicles, use module scans, freeze frame and live data to gather evidence. • 1. Scan every module; save the 29F4 status, frequency, source module and freeze frame. • 2. Check battery voltage and visually inspect relevant fuses, grounds, connectors and wiring. • 3. Compare commanded and actual live values, and assess companion DTCs first. • 4. Complete physical tests with the BMW test plan valid for the vehicle and engine; avoid guess-based replacement. • 5. After repair, clear codes, complete the appropriate drive cycle and rescan every module. Is the code active? YES → Supply and basic physical checks → Live data → Component test NO → Save records → Clear code → Verify under similar conditions If it returns → Follow the vehicle-specific BMW test plan The fastest OBDThink split is to see whether the code is currently active and which module records appeared at the same time. Repair • Low cost: correct a loose connection, contaminated connector, hose or supply issue. • Medium cost: repair or replace a sensor, valve or peripheral unit only after testing confirms it. • High cost: proceed to a controller, pump or major mechanical repair only when the test plan proves the need. A successful repair means the code does not return, the warning is gone and relevant actual values behave normally. Save the final scan. Can You Drive with This Code? Do not extend the drive if you smell fuel, notice rough operation or see a new warning; stop safely and arrange inspection. 29F4 is a diagnostic starting point; the correct repair removes the measured cause rather than merely clearing the code.