11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCheck Engine Light
Reported or suspected cause
o2 sensor and a bad exhaust manifold gasket
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that report identifying a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Reported cause · Original poster
Mine was caused by an o2 sensor and a bad exhaust manifold gasket.
Leading evidence: 'o2 sensor and a bad exhaust manifold gasket' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'o2 sensor and a bad exhaust manifold gasket' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check brake action and watch your temperature' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
It will tell you what the problem is (and reset the light) and you can then decide if it is bad enough to call a tow truck.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
A call to the dealer before driving is probably a good idea.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
its a tough call but but if you haven't had any previous problems then most likely the techs just knocked a wire loose somewhere, like on an 02 sensor or something.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Check your vital fluids, look for leaks, listen for strange engine noises, check your brake action and watch your temperature...
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause
its a tough call but but if you haven't had any previous problems then most likely the techs just knocked a wire loose somewhere, like on an 02 sensor or something.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
11 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Ok....just got my first CEL on my 996 C4....It came a day after the 15K service on my new engine, so I am suspecting its something they did at the dealer....Its still under warranty so I'll take it back in the morning and see whats going on. The car drives perfectly, no power loss, sounds fine, all gauges look good. Is there a problem with driving it to the dealer? Any ideas?
Just my own opinion, there are a lot more knowledgeable people on here...
If the car is still under warranty the dealer can tell you how to handle it, no problem. If it's out of warranty you might want to invest $100-200 for one of the many diag/code capture tools available. It will tell you what the problem is (and reset the light) and you can then decide if it is bad enough to call a tow truck.
Check your vital fluids, look for leaks, listen for strange engine noises, check your brake action and watch your temperature... its a tough call but but if you haven't had any previous problems then most likely the techs just knocked a wire loose somewhere, like on an 02 sensor or something. Be safe.
Newport,
The owner's manual for my '04 states that it is "usually driveable and will not require towing" but to see the dealer as soon as possible. It also says that if the light is flashing, "severe catalytic converter damage and power loss will soon occur."
FWIW, when I experienced a CEL on my Audi S4, the dealer told me it would be OK to drive for a day or two as long as the light wasn't flashing.
A call to the dealer before driving is probably a good idea.
Good luck!
Maybe it's a coincidence that CEL came on after service. It may be the MAF sensor knocked loose from an air filter change/inspection. It's no problem driving it to the dealer.
It can be as simple as the gas cap is loose or as complicated as the EVAP canister valve is faulty -- with the MAF/O2 sensors and vacuum leaks in between. My car has had 2 CEL events. 1st was a loose bracket on the gas filling tube breaking the vacuum seal. And the second being the EVAP canister valve -- this one is still being worked on at the dealer since last week. They have to drop the gas tank to replace this part, which means dropping the front suspension member, and requiring a front wheel alignment after everything is done. Part is on order and should arrive this Monday (I hope).
Sorry for venting but it has been painful not being able to drive my car for 10 days now -- and stuck with a boring Toyota Camry rental for now... So consider yourself lucky if it is not this EVAP thingy that's gone wrong... And you should be OK driving to dealer as long as it is not flashing.
My bet is that it's an MAF fault. I had those frequently in my old Porsche and it was such a hassle. The CEL became such an annoyance. Of course, it could also be an outgas/exhaust filter sensor that checks for higher emissions as per environmental concerns. From my experience, that last error has absolutely no impact on driveability and just tells the mechanic that you are polluting a bit more than you should. Mechanics often suggest a $400 O2 sensor/filter replacement. Such a joke.
As long as it's not flashing you're fine. If it is ever flashing, do not pass go do not collect $200 do not do ANYTHING. Have the car towed to your dealer.
YES!... my car is BACK!.... Life is good!... CEL is gone!... Back to business and enjoying what a P-car is all about... I'll be travelling through Big Sur later this week and that will make it all good!
Yeah, until warranty runs out. Then talk to me. It gets silly to keep repairing those things. Hopefully, Porsche resolved the issue on newer cars (mine's a 2000).
This is a source reference. Confirm exact model applicability in the original material.
