15 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
exhaust leak
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
It turned out to be an exhaust leak on a flexi pipe.
Leading evidence: 'exhaust leak' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'exhaust leak' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Inspect basically' (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 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
Turned out to be lambda sensors that were badly carbonated and a dirty throttle body and vacuum hoses.
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 performed work without a confirmed outcome
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.
Performed · outcome unconfirmed
Cam cover off , vario cam removed and inspected basically .
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
It could be lambda sensors, you have to change 2 at a time or all four worst case.
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
All cleaned up, two new lambda sensors and now running like a dream (with no check engine light!).
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.
15 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T074343Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
good afternoon all,
my 98 996 has the check engine light on. it drives fine, but the only symptom I can see is a slightly lumpy idle. I have it booked in for diagnostic but wondered if any of you guys may be able to give me a heads up?
cheers
chris
My 2003 C4S was just in at my local Indy last week with the exact same symptoms.
Turned out to be lambda sensors that were badly carbonated and a dirty throttle body and vacuum hoses.
All cleaned up, two new lambda sensors and now running like a dream (with no check engine light!).
Could be all sorts of things. A £15 OBD2 reader from Euro Car Parts will tell you what is wrong, even down to the correct cylinder, if it's not exhaust sensor related.
Maybe O2 sensors as above, but equally could be a plug failing, coil failing or even a coil pack connector slightly loose, as one was on mine, where the rubber sleeve was on back to front, not allowing the locking tab to lock.
:yeah:
With no fault code its pure guesswork im afraid .. a duff lambda sensor which the car has flagged up a fault code ( so knows it's an issue ) won't normally cause a running issue as it ignores this sensor .
Don't even think of throwing a couple of lambda sensors at the car until you get the fault code read out young man !
Please also be aware .. some lambda sensor fault codes mean the sensor is fine but there is a separate issue such as maf , air leak etc .
I got a CEL every so often and when I plugged my cheap OBD-II reading it was a Catalytic Converter Bank 1 efficiency below threshold. I cleared the code and it's not come back since. This was all around the same time my coils were damaged by a failed water pump which covered them in steaming hot coolant.
Like others have said, without the actual error codes then it's all guess work.
All.
I got an ODB2 reader and it gives 300 to 303, cylinder misfire.
I have cleared and idled the car on the drive (which is when the cel came on initially) and it hasnt re-appeared.
I'll drive it later, but any ideas about what threw the codes up when the car was just idling?
Cheers all!!
When did you last have the coils changed? Do you notice any spluttering at low revs? When my coils were on their way out idle was rough and it was a challenge to not stall the car in 1st unless I really pushed the revs over 3k!
The codes are general misfire and cylinders 1,2 and 3 misfiring ..
On a later car this would be the high lift solenoid but as yours is a 98 and does not have this i would say the vario cam unit might have very worn slippers or perhaps just isn't working .
Difficult to answer ..
I've seen the wiring on the solenoids burn out and the car runs ok .. ish and owners leave it like this ..
I've seen very worn slippers on the vario cam and again the cars were running ok ish ..
Best guess you should be fine and as variocam replacement is not cheap and worn slippers can only be proved on a strip down then you need to be prepared to spend a few bob on it .
Cam cover off , vario cam removed and inspected basically .
There is a test that can be done using a tester but even with Piwis testers i find it a bit hit and miss with proving an inop vario cam .
In short .. i would think so judgeing by what ive seen but as always .. caveat .. i can't say for certain .
caveat in this case ..
Before you make your final decision, you might want to consider the caveat in this agreement.
Please also bear in mind .. this is an educated guess from me .. to prove a garage needs to diagnose it .
Thanks so much for your time. The lumpy idle would suggest exactly what youve suggested, so i'll run it and see how we go. Of course i'll update.
Thanks again.
Just an update all. Once tjhe codes were cleared, car is now running great (still a slight lumpy idol, briefly until it settles). Engine light has stayed off.
Thanks again for your help.
This is a source reference. Confirm exact model applicability in the original material.