5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHC4 2000 996 misfire
Leading reported evidence
Install two years ago
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
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 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.
Leading evidence: 'Install two years ago' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'confined' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check any pending and active codes and the cam deviations' (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 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 · Original poster
this time i ran the car for a hour and a half (at tickover)while i changed a window lifter.
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 · Original poster
this time i ran the car for a hour and a half (at tickover)while i changed a window lifter.
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.
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
The misfire codes point to bank 2 so maybe the problem is confined to bank 2.
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.
5 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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T165639Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
hi
first post so...
i rarely use this car , a few weeks ago i decided to start it up and run it for a while to clear the cobwebs etc. it started but the noise was somthing else , it was misfiring and the exhaust sounded like it was blowing. there was also a disturbing poping noise coming from the engine .
i took it around the block and the issue cleared.
last weekend the same happened again . this time i ran the car for a hour and a half (at tickover)while i changed a window lifter.
the engine warmed up and it idled fine during this time, the engine would rev and it sounded normal.
i drove the car half a mile again to clear the cobwebs . the misfire redeveloped, i ended up rolling down my street as it was stalling continuously. i got on my drive to find smoke coming out of the left rear wheel arch it was stinking of either melting plastic or clutch.
( i didnt hammer the car)
i had a code reader to hand on these occasions it read misfire bank 4,5,6,
the engine was rebuilt by hartech 18 months ago
a new clutch was fitted two years ago.
any advice would be great
cheers
mike
While bad gas is a good possibility it would have to be really really bad.
My limited experience with bad gas is from a family member's car sitting 6 months with the same gas in the tank. The engine started and ran ok with no symptoms. The only thing I noticed was the engine felt a bit flat but I was not used to the car and assumed this was the way it was.
But I drove the car enough to run the fuel level down and added fresh fuel and the transformation of the engine afterwards with fresh fuel was remarkable.
So, I'm going with rodent damage. Partially because of the severity of the engine's behavior but also because of the smoking.
My advice would be to get the car to a qualified shop for a thorough inspection for any signs of rodent infestation.
The misfire codes point to bank 2 so maybe the problem is confined to bank 2. I would suggest using Durametric to check for any pending and active codes and the cam deviations.
Have you actually looked under/around the area where it was smoking? If smoke's coming from the car from anywhere other than the exhaust pipes, that's where I'd start.
Can you be a little more specific about when the car was previously started? Had it been sitting for 2 weeks, 2 months, or...
This is a source reference. Confirm exact model applicability in the original material.
