Jump to content

2025 - 2026 3.0 LZ0 Crankshaft End Play

JohnMr19
 Share

Recommended Posts

JohnMr19 Enthusiast

JohnMr19

Posted
Posted (edited)

Has anyone here experienced issues with this?  GM has issued a bulletin (25-NA-307) for bellhousing noise and P06DD for 2025 - 2026 3.0 Duramax LZ0's.  Too much crankshaft end play from thrust bearing wear could lead to engine failure.  I just purchased my 2026 Silverado HC specifically with the LZ0 because I had one in 2023 that had zero issues and loved it.  I wanted to avoid the lifter and crankshaft bearing issues the V8's have been experiencing (had a 6.2 with lifter failure) and was hoping for years of trouble-free reliability as this will likely be my last new truck as retirement is getting closer.  So far I have just over 2,200 miles with zero issues and don't seem to have used any oil yet.  I'm wondering just how wide spread this issue could be.

https://www.duramaxnews.com/post/lz0-3-0-duramax-gm-flags-crankshaft-end-play-behind-bellhousing-noise-p06dd-25-na-307

 

IMG_4828.jpg

Edited by JohnMr19
Add link
  • 2 weeks later...
SPASierra Enthusiast

SPASierra

Posted
Posted

Based on the numbers from the site you posted, it isn't a widespread issue yet.  I have just over 3300 miles on my 2025, and will just keep an eye on it.

newdude Senior Enthusiast

newdude

Posted
Posted (edited)

We had one fail prior to the TSB coming out.  Had about 5500mi on it.  Happened in July this year.  It ran and had no noise but had the P06DD set and low oil pressure.  Tech pulled the oil pan and it was grey anti-sieze colored engine oil all over the place, and the thrust bearing sides were ejected into the pan.  

 

I don't have a picture of the oil and oil pan, but here's the pieces of the thrust bearing side and what it's supposed to look like.  For whatever reason on the LM2 and LZ0 Duramax, and L3B Turbomax, the thrust bearing is a three piece unit.  So there is the upper bearing shell and then another p/n for the thrust sides of it.  On the V8s though, the thrust looks the same but the sides of it are clipped to the bearing and not just loose installed next to the bearing separately.  

 

I won't be shocked if more show up across the US, even if its a small number of failures.  There's been a few in the GM Technician Facebook group already.

 

 

IMG_2941.jpg

Edited by newdude
  • Sad 1
Atlas Senior Enthusiast

Atlas

Posted
Posted

I'm aware of the issue, and have just over 1400 miles on my 2025. It's sad because I was avoiding DFM (5.3), failing 6.2's, and the 2.7 wasn't for me. Now this is floating around in the back of my head. Should we drive it to Thanksgiving (700 mile road trip) or leave it parked that week and put miles on it when we're not on a tight timeline.

 

The engine doesn't seem to have used any oil. I changed it at 500 and will change it again at 1500 now that I'm keeping an eye on this issue. Oil changes won't prevent the issue, but if I'm seeing metallic, I want to try to catch the issue early.

  • Like 1
customboss Senior Enthusiast

customboss

Posted
Posted
1 hour ago, Atlas said:

I'm aware of the issue, and have just over 1400 miles on my 2025. It's sad because I was avoiding DFM (5.3), failing 6.2's, and the 2.7 wasn't for me. Now this is floating around in the back of my head. Should we drive it to Thanksgiving (700 mile road trip) or leave it parked that week and put miles on it when we're not on a tight timeline.

 

The engine doesn't seem to have used any oil. I changed it at 500 and will change it again at 1500 now that I'm keeping an eye on this issue. Oil changes won't prevent the issue, but if I'm seeing metallic, I want to try to catch the issue early.

Drive it. 

  • Like 4
JohnMr19 Enthusiast

JohnMr19

Posted
  • Author
Posted

I just completed my fourth 540-mile trip today and the truck continues to run flawlessly.  Just went over 3,100 miles and it still hasn't used any oil.  I'm keeping my fingers crossed!  I'm assuming they won't measure the end play unless the truck starts making noise and/or throws the code?

newdude Senior Enthusiast

newdude

Posted
Posted
21 minutes ago, JohnMr19 said:

I just completed my fourth 540-mile trip today and the truck continues to run flawlessly.  Just went over 3,100 miles and it still hasn't used any oil.  I'm keeping my fingers crossed!  I'm assuming they won't measure the end play unless the truck starts making noise and/or throws the code?

 

 

Correct.  If you hear noise or that code is present and you take it in for diagnostics, the TSB should be followed by the dealer to determine if it needs an engine based on thrust measurements.

 

 

Jus Cruisin Enthusiast

Jus Cruisin

Posted
Posted

My 3.0l engine failed at 5,403 miles. It just stopped running while accelerating away from a roundabout. No warning, no dash lights. Just quit and I coasted to a stop. I had steering. A message popped up on the screen that read "please restart engine" or something like that. It wouldn't and it was towed to the dealership. They determined it siezed. GM didn't pay for them to tear it down, just immediately approved a new engine. I doubt I'll ever find out what failed. It took 50 days to get the truck back. I have 300 miles on the truck since and it's running just fine. Fingers crossed it was a fluke. 

JohnMr19 Enthusiast

JohnMr19

Posted
  • Author
Posted

I should mention the truck does have one issue that is completely unrelated to the topic, but is still frustrating.  I've had to re-pair my iPhone four or five times since I bought the truck.  Apple Car Play will randomly not work on startup and when I check my bluetooth settings, my phone is no longer listed.  When I try to pair from the phone, it fails and I have to "Forget" the connection.  It just did a OTA update recently and I hoped that would fix the issue, but it's happened again since then.  I believe it happens when I remote start the truck.  At other times it will work, but can take longer to finally connect.  Not a deal breaker for the truck, but frustrating none the less.

  • 1 month later...
JohnMr19 Enthusiast

JohnMr19

Posted
  • Author
Posted

I have 4500 miles on the truck and no issues whatsoever.  I even towed my cargo trailer 550 miles without any issues.  Roads were pretty crappy, so it was slow going but the truck got around 15 MPG towing.  So far so good - fingers crossed!

  • Like 1
  • 2 weeks later...
T-Town-Z Enthusiast

T-Town-Z

Posted
Posted

I was looking to purchase one of the 3.0 Duramax trucks back in the fall, but then started reading about the bearing failures.  I decided to hold off at that time.

I'm ready to go shopping again.  Does anyone know if there was a date range of when the bad engines (and trucks) were produced and if GM has it taken care of it yet ?

  • 3 weeks later...
Atlas Senior Enthusiast

Atlas

Posted
Posted
On 1/9/2026 at 8:51 AM, T-Town-Z said:

I was looking to purchase one of the 3.0 Duramax trucks back in the fall, but then started reading about the bearing failures.  I decided to hold off at that time.

I'm ready to go shopping again.  Does anyone know if there was a date range of when the bad engines (and trucks) were produced and if GM has it taken care of it yet ?

 

GM's lack of information is frustrating. I have a feeling they might know by now which VINs are potentially affected but as far as I know they're not saying. Model year 2026 trucks are said to be affected based on what some of the dealer techs who run Youtube channels are saying. Build dates are anywhere from mid-late 2024 for model year 2025 trucks, through trucks currently being built. There are reports of repeated failures, i.e replacement thrust bearings also failing.

 

Atlas Senior Enthusiast

Atlas

Posted
Posted (edited)

1700 miles on my truck. This is such an ugly cloud hanging over this vehicle, and in the back of my head. I've been through one of these before with another vehicle, an FCA product with a 3.6 pentastar... manufacturer wouldn't do anything about a manufacturing defect until failure occurs. In that case I was left waiting and wondering for 3 years if the engine was just going to suddenly fail, and eventually it did. That's just an incredibly sucky ownership experience. GM should do better. @GMCustomerService

 

I've thought about just getting rid of this truck. But what would I replace it with? Not a 6.2..ha! 5.3 is said to be going away, and there's no way in hell I'm buying a first model year engine from GM or anyone else when the 2027 trucks come out.

 

Mine is a Feb 2025 build date which puts it right in the line of fire for all the reported failures.

 

 

Edited by Atlas
  • 2 weeks later...

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   5 Members, 0 Anonymous, 1,769 Guests (See full list)

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...