Geo OBD-II codes are diagnostic trouble codes stored by the vehicle’s onboard computer to identify emissions, powertrain, and chassis faults. These include both generic standardized codes and manufacturer-specific identifiers unique to General Motors applications.
Because these codes indicate detected conditions rather than confirmed component failures, exact application verification is required. Proper diagnosis depends on retrieving the specific code and following the manufacturer’s diagnostic workflow before replacing parts.
Quick Navigation
Key Takeaways
- Geo vehicles use both generic OBD-II (P0xxx) and manufacturer-specific (P1xxx) diagnostic trouble codes.
- Connecting a compatible scan tool to the OBD-II port retrieves stored codes and freeze-frame data for accurate diagnosis.
- Manufacturer-specific codes often relate to unique General Motors systems like specific EVAP monitors or ignition controls.
- Proper diagnosis requires verifying the exact code definition for your specific Geo model and engine before replacing components.
Geo OBD-II Code Description and Implications
Geo fault codes encompass both standardized generic codes and manufacturer-specific identifiers. Generic codes cover universal systems like fuel metering, ignition, and emissions monitors.
Manufacturer-specific codes address systems unique to General Motors platforms, which produced Geo vehicles. These include specific EVAP system monitors, ignition control circuits, and immobilizer systems. The Engine Control Module (ECM) stores these codes when a parameter falls outside its expected range.
| Code | Description |
|---|---|
| P1106 | MAP/BARO Circuit Intermittent |
| P1111 | IAT Sensor Circuit Intermittent |
| P1113 | IAT Sensor Circuit High Input |
| P1133 | HO2S Insufficient Switching Bank 1 Sensor 1 |
| P1336 | Crankshaft Position System Variation Not Learned |
| P1351 | Ignition Coil A Primary Circuit Malfunction |
| P1404 | EGR Valve Closed Position Performance |
| P1441 | EVAP System Flow During Non-Purge |
| P1450 | Unable to Bleed Up Fuel Tank Vacuum |
| P1500 | Vehicle Speed Sensor Intermittent |
| P1600 | Loss of KAM Power |
| P1602 | Immobilizer Communication Error |
| P1626 | Theft Deterrent Fuel Enable Signal Not Received |
| P1635 | 5 Volt Reference Circuit Malfunction |
Common Causes of Geo OBD-II Codes
Diagnostic trouble codes in Geo vehicles stem from various electrical, mechanical, and environmental factors.
- Wiring issues, including chafed harnesses, corroded connectors, or poor grounds in the engine bay or chassis networks.
- Failing sensors, such as mass airflow sensors, oxygen sensors, or camshaft position sensors.
- Mechanical faults, including vacuum leaks, EGR valve blockages, or internal engine wear.
- Emissions system faults, such as a loose fuel cap, failing EVAP purge valves, or catalytic converter efficiency issues.
Symptoms Associated With Geo OBD-II Codes
Symptoms vary widely depending on the specific system affected and the severity of the detected condition.
- Illuminated Check Engine Light or Service Engine Soon light on the instrument cluster.
- Reduced engine performance, hesitation, or rough idling due to fuel or ignition system faults.
- Transmission shifting irregularities if the fault involves speed sensors or solenoid circuits.
- Failure to pass emissions inspections due to pending or confirmed readiness monitor faults.
Diagnosing Geo OBD-II Trouble Codes
Diagnosing Geo codes requires a scan tool capable of reading both generic and manufacturer-specific P1xxx definitions.
First, retrieve all stored codes and freeze-frame data to understand the exact conditions when the fault occurred.
Verify the specific code definition for your exact Geo model, year, and engine, as P1xxx codes vary between General Motors platforms.
Perform targeted electrical and mechanical tests based on the manufacturer service information rather than relying on generic code descriptions.
Repairing Geo OBD-II Issues
Repairs must follow confirmed diagnostic testing to address the root cause of the fault.
If wiring damage or connector corrosion is found, repair the harness and ensure proper environmental sealing.
If a sensor or actuator fails manufacturer testing, replace it with a component meeting the exact vehicle specification.
After repairs, clear the codes and perform the required drive cycles to verify that the specific monitor completes successfully.
Cost Considerations for Geo OBD-II Repairs
Cost depends on diagnostic time, component accessibility, required parts, programming requirements, and labor.
Simple fixes like replacing a fuel cap or a basic sensor are straightforward, while diagnosing intermittent network faults or replacing integrated control modules requires specialized equipment and higher labor investment.
Prevention Strategies for Future Occurrences
Inspecting exposed wiring harnesses and ensuring electrical connectors remain clean and dry can help prevent intermittent circuit faults.
Following the manufacturer’s recommended maintenance schedule for oil changes and fluid services helps prevent mechanical faults that trigger emissions or ignition codes.
Troubleshooting Tips and Best Practices
Do not assume a generic code description perfectly applies to a Geo manufacturer-specific P1xxx code. Always verify the exact factory definition.
Use a high-quality scan tool that supports General Motors-specific protocols to access advanced modules like the ABS, airbag, and body control systems.
Check for technical service bulletins related to software updates or revised components for your specific vehicle, as older models may have known calibration updates.
More OBD-II Codes
| P1050 | P1062 | P1083 | P1084 |
| P1086 | P1088 | P1111 | P1112 |
| P1114 | P1115 | P1116 | P1117 |
| P1118 | P1119 | P1120 | P1121 |
| P1122 | P1123 | P1124 | P1125 |
| P1126 | P1127 | P1128 | P1129 |
Frequently Asked Questions
Are Geo OBD-II codes different from other brands?
Geo uses standard generic P0xxx codes that are universal across all brands. However, it also uses manufacturer-specific P1xxx codes that are unique to General Motors platforms.
Can a generic scanner read Geo specific codes?
Basic generic scanners will read universal P0xxx codes. To read and interpret manufacturer-specific P1xxx codes and access advanced modules, an advanced scan tool with GM software is required.
Will disconnecting the battery clear Geo codes?
Disconnecting the battery may temporarily clear some codes, but it does not repair the underlying fault. It also resets readiness monitors, which can cause the vehicle to fail an emissions inspection.
Do all Geo codes illuminate the Check Engine Light?
No. While powertrain and emissions faults typically illuminate the Check Engine Light, codes related to the chassis, body, or advanced systems may trigger different warning lamps or cluster messages.
Is it safe to drive with a Geo OBD-II code?
Driving safety depends on the specific code and symptoms. If the vehicle experiences severe misfires, stalling, or a flashing warning light, driving is not recommended until the issue is diagnosed.
What Should You Do About Geo OBD-II Codes?
Confirm the exact factory definition for any stored codes based on your specific Geo model, year, and engine configuration. Because General Motors utilizes both generic and manufacturer-specific identifiers, following the applicable diagnostic procedure is essential.
Inspect the relevant systems and components for confirmed faults. Repair or replace the confirmed failed components, then retest the system and complete the necessary drive cycles to verify the repair.
