7 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996TT Bore Scouring
Leading reported evidence
Check though lengthy process
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.
Performed · outcome unconfirmed
But can be checked, though lengthy process on a 996TT.
Leading evidence: 'Check though lengthy process' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check though lengthy process' (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
Not a common issue but worth checking with boroscope.
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 · Original poster
I had the car running the other day, it had a lot of smoke on start up then settled down once warm but I did note that when it was iddling there was smoke coming out of the passenger side exhaust.
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 · Original poster
Have had a compression and leak down test completed which didn't show anything of interest.
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
I haven't heard of bore scoring but bore ovaling on the 996, but you said the test numbers showed nothing wrong.
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 · Original poster
I had the car running the other day, it had a lot of smoke on start up then settled down once warm but I did note that when it was iddling there was smoke coming out of the passenger side exhaust.
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.
7 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Pelican Parts: 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: 20261026T081417Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi All
Can anyone enlighten me to the likelihood of bore scouring in 996TTs. I have a 2001 996TT which used about 1 litre of oil in 1 day while covering 500kms. I took it to my regular mechanic who consulted with a specialist independent Porsche garage. Thet said that from what was described it is likely to be bore scouring and I would need to get the engine rebuilt. They said it is a common problem and that they currently had 2 others they were working on with the same issue.
I was aware of this being an issue for the 996 Carreras but hadn't heard of it being a common issue for the Mezger engines of the turbos. Interested in your feedback.
Thanks.
Thanks Jeff, sorry been off line for a number of reasons. Have had a compression and leak down test completed which didn't show anything of interest. I had the car running the other day, it had a lot of smoke on start up then settled down once warm but I did note that when it was iddling there was smoke coming out of the passenger side exhaust.
In the middle of moving house at the moment so once settled will put the boroscope to work.
I haven't heard of bore scoring but bore ovaling on the 996, but you said the test numbers showed nothing wrong.
Smoke on start up and oil consumption could be valve guides in the past with older models, strange symptoms you have with normal leakdown and compression maybe the car has been sitting needs a good blow out of carbon causing issues in pistons and valves
