P0605
Internal Control Module Read Only Memory (ROM) ErrorP0605 is a generic OBD-II powertrain diagnostic trouble code: Internal Control Module Read Only Memory (ROM) Error. It is logged by the engine control unit when the powertrain monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.
What P0605 means
P0605 is set when the powertrain control module (PCM/ECM) detects that its internal Read Only Memory (ROM) has failed a self-check. ROM is a non-volatile chip that holds the module's core firmware: the operating system, control algorithms, and calibration tables that govern every aspect of engine and transmission management. Unlike RAM (which holds transient runtime data) or EEPROM (which stores learned adaptive values and immobilizer keys), ROM is programmed once and is not rewritten during normal operation — only a deliberate reflash procedure can update it.
When the PCM's power-on self-test or a periodic background checksum check detects that the ROM contents do not match their expected signature, the module logs P0605 and illuminates the MIL. Depending on severity, the module may fall back to a reduced operating mode or refuse to start the engine entirely. The code does not self-resolve — a ROM integrity fault persists until either a successful reflash restores valid firmware or the module is replaced.
The most common triggers are a failed or interrupted reflash that left invalid code blocks in ROM, a manufacturing defect that manifests after prolonged heat cycling, or physical damage from a voltage spike, moisture intrusion, or impact. Faulty PCM power supply or ground circuits that allow voltage outside the 9–16 V operating range can also stress ROM cells over time and cause read errors.
Common causes
Most-frequently reported root causes when P0605 is logged.
-
1
Failed or interrupted ECM/PCM reflash leaving incomplete or invalid ROM code blocks.
-
2
Manufacturing defect in the ROM chip that develops after extended thermal cycling.
-
3
Voltage spike or electrical surge (e.g., jump-start with reversed polarity) damaging ROM circuitry.
-
4
Moisture or corrosion intrusion into the PCM housing degrading internal memory contacts.
-
5
PCM power supply voltage outside the normal 9–16 V operating range causing read errors.
-
6
Loose, corroded, or open PCM ground circuit increasing reference noise on the memory bus.
-
7
Physical impact or vibration that cracks the ROM IC or breaks solder joints inside the module.
Symptoms drivers notice
How to diagnose P0605
A typical diagnostic flow when this code is present.
-
1
Connect a scan tool, record all stored DTCs and freeze frame data, and note any communication fault codes alongside P0605.
-
2
Check PCM supply voltage at the module connector with the ignition on — expect 11.5–14.8 V; test all ground pins for continuity and resistance less than 0.1 ohm to chassis.
-
3
Inspect PCM wiring harness, connector pins, and the module housing for signs of moisture, corrosion, or physical damage.
-
4
Run an OEM-level ROM checksum or self-test routine using a factory or J2534 pass-through scan tool to confirm the ROM integrity fault.
-
5
Attempt a full PCM reflash using the latest OEM-approved calibration via a J2534 pass-through programmer; ensure battery voltage is maintained above 12.5 V with a battery support unit throughout the process.
-
6
If the reflash completes successfully and P0605 does not return after a full drive cycle, the repair is confirmed.
-
7
If the code returns after a successful reflash or the module is unresponsive to programming, replace the PCM and perform any required immobilizer/anti-theft relearn procedures.
Related powertrain codes
Frequently asked questions
Can P0605 be fixed by simply clearing the code and driving?
No. P0605 indicates a hardware self-test failure in the ROM chip itself. Clearing the code does not repair corrupted or damaged memory; the fault will return as soon as the module completes its next self-check, typically within the same drive cycle.
Is P0605 the same as P0604 or P062F?
No — each targets a different memory type. P0604 covers RAM (runtime working memory), P0605 covers ROM (the fixed firmware/calibration image), and P062F covers EEPROM (stored learned values and immobilizer data). The distinction matters because P062F is often recoverable by reflashing, whereas P0605 may indicate physical ROM damage requiring module replacement.
Will my car pass an emissions test with P0605 stored?
No. Any stored DTC that illuminates the MIL is an automatic failure on OBD-II emissions inspections, and P0605 will always keep the MIL on until the underlying fault is resolved.
Can a bad battery cause P0605?
Indirectly yes. A severely degraded battery that allows supply voltage to drop below about 9 V, or one that produces voltage spikes during charging, can stress ROM memory cells. Always verify battery and charging system health before condemning the PCM.
Disabling P0605 in software
RaceTune can permanently disable P0605 — and any other OBD-II diagnostic trouble code — on every ECU family we support. The monitor is disabled inside the ECU itself, so the fault stops being logged: the warning light stays off and the engine never enters limp mode for this code. The change is tied to your exact software version.
Software modifications affect emissions compliance and are not road-legal in many jurisdictions. RaceTune service files are intended for motorsport, off-road, and export use.
Got P0605 in your scan?
Upload your ECU file — we'll identify the exact software version and confirm whether a disable is available for your car.
Upload your file