P0605
PowertrainInternal Control Module Read Only Memory (ROM) Error
Most people meet this one as a car that suddenly won't start, or one that drops into limp mode for no obvious reason, sometimes with a fistful of dashboard lights coming on at once. What the ECU is telling you is that it ran its self-check and the read-only memory failed it. That ROM holds the core operating software the module runs on, so when the check comes back bad, the ECU often stops trusting itself and either limps or refuses to fire at all.
ⓘ Information only. This page provides general educational information about fault code P0605. We do not assess the urgency or safety implications of any specific fault. That requires in-person diagnosis by a qualified mechanic. Full terms.
Recommended next steps
Whether a fault is urgent, drivable, or routine depends entirely on the cause on a specific vehicle, and that can only be determined by a qualified mechanic with diagnostic equipment. If a warning light is illuminated, the most reliable next step is professional diagnosis.
What does P0605 mean?
P0605 is a Powertrain (engine, transmission, fuel system) fault code. It indicates: Internal Control Module Read Only Memory (ROM) Error.
This is a standardised OBD-II code. The technical definition is the same regardless of the make or model of vehicle, although specific causes and symptoms can vary between vehicles.
Symptoms commonly associated with this code
Symptoms that drivers often report alongside this code. Not all may apply to every case:
- • Check engine light on solid, frequently with other warning lights joining it
- • No-start, or the engine cranks and cranks but never catches
- • Car drops into limp mode with reduced power and a flat-feeling throttle
- • Dashboard displays flickering, freezing, or showing nonsense readings
- • Loss of electronic helpers like traction control or electric power steering
- • Sudden stalling or a complete loss of powertrain control while driving
Possible causes
Causes commonly associated with P0605, listed in approximate order of typical investigation. The actual cause on a specific vehicle can only be confirmed by professional diagnosis.
- 1. A botched reflash or interrupted software update, by far the most common reason a healthy module throws this. If the laptop dropped connection or the battery died mid-programming, the ROM can end up half-written
- 2. Voltage spikes from a dying alternator or a battery on its way out, which can corrupt what's stored in the module
- 3. Poor or corroded ground connections to the ECU, giving it dirty power and unreliable readings
- 4. Water ingress into the module from a leaking scuttle or bulkhead, which is a known killer of ECUs sat low in the engine bay
- 5. Cracked solder joints inside the module after years of heat and vibration
- 6. An outright hardware failure of the processor or memory chip, which means the module itself is finished
How mechanics typically diagnose
A typical diagnostic sequence used by mechanics, provided here for educational reference only. Diagnostic work should be performed by a qualified mechanic with the appropriate tools and training.
- 1. Pull every stored code and write them all down before you touch anything. P0605 rarely arrives alone, and the codes sitting alongside it often point at the real trigger, a flat battery or a recent failed update
- 2. Check the battery and charging system properly. A weak battery or a charging fault that lets voltage swing wildly can corrupt the module, and there's no point reflashing onto bad power
- 3. Look up manufacturer TSBs and recalls for the exact model and year. Several makers have issued software fixes for ECUs that set this code, and a known reflash can save you a fortune
- 4. Inspect the ECU connectors, the wiring, and especially the ground points for corrosion, green crust, or water. Dry the module out and clean the grounds if you find moisture
- 5. Attempt a reflash with the correct manufacturer software if an update exists for the car. A clean reprogramme fixes a fair share of these when the hardware is still sound
- 6. If the module rejects the reflash or the fault stays after a clean reprogramme, the hardware is gone and you're into a replacement coded to the VIN
Common questions about P0605
If I clear the code, will it stay gone or come straight back? +
If a flat battery or a wobbly charging system caused it, clearing the code after you've sorted the power can stick. If the ROM itself is corrupted or the module has failed, it'll set again almost immediately, often before you've driven off the drive. Clearing it is fine as a test, but treat a fast return as the module telling you the fault is real and not a one-off glitch.
What am I risking if I just keep driving it? +
The big risk is the module dropping into safe mode without warning, which can mean sudden power loss or limp mode while you're moving. That's no fun on a motorway slip road or pulling out of a junction. There's also a chance the underlying voltage or moisture problem keeps degrading the module until a reflash won't save it and you're forced into a full replacement. It's not a code to ride out for months.
How quickly do I need to deal with this? +
Sooner rather than later. A no-start or unpredictable limp mode makes the car unreliable and potentially unsafe, so book it in promptly. If it's still drivable and behaving, get it diagnosed before any long trips rather than waiting for it to strand you. The cheap end is a reflash or a battery and earth repair at an independent garage. The expensive end is a coded replacement ECU at a dealer, which can run into four figures, so catching it early is worth it.
Information only, not professional advice
The information on this page is provided for general guidance and educational purposes only. It is not a substitute for diagnosis or repair advice from a qualified mechanic. Always verify any fault before paying for repairs. carfaultcodes.co.uk accepts no liability for decisions made based on this information. Full terms →