14 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHHELP!! Misfire - CEL
Leading reported evidence
Check oil it was getting a little
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 · Original poster
Nothing else, checked the oil it was getting a little on the low side to I topped of putting it in the middle of the electronic measure.
Leading evidence: 'Check oil it was getting a little' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check oil it was getting a little' (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.
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.
14 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: 20261026T052503Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
This afternoon I washed all the salt grime of the car and then pulled it inside - got a bit of a belt squeal(same as last time I washed it). Nothing else, checked the oil it was getting a little on the low side to I topped of putting it in the middle of the electronic measure.
So this evening my wife took the car out to a meeting and on her way back CEL came on and then a few minutes later "DRIVE TO WORKSHOP". I took it out in the neighborhood and there is a clear misfire although somewhat intermittent.
Clutching at straws but could the wash have gotten water in somewhere to cause trouble?
Have to go to the Indy(3 miles away) tomorrow morning or the local dealer - although that is 19 miles away. What is the consensus for the whether it would be safe to drive to the dealer? Indy is good but not much capacity.
Buy an obdII reader and pull the codes. Don't drive it until, at a minimum, you know what code(s) are being thrown. Without knowing what the car is trying to tell you, it's impossible to guess if it can be driven safely.
5CHN3LL - thanks for the advice but this is my only car and have no idea how long it will take to get a OBDII reader.
Is it normal to sometimes have a single drop below the blue coolant cap. Couldn't tell the color but felt slippery/oily
OBDII scanners are available anywhere you can buy car parts. The water could dry out overnight so fire it up in the morning and if the misfire is gone, you are good to go to the shop. There is a good chance it will be gone.
Thanks Imo000 for the encouragement. I did at one point aim the hose a little too acutely at the rear fins, so that was my first thought. My local Advance Auto Parts has an actron scanner available to I will stop in tomorrow. Thankfully my day is somewhat open and my wife reminded me that my in-laws are out of town so I have a car.
Turned the engine over this morning and fired right up with out a misfire - has not returned since. Local Indy scanned and nothing specific came up.
Maybe the wash
It's the wash for aure but it was not supposed to cause any issues. You have something going on that probably will surface again, probably in a good rain storm.
That's classic behavior of misfires caused by moisture/dampness from water getting on the coils from either a car wash or sitting out in the rain or even (in my experience) sitting out overnight in heavy fog.
I note you live in PA and if you drive the car year round the odds are the coils are just getting near the end of their service life due to exposure to the elements.
Often when the CEL flashes if the engine is shut off then restarted some time later the transitory problem that caused the flashing CEL is gone and the codes associated with the problem or cause are gone.
At least they are no long active codes. The codes may have been moved to the permanent error code memory.
In this memory the error codes can only be removed by the DME after so many engine warm up cycles with the cause of the error code absent. However, their presence in the permanent error code memory should not cause the CEL to come on let alone flash.
CEL was never flashing - it just came on steady.
I do live in Pittsburgh but the car has spent most of it's life in FL and a few years in Charleston SC. I've only had it for 2.5 months.
