P0604
Internal Control Module Random Access Memory (RAM) Error
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
Available brands with manuals
AUDI 11
6-speed manual gearbox 0B1, front-wheel drive — Workshop Manual (Edition 05.2014)
Workshop ManualAudi A3 (1997) – 1.6L 4-cylinder (2‑valve) Engine Mechanical Components Service Manual (AEH, AKL, APF) – Edition 07.2002
Workshop ManualAUDI A3 (2004) Workshop Manual — 2.0L FSI Turbo (4‑cyl, 4‑valve) Engine, Mechanics — Edition 03.2017
Workshop ManualAudi A3 2004 — Electrical System (Workshop Manual, Edition 02.2018)
Workshop ManualAudi A4 / A4 Cabriolet – 4.2 l V8 (5‑valve, timing chains) – Workshop Manual (Mechanics) – Edition 04.2007
Workshop ManualAudi A4 / A4 Cabriolet — Auxiliary Heater Workshop Manual (Edition 08.2004)
Workshop ManualAudi A4 / A4 Cabriolet (1.8T 4‑cyl turbo) — Motronic Injection & Ignition System Service Manual (Edition 01.2015)
Workshop ManualAudi A8 (2003) — Electrical System Workshop Manual (Edition 08.2014)
Workshop ManualAudi Q4 e-tron (Type F4) - Self-study Programme SSP 685
Workshop ManualAudi Q8 (2018) — Electrical System Workshop Manual (Edition 05.2019)
Workshop ManualAudi Servicing Manual — 7‑Speed Dual Clutch Transmission 0CJ / 0CL / 0CK / 0DN / 0DP / 0HL (Edition 05.2018)
Workshop ManualLAND ROVER 3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualP0604
- Error in the memory (RAM) of the control unit
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
P0604
Control Module Random Access Memory (RAM)
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
P0604
Internal Control Module Random Access Memory (RAM) Error
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
P0604
Internal Control Module Memory Error
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
Repair manuals for LAND ROVER
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualP0604
Internal Control Module Random Access Memory (RAM) Error
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
P0604
RAM fail
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
P0604
Electronic Control Unit (ECU) Fault - Random Access Memory (RAM)
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
Fault status
Similar codes
P0604
PCM RAM memory - fault
Causes
- Intermittent or low battery/charging system voltage (power interruptions during write)
- Corroded, loose, or damaged power/ground connections to the control module
- Software corruption or failed calibration update
- Failed or degraded memory IC or module hardware (solder joint, internal component)
- Water intrusion, contamination, or physical damage to the module
- Electrostatic discharge (ESD) event or electrical surge from aftermarket equipment
Symptoms
- MIL (Check Engine Light) illuminated
- Intermittent driveability issues (stalling, rough idle) or no-start
- Loss of communication with the affected control module on scan tool
- Random or incorrect sensor/actuator behavior
- Multiple unrelated stored diagnostic trouble codes
What to check
- Retrieve freeze frame and full code list with a capable scan tool; note related codes
- Check battery state of charge and charging system voltage (key on, engine running)
- Visually inspect module connectors and wiring for corrosion, bent pins, damage, or water
- Verify good chassis and engine grounds and power feeds to the module
- Attempt communication with the module; note intermittent connect/disconnect
- Check fuses and relays supplying the module
Signal parameters
- Battery voltage at module (Key ON, Engine RUN) — expected ~11.5–14.8 V
- Ground resistance/continuity to module chassis ground
- CAN/LIN bus Tx/Rx activity and error counts (communication presence)
- Module self-test or diagnostic status flags (memory test pass/fail)
- Freeze frame parameters at time of fault (engine speed, ignition status)
- Module software part number and calibration ID (for reflash checks)
Diagnostic algorithm
- Connect a manufacturer-level or capable scan tool. Record P0604 and any related codes and freeze-frame data.
- Check battery voltage and charging system. If battery is weak, charge or replace before further testing.
- Inspect all power and ground connections to the affected module; clean and tighten terminals. Repair damaged wiring/connectors.
- Clear codes and attempt to reproduce. If the code does not return, monitor vehicle for intermittent faults.
- If code returns, check module communication on CAN/LIN buses. Diagnose any bus wiring or other module faults found.
- If wiring/power/grounds are good, check service bulletins for software updates. Reflash or update module software per manufacturer procedure.
- If reflash fails or code persists after a successful reflash, perform module bench or dealer-level diagnostics to test internal memory/hardware.
- If module hardware is confirmed faulty, replace the control module and program/configure with correct VIN/calibrations. Re-test and clear codes.
- After repair, verify no related codes remain and perform a road test to confirm normal operation.
Likely causes
- Battery disconnected or vehicle jump-started while module was writing
- Weak battery or charging system causing voltage dips
- Corroded ground/connector pins at the module
- Failed module memory chip or internal processor fault
- Recent software reflash that failed or became interrupted
- Aftermarket alarm, charger, or remote start interfering with module power
