← Back to list

2006 Chevy Cobalt 2.2L Engine Power Loss with P0106, P0068, and P0101 Codes - Diagnosis Tips

Model: 2006 Chevy Cobalt Fault Code: P0068 Posted: 2016-01-01 19:59

I'm experiencing reduced engine power followed by complete engine shutdown on my 2006 Chevrolet Cobalt 2.2L. When I connect a code reader, it consistently shows trouble codes P0106, P0065, and sometimes P0101. I've already replaced the MAF sensor, MAP sensor, and throttle body (which includes the built-in sensor). Despite these replacements, the codes persist and the symptoms remain unchanged. I'm looking for reliable troubleshooting steps to resolve this issue. The problem is not isolated — it affects both performance and drivability. Can anyone provide insight into possible root causes or suggest a systematic diagnostic approach? Note: I understand that OBD-II codes do not always indicate a faulty sensor; they can also point to wiring, connector issues, or signal interference. A proper diagnosis likely requires live data monitoring from the engine control module (ECM) to assess real-time sensor inputs and cross-reference them with expected values.

Related fault codes

P0068P0101P0106

Comments (2)

Anonymous 2016-01-02 06:19

Without a scan tool that provides live data PIDs, your analysis is limited. A vacuum leak could be the underlying cause. OBD-II codes do not confirm sensor failure — they only indicate a detected issue. Possible causes include faulty wiring, damaged connectors, or signal degradation. You can manually test the circuit using a DC voltmeter by measuring voltage at the sensor terminals and comparing it to the PCM input signals.

Anonymous 2016-01-02 11:40

Modern engine control modules (ECMs) use built-in logic to evaluate multiple sensors and detect inconsistencies. The ECM may flag a code even if one sensor is functioning, based on mismatched data or signal timing. To properly diagnose this issue, you need a scan tool with live data streaming capability to view actual sensor readings in real time. Without this, troubleshooting becomes speculative. If I were you, I'd consider scheduling an ASE-certified diagnostic session at a professional shop specializing in electrical and electronic systems. Have you already invested significant money into repairs without resolving the issue? Also, check for low idle — it may be a symptom of underlying problems. Your current code reader might not read manufacturer-specific stored codes that could provide additional insight. I can't offer more specific guidance without live data access.