Jump to content

Whirring / Whining Noise 6L80

movario

By movario
in Troubleshooting & Recalls

 Share

Recommended Posts

movario Enthusiast

movario

Posted
Posted

Hi

 

I have that whining/whirring noise in the video when idling. No other issues, no fault codes. It comes on and off, and is only noticeable when idling. It comes from the rear part of the transmission. TC is new. Oil is also new.

 

Any ideas?

 

 

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

Does it change if it's neutral or in gear?

 

Kinda sounds like a solenoid/pump turning off, changing pitch and turning off. Beats me if that transmission related or not.

  • 2 months later...
SavageSierra Enthusiast

SavageSierra

Posted
Posted
On 2/24/2022 at 4:52 AM, movario said:

Yes, it's there in P and N, and goes away as soon as you are in D or R.

Mine has the exact symptoms. Did you figure out what it was? Torque converter?

movario Enthusiast

movario

Posted
  • Author
Posted
34 minutes ago, SavageSierra said:

Mine has the exact symptoms. Did you figure out what it was? Torque converter?

 

No, is still there. Torque Converter is new. I suspect that the problem is with worn checkballs in the valve body. Those are made vom plastic and get worn over time. I think that those let a little fluid pass by which causes the noise.

  • Haha 1
SavageSierra Enthusiast

SavageSierra

Posted
Posted

I appreciate the reply.
 

My truck is going to a transmission shop in a couple days. It has been whining like the video for about a month. It just started shuddering a little bit too.

 

I dropped the pan and there was no metal floating around just “normal” amounts on the magnet. I also changed the filter and have been driving it for two weeks with no improvement. 
 

We’ll see what the shop says about the shuddering and whining. Might be time for torque converter. I’ll post an update once I know more. 

OffTheAir Enthusiast

OffTheAir

Posted
Posted

Hi all,

This is going to sound absolutely crazy, and I can't verify if it is related or strictly a coincidence, but I was experiencing this noise last Fall and it was resolved after I replaced my exhaust manifold bolts (had three broken on the passenger side). I can't imagine why such a noise would be produced, but I hope this information is of use and can shed some sort of light.

For context, my situation was the exact same, I experienced this noise pretty much every day at idle, and it went away after I drove off. I couldn't figure out what it was and it seemed harmless so I kind of just endured it, even though it was annoying. Later in the year when it got a little colder and I got the "chattering" noise, I pinpointed the bolts and ever since that repair the noise has never come back. I guess I figure there must be some sort of connection because quite literally all I did was replace the bolts on the passenger side, nothing else.

 

Hopefully this information helps. I can say with certainty I do not believe this is a torque converter issue.

 

 

pokismoki Senior Enthusiast

pokismoki

Posted
Posted (edited)

the PR valve has been having issues on these transmission, could be a worn valve or the pump face surfaces are worn too..

Edited by pokismoki
movario Enthusiast

movario

Posted
  • Author
Posted
19 hours ago, OffTheAir said:

Hi all,

This is going to sound absolutely crazy, and I can't verify if it is related or strictly a coincidence, but I was experiencing this noise last Fall and it was resolved after I replaced my exhaust manifold bolts (had three broken on the passenger side). I can't imagine why such a noise would be produced, but I hope this information is of use and can shed some sort of light.

For context, my situation was the exact same, I experienced this noise pretty much every day at idle, and it went away after I drove off. I couldn't figure out what it was and it seemed harmless so I kind of just endured it, even though it was annoying. Later in the year when it got a little colder and I got the "chattering" noise, I pinpointed the bolts and ever since that repair the noise has never come back. I guess I figure there must be some sort of connection because quite literally all I did was replace the bolts on the passenger side, nothing else.

 

Hopefully this information helps. I can say with certainty I do not believe this is a torque converter issue.

 

 

Thanks, i'll check on that.

 

4 hours ago, pokismoki said:

the PR valve has been having issues on these transmission, could be a worn valve or the pump face surfaces are worn too..

 That's something I also consider. But that would mean transmission out again :(

  • 2 months later...
Romereo34 New Member

Romereo34

Posted
Posted

Have you had any luck figuring out the noise? My truck just started doing same thing a week or so ago. No clue where to even start but it’s driving me insane already. And it doesn’t do it all the time. Sometime It will when I put in park and sometime it doesn’t. Beats me 

  • 1 month later...
mike1993420 Enthusiast

mike1993420

Posted
Posted

Interesting you mentioned checkballs I recently changed my checkballs with "better" brown ones and also I was missing the number 4 ball so I added it in put everything back together and have the same whirring noise loud in park and neutral and quiet in driver and reverse!! Did u ever figure it out???

  • 1 month later...
movario Enthusiast

movario

Posted
  • Author
Posted

So, I replaced the valve body and still no difference.

 

BUT after replacing, I accidentially overfilled the transmission slightly. And the noise was almost always there and much louder. After I corrected the fluid level to the correct HOT level, the noise was back to normal.

 

So I suspect it has something to do with the fluid. Someone mentioned he changed the transmission oil to another manufacturer, and that solved the problem. I used Ravenol Oil (German Manufacturer) with Dexron VI specification. But maybe I should try AcDelco/GM Genuine?

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

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