Mode Three stored codes are the confirmed emissions-related trouble codes that a scan tool retrieves when it asks the engine computer for its fault list. When a code reader shows the codes behind a lit check engine lamp, it is almost always using this service.
OBD-II defines ten standard diagnostic services, often called modes and numbered 01 through 0A. This article focuses on Mode 03: what it returns, how it differs from the services that show pending and permanent codes, and the limits every DIYer should understand before acting on a result.
The Request Behind Every Read Codes Button
Pressing read codes on a basic scanner sends a standardized request over the diagnostic connector. In the SAE J1979 standard, that request is service $03, written in hexadecimal and commonly shortened to Mode 3. Any emissions-related control module that has confirmed faults answers with its list.
Because the request is standardized, it works the same way on every OBD-II vehicle, whether the car uses an older protocol such as ISO 9141-2 or the CAN network required on US vehicles from model year 2008. The tool does not need brand-specific software to perform it.
That universality is the reason inexpensive code readers are useful. They may lack advanced features, but they can always ask Mode 3 for stored codes and display the five-character results in a format any service reference can interpret.
What Counts as a Stored Code
A stored code, also called a confirmed code, is a fault the computer has verified rather than merely suspected. For most emissions monitors, a fault must appear on two separate qualifying trips before the code moves from pending to confirmed and the malfunction indicator lamp lights.
Some faults confirm immediately. A severe misfire that could overheat the catalytic converter, for instance, can set a confirmed code such as P0300 or P0301 and flash the warning lamp on the first occurrence. The exact logic is set by each manufacturer within the regulations.
Once confirmed, the code stays in Mode 3 memory until it is cleared with a scan tool or erased automatically after enough fault-free warm-up cycles. Turning off the lamp on its own does not remove the stored record, which helps technicians reconstruct past problems.
How Mode Three Fits Among the Code Services
Three OBD-II services return trouble codes, and each answers a different question. Reading all three gives a far more complete picture than relying on Mode 3 alone.
Mode 03: Confirmed Codes
Mode 3 reports codes that have matured to confirmed status. These are generally the codes responsible for a steady malfunction indicator lamp. They are the starting point for most repairs, because the computer has seen the fault more than once or judged it serious enough to confirm right away.
Mode 3 is also the list most repair shops and parts counters print first when they scan a car.
Mode 07: Pending Codes
Mode 7 reports faults detected during the current or most recent completed drive cycle that have not yet confirmed. A pending code can exist without any warning lamp. It is an early warning, and it is often the quickest way to check whether a repair actually fixed the problem.
Many basic readers hide pending codes behind a separate menu, so look for it.
Mode 0A: Permanent Codes
Mode 0A, sometimes called Mode 10, reports permanent codes. These mirror confirmed codes that commanded the lamp on, but they cannot be erased with a scan tool. The computer removes them only after the related monitor runs and passes, which prevents faults from being hidden by clearing.
Permanent codes matter most in states that use plug-in OBD-II emissions inspections.
Reading Stored Codes Step by Step
Retrieving Mode 3 codes is simple, but a careful routine prevents mistakes and preserves information you will need later. Do this before any parts are touched and before anything is cleared.
- Park outdoors or in a ventilated space, set the parking brake, and turn the engine off.
- Plug the scan tool into the 16-pin connector under the driver’s side of the dashboard.
- Turn the ignition on, engine off, unless the tool instructs otherwise, and select read codes.
- Write down every stored code exactly as shown, including the letter and all four digits.
- Check pending and permanent codes and freeze frame data before closing the session.
If the tool reports that it cannot communicate, confirm that the ignition is on and the connector is fully seated. Communication problems are a separate diagnostic issue and should not be confused with a car that simply has no stored codes.
Making Sense of the Codes You Retrieve
Each Mode 3 result is a five-character code. The letter shows the system, with P for powertrain being by far the most common in this service. The second character shows whether the definition is generic SAE, shown as 0, or manufacturer-defined, shown as 1; the meaning of 2 and 3 depends on the letter.
Generic codes have published standard meanings. P0171 means system too lean bank 1, and P0442 means a small leak was detected in the evaporative emissions system. Manufacturer codes require the vehicle’s own service information, because their definitions are not shared across brands.
Read the definition carefully. A code describes what a monitor saw, such as a lean condition, not the part that caused it. A lean code can follow a vacuum leak, a weak fuel supply, or a sensor error, so the definition guides testing rather than replacing it.
What Mode Three Does Not Show
Mode 3 is limited to emissions-related codes. A clean Mode 3 result does not mean the whole vehicle is fault-free, because several kinds of faults are usually reported elsewhere.
- Airbag (SRS) faults, which live in the restraint control module.
- ABS and stability control faults stored in the brake module.
- Body and comfort faults such as power windows, locks, and lighting.
- Network communication faults recorded by modules outside the emissions system.
Many manufacturers also store enhanced codes in the engine and transmission computers that are outside the generic service. These require manufacturer-level access. Professional scan tools can read them, while basic code readers often cannot, which is why a technician may find codes your tool missed.
Mode 3 also does not explain conditions at the moment the fault occurred. That information lives in freeze frame data, retrieved through Mode 2. Pairing the stored code with its freeze frame snapshot makes the result far more meaningful during diagnosis.
Why a Lit Lamp Can Show No Stored Codes
Occasionally a scan tool reports no codes while the warning lamp is on. One possible reason is that the tool is not reaching the correct module or protocol. Rechecking the connection, ignition position, and tool compatibility usually resolves this.
Another reason is that the light is not the malfunction indicator lamp at all. Many dashboards use similar amber symbols for other systems, and those faults live in other modules. Confirm which lamp is on using the owner’s manual.
On rare occasions, a lamp can be commanded on by a module the generic service does not query, or by a fault in the instrument cluster itself. If basic checks do not explain a lamp with no stored codes, a technician with manufacturer-level tools should take a look.
Common Mistakes With Stored Codes
The most expensive mistake is replacing the part named in a code definition without testing. An oxygen sensor code may point to wiring, an exhaust leak, or an engine condition the sensor is correctly reporting. Test before replacing parts, every time.
Another mistake is fixing only the last code on the list. When several codes appear, one fault often triggers others. Electrical or sensor circuit problems frequently cause downstream efficiency or performance codes, so review the full list and think about which fault could explain the rest.
A third mistake is clearing codes immediately to see if they come back. Clearing erases freeze frame data and resets readiness monitors, discarding useful evidence. Record everything first, and clear only after a repair has been made and you are ready to verify it.
When Professional Help Makes Sense
Mode 3 codes are a strong starting point, but some situations go beyond basic tools. Manufacturer codes, multiple related faults, or intermittent problems that appear and disappear often require deeper data and specialized test equipment.
Seek a qualified technician quickly when a flashing malfunction indicator lamp accompanies misfire codes, because continued driving can overheat the catalytic converter. Hybrid and electric vehicles with codes related to high-voltage systems should be handled only by trained technicians, never by DIY probing.
Bring your notes when you visit a shop. A list of stored, pending, and permanent codes, along with freeze frame details and any recent repairs, helps the technician start in the right place and avoids paying for steps you have already completed.
Turning Stored Codes Into a Repair Plan
Treat each stored code as a lead. Start with the code definition from a reliable source, then check for technical service bulletins and known issues for your vehicle. Inspect the obvious first, including connectors, vacuum hoses, and the fuel cap where relevant.
Next, perform tests that confirm or rule out each possible cause. Live data, visual inspection, and basic electrical checks can narrow the list before any parts are purchased. Keep notes on what you tested and what each result showed.
After the repair, clear the codes with the scan tool, complete normal driving, and check Mode 3 and Mode 7 again. A stored code that does not return, combined with a completed monitor, is the clearest sign the problem has truly been solved.