Jump to content

2011 Chevy 2500HD was fixed.. But it sounds worse than before?

Keelay

Recommended Posts

Keelay Enthusiast

Keelay

Posted
Posted

Hi everyone, I know the last post I wrote was quite long so let me try and narrow this one down a bit. I actually received my truck back from the dealership yesterday (to my surprise). It had been snowing, with some rain for the past 24 hours so I decided to put it into 4WD. The front differential had just been rebuilt and I figured I would give that a shot as well. To my surprise, the driving noise was back and was louder than it had been before. Regardless of driving straight, making turns or whatnot, it was loud as hell. I know that there is a different feel and sound to a 4WD vehicle when the road conditions aren't necessarily bad, yet I had never (since the day I purchased this truck) had such trouble driving or heard such a loud noise coming from the front end. I am really curious to hear some ideas on what might be causing this? Also I should mention that the noise I am hearing is not the noise I am used to hearing while in 4WD. It sounded very much like grinding metal more so than a locked differential.

 

Thoughts?

 

Oh! Also, the GM dealer told me not to bring it back, saying that it was most likely just me. I wish I was joking, but that is exactly what I was told. This is not my first 4WD vehicle. I have driven forestry firetrucks that sound better when they are driving in perfect conditions in 4WD.

cparks555 Senior Enthusiast

cparks555

Posted
Posted

I couldn't tell you whats wrong with your truck, but I can tell ya the dealer can't say don't come back. I had my truck in four times in three months for trans problems, finally fixed it just to get rid of me. I suggest you keep on them, but nicely.

Big D's H D Enthusiast

Big D's H D

Posted
Posted

If all talks with your dealer don't fix the problem, your next call should be to the district rep for your dealer! Give him the complete

history of events,and the Don't come back statement told to you. Nicely tell him that you are a loyal customer and think that a company that was on the brink of Bankrupacy Should be treating it's Valued customers right! That dealerships quality rating will go down and they don't want that. I had a issue last year with my wifs envoy 2003 dash cluster it was replaced 4 years ago and quit again this year the dealer said not covered I called the district rep and they installed a new cluster Good luck Dave

Keelay Enthusiast

Keelay

Posted
  • Author
Posted

I got a call yesterday in the late afternoon and was informed that the front differential (which had just been rebuilt) blew out the rear seal. I noticed a crack in my transfer case which was leaking fluid everywhere. Any idea what might lead to a rear seal blowing and how this could affect everything behind it? Seems like a big deal. I know GM hasn't figured out what caused it, and still hasn't given me a diagnosis or idea of what even needs to be repaired. Just looking for some mechanical advice or hints as to what might have caused/be causing this problem on such a new truck.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

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