Start by saving the complete report, then relate faults to symptoms and the conditions in which they occurred. Several codes can share a cause, describe consequences of the same problem or represent independent faults. The number of entries tells you neither how many parts need replacing nor the order of checks.
First, assess the vehicle’s condition
01 · Save the report
Before clearing, keep the reference information.
Clearing codes can remove useful evidence and reset some monitors. Export the report or take readable screenshots before any work.
Prepare this checklist:
- Vehicle: model, year, exact engine and mileage.
- Complete scan: all codes, descriptions and any subcodes, without selecting only the first result.
- Control modules: which module recorded each fault, which modules were scanned and which the tool could not read. An engine OBD reader may show only part of the vehicle.
- Statuses: copy the tool’s exact terms. A confirmed code is not necessarily present at that moment.
- Available data: freeze frames, occurrence counts, associated mileages or dates, where available.
- Symptoms: difficult starting, jerking, loss of power, dashboard messages, cold or warm conditions.
- History: when the problem started, recent repairs, a disconnected battery, an incident or previous code clearing.
To interpret the report’s terms, read our guide to fault code status.
02 · Form hypotheses
Look for a link without assuming one.
Codes read together did not necessarily occur together. Memory can contain a recent fault, an intermittent issue and a record of an older event.
Compare their recording conditions. Similar mileages, symptoms that began together and consistent values can strengthen the case for a link. Clocks, counters and available data vary between control modules: do not infer a precise timeline without checking their meaning.
The freeze frame data shows some parameters stored when the fault was detected. It helps place the event in context, but is not always available for every code.
Then group faults by function: electrical supply, intake, combustion, emissions control, communication between modules… Look for a possible technical connection: a shared circuit, information used by several systems or an expected consequence of the first problem.
An electrical line of enquiry becomes relevant if the report and history support it, for example after difficult starting accompanied by low-voltage faults. A large number of codes alone does not identify the battery as the cause.
03 · Compare two lines of reasoning
One report, two lines of reasoning.
The following examples are entirely fictional. They illustrate a method and represent neither customer cases nor diagnoses performed by Diagolia. Descriptions are simplified; on the vehicle, keep the tool’s wording and check the applicable documentation.
Report A: a possible shared cause
Fictional context: V6 petrol engine with two cylinder banks, rough idle and engine warning light. The engine control module contains:
- P0171: system too lean, bank 1.
- P0174: system too lean, bank 2.
The evidence. Both banks show the same category of fault. Unmetered air, an incorrect air measurement or a fuel-supply problem affecting the whole engine could explain the connection. The codes alone cannot distinguish these possibilities.
What is missing. You need the conditions in which the fault occurs and a comparison of both banks’ fuel trims: the fuel adjustments made by the control module. Intake condition and recent work also matter.
The confirmation check. The workshop compares data under the manufacturer’s specified conditions, then selects a targeted check. If unmetered air is suspected, a leak test with suitable equipment can locate it. A negative test calls for reassessing the hypothesis; it does not justify replacing the airflow meter by default.
After repairing an actual leak, engine operation and both banks’ behaviour still need checking. Symptoms and faults disappearing together, after the necessary checks, strengthen confirmation of the shared cause.
Report B: two possibilities to keep separate
Fictional context: petrol engine, recently developed jerking. Two codes appear in the engine control module:
- P0301: cylinder 1 misfire detected.
- P0456: a very small leak detected in the evaporative emission control system, known as EVAP.
The evidence. The misfire fault matches the current jerking. An earlier report already contained P0456 when the engine was running normally. This difference points towards two possible problems, even though both codes are in the same module.
What is missing. Check when the misfires occur, whether they remain concentrated on cylinder 1 and whether the EVAP fault is still reproducible. History alone cannot exclude every link: the vapour purge circuit communicates with the intake.
The confirmation check. The workshop investigates the misfire with appropriate ignition, injection or mechanical checks, based on the initial findings. The EVAP circuit has its own leak and purge-control procedure. P0301 does not condemn a coil; P0456 does not automatically condemn a fuel cap.
If a misfire cause is confirmed and corrected, smooth engine operation alone does not close the EVAP fault. Each possibility needs its own final verification.
04 · Verify on the vehicle
A useful check answers a question.
A useful order combines three criteria: safety, consistency with the symptom and the check’s ability to distinguish hypotheses. The first code displayed does not automatically take priority.
Before replacing anything, ask a specific question: ‘What would confirm this cause?’ Then record the result. This avoids accumulating replacement parts and helps explain what actually changed.
After the work, check the symptom and expected measurements. Any code clearing comes after saving information, as part of the procedure. A code absent immediately afterwards does not prove the repair: its monitor may not have run yet.
Tests, electrical measurements and fuel-system checks should be left to someone with suitable equipment and skills. Never consult a tool while driving. For the driver, retaining information and describing the problem precisely already provides practical help with diagnosis.
Prepare your case with Diagolia
Gather vehicle details, the complete code list, symptoms and checks already performed. These put each fault in context, help distinguish possible links and prepare useful checks.
Suggested causes remain hypotheses to confirm on the vehicle. Checks and the final decision remain with the professional.
Remember: keep the report, look for links without assuming them, then select a check that can confirm or rule out a possibility. Multiple codes call for organised reasoning before a repair decision.