Silverado or Sierra No-Crank With a Code Avalanche? Load-Test Grounds G132 and G134
Many Codes? Check The Main Grounds
Preserve the full scan and battery state, then inspect G132 and G134 for looseness, breakage and routing damage. Measure voltage drop while the circuit is actually loaded; an unloaded continuity beep cannot prove a main ground will carry starter or module current. This is one of the few cases where a long, intimidating scan can become simpler when every complaint is placed on the same return path.
The useful tool category here is a loaded voltage-drop comparison on the exact ground path identified by current GM service information, but only after the safe test point and decision are clear. The AUTOOL BT210 is one practical route for that bounded step. BT210 can measure voltage and continuity on identified 9–30V vehicle circuits and support a loaded ground comparison; it cannot choose GM’s test points, supply a safe cranking load, prove every stored code came from the strap or replace inspection of orientation and movement damage.
The useful mental picture is not a dozen failed modules. It is starter current, charging current and multiple controllers all trying to return to the battery through a path that may be loose, broken or pulled by powertrain movement. The code avalanche records the consequences downstream; G132 and G134 are the shared question upstream.
Quick answer: Preserve the code avalanche and battery state, then inspect and load-test G132/G134 because unloaded continuity cannot prove a main ground carries current.

In this guide
- Freeze the code avalanche before charging or clearing
- Check battery state without blaming it yet
- Find both G132 and G134
- Inspect looseness, breakage and powertrain-movement damage
- Load the circuit before measuring voltage drop
- Repair orientation as well as contact
- Rescan modules in one pass
- Verify crank, auto-stop restart and the original accessory state
Freeze the code avalanche before charging or clearing
Before connecting a charger or clearing anything, save a complete module scan and photograph the cluster. Record whether the vehicle was a no-crank, a crank/no-start, a stall with no restart, an auto-stop that would not restart, or simply a discharged battery. Those phrases are not interchangeable. Also record transfer-case learn failures, steering or brake messages, radio resets and any recent engine, transmission or collision work. The original battery voltage and the order in which warnings appeared help distinguish a common supply/return event from several unrelated old codes.
Check battery state without blaming it yet
Check open-circuit voltage only after noting the as-found state, then assess the battery with a method appropriate to its type and state of charge. A weak battery can create communication codes and prevent cranking, but it can also be the victim of poor charging through a bad ground. Clean battery posts and a passing conductance result do not clear the rest of the return path. If the battery is frozen, leaking, swollen or unusually hot, stop. If it needs charging, preserve the pre-charge evidence so a restored state of charge is not mistaken for the root repair.
Find both G132 and G134
PIT5689M covers 2019–2024 Silverado and Sierra 1500 and 2020–2024 2500/3500 HD configurations, but current GM service information must identify the actual locations and routing. G132 is the engine-to-body ground connection at the right rear of the engine compartment on the path GM illustrates; G134 is the related strap connection that can be affected as the powertrain moves. Do not choose a bolt by proximity or internet photograph. Engine, body style and service history can change access and the safest meter points.
Inspect looseness, breakage and powertrain-movement damage
Look before loosening anything. A strap can be broken inside its insulation, partially pulled from a terminal, loose at a stud, trapped, twisted or routed so normal engine roll tugs it. Check witness marks, green corrosion, overheated eyelets and paint or contamination under a terminal. Move the harness only as current SI permits and watch both ends; an intermittent opening may appear only at a particular engine position. Photograph orientation before disassembly because restoring electrical contact while leaving the strap taut simply schedules the next failure.
Load the circuit before measuring voltage drop
Measure from the battery negative reference to the engine and body side while the problem circuit is carrying current. During a safe crank request, a compromised connection can show a meaningful voltage difference that disappears when the key is released. Use fused leads, secure them away from belts and fans, and never stand in a vehicle’s path. A continuity beep uses tiny current and may pass through a few remaining strands; starter and module loads cannot. Interpret the reading against current GM limits and the exact endpoints—not a universal social-media number.
| Test result | What it actually supports |
|---|---|
| Continuity passes with everything off | Only that a small test current found a path |
| Voltage drop rises during crank on one ground path | Resistance under real load; inspect that path |
| Drop is normal but battery voltage collapses | Battery/load or another connection remains open |
| Grounds repaired but one local code returns | Diagnose that circuit independently |
Repair orientation as well as contact
Repair the connection and its mechanical cause together. Follow GM’s fastener, surface-preparation and torque instructions; do not grind protected sheet metal or add an improvised strap without authorization. Route the repaired strap with the correct slack and bend, clear of exhaust heat, sharp edges and moving shafts. Replace damaged terminals or straps with the specified parts. A shiny contact face is not enough when a broken conductor, wrong orientation or inadequate strain relief remains between the two meter probes.
Rescan modules in one pass
After stable power is restored, run one full-vehicle scan rather than opening modules one at a time. Separate current codes from history created during the low-voltage event. Clear only after the original report is attached to the work order, cycle the vehicle as prescribed, then see which faults actually return. A remaining local code deserves its own test; the ground bulletin is not permission to erase every complaint. Conversely, a dozen modules returning together still points back to shared voltage and network conditions before a dozen parts.
Verify crank, auto-stop restart and the original accessory state
Verify the exact failure modes the owner reported: several normal cranks, charging voltage under relevant loads, an auto-stop restart if equipped and safe, transfer-case operation if that was involved, and the accessory state that preceded the event. Repeat the loaded drop test after the repair and record both values. Inspect the strap while the powertrain moves within the safe procedure. If the battery again discharges while parked, begin a sleep/current-draw diagnosis rather than stretching the ground explanation beyond the evidence.
The best handoff includes the as-found battery voltage, full pre-clear scan, exact no-crank description, loaded readings with endpoints and operating state, photographs of G132/G134 orientation, repair torque and the post-repair rescan. That compact record turns a frightening code list into a testable electrical story—and proves the truck starts because current has a sound way home.








Comments 0
Questions, fixes, and real-world diagnostic notes from readers.
Be the first to share a diagnostic result or ask a follow-up question.