Get The Analogue
Diagnostics · BMW E30, BMW E36, BMW E46, BMW E9x, BMW F-series

Check Engine Light On? How Serious Is It and What Should You Check First?

Triage a steady or flashing check engine light, preserve fault evidence, and choose the first physical test without guessing at parts.

By Chase Waters · · 6 min read

A flashing check engine light, severe shaking, smoke, stalling, overheating, an oil-pressure warning, or a strong fuel smell calls for an immediate reduction in risk. Move out of traffic safely, shut the engine off when conditions warrant it, and arrange recovery rather than trying to drive through the fault. A steady light on a car that runs normally is usually less urgent, but the first useful checks are still the warning behavior, other symptoms, the fuel cap and anything recently disturbed, followed by a complete scan before any codes are cleared.

That scan is the start of diagnosis, not a parts order. Save every code, whether it is current, pending, intermittent, or stored, plus freeze-frame and mileage data when available. On a BMW, I also want manufacturer-specific DME faults because a generic P-code may leave out useful detail.

Are there some ways for me to find out what is the source and severity of error?

Yes. That is the exact question a 2013 BMW 328i owner asked in a BimmerFest discussion after the light appeared while the car seemed to drive normally. Severity starts with what the lamp and the car are doing now. Source starts with the stored evidence.

The US EPA check-engine-light guide separates a light that stays on from one that blinks. It advises prompt attention for a steady light and quick action with minimal driving for a blinking light, which can accompany a severe problem such as a misfire.

Do not use lamp behavior as the only safety test. A separate red oil-pressure or temperature warning, heavy smoke, a strong raw-fuel smell, loud mechanical noise, severe shaking, repeated stalling, or a major loss of power can make even a steady check engine light unsafe to ignore. Read the exact owner-manual instruction for the car when possible.

Check these things before clearing the light

Start with a short triage, not a broad inspection:

  1. Confirm the lamp. Was it steady, flashing under load, or briefly flashing at startup as part of the bulb check? Do not confuse it with an oil, coolant, charging, or transmission warning.
  2. Note the operating condition. Record cold start, warm idle, acceleration, cruise, fuel level, weather, speed, and any change in sound, smell, power, or fuel economy.
  3. Check simple context. Make sure the fuel cap is present and correctly seated. Look for an intake hose, electrical connector, vacuum line, or ground disturbed during recent work. Do not assume the cap is the cause just because it is easy to check.
  4. Check fluids safely. Verify oil and coolant level using the car's specified procedure after allowing for temperature and pressure. Never open a hot cooling system.
  5. Scan before erasing. Save codes, status, fault frequency, mileage, freeze frame, readiness status, and any BMW-specific fault details the tool can access.

Freeze frame is a snapshot of conditions around a detected fault. Depending on the vehicle and tool, it can include engine speed, calculated load, coolant temperature, vehicle speed, fuel-system status, and trims. It may show that a lean fault set at warm idle or that a misfire appeared under load. That changes the next test.

Clearing codes can remove useful context and reset emissions readiness monitors. The CARB OBD II fact sheet explains that a dead or disconnected battery, a recent repair, or cleared memory can leave readiness indicators incomplete until the car runs its self-checks again. Photograph the scan results or export a report first.

Let the code choose a test branch, not a replacement part

A diagnostic trouble code reports what the control system detected. It rarely proves why it happened. A sensor-related fault can come from the sensor, its connector, wiring, power or ground, an air or exhaust leak, a mechanical condition, or a signal that is truthful but outside the expected range.

BMW's own Service Information B12 09 16 shows why the distinction matters. For N20 fault 118602, BMW's procedure does not jump straight to an oxygen sensor. It calls for checking the sensor electrical system and heating, mixture control, wiring and plugs, tank ventilation, intake and exhaust leaks, crankcase ventilation, injection, air-mass measurement, ignition, crank and cam sensors, and the throttle valve. The named sensor is only one branch.

Use the fault family and saved conditions to choose the first physical test:

  • Misfire faults: If the light flashed or the engine shakes, stop loading the engine. Inspect plugs, coils, connectors, contamination, injector evidence, fuel supply, unmetered air, and compression as the pattern requires. A controlled coil or plug substitution can be useful, but only if positions and conditions are recorded.
  • Lean or rich mixture faults: Compare fuel trims by bank and condition. Smoke-test the intake and crankcase paths for leaks. Check fuel delivery and sensor plausibility rather than cleaning or replacing the MAF by default.
  • EVAP faults: Inspect the cap seal and filler area, but use an appropriate leak or functional test for the actual code. A loose cap cannot explain every EVAP fault.
  • Oxygen-sensor or catalyst faults: Look for mixture problems, misfires, exhaust leaks, wiring faults, and relevant service information before condemning a sensor or converter.
  • Temperature, pressure, or position faults: Compare the signal with a known physical state or an independent measurement, then test its circuit. Implausible data is evidence, not automatic proof of a failed sensor.

After a repair, reproduce the original condition when it is safe. Confirm the fault stays absent, the relevant live data makes sense, and the monitors can run. Simply switching off the lamp does not verify a repair.

Account for the car's diagnostic generation

The Analogue focuses on enthusiast cars from 1987 through 2018, but support depends on the vehicle and diagnostic generation. CARB's fact sheet says first-generation OBD requirements began with the 1988 model year in California, while OBD II became standard on US-market gasoline passenger cars and light trucks for 1996. Some 1994 and 1995 cars also had OBD II.

For a 1996 to 2018 US-market BMW, a generic OBD II reader can retrieve emissions-related P-codes and common data. BMW-capable access can add manufacturer faults, status, counters, test plans, and data that a generic reader may not expose. Use that extra information to sharpen the test, not to clear every module or run unrelated service functions.

For a 1987 to 1995 BMW, connector location, fault retrieval, terminology, and available data depend on chassis, engine, market, and production date. Some cars use an under-hood diagnostic connector or a model-specific fault procedure. Identify the exact car before buying an adapter or applying a later OBD II workflow.

Check engine light questions

Can I drive with a steady check engine light?

Often, a short and gentle trip to a safe location or repair facility is reasonable when the car runs normally and no other warning or symptom appears. It is not a blanket permission. Stop for oil-pressure loss, overheating, severe shaking, smoke, stalling, a strong fuel smell, major power loss, or any owner-manual instruction to stop.

What should I check first when the check engine light comes on?

First decide whether it is flashing and whether the engine has a severe symptom. Then check other warnings, the fuel cap, fluid levels by the proper procedure, and anything disturbed during recent work. Scan and preserve the complete fault record before clearing it.

Does a fault code tell me which part to replace?

No. It identifies a detected condition and the diagnostic branch that needs attention. Confirm the cause with wiring checks, leak tests, pressure measurements, component substitutions, or mechanical tests suited to that fault and vehicle.

Why did the light turn off by itself?

The monitored condition may not have repeated, but a stored or history fault can remain. Scan it before assuming the car fixed itself. The old code, its status, and its operating conditions may be the best evidence available for an intermittent fault.

Questions owners ask

Are there some ways for me to find out what is the source and severity of error?

Yes. First separate a flashing warning or severe running problem from a steady light on a normally running car. Then save every code, its status, and freeze-frame data before selecting a physical test for the affected system.

Can I drive with a steady check engine light?

A steady light usually calls for diagnosis soon, but it does not prove the car is safe for every trip. Stop if you also have overheating, oil-pressure loss, severe shaking, smoke, a strong fuel smell, stalling, or major power loss.

What should I check first when the check engine light comes on?

Check whether the light is flashing, assess how the engine is running, verify oil pressure and coolant warnings are absent, inspect the fuel cap and obvious recent-work issues, then scan and save the complete fault record before clearing anything.

Does a fault code tell me which part to replace?

No. A code identifies a condition, circuit, monitor, or system that needs diagnosis. Wiring, leaks, mechanical faults, supply problems, and the named component can produce related evidence, so a physical test must confirm the cause.

Are there some ways for me to find out what is the source and severity of error?

Read the stored and pending codes with their freeze-frame data, then assess whether the light is steady or flashing and whether the engine is running poorly. The code identifies the system that detected a problem, not automatically the failed part.

Sources

  1. BimmerFest owner discussion: How to check the error when Check Engine light is on
  2. US EPA: What To Do With the Check Engine Light
  3. California Air Resources Board: OBD II Systems Fact Sheet
  4. BMW Service Information B12 09 16 via NHTSA