Jump to content

How many miles do you have on your 6.0 liter motor?

john857

Recommended Posts

wellinghurst Enthusiast

wellinghurst

Posted
Posted

2003 with 42k-although only 10k the past 2 years (company car)

 

Only trouble is the steering shaft and recalls on tailgate cables and rear seatbelt. I got my scratched up tailgate repainted for free with the cable recall, so that was a nice add-on.

 

As soon as my extended warranty is up next year, can you spell SUPERCHARGER....

 

The my name will be veryblack+verylong+veryfast

 

This is the best toy I've ever bought!

  • Replies 319
  • Created
  • Last Reply
john857 Enthusiast

john857

Posted
  • Author
Posted
2003 with 42k-although only 10k the past 2 years (company car)

 

Only trouble is the steering shaft and recalls on tailgate cables and rear seatbelt. I got my scratched up tailgate repainted for free with the cable recall, so that was a nice add-on.

 

As soon as my extended warranty is up next year, can you spell SUPERCHARGER....

 

The my name will be veryblack+verylong+veryfast

 

This is the best toy I've ever bought!

john857 Enthusiast

john857

Posted
  • Author
Posted

Hi all,

 

Just wanted to thank all of you for your input on the number of miles you put on your trucks. It really is good to know that most of you are having very good reports on the the 6.0 liter motor. I hope I have the success that you are having. I only have one major complaint and that is with the leather seats. Mine are coming apart and I have not put any hard use miles on this truck. It has not been used as a work truck mostly used to tow my boat. The leather seems to be very thin - anyway was not covered by warranty. Thanks again. John (second try - must have hit the wrong key)

Engineer Enthusiast

Engineer

Posted
Posted

My wife's truck has just short of 60K on it's 6.0, no issues. Just a little csk.

 

We bought her truck with 54K on it, however, I know the previous owner and his only complaints were replacing the A/C switch on the A/C receiver dryer twice.

 

I have towed my gooseneck trailer with a Bobcat on it behind her truck, approx 10,500lbs, and it motored on like a champ.

 

We probably will have this rig for a long time.

 

My wife's dad however, has a GMC with the 4.8L engine. Essentially the same engine as the 6.0L, and his truck is approaching well over 150,000mi.

 

GM hit a homerun with the 6.0L engine, it is a shame they struck out in their next at-bat by discontinuing the 8.1L engine.

ssorone New Member

ssorone

Posted
Posted

Only 4000 miles on mine, and I must say that it sure is lagging in the power department! Is there anything that you can do to wake these things up? I know its got the power locked up in there somewhere, I need to find it.

ssorone New Member

ssorone

Posted
Posted

Only 4000 miles on mine, and I must say that it sure is lagging in the power department! Is there anything that you can do to wake these things up? I know its got the power locked up in there somewhere, I need to find it.

chevyfan05 Enthusiast

chevyfan05

Posted
Posted
I was just curious as to how many miles some of you have on your 6.0 liter motors without any problems. With the cold engine knock etc, it would interesting to here how many miles you have on this motor. Thanks for your input.

 

i have 22k miles on my 6.0 and it has never had a knock

DownhomeVA Enthusiast

DownhomeVA

Posted
Posted

Sittin at 41,000 on my 02 2500hd. engine has started making "funny" noises recently, i thought it was because i drove it too hard a couple days. I haven't decided if I'm going to take it in for a check up or not. most of the noise is when the engine is cold. haven't had any problems at all though to speak of!

Happy Enthusiast

Happy

Posted
Posted

Have 13,000 on my 2005. Had to replace water pump about 12,000. Dealer said it was not normal. Hope he is right. Anyway, I love my truck. So much better than my old 1985 Dodge. Of course the Dodge didn't cost me near as much either.

ldposse New Member

ldposse

Posted
Posted

I'm at 186,9xx miles on my '01 2500HD. I bought it about a month ago with 185,443 on the clock. The 6.0L has a little cold start knock, but it runs great. If there is one good thing about GM, they sure know how to build a gas pushrod V8! I also have a 2002 Trans Am that I bought new, it is equipped with the LS1, and with 63k miles of dealing with my heavy right foot, runs as good, if not better than the day I drove it off the lot!

  • 3 weeks later...
s10473 Enthusiast

s10473

Posted
Posted

I have 48,249 on my 03 with a 6" Lift, Supercharged and no problems as of yet. Hopefully this trend will continue.

  • 1 month later...
cvandegna Enthusiast

cvandegna

Posted
Posted

Rolled 48,000 yesterday on my '04. Been lifted since 1,600 miles. Always towed 50%. (Last week dragged my 7000# RV up a 2 mile 50% grade after a 250 mile highway tow = 2 MPG inst fuel econ WOOOHOOO!)

  • No engine/drivetrain issues (other than CEL recently because of dirty MAF)
  • Paint worn off radio buttons
  • Passenger power window motor on last leg
  • Me thinks am developing the dreaded steering clunk

I wish GMs trim and other mechanical items held up as good as the powertrain now does... Let's see if the tranny will make it past the old 75K threshold.

anealysr Enthusiast

anealysr

Posted
Posted

I got 164k on mine. Runs great but of course I have the cold knock too, I just let her run for a minute or so before driving her.

Archived

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

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