Jump to content

Recommended Posts

Posted

I just purchased a 2021 also and the first time I drove it smell like coolant check the reservoir and sure enough it was low, top it off and is getting low again, no signs of leakage or puddles under the truck but I sure smell it after a long drive, bringing it to the dealership next week hopefully they find something

  • 2 months later...
Posted

Has the problem been fixed? My 2020 LM2 keeps getting low and I’ve been continuing to fill it up. No leaks in the driveway and no smell, yet the tank keeps coming up short. 

Posted

I had a similar problem with my 02 avalanche. The low coolant light would come on about every 4 months. Never on the stick or ground. I’d add about 1qt. About 2 years in I was getting an oil change with my annual inspection. The service writer said my oil came out in clumps at first. I found out later some models had problems with small cracks in the head. In went some bars leak one year later no light.

  • 3 weeks later...
Posted

Anybody figure it out for sure yet? Same issue, 2021 Silverado with the 3.0 Duramax. No visible leaks, I don't think I've ever smelled coolant but I also always park outside, and yet the main reservoir loses the same amount as in OP's picture. I've filled it once to the line indicated on the tank (as well as I the manual), but it has gone down again since. 15,000 miles and no other complaint.

  • 1 month later...
Posted

I am also wondering if anyone else has insight on this. I also

smell coolant 1 in 20 times or so around the front of the truck after driving. My reservoir is also down about   1/2 of an inch. Anyone have any updated info I have a 21’ AT4 LM2

  • 1 month later...
Posted

I purchased a used 2021 3.0L Silverado High Country in October. I've had to top the coolant reservoir once not overly worried about that. I've been topping up the turbo coolant reservoir once a week but can't find it leading anywhere. Anyone else have a solution? 

Posted

UV dye kit will find the smallest leaks. They have kits for every fluid in a vehicle. 

  • Like 1
Posted

My 2014 had the infamous radiator leak at the upper hose connection.  Got it replaced under warranty, with the same defective part and 6 months later, leaking again.  GM released an updated part number, but I already traded the truck in on a 2020.  I get the 2020 home and check the fluids the day after, and the coolant is low!  

 

C'mon Man!  


I top it off, and come to find out, it was just an air pocket in the heater core.  It burped and was fine since.  I do wonder if some of the radiators still have the same issues in small batches......

Posted
34 minutes ago, SteveCZ said:

My 2014 had the infamous radiator leak at the upper hose connection.  Got it replaced under warranty, with the same defective part and 6 months later, leaking again.  GM released an updated part number, but I already traded the truck in on a 2020.  I get the 2020 home and check the fluids the day after, and the coolant is low!  

 

C'mon Man!  


I top it off, and come to find out, it was just an air pocket in the heater core.  It burped and was fine since.  I do wonder if some of the radiators still have the same issues in small batches......

I had to do the same thing as I use to get that bubbling sound inside the cab at the heater core on start up on my 2019, I burped all the air out by just squeezing the top radiator hose and I could see the air bubbles going into the coolant tank I then had to add more anti-freeze and have not had the bubbling sound at the inside heater core since and that's been about 3yrs ago.

  • 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
  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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...