15 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHHorrible noise and misfire
Leading reported evidence
Inspect by a garage
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
Either way it needs to be inspected by a garage before using any more ...
Leading evidence: 'Inspect by a garage' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check of the cams' (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
I'm in the Midlands and these are a couple of indy's I've used before:
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
Basically a timing check of the cams then move on .
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
A mis-fire and then rough running sounds like the timing chain has slipped, so hopefully just a broken cam chain tensioner and not bore score!
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 have a longer video of it running taken from under the engine which highlights the 'tapping' if that would give any more pointers.
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: 20261026T163944Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Had a nasty noise develop today on my way home which sounded like a metallic tapping noise and a heavy misfire. Noise is on bank 2 and the car wouldn't idle when I pulled over. Sounded a bit like a stuck/collapsed lifter but I need it looked over to see what the damage is.
Any recommendations around Staffordshire?
Before you take the car anywhere I'd advise ringing up a respected Indy and describing the symptoms to get an idea what it could be. I don't know any in Staffs as my guy is in West Yorkshire and can take engines apart in his sleep.
When Bank2 is mentioned it takes you down the Borescore path and hopefully it's not that.
Do some reading and look for:
1) A rythmic ticking noise that sounds similar to that of a hydraulic lifter.
2) One exhaust pipe has more soot than the other.
3) Increased oil consumption.
4) Extremely black engine oil.
There are other symptoms, but these you can diagnose without taking the engine apart, and whilst I'm not an expert the misfire is throwing me as I didn't think this was an indciator in the early stages? What's the state of the plugs in Bank2?
I'm in the Midlands and these are a couple of indy's I've used before:
https://www.cmsporsche.co.uk/
- Telford
https://ramusporscha.co.uk/
- West Brom
Not exactly on your doorstep though.
A mis-fire and then rough running sounds like the timing chain has slipped, so hopefully just a broken cam chain tensioner and not bore score!
I've not used Hartech myself, but that is where I would be going. Best of luck! :thumb:
If you email your video to here i'll see if i can post it for you ..
[email removed]
Bore score when at its worst will cause a deep knocking noise .. it takes a while to develop into that though so a sudden noise won't be this .
Video link ..
https://youtu.be/iQ30YZqLi5c
Don't run the car anymore .. IMS / Tensioner failure is my best guess .. it's not as bad as normal when these fail as they don't run or do make horrendous noises so hopefully i'm wrong and it may be a tensioner failure .
A tappet failure whilst noisy won't end like that as that's more chain .
Either way it needs to be inspected by a garage before using any more ... that's my main point .
Basically a timing check of the cams then move on .
Sorry .
Thanks for that deMort.
I'll ring a couple of the more local guys to see if they will look at it and then go from there. I have a longer video of it running taken from under the engine which highlights the 'tapping' if that would give any more pointers.
Variocam pad failure (and / or chain guides) could well be the cause of the issue, this causes the timing chain to slip. If you're interested take a look at this video from 9.25 onward
