B2005 on 2013-2015 Audi S8 (4.0 TFSI vehicles with reproducible 1000-3000 rpm vibration; diagnose J931 before mount replacement) — Invalid Data Record
1 vehicles · 1 makes
How to diagnose and fix B2005: most-reported vehicles
Ranked by owner reports. Each card gives the symptoms, how to confirm the cause, the fix, parts and sources for that vehicle.
Audi S8 · 2013–2015
Audi TSB 2036392/6 covers 2013-2015 S8 4.0 TFSI vehicles with vibration around 1000 and 3000 rpm and possible B201000 or B200500 in the sub-frame mount controller J931. Work on electrical-system controllers J519/J520 can deactivate J931 active-mount basic settings. The bulletin does not establish that both mounts commonly fail at 60,000-100,000 miles.
Common Symptoms
- Vibration near 1000 or 3000 rpm
- Judder when cylinders are switched off
How to Fix
Reproduce the vibration under Audi’s specified driving conditions and scan J931. If the bulletin applies, verify J931 software, perform the required SVM update and basic settings, align the exhaust without tension, repeat basic settings and follow the referenced diagnosis if vibration remains. Inspect mount hardware only after the software, calibration and exhaust path. Do not disable cylinder-on-demand or replace both mounts from the former card.
Sources for this issue (1)
Find B2005 by make
Browse every documented model and issue for your make.
B2005 code reference
General diagnostic-code context. The code alone does not confirm a cause for your vehicle; use the applicable issue card and its sources.
Frequently asked questions
What does B2005 mean?
B2005 stands for "Invalid Data Record." A control module has found that the parameter or coding data set stored in its own memory is invalid or corrupt. The module cannot verify its configuration, so it limits or disables its functions until a valid data record is written back. On Audi 4.0T V8 models it is most often seen in the active engine mount (subframe mount) control module J931, where it appears alongside B2010.
What are the most common causes of B2005?
The most common causes of B2005 are: Corrupt or missing parameter data in the control unit, Incomplete or aborted SVM (Software Version Management) coding session, Module coded to the wrong part number or variant, Control module firmware fault, Low system voltage during a previous programming attempt. The specific cause varies by vehicle.
How much does it cost to fix B2005?
Repair costs vary widely depending on the root cause and vehicle.
Which vehicles are affected by B2005?
Au7o has documented B2005 across 1 vehicle models from 1 manufacturers: Audi.
Content compiled with AI assistance using NHTSA complaints, TSBs, and owner reports. May contain errors. Always verify with your vehicle's service manual.