Yes, odd indeed.

Turns out my mechanic has a nice snap-on scanner that can check every system, and he was open late enough so he could scan today. But still nothing, no ABS, no airbags, nothing but old history(before this latest flashing the other day).

So I'll just have to keep monitoring it. I still don't even know what caused the misfires, But I'll take it one day at a time. Maybe it was misfires, but not enough to trigger a code?

 

? Keep us posted!!

 

Roger, Roger!!

 

But my name is Steve! Just don't call me Shirley.

 

2 misfires in a drive cycle will set a CEL the first sets pending. If it happens in 2 consecutive cycles it goes "permament"/"historic". That's what puzzles me. Misfires are a "imminent cat killer" so they only get one chance.

 

To kill a cat??? Or slang term for catalytic converter???

 

only if they are playing a piano.

 

There are a number of codes that can be set that will not force a "limp-in" mode situation, but none would normally be associated with failures bad enough to cause a flashing SES light.

The other odd thing is that any issue bad enough to make the light flash is inherently bad enough to set a "hard" code, meaning that even if the situation causing the light to flash resolves itself, the light should remain illuminated and just go solid after the event.

This, along with the fact the car did not go into "limp-in" mode leaves me inclined to agree with RJ_RS_SS_350 that it may have been a series of soft codes identifying an intermittent problem rather than the "stop now" flashing of a qualifying event.

The only other option I can think of is that you're experiencing an ECM/Electrical problem, That's about the only way I can think of it occuring a second time and not have a single "pending" code.

 

The fist time it did set the 300 301 302 codes, but, yeah the second time, nothing. He said the reader communicated with every module on the vehicle and showed no issue at all.

 

Bonus!! Drive her McIver!! But keep an eye on the CEL!!