10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHSuspension clonk - running out of ideas...
Leading reported evidence
Disconnect front drop links
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
Make a test drive with disconnected front drop links.
Leading evidence: 'Disconnect front drop links' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Disconnect front drop links' (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
Inspected the drop links, they felt fine and no play
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 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 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
It started appear when I installed coil overs (JIC ZMS ).
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.
10 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: 20261026T130754Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I have a clonk in the right front that I can't figure out what it is. It started appear when I installed coil overs (JIC ZMS ). The coilovers has monoball camber plates, so not using stock shock mounts.
It is most noticeable going over dips/potholes, so sharp edges. Doesn't matter if I turn or not. The faster the more violent the clonk is.
Have done the following in:
1. Replaced lower control arms (the one with the ball joint)
2. Replaced lower control arm link (tuning fork)
3. Tighten the top nut of the coil overs and greased everything.
4. Inspected the strut mount camber plates
5. Inspected the drop links, they felt fine and no play
6. Inspected tie rods, felt fine and no play.
7. Inpsected the swaybar bushings (might as well replace these, cheap and easy).
8. Fastened the spare tire bolt.
I can't think of any more suspension components to replace/inspect.
Any ideas?
Make a test drive with disconnected front drop links. Zip tie them out of the way...
If that doesn't solve the issue, swap the left and right struts as it might be the shock.
These are the 2 that I tracked down:
https://rennlist.com/forums/996-foru...-arms-wow.html
https://rennlist.com/forums/996-foru...ght-turns.html
Sounds like you've already replaced things; just make sure everything is torqued correctly. "Pretty tight" is not tight enough on some of the control arm fasteners and will allow things to shift and clunk.
No, in the end I accepted it as going to fast over potholes with stiff suspension.
My race car Miata does a similar thing but the clonk is more of a bang (maybe because I have a helmet and no muffler).
Someone said that this is what monoball (
spherical bearings
) top mounts do and the price you have to pay for the increased performance, however I am not a suspension expert so can't really comment on that.
I apologize if this was not clear but it's mentioned in the AD.
Edit:
Just remembered someone also said that the bearing might be a little worn and that causes the clonk. But again, I don't know if that is true.
I can confirm that a worn monoball will knock. I have them on my fronts and although I couldn't really "feel" any play with the bearing in hand, when I replaced them with new bearings, the noise was gone completely.
How did you replace them? Pressed them out?
I removed the shocks to sell them (restoring the car to stock). The handling was amazing with these.
thanks
This is a source reference. Confirm exact model applicability in the original material.