Intermittent fault codes are trouble codes caused by a problem that is present only some of the time. The check engine light may come on for a few days and then go out, or a code may appear in memory even though the car seems to run perfectly when you inspect it.
These faults frustrate owners and technicians alike, because a problem that is not happening right now is hard to test. This guide explains why intermittent faults occur, how the OBD-II system records them, and which practical methods help you catch the condition in the act and fix it for good.
Why Some Faults Refuse to Stay Put
A permanent failure, such as a fully broken wire, sets a code every time the monitor runs. An intermittent failure appears only when certain conditions line up, such as engine heat, road vibration, rain, a cold morning or a specific engine load.
When those conditions pass, the circuit works again and the monitor reports a pass. The module may then turn the warning lamp off after a number of good trips, but it usually keeps a record of the earlier fault in memory for a while.
That stored record is valuable. It proves the fault happened, even if you cannot reproduce it on demand. Treat it as evidence rather than as a glitch to be cleared and forgotten.
How OBD-II Records a Fault That Disappears
OBD-II uses several code states. A pending code appears when a monitor detects a problem once. If the fault repeats on a later trip, the code becomes confirmed and the warning lamp usually turns on. Exact rules vary by monitor and by manufacturer.
If the fault stops recurring, the lamp often goes off after several consecutive passing trips, while the confirmed code stays stored for additional drive cycles before it ages out. Many scan tools show these states separately, so check every category, not only the active list.
Freeze frame data adds another clue. It captures engine conditions such as speed, load and temperature at the moment a code set. For an intermittent fault, those values describe the exact situation you need to recreate during testing.
Common Sources of Intermittent Codes
Most intermittent problems trace back to things that change with temperature, movement or moisture. Electrical connections top the list, but mechanical and fuel-related causes appear too.
Typical sources include:
- Loose, corroded or spread connector terminals.
- Wires broken inside insulation that separate when the harness moves.
- Grounds with rust or loose fasteners that fail under load.
- Components that fail only when hot or only when cold.
- Water that enters a connector or module during rain or car washes.
Notice whether the code appears after heavy rain, on rough roads or only on long drives. Patterns like these point toward moisture, vibration or heat as the trigger, which narrows the search before you lift a single tool.
Keep a simple log with the date, weather and driving conditions each time the light comes on.
Techniques for Catching an Intermittent Fault
The key is to make the fault happen while you are watching. Each technique below tries to recreate the conditions that trigger the failure.
Recreate Freeze Frame Conditions
Review the freeze frame data and note the engine temperature, speed and load when the code set. Then drive under similar conditions with a passenger watching live data on the scan tool. Faults that appear only at highway speed or only on a cold start often show themselves this way.
Repeat the test more than once if needed, since some faults need several minutes in the right conditions.
Use the Wiggle Test
With the engine running in a safe, ventilated area and the parking brake set, gently flex harness sections and connectors related to the code while watching live data. A sudden change, dropout or spike shows the weak point. Work one small section at a time so you can pinpoint the spot.
Apply Gentle Heat or Moisture
Some service manuals suggest warming a suspect component with a hair dryer or misting a connector lightly with water to reproduce a fault. Use these methods carefully and only as the manual describes. Never spray water on ignition parts or high-voltage components.
Change only one condition at a time, so that when the fault appears you know exactly which factor triggered it.
Using Live Data and Recording Features
Many scan tools can record live data during a drive and play it back later. This is ideal for intermittent faults, because the passenger can start recording when symptoms appear and you can study the values afterward at home.
Look for a sensor value that suddenly drops to an extreme, flatlines or disagrees with related sensors at the moment of the symptom. A coolant reading that briefly jumps to an impossible value, for example, points to a connection problem rather than a real temperature change.
Choose a small number of related values to record. Recording too many parameters can slow the data rate on some tools and make brief dropouts harder to see in the playback.
Why Clearing the Code Too Soon Hurts Diagnosis
It is tempting to clear an intermittent code and see whether it returns. Doing this erases the freeze frame data and stored history that describe the original event, which removes some of your best clues.
Clearing codes also resets readiness monitors to not ready. If an emissions inspection is due, the vehicle may fail simply because the monitors have not had time to run again after the codes were erased.
Record every code, its status and the freeze frame data before clearing anything. Photographs of the scan tool screen are an easy way to keep this information for later comparison.
Some scan tools can also save a full report to a file or print it. Keep that report with your vehicle records so the history is not lost.
A Practical Routine for Intermittent Problems
A consistent routine keeps the search organized when the fault may take days or weeks to reappear. Following the same steps each time also makes your notes easier for a technician to use.
- Save all codes, code states and freeze frame data before doing anything else.
- Read the service information description and the conditions that set the code.
- Inspect connectors, grounds and harness routing on the affected circuit.
- Try to reproduce the fault using freeze frame conditions and the wiggle test.
- Repair only what testing confirms, then verify with a road test and passenger.
If the fault returns after a repair, compare the new freeze frame data with the old record. Different conditions may suggest a second problem, while identical conditions suggest the first repair missed the real cause.
Resisting the Urge to Replace Parts
Intermittent faults lead many owners to replace parts one after another, hoping the problem will vanish. Sometimes the code stays away for a few weeks by chance, which makes the wrong part look like the fix.
A trouble code identifies a fault that a monitor detected, not a specific part that failed. Test before replacing anything. When a connector or ground causes the problem, a new sensor will plug into the same faulty connection and the code will eventually return.
Confirm the fault with evidence such as a recorded dropout, a failed wiggle test or a measured voltage loss. That proof is worth more than any guess, and it protects you from spending money on parts that were never broken.
Safety During Road Tests and Engine-Running Checks
Never operate a scan tool or study live data while driving. Bring a passenger who can watch the screen, start recordings and call out values while you concentrate on traffic and road conditions.
For checks with the engine running in the driveway, set the parking brake, work outdoors or with good ventilation, and keep clear of the cooling fan, belts and hot exhaust parts. The fan can start without warning on many vehicles.
If an intermittent code involves the airbag system or a hybrid high-voltage system, do not attempt wiggle tests or probing yourself. Those systems require trained technicians and manufacturer procedures.
Wear eye protection when working near a running engine, and let hot components cool before you touch connectors mounted on or near the exhaust.
Building a Long-Term Record for Your Vehicle
Intermittent fault codes become much easier to solve when you keep a record over time. Note each appearance of the code, the weather, the driving situation and any symptoms, along with the freeze frame values captured by your scan tool.
Patterns usually emerge within a few events. A fault that appears only after rain points toward water entry, while one that appears on long trips points toward heat. That pattern is often what connects the code to a specific connector or component.
If the cause remains hidden, share the full record with a qualified technician. Detailed notes and saved data can turn a difficult intermittent problem into a focused diagnosis and save you from paying for repeated guesswork.