Drivetrain Malfunction: 328ixd ‘15 With Undervoltage and Electrical Faults
A test order for an F30 328i xDrive with undervoltage, communication, Valvetronic, injector-supply, and fuel-valve faults.
A 2015 BMW F30 328i xDrive that intermittently misfires, cranks poorly, and shows a drivetrain malfunction alongside undervoltage and several electrical faults needs one event proved before parts are ordered. Codes 800B9F, CD9437, 135B11, 113026, and 11C404 do not collectively prove a bad battery, Valvetronic motor, injector, fuel valve, or control module. I first establish whether their timing fits one supply-voltage disturbance, then retest any fault that survives under a known-good electrical supply.
Drivetrain Malfunction: 328ixd ‘15. Is this one fault or five?
The owner report behind this question lists intermittent misfire and cranking trouble with these fault descriptions:
800B9F: undervoltage detectedCD9437: FlexRay communication error in the event of undervoltage135B11: Valvetronic servomotor control phase V, line interruption113026: ignition and injector relay or injection supply voltage, short circuit to ground11C404: quantity control valve control, line break
That mix contains a useful clue: undervoltage and communication trouble appear beside several circuits that depend on stable power and control. It does not settle the cause. A discharged or weak battery is only one possibility. A poor main connection, ground path, charging fault, interrupted relay supply, local harness fault, or more than one defect can produce a similar list.
I do not count codes and pick the part named most often. I group them by module, supply path, status, mileage, and timestamp. If several modules recorded voltage or communication faults during the same start attempt, a common event moves up the list. If 135B11 is currently present while the voltage faults are old and stored, the Valvetronic branch may be independent.
Preserve the event before clearing anything
I save the complete vehicle scan, not just the DME page. For each relevant fault I want the exact control unit and wording, current or stored status, occurrence count, mileage, system voltage, engine speed, and any available environmental data. I also record when the owner saw the warning: first cold start, hot restart, during cranking, at idle, or while driving.
The sequence matters. A voltage collapse during cranking can make modules reset and communication stop. A stalled engine can also leave low-voltage evidence after the original problem. Without time context, the scan cannot tell those stories apart.
BMW's energy diagnosis bulletin says the energy diagnosis test plan is selected automatically when a power-management fault is stored and can also be selected manually. Its list of possible histories includes prolonged terminal use, extended parking, and stationary vehicle use. The point is broader than battery replacement: BMW's own process considers how the energy deficit occurred.
Before disconnecting anything, I document battery age and specification, recent replacement or charging, long storage, jump starts, water intrusion, aftermarket electrical equipment, and recent engine-bay work. Those facts can explain an event or direct an inspection, but none is a test result.
Prove or reject a supply-voltage event
I start with a battery state-of-charge and condition test using the correct procedure for the fitted battery. A low open-circuit reading shows the battery needs attention, but it does not explain why it became low or prove it cannot support a start. I charge and retest as the equipment manufacturer and BMW service information require, rather than diagnosing from one parked voltage reading.
Next I capture voltage at the battery posts during the actual crank complaint. I compare that with voltage at the vehicle's relevant supply points during the same event. A meter with minimum capture or a suitable recorder is more useful than watching a display because the drop may be brief. I use the vehicle-specific BMW limits and test conditions, not an invented universal threshold.
Then I measure loaded voltage drop across the main paths. On the positive side, that means testing across the cable and connections while current flows. On the ground side, it means testing from the battery negative post to the engine and body paths under load. Fluke's voltage-drop guide explains why this must be done with the circuit operating: resistance that looks harmless without load can consume voltage when starter current flows.
The charging system comes next. I check charging behavior at the battery and compare it with the relevant front distribution point under controlled loads. BMW's energy-management training describes an actively managed charging target and electrical load reduction, so one idle reading is not enough to condemn an alternator. The correct test considers operating state, commanded behavior, connections, and repeatability.
If voltage remains stable at the battery but falls at the DME or relay-fed loads, the fault is in the path between them. If it falls at the posts, the test moves toward battery condition, starter demand, and charging history. Evidence should locate the loss before any module is blamed.
Retest Valvetronic, injector supply, and fuel control separately
After the main supply is stable, I save the original scan, clear the faults, reproduce the complaint under safe controlled conditions, and rescan. The faults that return as current now set the direction.
For 135B11, I inspect the Valvetronic connector and harness, then test the named motor phase and control circuit with the correct wiring diagram and BMW test plan. The line-interruption wording does not distinguish a disconnected terminal, damaged wire, motor winding, or control-stage problem. BMW's SI B12 04 15 also shows that Valvetronic phase line-disconnection faults can appear as secondary faults in a defined DME fault pattern. That bulletin covers specific engine and software combinations, so I use it as a reminder to check applicability, not as a repair instruction for every 328i.
For 113026, I test the ignition and injector supply path at the relay output and at the relevant load while the circuit is commanded and under load. A static continuity test can miss a weak terminal. I inspect the relay, fuse path, distribution, connectors, and harness before treating an injector as the cause. The fault description concerns shared supply voltage, not proof that all injectors failed.
For 11C404, I verify the quantity control valve's supply, control wire, connector fit, and load response from the exact wiring information for the VIN. I do not replace the valve because the description says line break. If its circuit passes and the fault does not return after the supply repair, it was evidence from the original event, not a confirmed failed valve.
CD9437 deserves the same discipline. A communication error explicitly associated with undervoltage can be a consequence of a module dropping offline. If it returns with stable supply, the FlexRay branch needs its own topology, connector, termination, and module-power checks. Replacing a communicating module before verifying its power and ground reverses the test order.
What a defensible repair result looks like
A defensible result ties the symptom to measurements. The work order should show the original full scan, battery test state, cranking-voltage capture, loaded positive and ground voltage-drop results, charging-system findings, and voltage at the affected supply during the complaint. It should also show which faults returned after the electrical supply was stabilized.
If repairing a connection or battery-related condition restores normal cranking and the grouped faults stay gone through repeated controlled starts, that supports a supply-event diagnosis. It still does not prove that every future drivetrain warning has the same cause. If one circuit fault returns, I continue on that circuit and authorize only the part the tests identify.
A battery can be discharged without being the root cause. A Valvetronic fault can be genuine even when an undervoltage event also occurred. The value of this sequence is that it separates those facts before expensive, unrelated parts erase the original evidence.
Questions owners ask
Does BMW fault 800B9F prove the battery is bad?
No. It proves that the module recorded an undervoltage condition. Battery condition, state of charge, cable voltage drop, charging performance, and the fault's timing still need to be tested.
Does 135B11 mean the Valvetronic motor must be replaced?
No. The line-interruption description can justify testing the motor phase, connector, harness, and control side, but it does not identify the failed part. First establish stable supply voltage, then see whether 135B11 returns as a current fault.
Can low voltage create communication and engine electrical faults together?
A shared supply disturbance can make modules reset, drop messages, or report implausible circuit states. That makes a voltage event a hypothesis worth proving, not proof that every stored fault is false.
What should be tested before injectors or a DME are replaced?
Save the complete fault record, test the battery and charging system, measure loaded voltage drop on the main positive and ground paths, and verify the relevant DME and relay supplies during the symptom. Then retest the individual circuit that remains current.
Sources
- Reddit r/F30 owner report: Drivetrain Malfunction: 328ixd ‘15
- BMW SI B61 13 05, Energy Diagnosis, via OEMDTC
- BMW Group University, F01 Energy Management technical training
- BMW SI B12 04 15, DME Internal and Valvetronic Faults Set, via NHTSA
- Fluke, Diagnosing Voltage Drops: Electrical Automotive Troubleshooting