Jump to content

2021 Sierra 2500HD Wind Noise

Bobb Thompson
 Share

Recommended Posts

truck27 Enthusiast

truck27

Posted
Posted

JMac72 let me know what they figure out please, I'd like a cleaner solution other than blue tape.  Ironically when I tried using clear smooth 3m tape in place of blue paint tape, the whistle came back.  From what I hear, GM moving onto the next model year and most likely no other updates will come out for 21 model.

KIMG8606.JPG

  • 1 month later...
  • 11 months later...
H20ENG Enthusiast

H20ENG

Posted
Posted

I noticed this for the first time yesterday. Mine is a 2022 gasser so the hood is slightly different than the diesels. Not sure if it's any different at this interface however.  Noise was loud at anywhere from 50 - 80mph and it seemed to come and go, likely with wind direction. Tried folding in the mirrors, running the wipers, etc but it stayed constant so likely this hood seal issue.

 After reading this thread I may try to put foam weather strippping behind the rubber seal to maybe help it stay pressed tight. Need to let everything dry out and get in there to see what options I have.

  • 2 weeks later...
GMC4Zee Enthusiast

GMC4Zee

Posted
Posted

My noise is still there with the mirrors retracted so its not them. Mine is more of a whistle. When it gets warmer out I will try the front hood tape. That may not be for a few weeks as we are in winter here in the NY.

  • 4 weeks later...
DuramaxGuy New Member

DuramaxGuy

Posted
Posted

I had a relatively annoying wind noise coming from my passenger side.  I ultimately had two issues.  The first was the "felt" board that was against the firewall on the passenger side was slightly misaligned.  After making the adjust the wind noise went down considerably, but was still present on the passenger side.  After doing a thorough look over around the passenger side, I saw my clearance light above the passenger side was not snuggly secure to the cab.  Although the water tight seal was there, I had about an ⅛" gap.  So I dropped the head board and tighten the screw securing the clearance light.  After the adjustment, the light fit flush and was tightly secure.  Took it for a test run up to 80mph and absolutely no wind noise on the passenger side.  The air noise sounds consistent all around and about the same as any other vehicle.  So if you are having this issue and you have clearance lights, take a took and make sure they are tightly secured.

  • 1 month later...
JVictor New Member

JVictor

Posted
Posted

I have the 2023 GMC Sierra 2500HD gas and the whistling noise is for sure coming from the marker lights on top of the cab.  I will have to pull the liner and tighten those.  I haven’t noticed anything from the hood or grill area.  I’ll post an update to let you know if that fixed it. 

Jettech1 Senior Enthusiast

Jettech1

Posted
Posted

I hate that some are hearing wind noise in their trucks.  For some reason mine is quiet as a tomb.  No noise at all....I hope you all find out the culprit for your noise because I hate noises in any 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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • 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
    • davester
      Replacement Radiator

      By davester · Posted

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