P0606
- Powertrain
- Generic (SAE)
Get it looked at now
The module controlling fuel, ignition, and often throttle has declared itself unreliable. Limp mode, sudden power loss, a stall, or a no-start are all realistic outcomes, and a stall at speed is a genuine hazard. It is not automatically critical because many cases turn out to be a power or ground fault or a needed calibration update rather than a dead module, but the vehicle should not be treated as dependable until it is diagnosed.
- Safe to drive
- Drive only as far as necessary to reach a shop, and avoid highways, heavy traffic, and towing. Sudden power loss, limp mode, or a no-restart are all possible, and a stall takes power steering assist with it while leaving the brake booster only about one or two pedal applications of reserve.
ECM/PCM Processor Fault
The engine computer failed its own internal self-test. The module is reporting that something inside it is not working correctly. That does not automatically mean the computer must be replaced, because bad power, bad grounds, and outdated software cause this too.
P0606 is set by the module about itself. The typical mechanism is a redundant monitoring processor cross-checking the main processor, or a memory and checksum integrity test, failing to agree. Some strategies also set it when an internal output driver reports a fault the module cannot attribute to an external circuit. Because the module has lost confidence in its own calculations, it usually falls back to a default fuel and throttle strategy, which is what the driver experiences as limp mode.
How the car detected itThe module runs continuous internal integrity checks: a watchdog timer, a second processor recomputing critical values and comparing them, and read-write and checksum tests on memory. A disagreement or a failed test sets the code, often immediately and often on the first occurrence rather than after two drive cycles, because the module treats its own integrity as safety-relevant. Low supply voltage and poor grounds cause the same internal checks to fail without any actual hardware defect, which is why supply quality has to be proven first.
A trouble code records what a control module measured. It does not identify which part failed. Test before replacing anything.
- Safe to drive
- Drive only as far as necessary to reach a shop, and avoid highways, heavy traffic, and towing. Sudden power loss, limp mode, or a no-restart are all possible, and a stall takes power steering assist with it while leaving the brake booster only about one or two pedal applications of reserve.
- Urgency
- Get it looked at now
- Will it pass emissions
- Not affected
- If ignored
- Expect the vehicle to become progressively less predictable: reduced power events, stalls, and eventually a no-start that leaves it where it stops. Other modules will set communication and sympathetic faults because they depend on data this module publishes. Nothing mechanical is being damaged, but the vehicle's reliability cannot be trusted while this code is present.
- Check engine light
- Solid
- Possible limp mode or no-start
- Multiple follow-up faults across modules
- Reset/relearn may be needed after repair
Many vehicles show no symptom at all beyond the warning light. The absence of a symptom does not mean the fault is not real.
These are the causes this code can have. For the order to work through them in, see what to check first.
| # | Cause | How often | Component |
|---|---|---|---|
| 1 | Internal processor or memory failure | Very common | — |
| 2 | Water ingress / corrosion in module | Occasional | — |
| 3 | Module software outdated, reflash may resolve | Occasional | — |
Ordering reflects how often each cause is responsible in general, not a probability for your vehicle. Confirm by testing.
In order. Each of these is cheaper or faster than what follows it, and each one can make the rest unnecessary.
Battery and charging system health
Low or unstable supply voltage makes a healthy module fail its own internal checks. This is the most common recoverable cause and the cheapest to rule out. Check for a P0562 or other voltage code stored alongside.
The module's power feeds and grounds
Voltage drop on a module ground is a classic producer of internal fault codes. Testing the feeds and grounds before condemning a module regularly prevents an unnecessary replacement.
Manufacturer reprogramming bulletins for this code
A meaningful share of P0606 cases on specific platforms are resolved by a calibration update rather than hardware. Checking takes minutes and can end the diagnosis.
Evidence of water intrusion or physical damage at the module
Corroded pins and a wet module housing explain the fault outright. Module location varies by manufacturer, and some are mounted where water collects.
Recent history: jump starts, welding, a flat battery, or an interrupted programming session
All of these damage or corrupt modules, and knowing it happened points you at the right answer immediately.
Scan every module, not just the engine controller
Tools Full-system scan tool
Record all codes network-wide and note whether communication faults, under-voltage codes, or a scatter of sensor faults are present. A P0606 alongside a low-voltage code is a very different problem from a P0606 standing alone.
ExpectedA clear picture of whether P0606 is isolated or part of a network-wide or voltage-driven pattern
Verify battery and charging system before anything else
Tools Digital multimeter, battery tester, scan tool
Load test the battery, measure charging voltage against the commanded target, and confirm the battery terminals and grounds are clean and tight. Fix any supply problem completely and then re-evaluate the code, because a healthy module can produce P0606 on a poor supply.
ExpectedA battery that passes load test and a charging system producing its commanded voltage
Voltage drop test the module's power feeds and grounds
Tools Digital multimeter, wiring diagram
Identify the module's supply and ground circuits from the wiring diagram, then measure drop under load rather than just checking for continuity. A ground with resistance reads fine with an ohmmeter and still causes the module to misbehave.
ExpectedMinimal drop on every feed and ground with the circuit loaded
Inspect the module and its connectors physically
Tools Flashlight, service information, pick set
Locate the module, which varies by manufacturer, and check for water staining, corrosion on the pins, green residue in the connector, and any evidence of heat or impact. Look for backed-out or spread terminals in the connector body.
ExpectedA dry module with clean, tight, fully seated connector pins
Check for a manufacturer calibration update or service bulletin
Tools Manufacturer service information, programming-capable scan tool, stabilized programming power supply
Search the manufacturer's bulletins for P0606 on that specific vehicle and engine. Where an updated calibration exists, apply it and see whether the code returns. This resolves a real proportion of cases without replacing hardware. Programming with a marginal battery is a known way to corrupt a module, so put the vehicle on a proper programming supply first.
ExpectedEither a current calibration already installed, or an update that clears the fault permanently
Look for an external circuit fault damaging or loading an internal driver
Tools Digital multimeter, wiring diagram
If the module reports a driver fault, a shorted external load can be the cause. Disconnect suspect actuators such as injectors, coils, and solenoids one at a time and see whether the fault clears. Replacing a module without finding such a short simply destroys the new module.
ExpectedNo shorted actuator or harness circuit on any module-driven output
Clear the code and characterize how it returns
Tools Scan tool
After the supply and connections are proven good, clear the code and note whether it sets immediately at key-on, only after driving, or only under specific conditions. Immediate return with proven-good power points strongly at hardware. Intermittent return points at a connection or supply issue still outstanding. Characterize it in a controlled setting rather than on the road, because the vehicle can drop into limp mode or stall without warning while you are collecting the data.
ExpectedThe code either not returning, or returning in a pattern that identifies the cause
Replace or reprogram the module only as the last step, with the correct procedure
Tools Manufacturer-level programming equipment, service information
If power, grounds, connectors, calibration, and external circuits are all proven good and the code persists, the module itself is at fault. Replacement requires the correct part number, programming to the vehicle, and usually immobilizer or key relearn and idle or throttle relearn afterward. Some modules can be professionally rebuilt at lower cost.
ExpectedThe code cleared and staying cleared, with all relearn procedures completed
| Repair | Only after you confirm | Typical cost | Who |
|---|---|---|---|
| Repair the module power feed or ground circuit | Excessive voltage drop measured on a module feed or ground under load, with the code clearing once corrected | $100–$450 | DIY |
| Replace the battery or repair the charging system | A failed battery load test or charging voltage below the commanded target, with the code not returning after correction | $180–$1,300 | DIY |
| Repair corroded module connector pins or a water-damaged connector | Visible corrosion, moisture, or backed-out pins found at the module connector | $150–$600 | Hard |
| Apply the manufacturer's updated calibration to the module | A published bulletin covering this code for the vehicle, with the fault not returning after the update | $100–$300 | Shop |
| Repair a shorted actuator or output circuit loading an internal driver | The fault clearing when a specific actuator or circuit is disconnected, with a short measured on that circuit | $150–$700 | DIY |
| Rebuild the existing module through a specialist repair service | All external causes excluded and the code persisting, with the module confirmed as the fault | $300–$800 | Shop |
| Replace and program the engine control module | Power, grounds, connectors, calibration, and external circuits all proven good with the code still present | $700–$2,500 | Shop |
US independent shop ranges, parts and labor. Module replacement cost is dominated by the part price and the programming, and some vehicles require dealer-level equipment for immobilizer relearn, which adds a separate charge. Specialist rebuild services are often substantially cheaper than a new module when the original can be repaired and returned already matched to the vehicle.
- Replacing the module as the first move. Power, ground, and calibration causes are common enough that skipping them wastes a large amount of money regularly.
- Fitting a used module from a salvage yard without matching part numbers and without programming or immobilizer relearn, which usually produces a no-start and a new set of problems.
- Ignoring a weak battery or a bad ground, which is the underlying cause in a meaningful share of cases and will fail the replacement module too.
- Skipping the search for a manufacturer calibration update, which sometimes resolves the code outright.
- Replacing the module without finding the shorted output circuit that damaged it, destroying the new module the same way.
- Clearing the code and continuing to drive because the vehicle seems fine, when an unexpected limp mode or stall is a realistic outcome.
- Jump-starting incorrectly or welding on the vehicle with modules connected, which is a known way to create this fault in the first place.
- Reprogramming on the vehicle's own battery without a stabilized supply, which can corrupt the module mid-flash and turn a software fix into a hardware replacement.
- ECM
- Definition
- Generic code set (SAE J2012 / ISO 15031-6) via the OBDexopen database, dedicated to the public domain under CC0-1.0.
- Diagnostic guidance
- Written and reviewed in-house. See our editorial policy.
- Review status
- Reviewed
Found something wrong? Tell us — we publish corrections.