Jump to content

'22 6.2L Can't Stop Whining

Anthony Bessel
 Share

Recommended Posts

Anthony Bessel Enthusiast

Anthony Bessel

Posted
Posted

I've been pulling my hair out trying to figure this out. My '22 6.2L has a very loud but very specific whining sound. 

 

What I know about the sound so far: 

  • Only occurs at 1600-1900RPM
  • The sound cannot be heard when outside the above RPM range
  • 100% dependent on engine speed
  • 0% dependent on wheel speed
  • Higher throttle angle makes the sound louder but the pitch remains the same
  • The sound does not occur in Park
  • The sound does not occur at speed, within the RPM range above, but with the transmission in neutral
  • 4WD mode has no effect on the sound

 

The sound itself is what I would expect to hear with a bad alternator or a worn ring/pinion. I've seen the bulletins on the 10L80/10R80 and I do understand that some whining noise is expected but my specific example is loud enough to overpower the radio, road noise, and Max Defrost with the windows up. It's slowly driving me insane. Enough so that I've started thinking about looking for something else. 

 

My dealer said it's a normal sound for the 6.2L but unfortunately I can't test that theory because 6.2L trucks are impossible to find on the lot without a name attached to them. I'm hoping someone here can chime in with their experience. 

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted
On 12/20/2022 at 9:54 AM, Anthony Bessel said:

I've been pulling my hair out trying to figure this out. My '22 6.2L has a very loud but very specific whining sound. 

 

What I know about the sound so far: 

  • Only occurs at 1600-1900RPM
  • The sound cannot be heard when outside the above RPM range
  • 100% dependent on engine speed
  • 0% dependent on wheel speed
  • Higher throttle angle makes the sound louder but the pitch remains the same
  • The sound does not occur in Park
  • The sound does not occur at speed, within the RPM range above, but with the transmission in neutral
  • 4WD mode has no effect on the sound

 

The sound itself is what I would expect to hear with a bad alternator or a worn ring/pinion. I've seen the bulletins on the 10L80/10R80 and I do understand that some whining noise is expected but my specific example is loud enough to overpower the radio, road noise, and Max Defrost with the windows up. It's slowly driving me insane. Enough so that I've started thinking about looking for something else. 

 

My dealer said it's a normal sound for the 6.2L but unfortunately I can't test that theory because 6.2L trucks are impossible to find on the lot without a name attached to them. I'm hoping someone here can chime in with their experience. 

This is certainly not what we like to hear, Anthony Bessel.  Please know, customer satisfaction is extremely important to us. Our team would be more than happy to take a closer look into the concerns with your truck. To do so, please send an email to [email protected] with ATTN: Anthony Bessel/GM Trucks in the subject line.

Please include your contact information, VIN, a brief description of your concern, and the name of your preferred dealership. We look forward to hearing from you. To learn more about GM’s Privacy Policy, please visit https://www.gm.com/privacy-statement.html. The information you provide may be monitored and recorded and is subject to the GM Privacy Statement.
 
Privacy Statement | General Motors
Your privacy is important to General Motors. This Privacy Statement addresses the personal information GM collects and how GM handles that personal information.
www.gm.com
 

Anthony Bessel Enthusiast

Anthony Bessel

Posted
  • Author
Posted

I found a Youtube video that demonstrates the sound. The link should take you to the 7:10 mark. As he pulls out you can see the tach. As the needle sweeps past 1500 to 2000 you can hear precisely what I'm talking about:

 

The difference is he only briefly enters that RPM range but for my style of driving I end up there often. 

 

 

Anthony Bessel Enthusiast

Anthony Bessel

Posted
  • Author
Posted

Does anyone else have this sound in their truck? I understand the 10L80 is going to exhibit some whining sound due to the nature of the design but in my case, the sound can overpower the defroster, radio, and road noise. I'm trying to understand if my case is normal or if there's something that needs looking at. 

briansol Enthusiast

briansol

Posted
Posted

i can't hear anything over his yapping in the video.  What exact second do you hear it?

 

I have something coming in too.  def not a belt or from the front of the truck.

 

seems to be behind me (rear drivers side).  high-pitched wine-like sound, but it's not rpm fluctuating.  it's either making it or it's not and it seems to be TPS controlled/activated.

 

i can only reproduce it when i'm driving slow (eg, with my wife and kids in the truck).  when i'm romping around solo, i never hear it because i'm in the throttle a lot heavier.

 

It's really 5% throttle, in the 20-50 mph range (observed)

same pitch regardless of speed or rpm (which tells me it might not be gear or diff wine at all).

 

 

When i park the truck i hear a similar high pitched noise for 20 seconds after turning it off.   I assume this is the fuel pump primer or something still running, but it's not the same sound.

  • 1 year later...
joshpen New Member

joshpen

Posted
Posted (edited)

I dont notice that specific whine in my 2022 Trailboss 6.2.  I do notice that it is not a smooth quiet idle compared to the multiple 5.3 litres I've had.  I do like the engine though.  But seems a little noisy.  The issue that is driving me crazy.  I am having a couple of strange issues.  I hear a prominent whine when dow shifting into lower gears and when down shifting it hunts for gears and have had it lurch and buck really bad. Especially if just driving normal or slowly.  Also happens if I have to stop quickly in traffic or if turning into another road and starting to accelerate etc.  It did it so bad the other day.  I thought someone hit me in traffic.  Is there a programming change for this.  Thinking torque converter to transmission issue.  The transmission to me got hotter than normal cruising in a car show this past summer.  It was like 95 degrees and high humidity.  Tranmission got to like 215 and was not towing.  Truck just hit 17,000 miles as time of this post.  Had 14k on it when transmission was a little warm.

Edited by joshpen
19 Denali ultimate Enthusiast

19 Denali ultimate

Posted
Posted

Stock air intake?  Check that all the clamps for all the air intake tubes/filter are tight.  I had a whine on my old Silverado that turned out to be from my new K&N FIPK.  I have a AFE momentum CAI and filter on my 6.2 but I don't get any noise.

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

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...