Jump to content

Intermittent flashing SES light

Mat Benjamin
 Share

Recommended Posts

Mat Benjamin Enthusiast

Mat Benjamin

Posted
Posted

2021 Silverado TB 5.3L.  

 

Bought with 13 miles on it.  When I hit around the 500 mile mark, I noticed that every now and again within a minute or two of starting and driving out of the neighborhood, I would get a flashing SES light.  Sometimes it stays on for 20 or 30 seconds and clears.  Other times I will shut the motor down and restart and all is fine.  It does this maybe once a week.  

 

Never felt the motor misfiring when the light was flashing, and the Onstar does not report any issues with it.  Right now it is just irritating, but as anyone else experienced this and more importantly found a solution?

Anacortes Army Guy Enthusiast

Anacortes Army Guy

Posted
Posted (edited)

SES?  Since no one else has asked or commented, please tell me what SES stands for.  "Service" something?  Thanks

Edited by Anacortes Army Guy
Chevrolet1 Enthusiast

Chevrolet1

Posted
Posted

Mat, we're guessing SES = Service Engine Soon? Which in your truck would be equivalent to the MIL = Malfunction Indicator Light (aka Check Engine Light). Here's a pic from my 2019 manual.

 

2019 Silverado Manual - MIL.jpg

kmeleon Enthusiast

kmeleon

Posted
Posted

He means SEL or CEL. And to Mat, I have the exact same issue exactly how you explain it. Start the truck (usually after it sits for my lunch break) and drive slowly out of my neighborhood and I get the flashing SEL which means the truck is misfiring. On star doesn't see anything but my code reader shows misfires on cylinder 1 and 6. Truck has been at the dealer for a over a week, they say they can't get it to do it. I tell them who cares, you see the misfires when you scan it.... Fix it. I've been under the impression that eventually it will break a lifter or valve spring. Although the dealer says they're seeing weird fuel readings on those injectors.... I've told them I'll come get the truck tomorrow, I'll drive it, it'll do it again and I'm bringing it right back and calling GM and starting the lemon law option or buyback process if they don't fix it. They claim they can't rip the engine apart because there are no parts available. He believes there may very well be a recall for trucks built from 6/20 thru 10/20. We shall see. 

Big Bopper Enthusiast

Big Bopper

Posted
Posted

Mine has the same thing. These are my thoughts on my 2021 5.3l Sierra. Just started this issue a week or so ago. 


I noticed mine at low speed (maybe 10-18mph) after sitting with the engine idling. This is under very hot conditions. 110 plus ambient and high under hood temps. This is just staying at this speed in the neighborhood. 
 

One thing I have changed was fuel brands. I was using maverick branded gas 88 octane. I changed back to Exxon Mobil after running the maverick fuel fill almost completely empty.

 

I haven’t had enough time to check it completely but I’m wondering if maybe too high alcohol content or RVP fuel. You never know what you’re getting. 
 

maybe gm has the misfire algorithm too sensitive? Also I’m not sure what speed the skip fire (dfm) starts to work?

 

as of today the light has not come back on. So as a first change, maybe run the tank empty snd switch to a top tier fuel or at least a different brand  

kmeleon Enthusiast

kmeleon

Posted
Posted
21 hours ago, Big Bopper said:

Mine has the same thing. These are my thoughts on my 2021 5.3l Sierra. Just started this issue a week or so ago. 


I noticed mine at low speed (maybe 10-18mph) after sitting with the engine idling. This is under very hot conditions. 110 plus ambient and high under hood temps. This is just staying at this speed in the neighborhood. 
 

One thing I have changed was fuel brands. I was using maverick branded gas 88 octane. I changed back to Exxon Mobil after running the maverick fuel fill almost completely empty.

 

I haven’t had enough time to check it completely but I’m wondering if maybe too high alcohol content or RVP fuel. You never know what you’re getting. 
 

maybe gm has the misfire algorithm too sensitive? Also I’m not sure what speed the skip fire (dfm) starts to work?

 

as of today the light has not come back on. So as a first change, maybe run the tank empty snd switch to a top tier fuel or at least a different brand  

 

BB, exactly the same as mine. Got the truck back today and then leaving work it flashed again. Drove straight to the dealer. They can't see anything but the code P0300. They ordered an injector for cylinder 1, we shall see. Makes sense because if it was a vlave spring or lifter it would be constantly misfiring. 

 

 

Mat Benjamin Enthusiast

Mat Benjamin

Posted
  • Author
Posted

Yes I am referring to the check engine light.  The build date of my truck is Mar 2021.  I have not had the issue in over a week.  Fuel wise I normally use BP or Shell 87 octane.  She is due for her first oil change so for ****** and giggles I'm going to take the filter apart and see what I see.  Sooner that later I am going to get a Pulsar so I can halt the DFM and see if that's a contributor.  Those who have taken theirs back to the stealership, let me know how the repairs work out.  

Big Bopper Enthusiast

Big Bopper

Posted
Posted (edited)

As mentioned above, after running the fuel tank almost empty, then refilling at a different brand station,  have gone one week or more without a misfire code.

 

Did go to the dealership so they could pull the history on this. Just the P0300. 
 

I believe fuel related. Make sure to run the tank empty. I tried refilling a couple times (to top off) previously and it didn’t seem to fix it. 

Edited by Big Bopper
Typo
  • 2 weeks later...
Big Bopper Enthusiast

Big Bopper

Posted
Posted (edited)

Found this on a competing site:

this is a “too sensitive” misfire calibration issue as mentioned above. 
 

PIP 5809 

 

2020 and 2021 5.3l misfire

 

bulletin with revised calibration to follow

Edited by Big Bopper
Additional info
Mat Benjamin Enthusiast

Mat Benjamin

Posted
  • Author
Posted

Update...

At the stealership to have the issue addressed.  Apparently there is a software update which was released on 7-5-21 to address this flashing MIL light with no misfire.  GM was allegedly aware of it and needed to tweak the PCM software.  

Jlsprad77 New Member

Jlsprad77

Posted
Posted

I had the same problem with my 2021 Sierra 1500.  It will show the flashing CEL about once a week for a few weeks, go off and then it went solid.  I took it in and they said it was problem with the lifters, which seems pretty common with trucks built between like September of 2020 and March of 2021. They replaced the right bank of lifters, and gaskets and bolts and sealed it up again. Changed the oil and flushed and refilled the coolant.   I got it back and it ran great for about 2 weeks, now just today the CEL came back on again.  Incredibly frustrating.  To have a brand new truck to have less than 3,000 miles on it and have this kind of major engine failures.  I don't think it has anything to do with fuel, but poor quality parts.  The service receipt said misfire on #4 cylinder due to failed intake lifter and bent push rod. I have always had F150's, and went with an almost $60K GMC this time and very disappointed.  I hope you can get your issue resolved.  I am heading back to the dealership again in the morning.  Now they will probably replace the left bank of lifters.       

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...