8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHImpending doom or neurotic fool...
Reported or suspected cause
variocam failure
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
I had the "lumpy idle" issue which turned out to be a variocam failure.
Leading evidence: 'variocam failure' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'variocam failure' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check however, i am not sure if there is much' (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 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
If you are worried get it checked, however, I am not sure if there is much that can be done.
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
The easiest way to check for problems is to get your car hooked up to a diagnostic computer.
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.
8 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
And occassionally when I pull up to traffic lights or stop rev counter will dip below 900rpms for a split second, go back to normal, dip again then settle at normal between 900 and 1000.
Having read this months article about early 996 engines in T911 should I be concerned by the following.
Page 99
Cracked Liners: " You may notice a tiny amount of coolant loss"
"Lumpy Idle" = Varioram Hydraulic mechanism failure
I've just had to top up my coolant!
And occassionally when I pull up to traffic lights or stop rev counter will dip below 900rpms for a split second, go back to normal, dip again then settle at normal between 900 and 1000.
Is there an easy and economical way to check this out or do I just wait for the big bang? Or am I being a neurotic fool worrying because I read something in a magazine, just like Daily Mail readers worrying because they read it in the paper and therefore it's going to happen!