B1193 – Crash event storage full and locked, System internal faults, Special memory fault (Volvo)

Volvo-specific code — factory diagnostic data

B1193 means the Volvo XC40 airbag system has locked its crash-event memory, so it may not record new crash data. You will usually see an SRS warning and reduced restraint system readiness until you fix the cause. According to Volvo factory diagnostic data, this code indicates “Crash event storage full and locked” and “System internal faults, Special memory fault” in the SRS(Supplemental Restraint System Module). This is a manufacturer-specific Volvo code, so the meaning and test plan come from the Volvo description, not a universal SAE definition. Treat it as a pointer to a memory-status problem inside the SRS module and its supporting power, ground, and network conditions.

B1193 Quick Answer

The SRS module reports its crash-event storage is full and locked, or it cannot access that special memory. Diagnose power, grounds, network stability, and module memory status before replacing any parts.

What Does B1193 Mean?

Official Volvo definition: “Crash event storage full and locked, System internal faults, Special memory fault.” In plain terms, the SRS(Supplemental Restraint System Module) has stored crash-related records and now refuses to write more, or it cannot reliably read its protected memory area. In practice, the Volvo XC40 may keep the SRS warning on and may limit certain self-checks until the module can confirm memory integrity.

What the module is checking and why it matters: The SRS module continuously verifies internal non-volatile “special” memory used for crash-event logging and system integrity. It also tracks a lock state that prevents overwriting after specific events. The code sets when internal memory checks, access routines, or the lock-status logic fails, or when the log reaches its limit and remains locked. This matters because you must prove the module has clean power, ground, and stable communication before you blame internal memory. Per SAE J2012-DA Section 6.1, the DTC message points to a suspected area, not the root cause.

Theory of Operation

Under normal conditions, the Volvo SRS module monitors crash sensors and restraint circuits, then stores key event data in non-volatile memory. The module also stores configuration, calibration, and diagnostic history. It uses that “special memory” to retain information even if battery power drops during a collision.

With B1193, the normal memory workflow breaks down. Either the crash-event storage reaches its capacity and stays locked, or the module detects a fault during memory read/write or integrity checks. Unstable module supply voltage, poor grounds, or intermittent network issues can interrupt internal transactions and trigger internal-fault logic, even when the memory hardware has not failed.

Symptoms

You will usually notice an SRS warning and limited system readiness when this code sets.

• SRS warning SRS/airbag warning message or lamp stays on
• Stored DTC B1193 present as current or history in the SRS module
• Lock status Scan tool shows crash-event log “locked” or “not erasable,” depending on tool wording
• Erase failure DTCs clear briefly, then return immediately after a key cycle
• Network side effects Other body or safety modules may store related communication or configuration faults
• Self-test limits Some SRS self-tests show “not completed” or “not available” until memory status passes
• Warning recurrence Warning returns after low battery events, jump starts, or repeated key cycles

Common Causes

• Crash event memory full: The SRS reaches its limit for stored crash data and blocks new storage, which triggers the internal memory fault.
• Crash event storage locked from a prior deployment event: A previous airbag or pretensioner activation can lock the event record, and the module then flags B1193 when it cannot write or finalize records.
• SRS internal non-volatile memory fault: EEPROM/flash wear, corruption, or a failed memory sector prevents reliable read/write operations, so the module logs a “special memory fault.”
• Low system voltage during key-on or write events: A voltage dip while the SRS powers up or writes event data can corrupt memory operations and set an internal fault.
• High-resistance power or ground to the SRS module: A poor feed or ground causes momentary brownouts under load, and the module then loses stable memory access.
• Connector fretting or terminal drag at the SRS module: Intermittent contact at the SRS connector can reset the module or interrupt write cycles, which looks like a memory lock/full condition.
• Harness damage near the SRS module mounting area: Pinched or rubbed wiring can create intermittent opens that drop power briefly and leave the crash storage in a locked state.
• Improper programming/configuration after prior service: A mismatched or incomplete SRS software/configuration state can prevent normal event storage management and set internal memory faults.

Diagnosis Steps

Use a scan tool that can access Volvo SRS functions and read freeze frame or event records. Have a quality DMM and back-probe leads for voltage-drop testing under load. Keep the battery charged with a regulated power supply during diagnosis and programming. Use service information for connector views and fuse locations. Follow all SRS safety procedures before disturbing connectors.

1. Confirm B1193 in the SRS and record whether it shows as pending, stored, or confirmed. Save freeze frame and event data, focusing on battery voltage, ignition state, and any “crash event stored/locked” indicators. Note related SRS codes, since they often explain why the module tried to write an event record.
2. Check fuses, power distribution, and grounds that feed the SRS module before you probe the module connector. Perform a visual inspection along the power path for heat damage, loose fasteners, or prior repair work. Verify the battery condition and charging system health, because low voltage can cause internal memory write faults.
3. Verify SRS power and ground integrity with voltage-drop testing under load. Load the circuit by commanding SRS wake-up with ignition ON and the vehicle in its normal operating mode. Measure voltage drop from battery positive to the SRS B+ feed, and from SRS ground to battery negative. Keep ground drop under 0.1V with the circuit operating, since continuity checks can miss high resistance.
4. Cycle ignition and watch the scan tool for immediate code return. A hard internal fault often returns right away at key-on. If the code only reappears after a drive cycle, treat it as intermittent and focus on power stability and connector contact quality.
5. Inspect the SRS module connector(s) and surrounding harness carefully. Look for terminal push-out, corrosion, moisture traces, or fretting marks. Confirm proper terminal tension and seating. Do not ignore signs of prior airbag work, since disturbed connectors often create intermittent resets that mimic memory faults.
6. Check for evidence of a prior crash event or deployment history in SRS data. Use the scan tool to view crash event records and any “event storage locked” status. Do not assume a module failure based on B1193 alone. The definition points to stored data management, not a specific sensor or squib circuit.
7. If the scan tool supports it, attempt the Volvo-approved SRS event memory service function. Follow the tool prompts exactly and maintain stable system voltage. If the function fails or reports “locked” without clearing, document the failure message. That result helps separate a simple full-memory condition from a true internal memory fault.
8. Differentiate freeze frame from a technician-triggered snapshot during testing. Freeze frame shows conditions when B1193 set. A snapshot captures live battery voltage and SRS supply stability during a road test or ignition cycle. Use the snapshot to catch brief voltage dips or resets that freeze frame may not show.
9. If voltage or connection issues appear, stress-test the harness and power feeds while monitoring SRS supply voltage on the meter. Perform a wiggle test near the module, grounds, and fuse blocks. Watch for sudden voltage-drop spikes or module communication interruptions. Stop if you risk disturbing SRS connectors without proper safety steps.
10. After repairs, clear codes and perform a controlled key cycle and road test. Re-scan all modules and confirm B1193 does not return. Verify the SRS warning indicator behaves normally and that no new SRS faults appear. If the code returns with verified power/ground integrity, treat it as an internal SRS memory or locked event condition that requires module-level service per Volvo procedures.

Professional tip: Treat B1193 as a “write integrity” problem until you prove otherwise. Most wasted time comes from chasing airbags, pretensioners, or impact sensors. First, prove stable SRS power and ground with voltage-drop under load. Next, confirm crash event status with the scan tool. Only then should you consider memory service functions or module replacement and programming.

Possible Fixes

• Restore clean SRS power and ground: Repair high-resistance feeds, ground points, or fuse block issues confirmed by voltage-drop testing under load.
• Repair connector or harness faults at the SRS module: Correct terminal tension, corrosion, water intrusion, or damaged wiring that causes intermittent resets or write interruptions.
• Perform the Volvo-approved crash event memory service function: Clear or manage event storage using the correct scan tool procedure once you confirm stable voltage and proper connections.
• Stabilize system voltage during operation: Correct weak battery or charging faults that create low-voltage events during key-on or module write cycles.
• Reprogram/configure the SRS module as required: Update software or complete configuration steps if service information indicates a programming-related cause.
• Replace the SRS module only after verification: If event storage remains locked and memory functions fail with proven good power/grounds and connectors, replace and program the module per Volvo procedures.

Can I Still Drive With B1193?

You can usually drive a Volvo XC40 with B1193, but you should treat the SRS system as unreliable until proven otherwise. This code comes from the SRS (Supplemental Restraint System Module) and points to crash event storage that is full and locked, plus an internal “special memory fault.” That condition can block normal SRS self-check logic and crash-data handling. If the airbag warning lamp stays on, assume the system may not deploy correctly in a crash. Do not attempt DIY SRS repairs. Keep driving only to reach a qualified Volvo-capable shop, and avoid unnecessary passengers until the fault is confirmed and corrected.

How Serious Is This Code?

B1193 ranges from a nuisance to a serious safety concern, depending on what the SRS module reports in data and what other SRS DTCs accompany it. If the only issue involves stored crash records that reached capacity, the vehicle may drive normally while the SRS lamp remains on. If the “locked” state follows a prior deployment event, or the module flags internal memory integrity problems, the SRS system becomes potentially compromised. Treat it as safety-critical. Proper diagnosis requires SRS-certified technician training and equipment, plus strict handling procedures around pyrotechnic components. Do not probe squib circuits or attempt module work without approved methods.

Common Misdiagnoses

Technicians often misread B1193 as a failed airbag, belt tensioner, or impact sensor and start swapping parts. That wastes money because the code does not identify a specific firing circuit. Others clear codes repeatedly and call it fixed, even though crash event storage can stay locked and reflag immediately. Another common miss involves power and ground integrity at the SRS module. Low system voltage, poor grounds, or corrosion can corrupt memory writes and mimic an internal fault. Avoid guesswork by confirming battery health, voltage-drop on SRS powers and grounds under load, scan-tool access to SRS data, and whether the SRS module reports “crash stored/locked” status.

Most Likely Fix

The most common confirmed repair directions involve restoring proper SRS module operation rather than replacing airbags. First, verify clean battery power and stable grounds to the SRS module, then correct any voltage-drop or connector issues that can cause memory write errors. Next, use Volvo-approved diagnostic software to read SRS crash status and event storage state. If the storage is full and locked due to a prior crash record, a controlled service procedure may be required to unlock, reset, or replace the SRS module. Do not treat module replacement as automatic. Prove the power/ground and network conditions first, then follow Volvo service steps for crash-data handling and programming.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.

Last updated: April 10, 2026