Jump to content

Paint chips and corrosion on 1 month old truck

DrPontiac
 Share

Recommended Posts

DrPontiac Enthusiast

DrPontiac

Posted
Posted (edited)

I purchased 2024 sierra 1500 AT4 June 20 2024 and already paint is chipping very easily off both front and back bumpers, the running boards are down to bare metal and lug nuts are starting to rust. 
Everything is stock from factory. 
has anyone heard or dealt with anything similar? 
my last 2015 hd had 200k on gravel roads and I could count the chips it had on one hand. 
the chips on bumpers are down to primer and looks like no adhesion. 

IMG_3073.jpeg

IMG_3075.jpeg

Edited by DrPontiac
gemarsh Senior Enthusiast

gemarsh

Posted
Posted

Those assist steps are aluminum so they won't rust atleast. I have the same and that corner will get worse. I am leaving the mud that will accumulate in that corner as a wear stoppage. 🤓

  • Haha 1
DrPontiac Enthusiast

DrPontiac

Posted
  • Author
Posted

The plate is definitely aluminum however there is rust already starting where I washed it yesterday in the corners

Bikerjon Enthusiast

Bikerjon

Posted
Posted
4 hours ago, DrPontiac said:

IMG_3076.jpeg

No paint chips or rust on my Trail Boss. At 5500 miles. No chips or rust on my last TB either. 2021 w/20,000.

newdude Senior Enthusiast

newdude

Posted
Posted

Did you buy this thing used???  All the acne in the first picture, it looks like bad paint work.  

 

The nuts "rusting", use some good wheel cleaner like Adams Polishes that will get rid of the "rust" which is most likely rail dust or brake dust.  

  • 4 months later...
silveradosid Senior Enthusiast

silveradosid

Posted
Posted (edited)

do you do a lot of highway driving, most of my driving is highway and it seems like bugs can chip the paint off at high speeds. i am at 90k miles and will be repainting my front bumper next summer, waiting for winter to be over when they stop using rock salt on the roads

Edited by silveradosid
BigGuy MDU Enthusiast

BigGuy MDU

Posted
Posted

I don't have a lot of rust on mine yet,  but my 24 silverado is filled with rock chips.  Most of them are down the sides of the box.  I do a lot of gravel road driving though so I kind of expected it.  Never should have gone with a black truck lol

redwngr Senior Enthusiast

redwngr

Posted
Posted (edited)

Do you have the mudflaps and the wide flat running boards to help with the gravel road issue?

 

image.thumb.jpeg.2e76b5e5d9e1bbbea838a6a30bf0a313.jpeg

 

 

Edited by redwngr
Z45 Senior Enthusiast

Z45

Posted
Posted

If you expect perfection then park it in the garage and never drive it.

  • 3 months later...
Dan208 New Member

Dan208

Posted
Posted

I have a 2024 GMC SIERRA SLT which is summit white in color. My truck has 15,000 miles on it and the paint is chipping along the door edges in areas that are not touched by hands or anything else. You can see the gray primer which looks to be pristine. This is frustrating as I have NEVER experienced this with all of my previous GM vehicles. I have an appointment with the dealer and am hoping to get this rectified. Will keep you posted. 

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted
On 4/17/2025 at 8:08 AM, Dan208 said:

I have a 2024 GMC SIERRA SLT which is summit white in color. My truck has 15,000 miles on it and the paint is chipping along the door edges in areas that are not touched by hands or anything else. You can see the gray primer which looks to be pristine. This is frustrating as I have NEVER experienced this with all of my previous GM vehicles. I have an appointment with the dealer and am hoping to get this rectified. Will keep you posted. 

We know how upsetting paint concerns can be. Although no outcome can be guaranteed, we are happy to learn more and get you into a service center. Please reach out to us via email at [email protected], and be sure to include your VIN in your email. By sending us a message, you consent to the information you provide being monitored and recorded by GM or those acting on GM’s behalf, subject to the GM Privacy Statement: https://www.gm.com/privacy-statement.

Dan208 New Member

Dan208

Posted
Posted

My dealership has touched these chips up. It doesn't look like the original paint job (rough finish) but at least they're trying. We'll see how long it lasts. Disappointing - 

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

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...