Jump to content

Annoying Rattle, Behind Passenger dash or firewall

eppieguy
 Share

Recommended Posts

eppieguy Senior Enthusiast

eppieguy

Posted
Posted

Has anybody experienced a rattle coming from the area of the passenger side dash, behind it, or passenger side firewall area? It's possibly the cowl under the windshield but not sure. I've gone around trying to bang on things with my hand to try to find something loose but no luck yet. It only happens with speeds over 35-40 MPH and seems to get louder the faster you go. I hate to take it to the stealership and have them just start taking things apart and create more rattles down the road. Any ideas would be appreciated.

  • Replies 40
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

KC-BG
KC-BG

That's exactly how I described it at times....as if two incredibly loud pieces of Styrofoam were being rubbed together. I was told it on the driver's half of the firewall but I do not know the exact l

Posted Images

BIGDOGx Senior Enthusiast

BIGDOGx

Posted
Posted
7 minutes ago, eppieguy said:

Has anybody experienced a rattle coming from the area of the passenger side dash, behind it, or passenger side firewall area? It's possibly the cowl under the windshield but not sure. I've gone around trying to bang on things with my hand to try to find something loose but no luck yet. It only happens with speeds over 35-40 MPH and seems to get louder the faster you go. I hate to take it to the stealership and have them just start taking things apart and create more rattles down the road. Any ideas would be appreciated.

I know i have been dealing with a super annoying rattle in my dash area and thought for sure it was on the upper part but i ended up holding the plastic cover directly under the steering column and the noise stopped. A quick search on the net turned up this video..

 

Pretty much shows how lose some of the bolts holding these trim piece can get, i know this is the older model truck but i would not doubt if the pieces used are very similar since the interiors are nearly identical from 14-to current.

eppieguy Senior Enthusiast

eppieguy

Posted
  • Author
Posted

I will have to start digging around under there, thanks for the suggestion.

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted
1 hour ago, eppieguy said:

Has anybody experienced a rattle coming from the area of the passenger side dash, behind it, or passenger side firewall area? It's possibly the cowl under the windshield but not sure. I've gone around trying to bang on things with my hand to try to find something loose but no luck yet. It only happens with speeds over 35-40 MPH and seems to get louder the faster you go. I hate to take it to the stealership and have them just start taking things apart and create more rattles down the road. Any ideas would be appreciated.

Hi, Drew. We hope you're enjoying your Silverado High Country with the exception of this dash rattle. If you're thinking about stopping by your dealership for an evaluation, we would be happy to provide an additional layer of assistance. Please keep us updated via private message if and when this rattle disappears. 

 

Anthony J.

 

eppieguy Senior Enthusiast

eppieguy

Posted
  • Author
Posted

Found it....... I guess GM was trying to save a penny, missing bolt that holds right front mud flap to body, the fender nut was rattling on the fender with no bolt in it, put a bolt in it, noise is gone. 

O Town Denali Enthusiast

O Town Denali

Posted
Posted
10 hours ago, eppieguy said:

Found it....... I guess GM was trying to save a penny, missing bolt that holds right front mud flap to body, the fender nut was rattling on the fender with no bolt in it, put a bolt in it, noise is gone. 

Good detective work.  Rattles drive me nuts. Luckily I am rattle free right now.   Glad you found yours.

cltsig Enthusiast

cltsig

Posted
Posted

I have also developed a grindy squeak, drives me nuts.  Happens pretty much constantly.  It seems to be under the radio area but hard to tell.  Grrrr...

NRBRGRNG New Member

NRBRGRNG

Posted
Posted

I have a  2019 Sierra Denali.  I have a similar rattle in my truck.  I only have 200 miles on it and it's driving me nuts.  

 

I thought it was the dash but now i'm localizing it to somewhere around the start button where panels come together.  Still haven't found it. 

NRBRGRNG New Member

NRBRGRNG

Posted
Posted
On 2019-01-14 at 12:51 PM, cltsig said:

I have also developed a grindy squeak, drives me nuts.  Happens pretty much constantly.  It seems to be under the radio area but hard to tell.  Grrrr...

I have the same issue.  It's somewhere around the region of the start button on one of the adjoining panels.   I only have a 150 miles on my Denali so i haven't had enough to time to pinpoint the exact location.  


I have been under the dash and screws "seem" tight so far on everything i checked out.

  • 3 weeks later...
Eljeffe316 Enthusiast

Eljeffe316

Posted
Posted

I have a brand new AT4 with 500 miles and the exact same squeak. Also drives me crazy but seems to happen when pressing the gas pedal.  Can’t figure it out but don’t want my dash torn apart...

cltsig Enthusiast

cltsig

Posted
Posted

I’m dealing with it until I can get in for my first oil change. Still there. It seems to squeak when the truck frame torques either way so I’m guessing it is near the firewall. That area is packed tight and nothing visible seems loose so it appears to buried.


Sent from my iPhone using Tapatalk

KC-BG New Member

KC-BG

Posted
Posted

I have this same squeaking with my AT4. 2,000 miles on it currently, but it has been doing it since around 300 miles. I agree that the squeak happens when the frame moves and appears to be coming from behind the climate controls, which is adjacent to the push button start. After one unsuccessful attempt to locate it by the dealer, I removed the majority of the console and center stack. Still could not pinpoint exactly where it was with the duct work in the way, but it was significantly louder. I am also guessing it at or close to the firewall. It is back at the dealer for round 2. 

BeardBros Enthusiast

BeardBros

Posted
Posted
On ‎1‎/‎14‎/‎2019 at 12:51 PM, cltsig said:

I have also developed a grindy squeak, drives me nuts.  Happens pretty much constantly.  It seems to be under the radio area but hard to tell.  Grrrr...

I have the same squeak under my dash. Like yours, I think mine is coming from the same area. I cannot reproduce it with out driving so it requires something under there to flex. So since it is a squeak I have been looking at the rubber and hard plastic parts. No fix yet.

  • 1 month later...
KC-BG New Member

KC-BG

Posted
Posted

Finally after 51 days at the dealer, a GM Field Engineer figured out the issue. There is a harness near the firewall on the engine bay side that was rubbing causing the squeak. They had to drop the drive shaft to get to it.

cltsig Enthusiast

cltsig

Posted
Posted
Finally after 51 days at the dealer, a GM Field Engineer figured out the issue. There is a harness near the firewall on the engine bay side that was rubbing causing the squeak. They had to drop the drive shaft to get to it.

Sounds like what was diagnosed with mine. Some type of wiring harness near bell housing in front of tranny. Mine didn’t require the driveshaft to be dropped though.


Sent from my iPhone using Tapatalk

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   6 Members, 1 Anonymous, 1,658 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...