2025 6MT - numerous bimmerlink errors. Am I making a $63,000 mistake?

[NocturnalEmber]

Car is still within my return policy for another few days, so I'm debating on whether or not to keep it based on the...interesting history. It sat unsold and was moved between a few toyota dealers for about eight months. Clean autocheck and carfax report and it drives fine.

I was hoping someone could help me make sense of these errors. Car has 9,200~ miles on it, 2025 6MT. Seems a bit weird for this many errors but I'm not familiar with BMW based systems, was hoping someone could chime in and tell me if I'm making a $63,000 mistake:

Error memory showed four errors. Info memory popped up with 55 something errors found. I cleared the info memory, and 14 of those 55~ something came back immediately after when I checked again. I did clear the error memory and did a drive for a few hours and the same four returned.


My instincts at this point are saying to avoid the car. I don't see any CEL's or any warnings. Though worth mentioning the car has had two battery replacements in its 9,200 mile life. I've had a concern with the VSC kicking on really conservatively (50 mph on a curved on ramp at half throttle) but I'm not sure if thats because of the different tires on the rear, it feels like its coming from the front when VSC kicks in.


If someone has any knowledge of Bimmerlink or the BMW systems I'd appreciate a heads up on if this is a car I should return within my return policy or if this is all relatively minor. Car drives fine otherwise, but I'd rather not be stuck with potential problems once this return policy ends.

PMA
1 error
803207: Sensor technology: noise detected

Body Domain Controller
1 error
804081: Production readiness to drive: faulty

Camera-based driver assist system
1 error
800ABF: KAFAS camera: field of view temporarily disturbed

Headunit High
1 error
B7F8F6: HDCP: authentication failed



*******INFO MEMORY*******


Crash Safety Module

7 errors

010012: Diagnosis master - info - fault memory blocked
803280: PDC cannot be activated
803181: CTA active without activation
010020: Speed - signal incorrect
803180: CTA cannot be activated
803282: RVC cannot be activated
803284: Park button reports errors


Central gateway module

13 errors

100100: Contact to FZM slave lost
100104: HW Weckgrund ZGW
100108: Functional subnet deactivation due to the startability limit
100109: Ignoring the functional subnet request due to the startability limit
10010A: Unauthorized request of a functional subnet
100203: DM software error info warning
100204: Message monitoring: no system context signal
100406: FsCSM does not send a response to F60 or F70
100600: Flexray protocol startup time is too high
100601: Unexpected asynchronous state on Flexraybus
CD0601: Ethernet: CRC error



Digital Motor Electronics
3 errors

213B02: Battery status detection: battery regeneration active
24000B: Timeout data EWS
21A026: Combustion engine: abnormal key / MSA start detected

Dynamic Stability Control (DSC)
2 errors

480AD4: RDC calibration
D35D1F: D-OBD 3 - EPS - Communication error Diagnostic status message, group error


Virtual integration system
6 errors

0305A9: QDM-QEI - limited model validity
030C67: INT-SVCHDL Input buffer overflow
03066F: QDM-ODO - degradation odometry
03065D: QDM-ZFM - Statistics proportion of linear travel range
0305AA: QDM-QEI - plausibility error
000002: FLEXRAY controller ACS error


Active Sound Design
1 error

3F100D: Message (status convertible roof, 0x342): failure or signal invalid


Roof function center
3 errors

801A0E: NVM_E_INTEGRITY_FAILED
3
801A20: CAN_E_TIMEOUT
801A57: Anti-theft alarm system: deactivation of IRS and inclination sensor via customer
function


Instrument panel
8 errors

B7F671: Combination: information error 9
B7F670: Combi: information error 8
B7F66C: Combination: information error 4
B7F756: Combination: External Vsync error
E106E1: SOME / IP error
B7F66A: Combination: information error 2
B7F67C: Combined: CAN input buffer, data loss
B7F779: Station wagon: mileage implausible

Telematic Communication Box
1 error

610036: Flight mode due to failed network registration

Headunit High
1 error

E1C601: Ethernet: CRC error



****INFO MEMORY CODES CAME BACK IMMEDIATELY AFTER CLEARING****


Crash Safety Module
7 errors

803280: PDC cannot be activated
010012: Diagnosis master - info - fault memory blocked
803181: CTA active without activation
010020: Speed - signal incorrect
803180: CTA cannot be activated
803282: RVC cannot be activated
803284: Park button reports errors


Central gateway module

101008: Non-resolvable ambiguous routing - SG not in the SVT target table
2

100102: Invalid LocalSleepReadiness message received


Digital Motor Electronics
3 errors

213B02: Battery status detection: battery regeneration active
24000B: Timeout data EWS
21A026: Combustion engine: abnormal key / MSA start detected

Dynamic Stability Control (DSC)
2 errors

480AD4: RDC calibration
2
D35D1F: D-OBD 3 - EPS - Communication error Diagnostic status message, group error

Sponsored

 

[3TMagnetMan]

Return it

 

[Hasan]

Is it possible that its still in delivery mode or whatever they call it?

 

[NocturnalEmber]

From what I can tell, the "Info Memory" is morelike a generic log? Not really any faults but I guess an "anything and everything" log of sorts?

Permanent faults turned up zero. So I'm assuming its just the 4 in error memory, but even those aren't throwing a CEL and the car doesn't have any drivability issues.

Can someone with Bimmerlink run a check on their car for the heck of it and see if you turn up with a ton of things showing in Info memory and Error memory?

Edit: The car has had a relatively tame life from what I can tell otherwise, I'm the second owner and it was traded in with 8,900~ miles maybe? So its still well within warranty and the vehicle history reports don't show anything concerning like service for repeated issues, just oil changes and the like.

So I guess I'm trying to determine if this is normal/justified.

 

[BMWAF]

I think this is just #BMWThings. No CEL: Nothing to worry about.

 

[NocturnalEmber]

I think this is just #BMWThings. No CEL: Nothing to worry about.

I'm hoping thats the case. The car drives fine otherwise, but I had a boulder in my throat when I saw that reading initially. It seems to be just like microsoft event viewer in windows, logs anything and everything even if not pertinent or important.

 

[tracer bullet]

According to Google, some things to check on for these might be:

803207: Sensor technology: noise detected - PDC sensor might be blocked, license plate or something aero added on?

804081: Production readiness to drive: faulty - May be a low or half dead battery, maybe from sitting a long time.

800ABF: KAFAS camera: field of view temporarily disturbed - Camera on the windshield for driving assist might be blocked (including condensation internally)

B7F8F6: HDCP: authentication failed - supposedly an issue connecting a phone to the car, maybe left over from a previous owner. Maybe try and erase all previous connections / owners.

I won't promise any of this is true but might be some stuff you could look at to see if these seem important.

If it truly drives fine and doesn't show signs of being abused by the former owner(s) then it's probably good to go, generally speaking. Although $63k sounds high to me but I really don't know what they normally go for, maybe that's on par.

You might use this to your advantage, tell them it's got some codes and you are considering returning it, see what they say. Maybe they'll fix them, or give you a discount to keep it. Worth asking.

 

[razorlab]

What different tires do you have on the rear?

 

[Strat-Supra]

Most likely the previous owner used bimmerlink or another app to code out a few things. The info memory errors are most likely from low battery voltage and disconnection. I have disconnected my battery multiple times to do work and left the battery disconnected for days/weeks, with/without a battery tender and have seen and still have some of the same errors.

No matter how many times I try to clear the errors, some of them won't delete. I've tried multiple apps/tools to no avail. I've done some research (not extensive) on the errors, everything I've found points to the battery being disconnected and low voltage. None of the codes have produced a CEL nor have I noticed any issues that I'm aware of.

I believe but can't confirm that sensors and other electronics continue to communicate with various modules (performing tests and who knows what) for ~20 minutes after the car is turned offed and locked. If the battery voltage drops too low or is disconnected during this time errors will be generated in info memory.

Again, I'm providing my opinions/beliefs based what I've experienced and discerned through research (not extensive), so take them with a grain of salt.

Understand your concern, I'd be concerned as well, the question is, will you ever feel comfortable knowing that they were there when you bought the car, even if they're not causing any issues you're aware of.

 

[NocturnalEmber]

According to Google, some things to check on for these might be:

803207: Sensor technology: noise detected - PDC sensor might be blocked, license plate or something aero added on?

804081: Production readiness to drive: faulty - May be a low or half dead battery, maybe from sitting a long time.

800ABF: KAFAS camera: field of view temporarily disturbed - Camera on the windshield for driving assist might be blocked (including condensation internally)

B7F8F6: HDCP: authentication failed - supposedly an issue connecting a phone to the car, maybe left over from a previous owner. Maybe try and erase all previous connections / owners.

I won't promise any of this is true but might be some stuff you could look at to see if these seem important.

If it truly drives fine and doesn't show signs of being abused by the former owner(s) then it's probably good to go, generally speaking. Although $63k sounds high to me but I really don't know what they normally go for, maybe that's on par.

You might use this to your advantage, tell them it's got some codes and you are considering returning it, see what they say. Maybe they'll fix them, or give you a discount to keep it. Worth asking.

That is about what I could find as well. The battery was replaced, and then that battery I believe was warrantied. According to Bimmerlink the battery charge is 80% and seems to be healthy though.

I didn't see any obstruction to the camera or any condensation, but I think that might be on the dealer to have to diagnose.

for the HDCP connection, good idea, I'll check to see if there are any other phones paired to the car still. I only have an android so its bluetooth for me right now though.

We had it up on a lift at the dealer and neither the techs nor myself could find any symptoms of abuse, which is partially why this is so confusing, there's no direct cause to point to and say "yep, that looks like that caused it."

 

[NocturnalEmber]

What different tires do you have on the rear?

Firestone Firehawk Indy 500's on the rear. Not what I would have personally chosen, but this was installed by the previous toyota dealer. I checked to make sure they were directionally mounted correctly and the right size, that at least checked out.

 

[NocturnalEmber]

Most likely the previous owner used bimmerlink or another app to code out a few things. The info memory errors are most likely from low battery voltage and disconnection. I have disconnected my battery multiple times to do work and left the battery disconnected for days/weeks, with/without a battery tender and have seen and still have some of the same errors.

No matter how many times I try to clear the errors, some of them won't delete. I've tried multiple apps/tools to no avail. I've done some research (not extensive) on the errors, everything I've found points to the battery being disconnected and low voltage. None of the codes have produced a CEL nor have I noticed any issues that I'm aware of.

I believe but can't confirm that sensors and other electronics continue to communicate with various modules (performing tests and who knows what) for ~20 minutes after the car is turned offed and locked. If the battery voltage drops too low or is disconnected during this time errors will be generated in info memory.

Again, I'm providing my opinions/beliefs based what I've experienced and discerned through research (not extensive), so take them with a grain of salt.

Understand your concern, I'd be concerned as well, the question is, will you ever feel comfortable knowing that they were there when you bought the car, even if they're not causing any issues you're aware of.

Well, given that it had a battery replaced I wouldn't be surprised. I honestly won't feel bad about it if its just a symptom of maybe being stored at the dealer for awhile and a battery replacement, because I can't find any fault codes, there's no other warning lights on, and the car drives fine otherwise. Had I not scanned it I'd never have known they were there.

 

[puzzled]

Definitely don't buy. Find another one. My 2020 has no errors and still on original battery.

 

[MavJ]

What different tires do you have on the rear?

this… hahahah iykyk

 

[NocturnalEmber]

Definitely don't buy. Find another one. My 2020 has no errors and still on original battery.

Thats what I just find odd. The car has a clean carfax and autocheck, yet its been through two battery replacements. One was under the customer, the other was covered internally by toyota when it was in dealer inventory.

The car doesn't have any sort of abnormal behavior but that is just so odd to have two battery replacements done.

Could the customer have let the battery die, toyota put a new one in and didn't program it, and then that necessitated a third? I mean stranger things have happened, but I'm scratching my head trying to figure out if there's something wrong with it otherwise and diagnostic wise its not coming up with anything...maybe I'm being pedantic?

Sponsored