OBD2 Code Guide: Definitions, Causes & Diagnosis

By Roger Holden. Updated November 10, 2026.

A trouble code tells you which test the engine computer failed, not which part to buy. Each guide gives the code's standard description, how the computer decides to set it, the causes worth ruling out in order, and when to stop driving, with sources for every one.

We check each code's wording against manufacturer service bulletins published by NHTSA and take monitor behavior from California's OBD II regulation. Diagnostic steps follow the order manufacturers give technicians: gather the evidence, fix related codes first, check for bulletins and software, then test the suspected part.

Code guides

How to read any OBD2 code

Generic codes have five characters. The letter names the system: P for powertrain, B for body, C for chassis and U for network communication. A 0 as the second character marks a generic code defined by the SAE J2012 standard; a 1 usually marks a manufacturer-specific code. The last three characters identify the fault.

Most emissions faults store a pending code the first time and a confirmed code, with the check engine light, if they're seen again on the next drive cycle in which the test runs. Under California's rules, the light turns off after three consecutive drive cycles without the fault. A light that goes out isn't proof of a repair.

Record stored, pending and permanent codes and available freeze-frame data before clearing anything. Clearing codes does not fix the fault; it can erase useful evidence and reset emissions readiness monitors.

Start with the check engine light assistant or read how to use an OBD2 scanner.