Jump to content

Paint Cracking 2007 H3

Eddie 70

Recommended Posts

Eddie 70 Senior Enthusiast

Eddie 70

Posted
Posted

I know this is not a hummer forum but I know you guys are pretty well informed about GM vehicles which the H3 is. I have a problem with my wifes H3. We bought it new, still had the plastic protectors on the paint when she picked it out. I do not obsess about keeping this truck spotless but do wash and dry it about once a month or so to keep it looking nice. Lately I have been noticing the paint is cracking on the hood and roof. This has me worried. Has anyone else with a GM vehicle had this kind of experience with the paint on their GM vehicle.

 

Any thoughts or experiences would be greatly appreciated.

pm26 Senior Enthusiast

pm26

Posted
Posted

What color is the vehicle? Can you tell if it is the clear coat on top, or the base coat underneath that is cracking? Are the cracks isolated or continuous? Seems like a paint defect that will probably require refinishing the affected parts. I would take it to a GM dealer and get their opinion on it. Your basic warranty is probably expired, but they may be willing to do something for you.

 

I would get some polishing compound or scratch remover wax and hand buff the cracked paint just to see if I could buff out the cracks. If they are all the way through the clear coat, then repainting is necessary.

Eddie 70 Senior Enthusiast

Eddie 70

Posted
  • Author
Posted

DSC05648.jpg

 

She still loves her truck and I am so glad she does even with todays gas prices and the MPG it gets. She only drives 5 miles or so to work so its not so big of a detriment to her, yet.

 

I am pretty sure it is in the clear that is cracking. Its killing me. I want the truck to be as good as it can be. I will take a few pics of it tomorrow and post them up for us to diagnose.

 

 

Thanks for the input already.

pm26 Senior Enthusiast

pm26

Posted
Posted

I almost bought one of those vehicles myself about 3 years ago when they were selling out the last remaining models. This one was a new left over with a 5 speed manual transmission, it was in California, and listed on eBay at a super low price. With my GM card rebate I could have bought it for $ 19k and change (there was buy-it-now option). Somebody beat me to it though. And I was somewhat concerned about bad fuel economy too and frankly I did not really need a full time 4WD vehicle.

 

I am surprised about the paint issues. I have two GM vehicles (2006 and 2009) and no paint problems with either. Maybe it is only certain colors that they have issues with.

BlackZ71Silverado Senior Enthusiast

BlackZ71Silverado

Posted
Posted
DSC05648.jpg

 

She still loves her truck and I am so glad she does even with todays gas prices and the MPG it gets. She only drives 5 miles or so to work so its not so big of a detriment to her, yet.

 

I am pretty sure it is in the clear that is cracking. Its killing me. I want the truck to be as good as it can be. I will take a few pics of it tomorrow and post them up for us to diagnose.

 

 

Thanks for the input already.

 

That's a good looking H3 she's got there. If I did not need a truck, I would have went with an H3. Great little suv's IMO.

  • 2 weeks later...
unit731 Senior Enthusiast

unit731

Posted
Posted

Is the vehicle garaged?

 

Are you positive that the vehicle has not been repainted? Hail damage from another part of country?

 

Any environmental issues where vehicle is parked?

Archived

This topic is now archived and is closed to further replies.

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   4 Members, 0 Anonymous, 592 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...