Home / DTC / P0606 — - PCM Processor Malfunction

P0606 — - PCM Processor Malfunction

Detailed page for trouble code P0606.

34,480codes
59brands
11,925generic
22,555specific
Reset
Code

P0606

GWM P — Powertrain

- PCM Processor Malfunction

Brand: GWM
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Internal PCM processor or circuit failure
  • Corrupted or failed PCM firmware/flash memory
  • Low or erratic battery voltage or poor power supply to PCM
  • Poor or intermittent power/ground connections at the PCM
  • Damaged or corroded PCM connector or wiring harness
  • Water intrusion or physical damage to PCM

Symptoms

  • Malfunction Indicator Lamp (MIL) illuminated
  • One or more drivability issues (stalling, no-start, rough idle)
  • No communication with PCM using a scan tool or intermittent connection
  • Multiple unrelated DTCs stored (communication and sensor errors)
  • Vehicle may enter limp mode or fail to start
  • Accessory systems controlled by PCM may not operate correctly

What to check

  • Read all stored DTCs and freeze-frame data with a capable scan tool; note occurrence count and related codes
  • Attempt to communicate with PCM; verify tool reports module presence and software part number if available
  • Inspect battery condition and measure resting/operating voltage (battery ≥12.4 V, charging ~13.5–14.8 V under charge)
  • Visually inspect PCM connector and wiring for corrosion, bent pins, water intrusion, or damage
  • Verify fuses and relays for PCM power circuits
  • Measure power and ground circuits at PCM for proper voltage and low resistance to chassis ground

Signal parameters

  • Battery/PCM supply voltage: nominal 12–14.8 V (engine run charging ~13.5–14.8 V)
  • PCM ground resistance: low (typically
  • CAN High (idle): typically ~2.5–3.5 V; CAN Low (idle): typically ~1.5–2.5 V; differential ~1–2 V
  • Diagnostic communication: ISO 15765 / J1939 or manufacturer protocol should enumerate the PCM and return identification and software part number
  • No valid processor heartbeat or CRC/validation response from PCM indicates internal fault

Diagnostic algorithm

  1. Record all DTCs and freeze-frame data; note occurrence counts and related codes before clearing
  2. Attempt to clear the P0606 code and cycle ignition; if code returns immediately or consistently, proceed
  3. Verify battery state-of-charge and charging system; charge or replace battery if voltage is low
  4. With ignition ON, measure PCM supply voltage at the module harness connector and verify fuses/relays feeding the PCM
  5. Measure resistance of PCM grounds to chassis; repair any high-resistance ground connections
  6. Inspect PCM connector and wiring for damage, corrosion, rodent damage, or water intrusion; repair harness or connector as needed
  7. Check CAN bus wiring and termination resistances; repair any short/open/poor splices; verify other modules on the bus can communicate
  8. If power/ground/wiring and bus are good, attempt to read the PCM identification and software version with a manufacturer-level scan tool
  9. If available, reflash or update PCM software per manufacturer procedure; ensure stable power and follow OEM reprogramming steps exactly
  10. If reflashing fails or module does not respond to programming and all external causes are eliminated, replace PCM with correct part and program module to vehicle (immobilizer and VIN matching may be required)
  11. After repair or replacement, clear codes and perform road test and re-scan to confirm fault does not return

Likely causes

  • Failed PCM processor or internal electronics
  • Corroded connector pins or harness shorting to ground
  • Blown fuse or faulty power/relay supplying PCM
  • Battery with low state of charge or weak charging system
  • Corrupted software after failed update or interrupted reflash
  • CAN bus short/open or CAN transceiver failure causing processor fault detection

Fault status

⚠️ Status
P0606 — PCM Processor Malfunction detected. Internal microprocessor or control module fault. MIL illuminated. Module may be unresponsive or communicating intermittently. Further electrical and module-level diagnostics required.
🔴 Repair difficulty: Hard
⏱️ Diagnostic time: 2-4 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email