00003 Control Module (ECU) - Internal Fault / Defective

Investigate soon

The ECU sees a problem in this circuit but cannot narrow it to a specific short or open. Start at the connector and the wiring before condemning the part.

Can you drive it? The engine light will stay on and the car may run in a reduced-power mode. Read the freeze-frame data to see the conditions the fault was logged under.

The definition

00003: Control Module (ECU) - Internal Fault / Defective.

What to check first

Cheapest and fastest checks first:

Read the freeze-frame data stored with the fault - engine speed, load and temperature at the moment it logged tell you whether this happens cold, hot or under load.
Check the connector at the part for corrosion, and that it is fully seated.
Clear the code and see whether it returns, and under what conditions.

What actually causes this on a VAG

In VAG's five-digit numbering, 00003 is not a fault description - it is the name of the thing at fault, and that thing is 'Control Module'. Everything useful is in the fault-type text printed next to it, and there are three quite different variants. 'Defective' means the module found something internally it did not like. 'No or incorrect basic setting / adaptation' means nothing is broken at all - a required setup procedure has simply never been run, which is a scan-tool job with no parts involved. 'Mechanical failure' is model-specific and can be surprisingly mundane; on some Audi door modules it means nothing more than the child lock being engaged. So before anything else, read the full line, note which module stored it, and note whether it is logged as static or sporadic. On its own the number says almost nothing.

Most likely causes, in order

Low or unstable supply voltage. The most common innocent explanation. A weak battery, a bad earth, a flat left overnight, a jump start or heavy cranking can all make a module log an internal fault, and the entry then sits in memory long after the electrical problem has passed. Get the battery and charging system tested, clear the code and see whether it returns.
A basic setting or adaptation that was never performed. If the fault text says 'no or incorrect basic setting / adaptation', the answer is to run the procedure, not to buy anything. This is common after a component has been fitted, a battery disconnected, or work done that a module expects to be followed by a setup routine. Some models have their own documented sequence - certain Audi brake electronics, for example, need the code cleared over several ignition cycles before it stays gone.
A failed or interrupted coding or software update. If programming was attempted without a support charger, or the session dropped out, modules commonly record an internal fault. Re-running the procedure correctly usually resolves it.
Water or corrosion getting into the module. Control units in the footwells, under seats, behind the plenum or in the boot all suffer from the same leaks - blocked drains, failed door membranes, boot seals. Damp carpet or a corroded connector next to a module reporting an internal fault is a strong clue.
Genuine internal failure. Modules do fail, often from cracked solder joints after years of heat and vibration. Confirming it means checking supply, earth and connectors first, then establishing that the fault is permanent and reproducible rather than a single historic entry.

Worth knowing: Do not replace a control module on the strength of this code alone. Charge the battery properly, clear the fault, drive the car and re-scan - many internal-fault entries never return, because they were only ever a record of low voltage. And if any coding or software work is planned, insist that a proper battery support charger is connected, since a voltage drop mid-programming is a good way to turn a recoverable module into a scrap one.

Reading the code is the easy part

A code names the circuit that complained. What tells you why is watching the sensor behind it while the engine runs — and that is where a code reader stops and a diagnostic tool starts.

VAGPULSE reads every module in a VW, Audi, Skoda or SEAT — not just the engine — shows the live measuring blocks behind this fault, gives you the freeze-frame conditions it was logged under, and clears it once you have fixed it. It also does what a generic OBD reader cannot on a VAG: service resets, coding, adaptations, and Stage 1–3 flashing with your original file saved first.

$249 once. No subscription, unlimited cars. Windows 10/11.

See VAGPULSE — $249 Look up another code

Software downloads instantly · cable ships September 30 · cable guarantee — refund if it won't connect

Prefer to work on your phone? The VAGPULSE Android app is a free download and its demo mode runs against a sample car with no hardware at all, so you can see exactly what it reads before spending anything. Reading your car with it needs the VAGPULSE cable, which comes with the licence.

Common questions

What does 00003 mean?

00003 means Control Module (ECU) - Internal Fault / Defective. The ECU sees a problem in this circuit but cannot narrow it to a specific short or open. Start at the connector and the wiring before condemning the part.

Can I drive with 00003?

The engine light will stay on and the car may run in a reduced-power mode. Read the freeze-frame data to see the conditions the fault was logged under.