AutoLogicTools

OBD-II trouble code

P0606: PCM Processor Fault

The powertrain control module has detected an internal processor or memory fault — the computer that runs your engine has flagged a problem with itself. Uncommon as codes go, and the instinct to condemn the computer is the expensive one — check supply, grounds and VIN-specific coverage before anyone orders a module.

High severityPowertrainPCM / ElectronicsDrivable short-term

Quick facts

System
Powertrain
Category
PCM / Electronics
Severity
High severity
Drivable
Usually safe to drive short-term
Repair cost range
$100 – $1,800
DIY difficulty
Shop recommended

Browse every code in P0600–P06DD, or start from the full code library.

What does P0606 mean?

P0606 is one of the very few OBD codes where the engine computer is reporting a problem with itself rather than with a sensor or actuator. Modern PCMs run continuous self-diagnostics — every few seconds the processor runs checksum routines on its memory, validates that its internal voltage rails are within spec, and confirms that its co-processors and watchdog circuits are responding. When any of those internal checks fail repeatedly, the PCM sets P0606 and (depending on which subsystem failed) may enter a default operating mode or refuse to start the engine entirely.

Unlike most codes, P0606 doesn't have a long list of cheap causes to chase. It usually means one of three things: a corrupted software image (often resolvable with a PCM reflash at the dealer), an underlying power supply problem to the PCM (chronic low voltage, a marginal ground connection, or a recent jump-start with reverse polarity), or a genuine PCM hardware failure that requires replacement.

Platform history is worth checking here in a way it is not for most codes, because module faults tend to cluster by design rather than scatter at random, and manufacturers periodically extend coverage or issue software fixes for them. Before paying four figures for a PCM out of pocket, spend ten minutes finding out whether someone else is meant to pay for it: run the VIN through the NHTSA recall lookup, ask a dealer to check for open campaigns, extended warranties and technical service bulletins against that VIN, and search owner forums for your exact engine and model year. Coverage programmes change over time and vary by market, so the only answer that means anything is the one attached to your VIN today — not a general claim about a platform.

Common causes

  • Chronic low battery voltage stressing the PCM — the cheapest cause on this list and the first to rule out
  • Marginal or corroded PCM ground connection
  • Water intrusion at the PCM connector or housing
  • Corrupted PCM software image (resolvable with reflash)
  • Reverse polarity jump-start damage
  • Internal PCM hardware failure — the expensive outcome, and the one to reach last
  • A known module defect on this platform and model year, which is why a VIN-specific coverage check comes early
  • Aftermarket tune or programming attempt that bricked the PCM

Symptoms

  • Check engine light on with P0606 stored
  • Engine may enter limp mode or default operating parameters
  • Possible no-start condition if the fault is severe
  • Other unrelated trouble codes may set simultaneously
  • Cooling fan or other PCM-controlled accessories may behave erratically
  • Sometimes intermittent — code clears and returns within days
  • Possible communication errors with other modules (U-codes)

Diagnostic steps

  1. 1.Check the battery voltage and the condition of every battery terminal and major engine ground. A failing battery or corroded ground is the most common root cause of intermittent P0606 — and the cheapest fix by far.
  2. 2.Run the VIN through the NHTSA recall lookup and have a dealer check for open campaigns, extended coverage and bulletins against that VIN. Module faults cluster by platform and manufacturers sometimes extend coverage for them, so this can turn a four-figure repair into a free one — but only a VIN-specific answer counts.
  3. 3.Check for a manufacturer technical service bulletin matching your VIN. Some P0606 codes are software-only and resolve with a free dealer reflash.
  4. 4.Inspect the PCM connector and harness for water intrusion, corrosion, or pin damage.
  5. 5.Scan for other codes — multiple module communication errors (U-codes) plus P0606 often point at the same root cause: power supply or ground.
  6. 6.If all of the above check out, the next step is professional PCM diagnosis at the dealer or a module specialist. Don't replace the PCM as a first guess — it's expensive and not always the fault.

Repair cost

$100 – $1,800

Battery, terminal, or ground repair: $100-$300 and often resolves intermittent P0606. PCM reflash at the dealer: $80-$250 if a TSB applies, sometimes covered under powertrain warranty. PCM replacement: $800-$1,800 including programming — the module itself is $500-$1,200, with programming and core charge accounting for the rest. If your vehicle is under a recall or extended warranty for this code, the cost can drop to zero. Always check coverage first.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with battery replacement preselected. Adjust labor rate and vehicle category to fit your situation.

DIY vs shop

Leave this one to a qualified shop. The barrier here is control module programming and configuration, which generally needs manufacturer software and a stable supply throughout. DIY attempts often produce a more expensive problem than the original code.

Related codes

Frequently asked questions

Is P0606 always a bad computer?

No — and assuming it is can be expensive. A meaningful share of these resolve with a battery, ground, or connector repair, and others are software issues a dealer can reflash. Genuine PCM hardware failure is the most expensive outcome and the one worth reaching last rather than first. Always check ground connections, battery condition, and recall coverage before authorizing a PCM replacement.

Should I check for recalls on this code?

Yes, and it should come before you authorise any expensive work. Control module faults cluster by platform rather than scattering at random, and manufacturers periodically respond with software fixes, extended coverage or campaigns. Run your VIN through NHTSA.gov/recalls, ask a dealer to check for open campaigns, extended warranties and technical service bulletins against that specific VIN, and search a forum for your exact engine and model year. Coverage changes over time and differs by market, so a VIN-specific answer is the only one worth acting on.

Can I keep driving with P0606?

Depends on what your engine is doing. If the engine is running normally and the only symptom is the check engine light, you can drive while you arrange diagnosis — but don't ignore it. If the engine is in limp mode (reduced power), running rough, or refusing to start, get it towed to a shop. PCM faults can be intermittent at first and then escalate, and being stranded by a no-start is much worse than being stranded by a tow.

Can a dead battery or jump-start cause P0606?

Yes, and this is one of the most under-recognized causes. PCMs are sensitive to voltage spikes and chronic low voltage. A reverse-polarity jump-start can damage the PCM permanently. Sustained operation with a weak battery, where voltage dips well down during cranking, can corrupt PCM memory over time. If you've had recent battery trouble or a sketchy jump-start, start there: replace the battery, clean and tighten the terminals and the main grounds, clear the code and drive it. An intermittent P0606 caused by supply problems often does not return once the supply is sound. Only if it comes back on a healthy electrical system does the module itself become the suspect — do not order a PCM on the strength of a bad jump-start alone.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.