P066F

3 Glow Plug Control Circuit High

P066F is a generic OBD-II powertrain diagnostic trouble code: 3 Glow Plug Control Circuit High. It is logged by the engine control unit when the glow monitor detects that a specific fault threshold has been exceeded — typically resulting in the malfunction-indicator lamp (MIL / check-engine light) being illuminated.

Code
P066F
Group
Powertrain
System
Glow
Severity
Critical (limp mode / no-start)
Need P066F disabled?
RaceTune permanently disables any OBD-II trouble code on supported ECUs — for motorsport, off-road, and export use.
→

What P066F means

P066F indicates that the PCM has detected an internal microprocessor performance fault. Modern ECMs use self-monitoring routines, watchdog timers, and redundant processing checks to verify that the main processor is executing correctly. When these internal checks detect erroneous results, timing violations, or processor task failures, P066F is logged.

This is one of the more serious internal module codes because it points directly to the computational core of the ECM. The processor handles all fuel, ignition, and emission control calculations, so a performance fault can affect virtually every engine management function simultaneously. Depending on the severity, the PCM may enter a safe-state or limp mode, drastically limiting performance.

Common physical causes include thermal damage, electrostatic discharge, voltage spike damage, and age-related semiconductor degradation. Software bugs or corrupted calibration data can also cause the processor to fail internal self-tests without any hardware fault.

Common causes

Most-frequently reported root causes when P066F is logged.

  • 1
    PCM microprocessor hardware failure due to age, thermal stress, or electrical damage.
  • 2
    Voltage spike or electrostatic discharge event damaging the processor core.
  • 3
    Corrupted PCM software or calibration causing the processor to fail internal consistency checks.
  • 4
    Inadequate PCM power supply or poor ground causing processor operational errors.
  • 5
    Moisture or contamination inside the PCM causing internal circuit faults.
  • 6
    Overheating of the PCM due to missing heat shields or proximity to heat sources.
  • 7
    Watchdog timer fault caused by processor task overrun in software.

Symptoms drivers notice

MIL illuminated, potentially alongside multiple other codes.
Engine in limp mode or significant power reduction.
Possible no-start or intermittent stall condition.
Multiple unrelated systems appearing to fault simultaneously.
Scan tool may have difficulty communicating with the PCM.

How to diagnose P066F

A typical diagnostic flow when this code is present.

  1. 1
    Attempt scan tool communication and record all stored DTCs; widespread unrelated codes alongside P066F are a strong indicator of a PCM internal fault.
  2. 2
    Check PCM supply voltage at the module connector under cranking and running conditions.
  3. 3
    Inspect all PCM ground connections for resistance and integrity.
  4. 4
    Examine the PCM for signs of heat damage, moisture intrusion, or physical damage.
  5. 5
    Attempt a PCM software reflash if communication is possible and a calibration update exists.
  6. 6
    If communication is stable and reflash does not resolve the fault, PCM replacement is required.
  7. 7
    After PCM replacement, program and configure the new module per manufacturer procedure and verify no repeat faults.

Vehicles where we've handled P066F

Platforms in our catalogue with confirmed P066F coverage.

BMW 320D
2016

Related powertrain codes

Frequently asked questions

Is P066F always a PCM replacement situation?

Not always. A software reflash can resolve the fault if it is caused by a calibration or firmware error. Hardware failure requires replacement.

Why are many unrelated codes stored with P066F?

When the microprocessor is performing incorrectly, it may generate false faults across all monitored systems simultaneously. P066F should be treated as the root cause in such cases.

Can a jump-start cause P066F?

Yes. Voltage spikes during jump-starting can damage sensitive processor components inside the PCM, potentially causing this fault.

Can P066F cause a no-start condition?

Yes. If the microprocessor fault is severe enough to prevent proper fuel and ignition control, the engine may not start or may stall immediately after starting.

Disabling P066F in software

RaceTune can permanently disable P066F — 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.

Permanent
The monitor is disabled in the ECU itself — not just cleared. It cannot return.
Tailored to your file
Each patch is matched to your specific software version — never a one-size-fits-all file.
Reversible
The original file is always preserved. Reflash the stock to return the ECU to factory state.

ECUs with a P066F disable in our catalogue

Confirmed coverage from our recipe database — we support many more families. Upload your file and our identifier will match it automatically.

  • Bosch EDC17C50 verified 1 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 P066F 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