Jump to content

Recommended Posts

Posted

I just bought a new 2024 RST.  I have excessive wind noise at 50mph and up, coming from the top of the driver side A pillar.  Is fairly constant but then is more gusty sounding when it’s breezy out.  In addition, the driver door doesn’t seem to stop much sound.  When I pass cars, it sounds like the window is cracked open or the door seals are not doing their job…. 
I’ve been to the dealership 4 or 5 times.  All they do is have different technicians drive the truck and they say that it’s all normal wind noise for this type of truck.

I love the truck, looks great, rides and drives great, but the wind noise is killing me!  I’m at my end… if anyone knows of a fix or can make a suggestion, I’m all ears!

Posted
On 4/8/2024 at 3:23 PM, ScottyO said:

I just bought a new 2024 RST.  I have excessive wind noise at 50mph and up, coming from the top of the driver side A pillar.  Is fairly constant but then is more gusty sounding when it’s breezy out.  In addition, the driver door doesn’t seem to stop much sound.  When I pass cars, it sounds like the window is cracked open or the door seals are not doing their job…. 
I’ve been to the dealership 4 or 5 times.  All they do is have different technicians drive the truck and they say that it’s all normal wind noise for this type of truck.

I love the truck, looks great, rides and drives great, but the wind noise is killing me!  I’m at my end… if anyone knows of a fix or can make a suggestion, I’m all ears!

We regret to hear of the wind noise concerns you are having with your 2024 Silverado and would like to help investigate this further. To get started, please send us an email to [email protected]. Be sure to include your Username and Forum name in the subject line with additional details. We will watch for your email. 

  • 4 weeks later...
  • 6 months later...
Posted

I have a 2024 GMC Sierra 1500 crew cab and have the same complaint as described by ScottyO. Have only had it for about 8 weeks and have not taken back to the dealer because I expect the same response as described.

Posted

There is a tech bulletin out for this. I have same truck makes same wind noise as you are describing.  It has something to do with plastic collars or some bolts creating wind noise. 

  • 1 month later...
Posted

Still have not resolved the wind noise on my 2024 RST. I’ve test driven other new 2024 RSTs and Trail Bosses, and they all have a very similar wind noise.  I’ve have the front driver door seal replaced by my dealership, no improvement. I had the dealership check the service bulletin about the firewall, and apparently that issue was not the case with my truck.  
I’ve pretty much given up on fixing the wind noise issue.  The fact that I heard the same issue on other new 2024 Silverados, I believe it is an inherent manufacturing defect, related to how the wind hits the A-pillar or windshield area. I have a suspicion that GM reduced the thickness and or quality of the actual windshield glass.  Probably to reduce vehicle weight for better gas mileage and or save manufacturing costs.  
 

Anyone else find a solution?

  • 7 months later...
Posted
On 12/21/2024 at 5:58 PM, ScottyO said:

Still have not resolved the wind noise on my 2024 RST. I’ve test driven other new 2024 RSTs and Trail Bosses, and they all have a very similar wind noise.  I’ve have the front driver door seal replaced by my dealership, no improvement. I had the dealership check the service bulletin about the firewall, and apparently that issue was not the case with my truck.  
I’ve pretty much given up on fixing the wind noise issue.  The fact that I heard the same issue on other new 2024 Silverados, I believe it is an inherent manufacturing defect, related to how the wind hits the A-pillar or windshield area. I have a suspicion that GM reduced the thickness and or quality of the actual windshield glass.  Probably to reduce vehicle weight for better gas mileage and or save manufacturing costs.  
 

Anyone else find a solution?

I have never any had wind noise in any of my Trail Bosses 2021, 23 or 25.

Posted

Open the door, sit facing out and pull it back against your knees then grab top of door frame (window up) and pull towards you a wee bit at a time. I seen a body tech do that once for door wind noise, worked.

  • Like 2
  • 7 months later...
Posted

I have same wind noise problem on my 2023 Chevy Silverado 1500 on both drivers and passenger doors. Changed passenger door seal and still doing it. So frustrating hen you spend that kinda money on a new vehicle. 

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

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