Oct 6, 2026Updated Oct 28, 20264 min read

OBD-II warning lights and codes, explained

By DriveMarker

The short answer

Read the code before you fear the light: OBD-II codes tell you which system noticed something, not what failed. The four lights below deserve attention today; everything else deserves a diagnosis, not a guess.

A lit dashboard is designed to make you panic a little. This page is the opposite: what these lights and codes generally mean, what they never mean, and the sensible order of operations before anyone sells you a part.

This is general information, not a diagnosis. Your owner's manual and a qualified workshop beat any guide, including this one.

The four lights worth not ignoring

  • Oil pressure. Stop as soon as it is safe and switch off. Low oil pressure means the engine may not be getting the lubrication it needs — continuing risks far bigger damage than the stop itself.
  • Temperature. Overheating. Stop safely, let it cool, and have it checked. Do not open a hot radiator cap.
  • Battery / charging. The car is running on borrowed time if the charging system has failed — it may get you a short distance, or not at all. Have it checked before a long trip.
  • Check engine (malfunction indicator). Steady: a fault code is stored — read the code and book a diagnosis. Flashing: stop as soon as it is safe and get it looked at.

Everything else on the dash — ABS, airbag, traction control, a service reminder — deserves attention, but usually in "diagnose and plan" rather than "pull over now" territory, unless your manual says otherwise.

Reading a code: P0xxx

Plug any OBD-II scanner into the port (your manual shows where it is) and you get codes like P0300. Read them left to right:

  1. First letter — the system. P = powertrain (engine and transmission), C = chassis (brakes, steering), B = body, U = network/can bus.
  2. Second character — generic or manufacturer. 0 = standardised code that means the same thing on any brand; 1 = a manufacturer's own code, which needs the brand's definitions.
  3. The rest — the specific condition. A system and a circumstance. Not a part number, and not a shopping list.

Which is the whole point: a code says which system noticed what, not what broke. "Misfire detected" is not "buy four coils today" — a coil, a plug, an injector, a vacuum leak and low compression can all throw the same flag.

Common codes and what they usually point to

| Code | What it flags | Common causes | | --------- | ------------------------------------------ | --------------------------------------------------------------- | | P0300 | Random or multiple misfire | Worn plugs, faulty coils, vacuum leak, low fuel pressure | | P0171 | System too lean (bank 1) | Vacuum leak, dirty mass-air-flow sensor, weak fuel pump | | P0420 | Catalyst efficiency below threshold | Ageing catalytic converter, exhaust leak, failing oxygen sensor | | P0442 | Small evaporative emissions leak | Loose or faulty fuel cap, cracked EVAP hose | | P0128 | Coolant temperature below thermostat range | Stuck-open thermostat, low coolant, faulty sensor |

None of these is a parts list. Each one describes a condition that several different components can produce. A P0300 with a rough idle and a P0300 that appears only under load may have different causes. That is why the diagnosis — the test, not the code — is what you pay a workshop for.

Before you book a repair

  • Write the codes down (photos of the scanner screen work) before you clear anything.
  • Clearing a code is not a fix. It erases the memory — and with it your best clue. Many codes return within a few drive cycles anyway.
  • Ask for the diagnosis, not the part. A workshop that quotes a repair before testing should be able to explain what the test showed.
  • Notice what changed around it. A fill-up at a new station, a cold week, a recent service — the context around a code is often the answer (and a fuel-related fault often shows up first as worse consumption — your log is evidence).

What this guide does not cover

Make-specific code libraries, hybrid and EV high-voltage faults, and anything that requires a proper scan tool and a road test. When in doubt, the manual plus a trusted workshop is the shortest path — the goal here was only to make sure the light does not win the argument before you have the facts.

If the diagnosis turns into a repair, the annual maintenance cost guide shows what common jobs typically cost and how to budget for them. And if you are simply overdue for a service, the maintenance intervals guide explains which checks belong in your own routine.

Common questions

What does OBD-II stand for?
On-Board Diagnostics, second generation — the standardised system in cars since the mid-1990s that monitors the engine and related equipment, stores fault codes and can be read with any OBD-II scanner or a workshop tool.
What does a P0xxx code mean?
The first letter says which system flagged the fault (P powertrain, C chassis, B body, U network), the zero means the code is a standardised, generic one rather than a manufacturer's own, and the remaining digits identify the specific condition — a system, not yet a part.
Should I drive with the check-engine light on?
A steady check-engine light usually means "book a diagnosis soon"; a flashing one generally means stop as soon as it is safe and have the car checked. If any oil pressure, battery or temperature light comes on, the advice is to stop safely and switch off as soon as you can.

Use the tools from this guide

Track your own numbers

Averages describe somebody else’s car. Log your fill-ups, costs and service in a free garage and the guide above turns into your own data.

Essential cookies run DriveMarker. With your permission, privacy-friendly analytics and advertising cookies do too. Cookie policy.