Common Car Diagnostic Error Codes Explained
Common car diagnostic error codes identify the system that noticed an abnormal condition; they rarely name the failed part. Record the full code, status, symptoms and freeze-frame data before deciding what to test.
Simple checks may find a loose connector or fuel cap, but recurring misfire, overheating, braking, airbag or high-voltage faults belong with a competent technician.
Read the code as a clue, not a parts order
A high-mileage owner may resent paying a diagnostic fee simply to hear “the computer says P0420”. Owning a reader can remove that first layer of uncertainty, but it does not supply the test plan. The RAC explains that diagnostic trouble codes are stored by the on-board system and read through a scan tool; thousands exist, and the exact vehicle context still matters.
The first letter gives a broad family: P for powertrain, B for body, C for chassis and U for network communication. Generic P0 codes are more widely standardised; manufacturer-specific codes and module data require the right information for the make, model, engine and year.
Ten common code patterns and sensible first checks
| Code | Typical description | Reasonable non-invasive check | Do not assume |
|---|---|---|---|
| P0300 | Random or multiple-cylinder misfire detected | Note rough running, fuel level and recent work; avoid heavy load | That one ignition coil is definitely faulty |
| P0301–P0304 | Misfire detected on a named cylinder | Record cylinder and freeze-frame; seek testing if flashing/rough | That replacing the spark plug must cure it |
| P0171 / P0174 | System too lean, bank 1 / bank 2 | Look for a loose intake hose or obvious air leak | That the oxygen sensor caused the lean reading |
| P0420 / P0430 | Catalyst efficiency below threshold | Check for related misfire or exhaust-leak codes first | That the catalytic converter should be replaced immediately |
| P0442 | Small evaporative-emissions leak detected | Check the fuel cap is correctly fitted and undamaged | That every UK car exposes the same EVAP detail |
| P0455 | Large evaporative-emissions leak detected | Inspect the fuel-cap seal and obvious disconnected hoses when safe | That clearing it repairs the leak |
| P0101 | Mass-airflow circuit range/performance | Check the intake path and connector for obvious disturbance | That the airflow sensor itself is the root cause |
| P0113 | Intake-air-temperature circuit high input | Check whether a connector was left unplugged after service | That “high input” means high air temperature |
| P0130 / P0150 | Oxygen-sensor circuit fault | Record bank/sensor designation and inspect accessible wiring | That an oxygen sensor alone explains every related code |
| P0401 | Insufficient EGR flow detected | Record operating conditions and related air-flow codes | That a home cleaning is safe or sufficient on every engine |
Descriptions vary by vehicle and software. Verify against manufacturer service information before acting.
A repeatable diagnosis sequence
- Record all modules, code numbers and statuses—stored, pending or permanent.
- Capture mileage, symptoms and freeze-frame data before clearing anything.
- Check battery voltage and recent work; low voltage or a disturbed connector can create multiple misleading symptoms.
- Group related codes and address the most fundamental fault first. A misfire can trigger catalyst-efficiency codes downstream.
- Perform only safe visual checks within your competence.
- After a verified repair, clear codes only if the procedure requires it, then rescan after an appropriate drive.
Where an older-car owner can genuinely save effort
The value is triage. You can tell a garage “steady EML, P0302 pending and stored, rough only on cold start” instead of “a light came on”. That sharper brief can reduce repeated explanation and helps you judge whether a quotation addresses the evidence. It does not guarantee a cheaper repair, and a professional diagnostic charge includes testing and interpretation—not just reading five characters.
Three mistakes that create bigger bills
- Firing the parts cannon: replacing the named-looking component without checking wiring, leaks or upstream causes.
- Clearing too early: deleting status and freeze-frame evidence before anyone has seen it.
- Ignoring severity: continuing to drive through a flashing misfire or overheating because the code “looks familiar”.
Use our car code reader procedure for the connection steps, and the warning-light triage when safety is the immediate question.
Product-page note
ScanVia currently lists a wireless XTOOL OBD2 code reader at £95.57. Confirm the exact model, vehicle/function coverage, app requirements and current terms before ordering; this article does not extend the product page's claims.
Frequently asked questions
Does a fault code tell me which part to replace?
Usually not. It identifies a detected condition or circuit. Wiring, leaks, voltage, another component or operating conditions may be the root cause.
Can a weak battery create several diagnostic codes?
Low system voltage can contribute to communication and sensor faults. Record the codes, check battery and charging condition safely, and avoid assuming every listed module has failed.
Is P0420 always a failed catalytic converter?
No. Catalyst efficiency is the detected condition; misfires, exhaust leaks, sensor issues and the catalyst itself are among the possibilities that require testing.
Why did a code return after I cleared it?
Clearing removed the record, not the cause. When the ECU detects the condition again, the pending or stored code and warning can return.
Sources
- RAC, engine, DTC and OBD codes (accessed 20 July 2026).
- RAC, what a car diagnostic test does (accessed 20 July 2026).
- The AA, engine management light guidance (accessed 20 July 2026).