Jump to content

2025 2500 HD Duramax Leaking tranmission

Derek Smay

By Derek Smay
in 6.6L Gas V8 (L8T)

 Share

Recommended Posts

Derek Smay New Member

Derek Smay

Posted
Posted (edited)

Anyone else having issue with their 2025 2500 HD leaking around the inspection cover? This is my first Chevy truck, and I noticed oil leaking from transmission around inspection cover in bell housing. The dealership where I purchased the truck cleaned out oil and had me drive to see if it was just residual oil. The oil leak continued and now another dealership did the reseal of front seal and whatever else was list in technical service bulletin last week. After about 50 miles truck now leaking again worse than before from same area. Truck only has 2700 miles on it and extremely disappointed after spending $75K that been into shop several times. I'm hoping GM could just send a replacement transmission hate the idea of all these repairs on a brand-new vehicle. It's going back to the dealership on Monday for them to have another look. 

thumbnail_image0.jpg

Edited by Derek Smay
Chevyfan3 Enthusiast

Chevyfan3

Posted
Posted

Insane that GM is still allowing this to happen and hasn't fixed the issue into the 25' model run. I had this same issue on my 23' and had to have the trans removed for the reseal tsb as well. After that it took some mile for the fluid to stop leaking, I would crawl under the truck and clean it up, pop off that cover and clean that area as well. I think I have about 6k on it now since the repair and it's been dry. I have seen guys end up having the trans replaced though for ones that wouldn't stop leaking so that's a possibility as well. I would clean it yourself and monitor and hopefully it stops, the convertor is tight to install on these transmissions so it can spill some fluid when they put it back together. 

 

I guess GM has decided they are not going to fix this issue on this generation of trucks which is pretty sad.

Derek Smay New Member

Derek Smay

Posted
  • Author
Posted

Thanks for suggestion I’ll give it a try. It’s going back to dealership Monday. It’s dripping pretty good I wiped driveway clean yesterday and here pic from today 

 

 

IMG_1478.jpeg

Chevyfan3 Enthusiast

Chevyfan3

Posted
Posted

Mine never got to where it was dripping on the ground like that, it was pooling inside the case though. So you're just be losing fluid at a pretty good rate then. If it's dripping your looking at having the transmission come out again to repair it unfortunately. 

 

I'm really starting to lose my faith in the gm truck product, not fixing known issues like this is ridiculous. The fact I had it in 23' and now your truck 2 years later same issue just shows you the level of commitment they have to improving or turning out a good product.

Derek Smay New Member

Derek Smay

Posted
  • Author
Posted

Crawled under this morning and it’s all around the pan not sure if they would have dropped pan or not. There was very little inside bell housing that I could feel so that may have been from before repair. 

 

 

Another JR Senior Enthusiast

Another JR

Posted
Posted
On 1/16/2025 at 11:04 AM, Derek Smay said:

Anyone else having issue with their 2025 2500 HD leaking around the inspection cover? This is my first Chevy truck, and I noticed oil leaking from transmission around inspection cover in bell housing. The dealership where I purchased the truck cleaned out oil and had me drive to see if it was just residual oil. The oil leak continued and now another dealership did the reseal of front seal and whatever else was list in technical service bulletin last week. After about 50 miles truck now leaking again worse than before from same area. Truck only has 2700 miles on it and extremely disappointed after spending $75K that been into shop several times. I'm hoping GM could just send a replacement transmission hate the idea of all these repairs on a brand-new vehicle. It's going back to the dealership on Monday for them to have another look. 

thumbnail_image0.jpg

Just a friendly heads up that you posted this in the gas engine subforum. 

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...