Chevrolet P1133 Code: HO2S Insufficient Switching (Bank 1 Sensor 1)
The front oxygen sensor on bank 1 isn't flipping between rich and lean often enough during GM's switch test.
At a glance
Severity: Low
- Meaning
- HO2S Insufficient Switching (Bank 1 Sensor 1)
- System
- Fuel & Air Metering · Powertrain
- Safe to drive?
- Yes, short term
- Typical repair cost
- $40–$1,400
- DIY difficulty
- Easy
GM's PCM runs a switch-count test on the upstream oxygen sensor once the engine is warm and in closed loop at a steady cruise. Over a fixed window of roughly 100 seconds it counts how many times the sensor signal crosses from below about 300 mV to above 600 mV and back; if the count stays under a calibrated minimum, P1133 sets for bank 1 sensor 1. A healthy zirconia sensor on a GM engine flips several times per second, so a low count usually means an aged, contaminated or cold sensor, not a mixture problem. You'll find this code mainly on 1990s and early-2000s Chevrolet engines, including four-cylinders, where bank 1 is the only bank, and V6/V8 trucks, where bank 1 is the side with cylinder 1 (driver side on small-block and Vortec engines).
Can I keep driving? Fine to drive in the meantime; the engine normally runs the same. Expect somewhat worse fuel economy, and don't leave it for months, because a lazy front sensor can let the mixture drift and overheat the catalytic converter.
How to read P1133
- P Powertrain
- 1 Manufacturer-specific
- 1 Fuel & air metering
- 33 Specific fault
Symptoms
- Check engine light on, often with no drivability change
- Fuel economy a few mpg worse than usual
- Scan data shows the front O2 voltage wandering slowly or sitting mid-range instead of flickering
- Sulfur or rich exhaust smell on higher-mileage engines
- P1134 or P0135 stored alongside it
Possible causes
Ranked by how often each cause is behind this code (editorial estimate).
- Worn-out upstream O2 sensor (high mileage, original sensor)
- Sensor poisoned by coolant, oil burning or silicone sealer (common after intake gasket leaks on GM V6 and V8 engines)
- O2 heater not working, so the sensor runs cold at idle and light load
- Exhaust leak ahead of the sensor at the manifold, flange or donut gasket
- Damaged signal or ground wire, corroded connector or pigtail melted on the exhaust
- Fuel control problem such as a leaking injector or high fuel pressure holding the mixture rich
Diagnosis step by step
Check for companion codes
Read all stored codes with a GM-capable scan tool. A heater code (P0135) or circuit codes (P0131/P0132) point to wiring or heater faults and should be fixed first; P1133 on its own points to the sensor itself or its environment.
Tools: OBD-II scanner
Watch the sensor at 2,000 rpm
Warm the engine fully, hold it at about 2,000 rpm and graph the bank 1 sensor 1 voltage. A good sensor should swing between roughly 100–200 mV and 700–900 mV several times per second; a slow, lazy wave or one that barely moves confirms insufficient switching.
Tools: OBD-II scanner
Force rich and lean
Snap the throttle or add a little propane at the intake to force the mixture rich, then create a small vacuum leak to force it lean. The voltage should jump above 800 mV and drop below 200 mV within a fraction of a second; if it can't reach those extremes, the sensor is worn out.
Tools: OBD-II scanner, Vacuum gauge
Test the heater
Unplug the sensor and measure heater resistance across the two same-colored heater wires; most GM heated sensors read a few ohms (roughly 3–10 Ω) at room temperature. With the key on, confirm 12 V on the heater feed at the harness side.
Tools: Multimeter
Inspect exhaust and wiring
With the engine cold, look for black soot trails at the manifold, the flange bolts and the pipe joint ahead of the sensor, and listen for ticking at cold start. Follow the O2 harness for melted insulation or chafing against the exhaust or transmission.
Tools: Flashlight
Replace and verify
If the tests point to the sensor, install a new bank 1 sensor 1 with anti-seize on the threads (most new sensors come pre-coated), clear the code and drive at steady highway speed so the switch test runs again.
Tools: O2 sensor socket, Torque wrench
Where the parts are
- 1Upstream O2 sensor
- 2Catalytic converter
- 3Downstream O2 sensor
- 4Diesel particulate filter
- 5Turbocharger
Repair options & costs
| Repair | DIY? | Estimated cost |
|---|---|---|
| Replace upstream O2 sensor bank 1 (DIY) | Yes | $40–$120 |
| Replace upstream O2 sensor bank 1 (shop) | No | $150–$320 |
| Repair O2 sensor wiring or connector | No | $80–$220 |
| Repair exhaust leak ahead of the sensor | No | $120–$450 |
| Fix coolant/oil consumption source that poisoned the sensor | No | $400–$1,400 |
Rough US estimates for parts and labor; shop rates vary by region. Not a quote.
Emissions / smog test impact
Will fail
With P1133 stored the check engine light is on, so the vehicle fails a US OBD emissions test; after the repair the O2 sensor monitor must run to completion before retesting.
Frequently asked questions
How is P1133 different from the generic P0133?
P1133 is GM's switch-count test: it simply counts rich-lean crossings over a fixed time. P0133 measures how quickly the sensor responds. Both usually lead to the same worn sensor, but P1133 was GM's own version used on many older Chevrolets.
Which sensor is bank 1 sensor 1 on my Chevy?
It's the oxygen sensor ahead of the catalytic converter on the side of the engine with cylinder 1. On a Chevy V6 or V8 truck that's the driver side; on a four-cylinder there's only one front sensor, near the exhaust manifold.
Can a new sensor set P1133 again right away?
Yes, if the cause is outside the sensor. Coolant or oil burning will poison a new sensor quickly, and an exhaust leak or a dead heater circuit will keep the count low. Rule those out before blaming the part.
Can I just clean the O2 sensor?
Not effectively. The sensing element is porous ceramic, and contamination sits inside it. Cleaners and torching don't restore switching speed; replacement is the practical fix.
Sources
- Manufacturer public service information (cross-checked)
- Methodology: How We Build Code Pages · Data Sources We Use · Editorial Policy