Jump to content

2016 Sierra 6.2L repeated lifter failures

martinto
 Share

Recommended Posts

martinto Enthusiast

martinto

Posted
Posted

First of all, I love my Sierra...except for the repeated lifter failures.  New in 2016, cross country trip and first failure on #6 lifter & pushrod damage; dealer in Iowa fixed in short order.  2020 another failure, but tech didn't indicate which lifter failed, I should have confirmed.  2021, #4 lifter fail and pushrod damaged.  This week, #4 again.  Dealer is doing a deep dive to investigate how deep the damage may be.  Warranty has covered all fixes and I have extended warranty, so $ not the issue at this point.  What concerns me is the frequency of failures and how that impacts the life of the engine.  Has anyone on this site experienced these repeat lifter fails?  I'm thinking to reach out to GM and request of review of the failures and what consideration can be given; i.e. replace the engine???  Dealer has been great, but I don't look forward to repeats every 1.5 to 2 years.  Thanks for any feedback.

  • Replies 37
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

It's Tim
It's Tim

Extended OCI? Just because you can doesn't mean you should...

diyer2
diyer2

Beating a dead horse but I still say oil changes are cheap insurance and more so today due to the complexity of modern engines.

rav3
rav3

I agree with you on the metal issue. He may be getting some of the 'old' stock of inventory. I read somewhere that they have changes the materials on tge lifters so they are harder &less susceptib

16LT4 Enthusiast

16LT4

Posted
Posted (edited)

Lifters are not a maintenance item.  For such a repeated set of failures, there is likely some underlying root cause of failure that isn't being addressed, lack of proper oil flow or fuel dilution being top of the list.

Edited by 16LT4
  • Like 1
rav3 Senior Enthusiast

rav3

Posted
Posted

Sorry to hear your issue, especially with such low miles. I recommend, if you so desire, to educate yourself as to the "main reason" (IMO) for these failures. As a tooling engineer for over 40 years, I have seen & understand how these lifters fail on these DOD AFM. Ther's one guy on youtube that shows how he sees these failures all the time & it really make sense to me. The "lock lugs" in those lifters end up causing a burr inside & cause the system to jam.  To me the only fix, short of deleting the AFM parts, is to add a Range DOD AFM delete unit to the OBD2 socket. This stops the engine from going to the 4-cylinder mode. I've done this & don't really see that much of a fuel mileage difference. 

Here's the video where he explains how it works & the cause for most failures. (Stuck lifter & bent push rod) Disabling the DOD will eliminate the collapsed DOD lifters from getting stuck on that burr/pennied edge shown in the video.

It's my understanding that GM changes the steel alloy material to make it harder, so the penning was less likely to occur. I hope that makes sense.

 

 

newdude Senior Enthusiast

newdude

Posted
Posted
3 hours ago, martinto said:

First of all, I love my Sierra...except for the repeated lifter failures.  New in 2016, cross country trip and first failure on #6 lifter & pushrod damage; dealer in Iowa fixed in short order.  2020 another failure, but tech didn't indicate which lifter failed, I should have confirmed.  2021, #4 lifter fail and pushrod damaged.  This week, #4 again.  Dealer is doing a deep dive to investigate how deep the damage may be.  Warranty has covered all fixes and I have extended warranty, so $ not the issue at this point.  What concerns me is the frequency of failures and how that impacts the life of the engine.  Has anyone on this site experienced these repeat lifter fails?  I'm thinking to reach out to GM and request of review of the failures and what consideration can be given; i.e. replace the engine???  Dealer has been great, but I don't look forward to repeats every 1.5 to 2 years.  Thanks for any feedback.

 

 

Did they ever replace the VLOM?  GM wants that replaced if it hasn't been done yet.  

martinto Enthusiast

martinto

Posted
  • Author
Posted

Thanks.  Don’t know what that is.  Not noted on the invoice summary.  Today they advised they need to replace the cam shaft.  I’m pushing back on what all these failures and repairs have on the engine reliability.  Only 48,000 miles

martinto Enthusiast

martinto

Posted
  • Author
Posted
3 hours ago, Snowcamo said:

Best comment ever💯💯💯

OCI?  I’m taking the position the given the frequency of failures…GM needs to step up.  May need the extended 3rd party warranty for other issues.  Given they now need to replace the cam shaft as well, big bucks on the horizon to the 3rd party or GM.  

 

3 hours ago, Snowcamo said:

Best comment ever💯💯💯

 

rav3 Senior Enthusiast

rav3

Posted
Posted
18 minutes ago, Snowcamo said:

Oil Change Intervral

 

Used to be 3k back in the day when engines outlasted vehicle ownership.

 

 

Interesting....my chevy dealer recommended OCI every 4k even under the Certified warranty when they were paying for it. 

I personally don't feel even 6k miles oil change is an issue with the new full synthetic oils. My oil isn't that dirty at 6k.

I feel that it's more of the mechanical design issue than oil failure. 

martinto Enthusiast

martinto

Posted
  • Author
Posted
54 minutes ago, Snowcamo said:

Oil Change Intervral

 

Used to be 3k back in the day when engines outlasted vehicle ownership.

 

 

Oil changes by the dealer at specified intervals…with synthetic.  All my maintenance is done by dealer service.  When my tranny had the famous shudder, they followed the TSB with the new Mobil Blue fluid.  No problems since then.  

martinto Enthusiast

martinto

Posted
  • Author
Posted
31 minutes ago, rav3 said:

Interesting....my chevy dealer recommended OCI every 4k even under the Certified warranty when they were paying for it. 

I personally don't feel even 6k miles oil change is an issue with the new full synthetic oils. My oil isn't that dirty at 6k.

I feel that it's more of the mechanical design issue than oil failure. 

Agree

Snowcamo Senior Enthusiast

Snowcamo

Posted
Posted

The failure is a 100% mechanical as is with all the 6.2 engines. Either lifter bore issues or just lifter failure issues.

 

 I'm not gonna get into another oil thread here. There's way too many oil threads out there and everybody has her own opinion. I'm just old school and I'll keep my 3K to the day I'll fade away lol.

 

 Only thing I will argue is there's no magical fluid that  Truly fixes a transmission problem. There's only cover ups and bandaids. What GM has for failures out there in transmission world is not something a fluid can truly resolve.  There is a reason why sonnax has a list of parts that are made just to resolve GM transmission issues.

OffTheAir Enthusiast

OffTheAir

Posted
Posted

These failures do happen, unfortunately, there's no denying that.

 

However, I'm with 16LT4 on this one - there is something else clearly going on here, whether the past repairs were not executed fully or there is something else internally that is very wrong. Maybe bad lifters were used?

 

I mean, we're talking about FOUR lifter failures in the span of six years, three of which are only one year apart. I won't speak for everyone, but most of the time when these failures do happen it's fixed and then you're back on the road for a while. It is not normal for this to become an annual repair.

Luckily, you're under warranty, but I definitely agree with investigating this a little more

martinto Enthusiast

martinto

Posted
  • Author
Posted
11 hours ago, OffTheAir said:

These failures do happen, unfortunately, there's no denying that.

 

However, I'm with 16LT4 on this one - there is something else clearly going on here, whether the past repairs were not executed fully or there is something else internally that is very wrong. Maybe bad lifters were used?

 

I mean, we're talking about FOUR lifter failures in the span of six years, three of which are only one year apart. I won't speak for everyone, but most of the time when these failures do happen it's fixed and then you're back on the road for a while. It is not normal for this to become an annual repair.

Luckily, you're under warranty, but I definitely agree with investigating this a little more

Thanks.  That is where I’m at.  Dealer says the cam shaft is damaged and needs to be replaced as well.  I question the durability of the engine given the history.  I requested what options to consider…extended warranty, which only covers cost of repair but at a cost of inconvenience, or should GM drop another engine in.  I’m sure there will be push back on either.  My service guy understands my concerns and is working to find an acceptable solution.  If he runs into a wall, I will need to escalate.  

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

    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
    • Grumpy Bear
      OCI, not when but why?

      By Grumpy Bear · Posted

      I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • revmanii
      Looking at ordering a '26 WT because I want a std cab, std bed

      By revmanii · Posted

      Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...