Jump to content

Bad Rattling sound

dh0765
 Share

Recommended Posts

dh0765 Enthusiast

dh0765

Posted
Posted (edited)

My truck is a 2003 Silverado Z71 4x4, and has 70k miles on it. Alway's garage kept, etc. I have developed a problem with a really fast/loud rattling sound, and it only when traveling over really rough pavement or driveway. I think it has to be suspension related, but can't determine what it would be. The first time I heard it, I thought it was some type of gear stripping/grinding, but I now think it is rattling and has something to do with the suspension system. I know I am not being real clear on what it sounds like, but it is hard to describe. Like I said, it is a fast rattling sound, almost to the point it could sound like gears slipping/striping. Upon looking, the only thing I can find wrong is on the drivers rear side, the bump stop is missing. I can't imagine that is causing the sound I am hearing, as that should only have an impact if hauling something really heavy or doing something to bottom out the suspension. I am replacing it, but the other issue seems to be more critical right now. The only time I hear it is on really rough road or on a driveway with large rock that causes a lot of suspension jumping. Any ideas what this could be?

Edited by dh0765
nickc12 New Member

nickc12

Posted
Posted

My truck does the same thing, I'm a GM ASEP student and have been in a dealership for almost two years and from what I've seen its usually the intermediate shaft. Really not dangerous, but if the sound bothers you they run about 75$ online.

 

 

Sent from my iPhone using Tapatalk

dh0765 Enthusiast

dh0765

Posted
  • Author
Posted

Thanks for your reply nickc12! Its not the intermediate shaft sound, as I am aware of that clunk, and replaced mine some time back. This is a MUCH LOUDER rattling sound from under the truck. I can't stress how loud and serious it sounds. Sounds like it is from up under the rear of the truck. I think it is a rattling, but could almost sound like a gear grinding/sound. I really don't think it is gears though, and more like something with the suspension.

Gurrzt Enthusiast

Gurrzt

Posted
Posted

Let your ho out the tool box brotha (word)

dh0765 Enthusiast

dh0765

Posted
  • Author
Posted

Bump.... Anyone have any other suggestions of what this could be? I wan't to clarify that this is not a clunk sound. It is a loud rattling sound and only happens when I am on a really rough surface that shakes the suspension quickly.

cjb321 Enthusiast

cjb321

Posted
Posted

check the sway bar bushings like silveradosid said, i had an old regal that rattled and thats what it was.

Don'tGiveATruck Enthusiast

Don'tGiveATruck

Posted
Posted

My front brake calipers didn't have the little clips that the tops and bottoms of the brake pads ride along and that caused a bit of a rattle. It wouldn't rattle when I had my foot on the brake but when they were loose they made a bit of sound on rough roads.

  • Like 1
Nanotech Environmental Enthusiast

Nanotech Environmental

Posted
Posted (edited)

Any other suggestions of what I can look at?

It could be a couple things-

 

-The mounts for the lower rear shocks are not fully tight. If this is the case, they make a lot of noise from jostling over every single bump in the road, large and small. They need to be pretty tight, and the lower shock eye can come loose in the shackle mount over time and use. I had this happen recently, and was a bit flustered about what it was for a while. Once I found the cause, it took a couple minutes with a couple wrenches to tighten things back up. If you can wiggle the shock by hand, its too loose.

 

-Something is wrong with the rear springs, or spring mounts.

 

-You could have something going wrong in the rear axle/differential, which could be pretty serious.

Edited by 3beejay3
BlackZ71Silverado Senior Enthusiast

BlackZ71Silverado

Posted
Posted

If it's possible for you to post a video of this sound, you may get a few more responses. It is really difficult to diagnose a sound over the internet without actually hearing what's going on.

ifixedit Enthusiast

ifixedit

Posted
Posted (edited)

I know exactly what's making that noise. The 03's (and other years?) have that annoying steering column / steering shaft rattle / clunk that will develop / worsen over time. Yes, it does it over bumps, even on some fairly minor bumps, mine does it as well. It is supposedly due to lack of grease where the steering shaft pieces slip over each other somewhere under the hood. Mine has been more minor so I haven't investigated yet, but a friend had the same problem with his 03. Sorry I don't have all the details but I guess there's a bolt you can take out and slide things back and forth to get the grease where it's supposed to be and you can also then re-grease, put it back together and the noise will go away, although this is reportedly the more temporary fix. I understand there is /are replacement part(s) that fixes the problem permanently.

Edited by ifixedit
dh0765 Enthusiast

dh0765

Posted
  • Author
Posted (edited)

Olwhiskey - I checked the clips on the calipers all the way around and they are all fine, and everything is good and tight. No problems found on that.

Silverado 4x4 - I do have bars. I checked all fasteners and they are all good and tight. No problems found on that.

BlackZ71Silverado - I will have to do this and see if I can get something posted.

ifixedit - You are referring to the intermediate steering shaft clunk issue. It is not this. It is not a clunking sound, it is a loud rattle. I fixed the intermediate shaft issue years ago with the new part that fixed that issue.

Edited by dh0765

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

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