Enter a scanner code or search the reference titles. You’ll see where the wording came from and what still needs checking before anyone can name a repair.
Works without an account or a recording.
Random or multiple-cylinder misfire detected
Powertrain / combustion
The code records a detected misfire pattern; it does not identify the failed part.
A code records what a control unit detected. It does not, by itself, identify a failed part or establish a repair.
These steps preserve the evidence a technician needs, without guessing a part from a code.
Record all codes, the reporting modules, code status and freeze-frame data before clearing anything.
Note the exact make, model, year, engine or powertrain, mileage, warning lights and when the symptom occurs.
Use the maker’s test steps and measured data to separate wiring, controls, mechanical issues and component faults.
For a red oil-pressure, brake or overheating warning, or a flashing engine warning with rough running, stop safely and seek assistance. Avoid probing restraint circuits or opening high-pressure fuel systems yourself.
A code alone cannot produce a credible UK repair quote. Ask for a written estimate after diagnosis, with the proposed work, parts, labour and VAT set out. Check a garage quote → NI Direct explains estimates and quotes ↗
These are openly licensed reference descriptions and a small set of Signal-authored summaries. They are not a live vehicle scan or a manufacturer workshop manual.
MIT-licensed OBDIICodes, pinned revision a146d4753057, reviewed 2026-09-18. Generic P0/P2 wording; individual entries have not all been independently verified.
Read the MIT notice ↗CC0 obdex, pinned revision bc58b0eb7273, reviewed 2026-09-18. Wider title coverage, with lower source authority.
Read the CC0 notice ↗SAE J2012 governs diagnostic code definitions and allocations. Its protected code data has not been copied into this lookup. Vehicle-maker and module wording is needed where a generic title is uncertain.