The BMW M5 F90 is a serious machine. It delivers huge power, sharp response, and a level of electronic control that keeps everything working together under pressure. But when the DME MG1CS201 starts throwing faults, the car can go from beast mode to complete headache mode very quickly.

You may see a no-start condition, drivetrain warnings, power reduction, or a stack of fault codes that seem to make no sense together. That is exactly what makes these cases tricky. The real issue is often not one fault code, but one root problem that triggers several others.

This guide breaks down what the BMW M5 F90 DME MG1CS201 faults mean, why they appear, and how an experienced technician would approach the repair. If you are dealing with immobiliser errors, battery problems, CAN communication faults, or DME internal faults, this will help you understand the bigger picture.

What the MG1CS201 DME Does

The MG1CS201 is the engine control unit used in the BMW M5 F90. It is not just responsible for fuel and ignition. It manages a much wider set of functions, including:

• Engine start authorization
• Torque delivery and power control
• Immobiliser communication
• Battery and power management coordination
• CAN network communication with other modules
• Engine protection and shutdown strategies

Because the system is so tightly connected, even a small voltage drop or communication issue can cause several faults at once. That is why these cars often look much worse on scan data than they really are.

Full List of Common Fault Codes

Here are the fault codes often seen in real diagnostic cases on the MG1CS201 DME:

• 1B2002 – Electronic immobiliser: No starting value programmed
• 1B2001 – Electronic immobiliser: Engine start blocked
• 216118 – Starter request while immobiliser is active
• 030E62 – Intelligent Battery Sensor: Battery current implausible
• 030E08 – Power management: Battery below startability threshold
• 021204 – DME power limitation, stage 1 malfunction
• 021203 – DME power limitation, stage 2 malfunction
• 100306 – DME internal fault, reading faulty
• CDA711 – Missing DSC torque message
• CDA737 – Vehicle speed signal missing from DSC
• CDA73A – Yaw rate signal missing, DSC communication error
• 1F0549 – Engine oil service reminder

When these appear together, the car is usually dealing with a system-level issue, not a simple sensor glitch. In other words, the problem is often electrical, communication-based, or programming-related.

What These Faults Really Mean

1. Immobiliser Sync Problems

Faults like 1B2001, 1B2002, and 216118 point to a start authorization problem. The DME is not getting the correct signal that allows the engine to start.

That can happen for several reasons:

• CAS, BDC, or DME synchronization lost
• ECU replaced without proper programming
• Incorrect donor ECU installed
• ISN data mismatch
• Voltage drop during coding or programming

When this happens, the car may crank and not start, or it may not crank at all. The DME is basically saying, “I’m not confident this start request is valid.”

2. Battery and Power Management Issues

Faults 030E62 and 030E08 usually point to battery or charging stability problems. BMW’s Intelligent Battery Sensor monitors current, voltage, and temperature. If the readings look wrong, the car goes into protection mode.

Common causes include:

• Weak battery
• Poor battery registration after replacement
• Faulty IBS sensor
• Loose ground connection
• Low cranking voltage
• Unstable jump-start voltage

This is one of the biggest reasons BMWs produce multiple unrelated faults at once. Low voltage can upset communication, memory integrity, and module wake-up behavior.

3. DME Internal Fault

Fault 100306 is a more serious one. It often suggests a real problem inside the DME itself, such as:

• Corrupted flash memory
• Failed software write
• Hardware degradation
• Heat or moisture damage
• Programming mismatch

This fault should not be ignored. Sometimes it is triggered by voltage or coding issues, but other times it points to actual ECU damage.

4. Power Limitation and Limp Mode

Faults 021203 and 021204 mean the DME has reduced engine output for protection. The car is trying to prevent damage.

This can happen when:

• Torque values do not make sense
• Sensor data is unreliable
• Communication is unstable
• Engine safety thresholds are exceeded

Symptoms may include:

• Reduced acceleration
• Limited boost
• Lower RPM ceiling
• Limp mode
• Warning messages on the cluster

5. CAN Communication Breakdown

Faults CDA711, CDA737, and CDA73A point to communication failures between control modules.

These codes often involve:

• DME
• DSC
• Transmission module
• Gateway module

Typical causes include:

• CAN wiring issues
• Low voltage on the network
• Faulty DSC module
• Wake-up failure
• Software corruption
• Communication interruption during startup

When the DME cannot trust the information coming from other modules, it may reduce power or block engine start altogether.

Why So Many Faults Show Up Together

This is where many owners get stuck. They see ten fault codes and assume the car has ten separate problems. Usually, that is not the case.

BMW uses layered protection logic. So one failure can snowball like this:

Weak battery → communication errors → immobiliser mismatch → start blocked → power limitation

That is why a single bad battery, failed IBS sensor, or programming error can produce a long list of scary-looking codes.

The scan tool is showing the symptoms. The technician has to find the root cause.

Real Diagnostic Workflow

Clearing codes first is a mistake. The right approach is to work through the system in a proper order.

Step 1: Check Voltage Stability

Start with the basics:

• Battery load test
• Battery voltage during cranking
• Ground point inspection
• IBS live data review
• Charging system check

If voltage is unstable, nothing else will be reliable.

Step 2: Check Communication

Next, verify that the DME is talking properly to other modules.

• Inspect CAN High and CAN Low integrity
• Check DSC communication
• Confirm gateway message flow
• Look for wake-up failures

A lot of BMW fault cases live here, not in the engine itself.

Step 3: Verify Immobiliser Alignment

If start authorization faults are present:

• Compare ISN data
• Check DME to BDC or CAS synchronization
• Confirm matching software and coding
• Verify whether a donor ECU was installed

If the security data is wrong, the engine will stay blocked.

Step 4: Inspect the DME Itself

If you suspect an ECU issue:

• Read and verify memory data
• Check flash integrity
• Review programming history
• Confirm software version compatibility

This is where advanced repair tools matter.

Step 5: Test the Start Sequence

Finally, confirm the system can authorize a clean start:

• Starter activation
• Fuel injection permission
• Torque request validation
• Engine response under load

A proper repair should solve the cause, not just erase the evidence.

Common Repair Solutions

The right fix depends on the root problem, but common solutions include:

Electrical Repairs

• Battery replacement
• Battery registration
• IBS sensor replacement
• Ground restoration
• Wiring repair

Software and Coding Repairs

• DME programming
• ECU reflash
• CAS/BDC-DME synchronization
• ISN alignment
• Software version correction

Advanced ECU Repair

• Flash recovery
• EEPROM repair
• ECU cloning
• Virginizing the control unit
• Hardware-level DME repair

In many cases, replacing the ECU without proper programming will not solve the issue. It can actually make the immobiliser problem worse.

How to Prevent These Faults Coming Back

BMW electronics are sensitive. That is the honest truth. A few simple habits can save a lot of pain:

• Register every new battery
• Keep battery voltage stable during coding
• Avoid weak jump-starts
• Maintain clean ground connections
• Use correct programming tools
• Do not swap ECUs without proper cloning or alignment

A lot of repeat faults happen because the original electrical issue was never fully fixed.

When Professional ECU Service Makes Sense

You should get expert BMW ECU help if the car shows:

• No-start or crank-no-start condition
• Multiple immobiliser faults
• Repeated CAN communication errors
• DME internal fault codes
• Power limitation with no obvious sensor failure

At that point, the issue is usually beyond simple code clearing. It needs proper testing, programming, and sometimes bench-level ECU repair.

FAQ

What does 1B2001 mean on BMW M5 F90?

It usually means the immobiliser is blocking engine start because the authorization data is missing or invalid.

Can battery problems cause DME faults?

Yes. Low voltage or a faulty IBS sensor can trigger several DME, communication, and start authorization errors.

Is a DME internal fault serious?

Yes. It can point to memory corruption, programming failure, or ECU hardware damage.

Why does the car show so many codes at once?

Because one core issue can affect the battery system, CAN network, immobiliser sync, and engine protection logic all at once.

Can the MG1CS201 ECU be repaired?

In many cases, yes. It may be repairable, reprogrammed, cloned, or recovered depending on the damage.