My check engine light came on; the dealer checked the codes and found
three cyclinders misfiring. After tune-up (all plugs were changed)
and the same day I drove 80 miles when the check engine light came on
again; the next day the dealer checked the code and found four
cyclinders misfiring! The dealer needed the vehicle for a day but no
loaners were avaiable for me so I’m driving around (with engine light
on) for a week when the original fan-belt failed. After having the
belt replaced, the check engine light has not come on (going on 4-days
and counting).
During this situation not once did I have any indication of misfires.
I had a friend who had a code reader to check the cause the second
time and the results confirmed the dealer’s findings. Can anyone
relate to misfirings regarding unusal code readings versus maintence
or (hard to believe) was it the fan belt?!

Signature
Posted at author's request, using http://www.AutoBoardz.com interface
Articles individually verified to usenet standards. Visit URL to contact author/report abuse
Thread archive: http://www.AutoBoardz.com/engine-misfires-ftopict209742.html
Carl 1 Lucky Texan - 24 Mar 2007 05:05 GMT
> My check engine light came on; the dealer checked the codes and found
> three cyclinders misfiring. After tune-up (all plugs were changed)
[quoted text clipped - 11 lines]
> relate to misfirings regarding unusal code readings versus maintence
> or (hard to believe) was it the fan belt?!
Odd, I once had the misfire-coded cel come on when driving to high
altitude. I also wonder if bad/watery fuel could be the problem?
Carl

Signature
to reply, change ( .not) to ( .net)
bgd - 28 Mar 2007 19:49 GMT
slow charge from bad belt may have caused weak delayed fire triggering a
code.
>> My check engine light came on; the dealer checked the codes and found
>> three cyclinders misfiring. After tune-up (all plugs were changed)
[quoted text clipped - 16 lines]
>
> Carl