Jump to content

OIL COOLER LINES - Check yours now! Urgent 2019 owners

romeactual
 Share

Recommended Posts

clowe1243 Enthusiast

clowe1243

Posted
Posted

Joining the club, mine just started (or atleast was noticed).  Thanks to this post, I was a little more relieved it wasn't just me (Out of warranty a while now).  The cover that is under it caught oil for quite a bit.  If it wasn't for for removing the cover while inspecting my lifts bolt, would have never noticed.  No burning oil, no drips in my parking spots.  My best guess is it was so little, I never caught low oil on the dip stick.

Google and the recall in cold climates tells me its weather related; couple cold years in DMV recently.  2019 6.2L with 55k miles.  Besides going custom AN hoses and fittings, and even aftermarket oil cooler, cant find an upgrade.  It is what it is, 7 years is this is my only issue thus far, I'll take it.

Still don't understand why they want to drop the coolant hose for the swap.  But my replacement will be here tomorrow, I'm sure I will figure it out why...lol.

  • Replies 36
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

romeactual
romeactual

I posted about this previously and had a decent outcome with reimbursement, wanted to share all the info I can. Looking through the forums, it appears its continuing to happen to more people! I would

relevante
relevante

I cut and flared the factory lines and used AN fittings and replaced the middle section with braided hose. Some others have just used rubber hose and hose clamps even I think if you dig back in this t

MaverickZ71
MaverickZ71

THIS. GM can't build oil cooler or transmission cooler lines worth a damn, since the 1990s. We're on the 4th set on our 09 Silverado. 🤬 In our experience, they sweat in a year or two, and then immedia

66ss3964spd Enthusiast

66ss3964spd

Posted
Posted

Also in the DMV, but haven't noticed anything on mine. But mine is a '23 and has just under 27K miles on it so maybe I have time. Regardless, I'll have a look at them in the next week or two.

 

Let us know how your swap out goes.

clowe1243 Enthusiast

clowe1243

Posted
Posted (edited)
On 3/17/2026 at 11:35 AM, 66ss3964spd said:

Also in the DMV, but haven't noticed anything on mine. But mine is a '23 and has just under 27K miles on it so maybe I have time. Regardless, I'll have a look at them in the next week or two.

 

Let us know how your swap out goes.

Swap went well.  But I know now why they want to lower coolant hose and radiator fans removed.  It was a pita routing them the correct way.  Thanks to the lift, the front diff wasn't in the way much at all.  Took about 4 hours of swapping position between under the hood, under the truck, and inside the fender, over and over again.  If this happens again, I will be doing AN lines at the rubber hoses.

Edited by clowe1243
richard wysong Senior Enthusiast

richard wysong

Posted
Posted

it will happen again, I went through 4 sets over the life of my 98 K2500, less than 200k when I wore it out and scrapped it. Gm parts everytime

66ss3964spd Enthusiast

66ss3964spd

Posted
Posted
18 hours ago, clowe1243 said:

Took about 4 hours of swapping position between under the hood, under the truck, and inside the fender, over and over again.

Well that sounds like approximately zero fun, especially if one doesn't have access to a lift.

 

Curious, though, that you mention the transfer case. I'd have thought the engine, and even trans, cooler lines would be well forward of the transfer case.

clowe1243 Enthusiast

clowe1243

Posted
Posted
On 3/24/2026 at 12:24 PM, 66ss3964spd said:

Well that sounds like approximately zero fun, especially if one doesn't have access to a lift.

 

Curious, though, that you mention the transfer case. I'd have thought the engine, and even trans, cooler lines would be well forward of the transfer case.

 

On 3/24/2026 at 1:18 PM, richard wysong said:

I bet he meant the front differential

 I meant front diff...smh...lol

  • Like 1

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,770
    Total Members
    8,960
    Most Online
    Paul8556
    Newest Member
    Paul8556
    Joined

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

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