10 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCheck Engine - Misfire
Leading reported evidence
Check engine came
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.
Leading evidence: 'Check engine came' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check engine came' (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
Check Loren's website renntech.org for the pcar codes if displayed code is not from scanner list.
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
If it was a simple bad gas misfire, the computer will clear itself during its next diagnostic cycle without the "misfire." A number of us were "poisoned" with bad gas when we filled up at the same time the tanker was filling the underground tanks.
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 doubt bad gas because I have had a few fill-ups.
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
get a cheapo obd2 scanner from like kragens or similar(i paid like $40 for one-actron)with reset button if need to reset small stuff.
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
If it was a simple bad gas misfire, the computer will clear itself during its next diagnostic cycle without the "misfire." A number of us were "poisoned" with bad gas when we filled up at the same time the tanker was filling the underground tanks.
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
If it over report coolant temperature (at colder temperatures) the engine controller will not enrichen the air/fuel mixture enough and a very rough running engine is the result.
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
If rough running persisted after secondary air injection pump shut off (engine controller usually goes closed loop around this time) may not be coolant temperature sensor, but a bad/cracked coil.
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: 20261026T220748Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I started up in "... cold" weather the other day and the car was obviously missing... Vibrating and Rough, High Idle. Check Engine came on. I shut down and restarted. Ran fine for a week.
This morning I turned on and same thing. Shut off and restarted and engine runs fine but Check Engine light still on.
Anyone else have this experience and any insight? By "... cold" I mean about 30 degrees F. Car has 80k. Well serviced and never on track. Late for 75k check up and oil change, but driven pretty gently.
Thanks in advance,
JKC
So get the codes read and report them back here. Also provide Model, MY, last time tuned and other pertinent info.
Then we'll be glad to help. Otherwise we play 1000 guesses and you spend lots of $$$
How much gas do you have? Did the CEL blink or was it steady the whole time?
Without the codes, I would speculate bad gas. Try driving the tank dry, filling up and driving some more. If it was a simple bad gas misfire, the computer will clear itself during its next diagnostic cycle without the "misfire." A number of us were "poisoned" with bad gas when we filled up at the same time the tanker was filling the underground tanks. Apparently, this stirs up the water and particulates in the underground tanks, and can get into your car. The CEL comes and goes until the bad gas is all used up.
But, you should still read the codes and report back, as there are other symptoms that could be classified as a "misfire" when they aren't.
-td
I will take into to the dealer next week. How else can I get the code? Do not really trust anyone else around here.
I doubt bad gas because I have had a few fill-ups. The CEL did not blink. Steady. It is running smooth now but I am wondering if it is ignition coil/packs...
Model straight up 1996, 2003 with the 3.6. Last time tuned 60k by dealer, I am now at 80k. (I know, I am overdue. The economy killed me).
Thanks for input.
JKC
get a cheapo obd2 scanner from like kragens or similar(i paid like $40 for one-actron)with reset button if need to reset small stuff. Scanner will have book on codes but there a few exclusive to pcars. Check Loren's website renntech.org for the pcar codes if displayed code is not from scanner list. Regards Mike
gas is a defective coolant temperature sensor. If it over report coolant temperature (at colder temperatures) the engine controller will not enrichen the air/fuel mixture enough and a very rough running engine is the result.
If rough running persisted after secondary air injection pump shut off (engine controller usually goes closed loop around this time) may not be coolant temperature sensor, but a bad/cracked coil.
Would help to know error code(s) and what long term fuel trims are. If you clear error code this clears long term fuel trims so read these first.
An OBD II code reader/data viewer is almost a necessity for anyone attempting to home diagnose engine "troubles". A device that reads DTCs, freeze frame data, and allows you to monitor/view engine sensor inputs and other values like coolant temperature, intake air temperature, long/short term fuel trims, OS sensor readings, etc., is what you want.
Sincerely,
Macster.
This is a source reference. Confirm exact model applicability in the original material.
