B1035 – Seatbelt pretensioner activation record (Suzuki)

Suzuki-specific code — factory diagnostic data

Last updated: April 11, 2026

Definition source: Suzuki factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.

B1035 means the Suzuki Swift SRS module stored a seatbelt pretensioner activation record. In plain English, the airbag system believes a crash event happened, or it has a stored deployment history, so the SRS warning light will usually stay on and the restraint system may not protect occupants as intended until proper post-collision service is completed. According to Suzuki factory diagnostic data, this is a manufacturer-specific body code for a pretensioner activation record, not a routine wiring fault. That distinction matters. This code points first to crash history and event storage in the SRS(Airbag) module. It does not, by itself, prove a connector, pretensioner, or module failed.

🔍Decode any Suzuki Swift VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data

B1035 Quick Answer

B1035 tells you the Suzuki SRS(Airbag) module has a stored seatbelt pretensioner activation record. Most often, the vehicle experienced a collision event and now needs OEM post-crash inspection, likely including module replacement and full SRS verification.

What Does B1035 Mean?

On Suzuki vehicles, B1035 means the SRS control unit recorded that a seatbelt pretensioner activation event occurred. For the owner, that usually means the restraint system has crash history stored in memory, and the SRS warning lamp remains on until the correct post-crash repair steps are completed.

Technically, the module monitors internal crash-event status and deployment records, not just a simple external circuit state. The official definition here is Seatbelt pretensioner activation record. That means the module logged an event associated with pretensioner firing criteria or deployment history. This matters because diagnosis starts with collision confirmation and event-data review, not with random parts replacement or extended circuit chasing.

Theory of Operation

Under normal conditions, the Suzuki SRS(Airbag) module watches crash inputs, internal logic, power supply integrity, and deployment loops. If crash thresholds are met, the module commands the appropriate restraint devices, including seatbelt pretensioners, to tighten the belts in a fraction of a second. After that event, the module stores a record so technicians can identify that the system saw a deployment-related incident.

This code sets when that stored record exists for the pretensioner event path. In most cases, the record reflects a real crash or a prior deployment history. Less often, improper prior repairs, module substitution issues, or power supply problems can leave misleading stored data. That is why you confirm vehicle history and inspect for physical collision evidence before you test any secondary circuits.

Symptoms

Drivers and technicians usually notice safety-system warnings and post-collision clues before anything else.

• SRS warning light: The airbag lamp stays on or returns immediately after code clearing.
• Stored crash history: The scan tool shows B1035 in the SRS(Airbag) module memory.
• Pretensioner deployment signs: The front seatbelt assemblies may appear locked, tightened, or previously replaced.
• Post-collision evidence: The Swift may show repaired body damage, replaced trim, or disturbed interior panels.
• Additional SRS codes: Other deployment, squib, seatbelt, or module memory codes may accompany B1035.
• Failed inspection after repair: The warning lamp remains on even after cosmetic collision repairs.
• History mismatch: The seller or owner reports no crash, but the SRS data suggests otherwise.

Common Causes

• Recorded collision or deployment event: The Suzuki SRS control module stored a pretensioner activation record after crash thresholds were met or a deployment occurred.
• Completed pretensioner deployment during a prior impact: A seatbelt pretensioner fired in an earlier collision, and the module retained that event in memory.
• Previous body repair without full SRS post-crash service: A repaired Swift may still carry the stored activation record if the post-collision SRS procedure stopped before module replacement and verification.
• Used or improperly configured SRS control module: An installed module from another vehicle can already contain crash data and set B1035 on startup.
• Seatbelt pretensioner or SRS components replaced without initialization: Parts replacement alone does not erase a stored crash record, so the module continues to report the event.
• Low system voltage during a severe event or unstable power supply: Voltage instability can corrupt event recording or create related SRS memory issues that require service information confirmation.
• Connector damage after collision repair: Impact damage, pin spread, or poor reconnection can add additional SRS faults that accompany the activation record and complicate diagnosis.
• Module memory fault or internal processing error: In rare cases, the SRS module can store invalid deployment history, but you must rule out actual crash history first.

Diagnosis Steps

Use an OEM-capable scan tool, current Suzuki service information, and a quality meter for power and ground voltage-drop checks. Keep SRS safety first. Depower the system before touching connectors. Do not probe squib circuits with standard test leads. For this code, focus on post-crash evidence and event history before you spend time on deeper electrical testing.

1. Confirm B1035 in the SRS(Airbag) module and record all stored and history codes. Save freeze frame or event data, especially battery voltage, ignition state, and any related deployment or restraint codes. Freeze frame shows the conditions when the code set. A manual scan-tool snapshot helps later if you need to capture an intermittent power issue during testing.
2. Inspect the Swift for collision evidence before meter work. Check front, side, and interior areas for replaced trim, deployed or missing airbags, locked or replaced belts, repair marks, and signs of previous body work. Then check SRS-related fuses and power distribution feeds. If the vehicle shows crash evidence, treat B1035 first as a stored post-crash record, not as a simple circuit fault.
3. Verify SRS module power and ground under load. Use voltage-drop testing, not continuity alone. Check each power feed and each ground path with the circuit operating. Ground drop should stay below 0.1 volt under load. A high-resistance connection can pass a static voltage check and still upset module memory or communication.
4. Inspect the SRS module connector, seatbelt pretensioner connectors, and nearby harness routing. Look for water entry, corrosion, loose locks, backed-out terminals, pin drag issues, and impact-related harness damage. Do not unplug or probe pyrotechnic circuits until the system is properly depowered and the service procedure allows it.
5. Use the OEM-capable scan tool to review SRS event records and module identification. Confirm whether the module reports deployment history, activation history, or replacement status. Compare module part information with the vehicle build data if service information supports that check. A used module with stored crash data can trigger this code even if the current vehicle was not recently crashed.
6. Inspect seatbelt pretensioner assemblies and belt hardware for physical deployment evidence. Look for belt webbing damage, retractor lock issues, heat marks, trim distortion, or replacement components that do not match the rest of the interior. On many Suzuki platforms, a pretensioner activation record points to a real event history even when the belt circuit currently tests normal.
7. If you find clear crash or deployment evidence, stop circuit chasing and follow Suzuki post-collision SRS service procedures. That path typically includes replacing deployed components, replacing the SRS control module when required by OEM procedure, and performing the specified setup and verification steps. Clearing codes alone does not correct a stored activation record after a confirmed event.
8. If no crash history exists, continue with secondary cause checks. Verify stable battery condition, charging performance, and clean module power supply behavior. Review all related SRS codes together. An internal module memory fault, prior repair error, or incorrect module installation becomes more likely only after you rule out actual collision history.
9. Check whether any additional SRS DTCs return immediately after clearing. A hard fault that resets on key-on usually points to an active issue, while a stored crash record follows a different logic path. On manufacturer-specific SRS systems, code behavior varies by Suzuki platform, so verify the exact clear and replacement rules in service information.
10. Confirm the repair only after completing the full post-crash or electrical repair path. Clear codes, cycle the ignition as specified, rescan all SRS modules, and verify the warning lamp proves out normally. Finish with a complete restraint system check using the scan tool and service information procedure for the Suzuki Swift.

Professional tip: B1035 does not automatically condemn a pretensioner circuit. It tells you the module stored an activation record. On a Suzuki Swift, that usually means you need a disciplined post-crash inspection and OEM service procedure review. Replace parts only after you confirm whether the vehicle truly experienced a deployment event or carries a used module with stored crash data.

Possible Fixes

• Complete the OEM post-crash SRS repair procedure: If the vehicle was in a collision, replace all required deployed components and follow Suzuki post-collision verification steps.
• Replace the SRS control module when service information requires it: A stored activation record often requires module replacement after a confirmed pretensioner deployment event.
• Replace deployed or damaged seatbelt pretensioner assemblies: Install only the correct Suzuki parts after you confirm physical deployment or impact damage.
• Correct previous repair errors: Reconnect loose SRS connectors, repair damaged harness sections, and restore any missing or mismatched restraint components.
• Install the correct configured module: If a used or incorrect SRS module was fitted, install the proper unit and perform any required setup or registration.
• Repair power or ground faults to the SRS module: Fix high-resistance feeds or grounds if voltage-drop testing shows unstable module power.
• Address battery or charging system instability: Correct low-voltage conditions if they contributed to module memory or related SRS faults.

Can I Still Drive With B1035?

You may be able to move the Suzuki Swift, but you should not treat it as fully protected. B1035 does not act like a normal circuit code. It tells you the SRS control module stored a seatbelt pretensioner activation record. That usually means the module logged a crash event or deployment-related threshold. If the pretensioner fired, the restraint system has already seen a serious event. The SRS warning lamp often stays on, and the system may not protect occupants correctly in another collision. Drive only as needed for post-collision inspection or transport to a qualified repair facility. Do not attempt DIY SRS repairs, and do not handle pretensioner connectors until you depower the system and follow Suzuki service procedures.

How Serious Is This Code?

This code is serious because it affects the body restraint system, not engine performance. In the rare case of a false record, B1035 may seem like an inconvenience because the car can still run and drive. Even then, the SRS system must be treated as potentially compromised. If the Swift was in a collision, this code points to a post-crash condition that requires full SRS inspection and likely module service before normal use. Diagnosis needs SRS-certified equipment, proper depowering steps, and technician training. Do not probe squib or pretensioner circuits with standard test leads. The correct process starts with crash verification, event data review, and Suzuki post-collision service procedures, not random parts replacement or repeated code clearing.

Common Misdiagnoses

Technicians often misread B1035 as a simple pretensioner wiring fault and start checking resistance at the belt hardware first. That wastes time and creates risk. On Suzuki vehicles, the code description points to an activation record, so the first question is whether the Swift was in a crash or had prior SRS repairs. Another common mistake is clearing the code and returning the vehicle without completing post-crash inspection steps. Some shops also replace a seatbelt assembly without checking SRS event memory, related deployment codes, collision evidence, or module replacement requirements. You avoid wasted spending by confirming crash history, inspecting for deployed or replaced restraint parts, reading SRS data with an OEM-capable scan tool, and following Suzuki post-collision procedures before touching components.

Most Likely Fix

If the vehicle was in a collision, the most common repair path follows Suzuki post-crash SRS service procedures. That typically includes replacing any deployed pretensioner-related components, performing a complete restraint system inspection, and replacing or servicing the SRS control module if the stored activation record requires it on that platform. After repairs, the system needs code clearing, scan-tool verification, and a full warning-lamp check. If no crash history exists, investigate secondary causes such as prior improper repairs, used module installation, connector damage from interior work, or power and ground issues that affected SRS memory integrity. Confirm the repair by verifying that B1035 does not reset during the module’s self-check and under the vehicle’s specific enable conditions listed in Suzuki service information.

Repair Costs

SRS/airbag repair costs vary significantly by component. Diagnosis must be performed by a qualified technician with SRS-capable equipment. Do not attempt airbag system repairs without proper training and safety procedures.