GrauTech Cleaner
Education6 min read

Airbag fault codes after deployment (B2000 and more), explained

After an airbag deployment the module logs specific fault codes such as B2000 'crash data stored'. Here is what they mean, why they won't clear, and what actually fixes them.

Fault codes that appear after a deployment

Once an airbag system has deployed, the airbag ECU (SRS control module) logs permanent fault codes and turns on the warning light. Unlike ordinary sensor faults, these codes are tied to the recorded crash event and do not clear with a normal reset.

If the light is on and won't go off, start with why the airbag light stays on after a crash.

The key code: B2000 / "crash data stored"

On VW Group vehicles, the most common code family after a deployment relates to a stored crash event — often seen as B2000 or described by testers as "Crash Shut-Down Activated" or "crash data stored". This is the module telling you that an impact was recorded in its memory.

This code is not a wiring fault. It is the record of the event itself, which is exactly what makes it persistent.

Other codes you may also see

Depending on what deployed, additional codes can appear, such as:

  • Igniter / squib circuit faults for deployed airbags or belt tensioners (resistance out of range because the pyrotechnic part has fired)
  • Seat-belt pretensioner faults
  • Occupant sensor or satellite crash-sensor faults if wiring was damaged in the impact

These hardware faults must be resolved by replacing the deployed components — a file service does not repair physical parts.

Why "clear codes" doesn't work

Clearing DTCs with VCDS, OBD or a dealer tester removes ordinary faults, but the stored crash event comes straight back, because it is held separately in the module. For background on what that stored data actually is, see what is crash data in an airbag ECU.

What actually resolves it

Two things generally need to happen:

  1. Replace the deployed hardware — airbags, pretensioners and any damaged sensors/wiring — so the circuit faults are physically fixed.
  2. Reset or replace the module so the stored crash event is cleared and the light can go out.

For the VW40 airbag ECU, the crash data lives in the module's memory. It can be cleared by resetting the module — via a new unit, a mail-in service, or an online file service where the supported dump is read, cleared and written back. That is what GrauTech Cleaner does for the VW40 family; see the file service process.

Safety and legality

An airbag warning light and a stored crash code mean the restraint system is not in a ready state. Deployed parts must be correctly replaced, the result must be verified by a qualified technician, and the module may only be reused where it is safe and legal. GrauTech Cleaner is intended only for professional, authorized workshop use — see the terms of service.

Related information and next step

Disclaimer: Airbag and SRS systems are vehicle safety systems. The service is intended only for authorized workshop use, and every result must be verified by a qualified technician before use. GrauTech Cleaner is not affiliated with Volkswagen AG, Audi AG, Škoda Auto, SEAT or Cupra.

FAQ about VW40 airbag ECU reset

What does B2000 mean on an airbag module?

On VW Group cars, B2000 (often shown as 'Crash Shut-Down Activated' or 'crash data stored') indicates the module has recorded a crash event in memory. It won't clear with a normal reset.

Why do the codes come back after clearing them?

Clearing DTCs removes ordinary faults, but the stored crash event is held separately in the module and returns immediately, keeping the airbag light on.

Does resetting the module fix igniter circuit codes too?

No. Circuit faults for deployed airbags or pretensioners are physical — the fired components must be replaced. A file service only clears the stored crash data.

Dealing with a stored crash code on a VW40 unit? Confirm the part number and start an online file service order.

Reset a VW40 module online

Related articles