BMW E09400: Transmission Display Message Missing at GWS
E09400 means the GWS did not receive transmission display message 0x3FD from the EGS or CCU. Diagnosis must separate a transmitter outage, a GWS supply problem, and a PT-CAN communication interruption before any module is replaced.
— Tekin Code
E09400 means Message (transmission train display data, 0x3FD) missing, receiver GWS, transmitter EGS / CCU. The GWS records it when the periodic transmission-status packet expected from the EGS or CCU disappears. The code describes lost information at the receiver; it does not by itself condemn the electronic gear selector.
What Does E09400 Mean?
E09400 is a communication DTC, not proof of an internal gearbox defect. The GWS needs message 0x3FD to interpret and present transmission train display data. If that packet stops while other network traffic remains available, the receiving selector stores the absence and may substitute a warning state or suppress part of its indication.
BMW software variants can route the information through EGS or CCU, so the exact transmitter and network branch must be confirmed by VIN. A missing-message code can begin with a module that went offline, interrupted PT-CAN wiring, unstable module power, or incompatible software after programming. The complete vehicle scan shows which direction deserves testing.
Code: E09400
Definition: Message (transmission train display data, 0x3FD) missing, receiver GWS, transmitter EGS / CCU
Receiver: GWS
Transmitter: EGS / CCU
Message identifier: 0x3FD
System: Transmission display communication
Note: Confirm the VIN-specific network topology
Save the full scan before clearing anything. If EGS or CCU is unreachable in the same scan, investigate its power and network presence before touching GWS.
What Symptoms Does E09400 Cause?
The most specific symptom is disagreement or interruption in gear-status presentation rather than a mechanical slipping pattern. The selector may illuminate incorrectly, the chosen range may appear late, or a drivetrain warning may accompany a momentary loss of the 0x3FD packet. Compare the selector, cluster, and scan data at the same ignition cycle; their timing is more useful than a warning lamp alone.
• The GWS display remains blank while the instrument cluster still reports the selected transmission range.
• The selector indication changes late after a range request, although the transmission engages the requested range normally.
• A drivetrain message appears at startup when EGS or CCU is temporarily absent from the vehicle scan.
• The stored event coincides with several PT-CAN missing-message codes in receivers that depend on EGS data.
• Selector lighting resets during a voltage dip, then E09400 becomes stored in GWS after communication resumes.
• The fault returns immediately after clearing whenever the transmitting module remains offline, without a test drive.
Why Does E09400 Occur?
E09400 is set because message delivery stops, and the cheapest causes should be separated from failed electronics. Begin with battery condition, wake-up behavior, and module supply evidence from the stored event. Then inspect the GWS and EGS or CCU network path. Only after power, grounds, connectors, and PT-CAN integrity are proven should software mismatch or an internal control-unit failure become the leading explanation.
• A low-voltage start interrupts EGS or CCU initialization before GWS begins monitoring message 0x3FD.
• A loose power or ground connection makes the transmitting control unit reboot during selector initialization.
• Moisture or displaced connector pins interrupt the PT-CAN pair at GWS, EGS, CCU, or an inline junction.
• Harness damage changes communication only when the center console, transmission tunnel, or nearby trim is moved.
• Programming leaves GWS and the transmitter with incompatible integration levels or an incomplete vehicle configuration.
• An internal EGS, CCU, or GWS fault persists after supplies and the network path pass loaded checks.
How Is E09400 Diagnosed with OBDThink?
Use OBDThink to record E09400, the reporting GWS variant, event status, and the complete control-unit scan before clearing stored fault codes. OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. Available live data differs by vehicle and adapter, so use the VIN-specific BMW test plan for the physical network branch and connector locations.
• 1. Save the GWS freeze frame and identify whether E09400 is currently present, intermittent, or only historical.
• 2. Review the full scan for an unreachable EGS or CCU and for matching PT-CAN receiver codes.
• 3. Compare ignition-on battery voltage in the event record with present voltage during selector wake-up.
• 4. Observe whether the GWS range indication follows the cluster while each selector position is requested once.
• 5. Load-test power and ground at the absent transmitter if the scan cannot establish communication with it.
• 6. Inspect the VIN-specific PT-CAN route and connector pins for moisture, displacement, twisting, or repair damage.
• 7. If modules remain reachable, verify compatible software and vehicle configuration with the BMW test plan.
• 8. Clear stored fault codes only after repairs, cycle ignition, rescan GWS, and repeat the selector check.
IF EGS or CCU is absent from the complete scan AND multiple receivers report its messages missing, THEN test transmitter power, ground, and wake-up first.
ELSE IF only GWS loses 0x3FD while the transmitter remains reachable, THEN inspect the GWS branch and connector pins of PT-CAN.
ELSE IF communication is stable but E09400 began after programming, THEN verify software compatibility and vehicle configuration before replacing hardware.
The fastest split is module availability: many receivers losing EGS data points upstream, while only GWS losing 0x3FD points toward its local branch or interpretation.
How Is E09400 Repaired?
Repair the proven interruption rather than replacing the gear selector because its memory contains the code. A voltage-related event may need battery, supply, or ground correction; a local network failure needs connector or harness work. Programming is appropriate only when the fault began after software work and network measurements remain sound. Control-unit replacement comes last and requires BMW-compatible configuration afterward.
• Low cost: clean and secure the affected battery, ground, or module-supply connection proven unstable under load.
• Low cost: reseat displaced connector pins and remove verified moisture at the affected GWS or transmitter connection.
• Moderate cost: repair the damaged PT-CAN twisted pair while preserving its routing, twist, and shielding arrangement.
• Moderate cost: correct incomplete BMW programming or vehicle configuration after confirming compatible hardware and stable voltage.
• High cost: replace EGS or CCU only when its supplies pass but it remains unavailable to all receivers.
• High cost: replace and configure GWS only after its local communication path and power supply pass testing.
After repair, E09400 no longer occurs through ignition cycles and every selector request matches the cluster without new PT-CAN receiver codes.
Can You Drive with E09400?
Driving may be possible when the selected range is shown correctly, engagement is normal, and no transmission or drivetrain warning remains active. However, E09400 concerns information used by the gear selector, so an intermittent display cannot be dismissed. Confirm that Park, Reverse, Neutral, and Drive requests agree between the GWS and cluster before moving the vehicle.
Do not continue if the displayed range conflicts with vehicle movement, the selector cannot confirm Park, the transmission enters limp mode, or the transmitter disappears from the scan repeatedly. Arrange diagnosis promptly even when the code is only stored, because a worsening PT-CAN or supply interruption can remove dependable range information at the next start.
Stop safely if the displayed gear disagrees with vehicle movement or Park cannot be confirmed.
What Questions Are Asked About E09400?
These questions help distinguish a communication record from a gearbox failure. The answer depends on which module is absent, whether 0x3FD returns after wake-up, and whether the selected range remains trustworthy. Preserve scan evidence before clearing E09400 because an intermittent network interruption can disappear while the ignition is cycled.
• Does E09400 mean the transmission is mechanically damaged? No. It reports a missing display-data message at GWS; mechanical transmission damage requires separate symptoms and tests.
• Can a weak battery store E09400? Yes. A startup voltage dip can delay EGS or CCU initialization, but the event record and other undervoltage codes should support that conclusion.
• Should the GWS be replaced first? No. The receiver may be correctly reporting a missing packet, so verify transmitter availability, supplies, and PT-CAN before replacing it.
• Why does E09400 return without driving? GWS monitors message 0x3FD after network wake-up, so a transmitter that stays offline can reproduce the code during ignition-on checks.
Treat the complete scan as a map of the interruption: establish who stopped transmitting, who else noticed, and whether power or PT-CAN failed first. That evidence turns E09400 from a vague selector warning into a focused test of the transmitter, local GWS branch, or software relationship.