11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHIs this an RMS leak??
Leading reported evidence
Check over the next couple days of driving
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
as stated before, get the area clean, and check over the next couple days of driving...
Leading evidence: 'Check over the next couple days of driving' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check over the next couple days of driving' (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
you might wipe it clean ans see how much/how long to repeat before getting all worried...
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
Went out on a Poker Run yesterday with the local chapter and had a blast.
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.
11 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
Still not a drop since my afternoon drive and wipe down.
I apologize in advance for the cross thread...just trying to get a quick response
Went out on a Poker Run yesterday with the local chapter and had a blast. I jacked the car up today to take the wheels off for a good cleaning and wax and noticed an oil leak, then quickly turned to find a decent patch on the garage floor. Hadn't had any leak up until now. Does this look like an RMS?
yup (or IMS flange plate leak)
FWIW mine will drip a couple drops after a track day, then go the rest of the month clean and dry... I have just kept it wiped up and will change it when the time comes, it has been a year and I have not lost a total of more than 1/16 cup of oil.....not worth getting excited IMO.....
you might wipe it clean ans see how much/how long to repeat before getting all worried...
(yours looks worse than mine though... but still....)
Thanks for the response.
We drove a sprited 130 or so miles yesterday on the poker run. I slowly pulled over to put the top up in the evening and the front bottomed out on one of my front tie downs so it was a solid jolt...don't know if that could have been just enough to upset something. Seeing the leak today kinda ruined the afternoon though!
as stated before, get the area clean, and check over the next couple days of driving... if the leak comes back...maintain the oil level, prepare for some wrench time or to spend some time with your mechanic...bring food and drinks..
GL.
I think so too. It seems to have slowed down A LOT. I just went for a short drive and no drips at all when I got back. I jacked it up and wiped down the wet stuff, so we'll see if it starts again.
On a drive earlier this morning I let my son shift in the neighborhood and he went from 2nd to 5th instead of 3rd. I've heard you shouldn't "lug" the engine at low revs, maybe 5th gear at low revs "lugged" it enough to temporarily gap the RMS?
Just turned 35K miles and yes this is the first...I was really hoping to one of those people that never experienced either an RMS or IMS problem.
Still not a drop since my afternoon drive and wipe down. It looks like it has slowed/stopped. If that is possible.
