Quick triage & tools

  • Scan first: read codes (all modules if you can) + live data that matches the symptom.
  • Power basics: battery voltage (resting + while cranking) and quick fuse checks before deep dives.
  • Have ready: basic scan tool, multimeter, and a way to confirm the symptom (road test / idle test).

Tip: if a step says “check wiring”, use Wiring diagrams basics → and Voltage drop testing →

Before you start

  • Write down when it stalls: idle, on decel, under load, hot only, after refuel, only in rain, etc.
  • When it stalls, note: do the dash lights stay bright or does everything die?
  • If you can, capture a short live data log (RPM, battery voltage, throttle position, fuel trims, rail pressure where available).

Useful guides: Voltage drop testing · Crank/Cam checks (no scope)

Decision flow

  1. Do you lose electrical power when it stalls?
    • Yes (dash resets, radio cuts, clocks reset) → suspect battery terminals, main grounds, ignition switch, main relay, or loose fusebox feed.
    • No (dash stays on normally) → proceed (engine-specific stall).
  2. Scan for codes (engine + body if possible)
    Even if no MIL, check history codes. Pay attention to U-codes (communication), crank/cam codes, throttle/ETC codes, and fuel pressure codes.
  3. Check battery/charging basics
    • Charging warning or voltage drops below ~12V while running → treat as charging/power issue.
    • Otherwise proceed.
  4. Does RPM drop to 0 instantly before the stall?
    • Yes → likely crank signal dropout (CKP sensor, wiring, heat-related failure, connector/ground).
    • No → proceed.
  5. Fuel delivery (pattern matters)
    • Stalls under load / motorway → suspect fuel pressure/flow (weak pump, clogged filter, low voltage at pump, HP pump issue on DI/diesel).
    • Stalls at idle / after decel → suspect air leak, sticky throttle, idle control, EGR stuck open, EVAP purge stuck open.
  6. Quick air/throttle checks
    • Look for split intake hose, loose clamps, PCV hose off, brake booster hose leak.
    • If it stalls coming to a stop: check throttle body cleanliness and throttle adaptation (where applicable).
  7. Communication / CAN glitches
    If you see intermittent U-codes, random dash behaviour, multiple modules going offline, or it happens in wet weather, inspect grounds + CAN physical layer.
  8. Confirm the fix with a repeatable test
    Don’t stop at “it didn’t stall once”. Recreate the condition that causes it (heat soak, rain, load, idle, etc.).

Print / save checklist

Tick these off as you work. If you need to hand this to a mechanic, print it as a short job card.

  • Freeze-frame captured / conditions noted
  • Battery voltage checked (resting + cranking)
  • Basic visual checks (hoses, connectors, grounds, fuses)
  • One test at a time (don’t change multiple variables)
  • Confirm fix by reproducing the original condition

What to do next

Use the links below to deepen the test you’re about to perform, cross-check related codes, or jump to a faster symptom-led flow.