Jump to content

Recommended Posts

Posted (edited)

I have a 2011 Sierra 1500 4x4 and have noticed a banging sound when going over medium and large sized bumps.  I have narrowed it down to the rear shocks but they are not blown.  I have Bilestein 5000 shocks on all 4 corners and have removed the rear two a couple times to inspect them.  Some googling led me to a couple people that had the same issue but no results in fixing it.  One guy suggested that it's the mounts or bushings but I don't see anything wrong with mine.  Has anyone else had this happen to them?

 

I wanted to add that I have the heavy duty leaf springs from the factory and they are in great shape.  I recently replaced the spring insulators with new ones and made sure the u bolts were tight.

Edited by kyleag89
Posted

I have the same truck, same issue, but I've always attributed it to the leaf springs.  I put on new springs, was better (but not totally gone) for a while , now back like it was.  Same description as you, over medium or larger bumps like over uneven ground.  I sprayed the leaf spring bushings with WD40, silicone, that helps for a while then its back.  Dealer said I'd likely never get rid of it.  I think maybe he knew something.  Somewhere....somehow there is a fix for EVERYTHING.  But I've not found it.  Following

Posted

I did check the leaf spring bushings and shackles the noise is 100% coming from the shocks.  I have been investigating this noise for months and finally figured it out by driving on and off the curb in front of my house while a buddy kneeled down as close as possible to listen.  He pin pointed it to the rear shocks and sure enough if I hit the shock with the palm of my hand I can re create the noise!  To me it seems as if the bolts for the shocks that go through the shock bushings are too small.  With the shocks removed I put the bolts through the bushing sleeves and they have a lot of play.  I find it odd that this became an issue after driving 45k miles and there's nothing that looks wrong.  I don't want to replace Bilestein shocks that are still working to find out it didn't fix the noise.  I'm at the point where I might find something to insert inside the metal shock sleeve to close up the gap and insulate the metal to metal clang I'm hearing.  My first thought was to buy larger bolts that fit the sleeve better and drill out the holes on the truck to fit them but don't want to make an irreversible mod like that if not nessessary.

  • 3 weeks later...
Posted (edited)

My noise is a croaking sound.  It sounds to me like something dry.  This may sound like a dumb question but I'm wondering this:  If I take the rear shocks off completely and drive over some uneven ground to see if the noise disappears will it hurt to drive it just a short distance just to test it ? 

Edited by Jworks
Posted

no it won't hurt anything.  creaking/croaking is usually ball joints, but that's not in the rear

  • Like 1
Posted (edited)

Richard, yeah its in the back. I'm not 100% sure but now I'm thinking its not the shocks.  I see no signs of leakage. From what I see in online videos this is a long standing issue with GM trucks.  I think I'm going to wait till after Thanksgiving and order some of those Spring-Things (rubber inserts).  I'll risk the $45 to get rid of this dry groaning sound. It really stinks that GM doesn't even care to offer a fix for this. 

Edited by Jworks
  • 4 weeks later...
Posted

In my case I solved the issue 100%.  Last week I received the Spring-Things I ordered.  I put them on myself and no more creaking, groaning, squeaking.  It was the leaf springs rubbing together.  I had some doubts but I gave it a chance and purchased the things.  I'm glad I did.  Noise gone.  This can be done cheaper at about half the cost by buying the 1/4"  rubber sheets on Amazon for about $19 and cutting out the inserts yourself.  If someone decides to do this I would recommend cutting them out in the shape as the ones at Spring-Things.com and tie them in with Zip ties.

Posted

Mine was the rear shock bolts.  I cranked them down with an impact and then finished them with a 24" long 1/2" breaker bar and they loosened themselves!  It was just the lower bolts on both sides.  I took them out cleaned the threads up and applied some blue loctite and cranked them back down.  It's been good now for a couple months.  About 6 months ago I had some noises from my leaves and I used an old wood chisel to seperate the ends and then put some new pads in there.  I had a few extra laying around from an add a leaf kit I purchased awhile ago because it was on clearance for $35!  Came with long leaves that fit under the main leaf, 4 leaf clips, 2 center pins, isolation pads, and 2 shims.  Not bad for $35.

  • 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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...