U0073 Bus-Off Code: Meaning, Related Codes, and Safe Diagnostic Steps
A U0073 code on a scan report points to a communication problem, not a confirmed failed part. Its standard description is control module communication bus A off. That means a controller recorded that communication on one vehicle network had shut down. Owners can avoid guesswork and unnecessary parts by learning what a bus-off state is, how related codes from U0074 through U0087 differ, which symptoms to note, and how testing proceeds.
What U0073 Means and What a Bus-Off State Tells You
The standard descriptor for U0073 reads control module communication bus A off. Manufacturers can add suffixes, failure-type characters, or their own wording, and any of these can change how the code should be read. Before interpreting a U0073 code, confirm the exact definition for the vehicle's year, make, model, and powertrain in its service information. Also note every character after the base code. The bus-off label describes a specific CAN bus behavior: a controller counted so many communication errors that it stopped taking part in that network.
CAN controllers keep running counts of their own transmit and receive errors. When those errors pass a defined threshold, the controller enters a bus-off state and withdraws from the network so that a faulty node cannot keep disrupting other traffic. It may try to rejoin later. The A designation names a network in the manufacturer's network topology. It does not identify a particular wire, connector location, or failed module. U0073 records a communication condition, and the code alone cannot show whether wiring, power, or a module caused it.
Interpreting Related Codes From U0074 Through U0087
Owners researching a U0073 code often see nearby codes such as U0074, U0076, or U0077 on the same report. Searches about other vehicles may turn up U0079, U0080, U0085, or U0087. It is tempting to read this range as a neat series of bus-off codes, one per network letter, but that assumption is unsafe. Codes in this block can describe different network fault conditions, and manufacturers may use their own wording. Confirm each code against the vehicle's year, make, model, powertrain, and service information instead of guessing from neighboring numbers.
Three details decide which diagnostic information applies: the full code with any suffix, the module that reported it, and the network name used in that manufacturer's wiring diagrams. A U0076 code stored by one brand's body controller may lead to a different circuit than the same number stored by another brand's engine module. If a definition for a code like U0081, U0083, or U0086 cannot be verified, record it as unresolved rather than guessing. A wrong definition can send testing toward the wrong network entirely.
Symptoms to Record and When to Stop Driving
Symptoms vary because they depend on which modules share the affected network. Some drivers see several warning lights at once, a blank instrument cluster, an inactive radio or climate display, or missing driver-assistance features. Others notice starting trouble, delayed or harsh shifting, or reduced power. Many vehicles show only one or two of these signs, and some show none. A stored U0077 code or similar communication fault can also remain after an intermittent event. The vehicle may seem normal today while that history still matters.
Useful notes include whether problems appear during cranking, after rain or a car wash, over bumps, in extreme temperatures, or soon after battery or electrical work. These patterns help a technician reproduce an intermittent communication fault, although timing alone does not prove the cause. If the vehicle stalls, loses essential functions, or shows steering or braking problems, stop in a safe place and arrange assistance. Judge driving safety by how the vehicle is actually behaving, never by the code number alone.
Electrical and Network Conditions That Can Trigger the Fault
Network modules need steady power and clean grounds to send accurate messages. Low system voltage can push controllers into error states, whether it comes from a weak battery, a charging problem, or heavy draw during cranking. An interrupted power feed or a poor ground can make a module drop off the network completely. A supply problem can look like a wiring or module fault. For that reason, battery condition, charging output, and module power and ground circuits all need proper testing before any component is blamed.
Physical network wiring is another possible cause. Chafed or pinched twisted-pair wires, loose terminals, connector corrosion, and moisture intrusion can all corrupt messages, and none should be treated as more likely without evidence. A malfunctioning module or transceiver can disturb the whole bus. A module reported as unreachable, however, may simply have lost power or its network connection. Recent collision repair, battery replacement, or aftermarket equipment such as remote starters, alarms, or trailer wiring is relevant history. Its presence alone does not make it responsible.
Safe Observations and Scan Information to Gather First
Before clearing codes or disconnecting the battery, save the complete scan report. It should include each code's status, the modules that reported it, and any freeze-frame or event data. Clearing codes first can erase the clues that separate a current fault from a past one. Scan-tool coverage also matters. A basic reader might show U0082 or U0084 without naming the module that set it, and it may not reach body, chassis, or gateway modules at all. A full module scan gives a much clearer picture of network communication.
Owner inspection should be limited to what can be seen with the vehicle parked safely and switched off. Look for obvious wiring damage, signs of water in the footwells or trunk, and loose or corroded battery connections. Do not unplug connectors, probe terminals, or pull on wiring harnesses. Write down any recent jump-starts, dead-battery episodes, water exposure, and repairs, along with how often the intermittent behavior happens. This record helps a technician reproduce the condition safely.
Professional Testing and Confirmation After Repair
A technician starts with the vehicle's network diagram and a complete module scan. Together these show which modules share bus A, which ones respond, and how multiple communication codes relate. A U0073 alongside several lost-communication codes tends to suggest a network-level problem, while a single silent module suggests a narrower search. Professional battery, charging, module power, and ground testing then checks whether a supply issue explains the pattern. Network signal evaluation and manufacturer-directed isolation of circuits or modules narrow the fault further.
A module should be replaced only when testing shows it is at fault, not just because it appears in a code description. Many replacement modules need vehicle-specific programming or configuration, so the repair plan must allow for that. Confirming the repair means checking that all expected modules communicate again, then running a follow-up scan for new or returning codes. It also means watching whether the original symptoms come back under the conditions recorded earlier. If an intermittent fault stays away across those conditions, that is much stronger evidence the repair has lasted.