How the BMW E65 7-Series CAS Module Causes a No-Start
The CAS — Car Access System — in the BMW E65 7-Series is the central authority for deciding whether the engine is allowed to start. It reads the transponder signal from the key, communicates with the DME, EGS and instrument cluster over the K-CAN bus, and only releases the starter once all authorizations are confirmed. When the CAS module develops an internal fault, the result is typically a complete no-start with no engine cranking and no error message beyond a vague key warning on the iDrive screen.
What the CAS Actually Controls
Unlike the older EWS immobilizer fitted to E46 and E38 models, the CAS in the E65 is a far more integrated unit. It manages not just the immobilizer function but also the comfort access system, interior lighting authorization, remote locking and unlocking, and the push-button start where fitted. The module sits behind the steering column trim and communicates via a local interconnect network as well as the main K-CAN bus. A failure in any of these communication paths can make the CAS appear completely dead even when it still has power.
The E65 was produced from 2002 through to 2008, and the CAS generation across that run is CAS2. Earlier E65 models used a slightly different hardware revision, and late post-facelift cars from around 2005 onward have updated CAS2 variants with revised software. This distinction matters when sourcing a replacement module because the software version must correspond to the vehicle equipment and the coding data stored in the unit must be transferred or rewritten.
Typical Symptoms When the CAS Fails
- Engine does not crank at all — starter motor silent even when key is turned or button pressed
- Red key warning symbol appears on the instrument cluster or iDrive screen
- Central locking responds to the key fob but start is still refused
- Car starts occasionally then refuses on the next attempt — intermittent authorization failure
- Battery voltage appears normal, starter relay clicks but engine does not turn
- KOMBI cluster shows "Transmission malfunction" or "Drive moderately" alongside start refusal
One particularly confusing presentation is when the car unlocks perfectly using the remote, the interior lights come on, the dashboard illuminates fully, and yet the engine will not crank. Owners frequently blame the battery or the starter at this point. A scan of the CAS module directly usually reveals the actual cause within seconds. For comparison, see BMW E65 7-Series CAS Module Failure: Common Faults and Repair.
Common Fault Codes from the E65 CAS
| Fault Code | Description |
|---|---|
| A804B | CAS: key not detected or transponder communication error |
| A804E | CAS: remote control signal outside valid range |
| A8062 | CAS: internal memory fault — EEPROM read error |
| A8065 | CAS: voltage supply below threshold during start attempt |
| A806A | CAS: K-CAN communication timeout with DME |
| A8070 | CAS: CAN message from EGS missing during start sequence |
| 280CF | DME: no start enable signal received from CAS |
Code A8062 in particular — the internal EEPROM fault — points to a hardware failure within the CAS unit itself rather than a wiring or key problem. When this code is present alongside a no-start, the CAS module has almost certainly failed internally and no amount of key reprogramming will resolve it.
Before Condemning the CAS Module
A no-start on the E65 has several possible causes, and the CAS should only be confirmed as faulty after a proper check. First verify that the battery voltage is above 12.4 volts at rest and holds above 10.5 volts during a start attempt — a weak battery can prevent the CAS from completing its authorization cycle cleanly. Next check that the key battery is fresh, as a low key battery causes the transponder signal to drop out intermittently. Check the CAS ground connection behind the steering column trim, as a corroded ground causes exactly the communication timeout codes listed above.
If voltage and grounds are confirmed good, pull a full fault code scan using ISTA, INPA or a compatible BMW-capable scanner. Read codes from the CAS, DME and instrument cluster simultaneously. If the DME shows a missing start enable from the CAS and the CAS itself shows an internal memory or communication fault, the module is the confirmed cause.
OEM Part Numbers for the BMW E65 CAS Module
The following part numbers cover common CAS2 variants fitted to the E65 7-Series. The exact number depends on production date, key type and whether comfort access was installed.
- 61.35-6 974 085 — early E65 CAS2, standard key, non-comfort-access
- 61.35-6 974 086 — E65 CAS2, comfort access equipped
- 61.35-6 943 196 — E66 long-wheelbase CAS2 variant
- 61.35-6 916 002 — pre-facelift E65, earlier software revision
- 61.35-6 979 508 — post-2005 facelift E65 CAS2 updated variant
Always cross-reference the part number on the original unit before ordering a replacement. The CAS module number is printed on a label on the unit housing. A mismatch in variant will cause coding problems even when the replacement module is correctly programmed, because internal variant bits may not match the car’s expected configuration. A related diagnostic guide is BMW E65 7-Series CAS Module Failure: Symptoms and Repair Guide.
Replacement and Coding Requirements
The CAS module stores the vehicle’s key data, mileage reference and immobilizer seed values. A replacement unit — whether new or tested used OEM — must be coded to the specific vehicle using BMW ISTA or equivalent professional tooling. This process rewrites the VIN binding, transfers or regenerates key sync data, and aligns the CAS with the DME and cluster. Without this coding step, a replacement CAS will not authorize the engine start any more than a faulty one would.
Used OEM CAS modules can be successfully fitted to the E65 provided they come from the same hardware variant and the coding process is carried out correctly by a workshop with the appropriate BMW access. A partially coded or incorrectly matched CAS is a common cause of repeat no-start complaints after a DIY replacement attempt.
Affected Vehicles
The CAS2 module and its failure pattern described here applies primarily to the BMW E65 760i, 745i, 745Li, 750i, 750Li and 730i built between 2002 and 2008, as well as the E66 long-wheelbase variants of the same generation. Vehicles with production dates before mid-2003 use a slightly earlier CAS2 revision. The comfort access variant was optional from around 2004 and uses a different internal antenna configuration. All variants are subject to the same EEPROM failure and K-CAN communication fault patterns described above.
Five Questions Owners Ask About the E65 CAS Module
Can a flat key battery cause the same no-start symptoms as a dead CAS?
Yes, a key with a discharged battery produces a very similar symptom — the car unlocks via the door handle sensor but refuses to start. Try holding the key directly against the steering column ignition ring or start button area. If the car starts with the key held in position, the key battery is the issue, not the CAS module itself. For additional context, read BMW E65 7-Series EGS Transmission Control Module Faults Guide.
Will fault codes always appear when the CAS has failed internally?
Not always. Some internal EEPROM failures prevent the CAS from completing its boot sequence, which means it cannot generate or store fault codes in the normal way. In these cases, a scan returns no communication with the CAS module at all rather than a list of codes. This no-communication result from the CAS is itself a strong indicator of hardware failure.
Does a used OEM CAS module need to come from the same vehicle?
No — a used CAS from a different E65 can be fitted and recoded to the target vehicle. The critical requirements are that the hardware variant matches (comfort access vs standard, correct software generation) and that a BMW-capable tool is used to recode the module completely. Coding rewrites the VIN and key data, so the origin vehicle does not matter as long as the hardware matches.
Can water damage affect the E65 CAS module?
The CAS module is located in a relatively protected area behind the steering column, but water entering the footwell from a blocked drain or windscreen seal can reach it over time. Corrosion on the connector pins or on the circuit board produces intermittent communication faults before causing a permanent failure. Inspect the connector carefully before assuming the module itself has failed internally.
How long does it take to recode a replacement CAS on the E65?
With the correct BMW ISTA setup and a stable power supply connected, the CAS coding procedure itself typically takes between twenty and forty minutes. Additional time is needed if new keys must be synchronized or if the DME alignment procedure must be repeated separately. The total workshop time for a straightforward CAS swap and coding on the E65 is generally one to two hours.
Find tested OEM electronic parts and modules at:
https://giantparts.eu/
