21 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHOne of these things is not like the other
Leading reported evidence
Clean before locking
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
That piston looks too clean, like it has been steam cleaned before locking.
Leading evidence: 'Clean before locking' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'detonation played a role in this one' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check cracks if the motor is apart you should listen' (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
I was really careful when I installed the heads on this rebuild.
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
BUT based on lots of signs I see, I'd suspect detonation played a role in this one.
Check cracks if the motor is apart you should listen
Suggestion or failed attempt
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 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 guess when they tell you to get your cases checked for cracks if the motor is apart you should listen.
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 piston head in that failed cylinder looks really clean compared to the others.
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.
21 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: 20261026T103553Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
[Image-only post; no author-written text. Original image references:]
https://cimg6.ibsrv.net/gimg/rennlist.com-vbulletin/400x400/partout_a2ef82f8a80ea021fa747bd2b41c4347894c8855.jpg
Definitely a rod failure , due to spun bearing? Is the big end of the rod turned blue? If the big end is blue, it failed due to lack of lubrication, if it is NOT blue , it failed due to stress and bolt failure.
The piston head in that failed cylinder looks really clean compared to the others. Maybe it had some water intrusion, got steam cleaned and lead to complete failure? I see cracked cylinder walls.
We haven't seen the rod, so no one knows...
BUT based on lots of signs I see, I'd suspect detonation played a role in this one. I've seen pistons explode due to knock sensors that failed, coupled to cheap gas/ bad gas.
One of the forum members who attended my class last year built a Boxster engine and left old gas (1.5 years old) in the tank. It exploded a piston in less than 100 miles.
I read the plugs, and every cylinder was detonating. I first saw this failure in 2008.
Thanks to all. I was really careful when I installed the heads on this rebuild. I suspect there was some coolant seepage. I had just gotten to about 1000 miles, the thing was running like a top. I took a 1 hour drive. Oil pressure was fantastic, coolant temp was perfect, no codes, just driving it and having fun.
Then in an instant it locked up. It must have hydro locked and somehow the piston got caught in the bore and the whole wrist pin pulled out. The rod is bent. The big end bearing feels good. I'll be splitting the cases to have a better look.
I didn't see any evidence of detonation on the plugs. I'll check again.
I guess when they tell you to get your cases checked for cracks if the motor is apart you should listen. But I think it cracked when the coolant rushed in and the rising piston made it all explode.
This is a source reference. Confirm exact model applicability in the original material.
