Cold Start -> SES ON -> Restart -> Fine ???

[LeiZ]

It happened to me several times during the last 3 months, especially when it's cold (<20°F). Last time it happened, followed by a fire, which I posted 2 weeks ago. Now whenever it sits there in cold weather for more than 3 days, it'll give me SES ON if you start it for the 1st time, and it'll be fine after restart.

Any suggestion? Fuel System? Starter? Battery? Wire? The spark plugs, CCV & hoses, Valve Cover Gasket and engine oil are all new.

Any suggestion is greatly appreciated. Thanks!

[Big "J"]

Need to put a OBD II code reader on it when it's showing the SES light. That will help narrow down what is doing or is wrong. No way to tell until then....Cold weather makes for weird things to happen.

[Roadkill]

what year and motor?

[LeiZ]

Sorry, 01' 3.0i.

The SES light is on only it shaks. If you restart it again, the SES light will go off. So do you suggest get the OBD II ready at hand before initial start? And read the code while it shakes?

I'll see if I can borrow a OBD II. Thanks for the suggestion!!

[sunny5280]

Originally Posted by LeiZ

Sorry, 01' 3.0i.

The SES light is on only it shaks. If you restart it again, the SES light will go off. So do you suggest get the OBD II ready at hand before initial start? And read the code while it shakes?

I'll see if I can borrow a OBD II. Thanks for the suggestion!!

The computer will store the code(s) in memory even if the SEL is no longer illuminated. Thus you should be able to use an OBD-II scanner to read them after the SEL is no longer illuminated.


The computer will eventually purge a stored code (assuming the condition which set the SEL is no longer being detected) upon a given number of "trips". Some codes will clear in 40 "trips" while others in 80. A trip is, essentially, what it sounds like: An off-start-on-off cycle of the engine. Basically normal driving. It goes something like this:

1. Computer detects one of the monitored systems has fallen out of specification, sets the SEL, and stores the code in memory.
2. The computer continues to monitor the affected system. If the condition which set the SEL falls back into spec the computer may clear the SEL. Typically there needs to be a couple of consecutive trips where the monitored system remains with spec before the computer will clear the SEL.
3. If the SEL is cleared the computer will retain the error code in memory for a predetermined number of trips. This allows you to read the fault code even if the condition which set the SEL falls back into spec. After the predetermined number of trips the computer will purge the code at which time there is no way to retrieve it.
4. An OBD-II scanner can clear the codes which results in the SEL being cleared. However if the condition which resulted in the initial setting of the SEL remains or falls out of spec the process starts over again.

The best thing you can do to troubleshoot an SEL is to get the code(s) read. The code(s) will give you an idea of where to begin your troubleshooting efforts.

Good luck.

[LeiZ]

WOW Sunny! That's quite a whell of info. Thanks! I'll get it read and go from there! Thanks!

Originally Posted by sunny5280

The computer will store the code(s) in memory even if the SEL is no longer illuminated. Thus you should be able to use an OBD-II scanner to read them after the SEL is no longer illuminated.



The computer will eventually purge a stored code (assuming the condition which set the SEL is no longer being detected) upon a given number of "trips". Some codes will clear in 40 "trips" while others in 80. A trip is, essentially, what it sounds like: An off-start-on-off cycle of the engine. Basically normal driving. It goes something like this:

1. Computer detects one of the monitored systems has fallen out of specification, sets the SEL, and stores the code in memory.
2. The computer continues to monitor the affected system. If the condition which set the SEL falls back into spec the computer may clear the SEL. Typically there needs to be a couple of consecutive trips where the monitored system remains with spec before the computer will clear the SEL.
3. If the SEL is cleared the computer will retain the error code in memory for a predetermined number of trips. This allows you to read the fault code even if the condition which set the SEL falls back into spec. After the predetermined number of trips the computer will purge the code at which time there is no way to retrieve it.
4. An OBD-II scanner can clear the codes which results in the SEL being cleared. However if the condition which resulted in the initial setting of the SEL remains or falls out of spec the process starts over again.

The best thing you can do to troubleshoot an SEL is to get the code(s) read. The code(s) will give you an idea of where to begin your troubleshooting efforts.

Good luck.

[Big "J"]

Yes, read it while it shakes....It will probably give you a misfire code if the engine is shaking. My daughters 2002 325i does the same when its really cold outside and all spark plugs aren't firing properly. I have her do the same... shut it off, wait a few seconds and try again. It starts back up just fine. I do a fuel injector cleaning with "seafoam" before and after winter, due to the gunk build up from the cold weather.
Good Luck!

[LeiZ]

That's very helpful, J. Thanks again!

Originally Posted by Big "J"

Yes, read it while it shakes....It will probably give you a misfire code if the engine is shaking. My daughters 2002 325i does the same when its really cold outside and all spark plugs aren't firing properly. I have her do the same... shut it off, wait a few seconds and try again. It starts back up just fine. I do a fuel injector cleaning with "seafoam" before and after winter, due to the gunk build up from the cold weather.
Good Luck!

[Nik]

Mine does the same. SES keeps flashing and when you restart it it's fine. If you are getting sudden drops of RPM while on Idle. It's propobbly MAF needs cleaning. If you get Lean bank on OBD, and are past 100k and havn't changed O2 sensors I would do so. (got them on order) Also could be dirty Injector as Big "J" said. try some Redline I as jst0208 reccomends. Also could be some gasket or hose leak. prety hard to find out like that.

[LeiZ]

YES, Nik! The sudden RPM drop happened to me twice, as far as I can recall. It was after almost an hour driving, and stopped at redlight. Seems like I need to clean the MAF like you suggested. I'll give it a try later this month.

Originally Posted by Nik

Mine does the same. SES keeps flashing and when you restart it it's fine. If you are getting sudden drops of RPM while on Idle. It's propobbly MAF needs cleaning. If you get Lean bank on OBD, and are past 100k and havn't changed O2 sensors I would do so. (got them on order) Also could be dirty Injector as Big "J" said. try some Redline I as jst0208 reccomends. Also could be some gasket or hose leak. prety hard to find out like that.