Jump to content

2014 Sierra humming noise

Oli4

By Oli4
in Troubleshooting & Recalls

Recommended Posts

RM4665 Enthusiast

RM4665

Posted
Posted

Update. I had this issue and took it to the dealer. They isolated it to the driveshaft, replaced it and it's 98% better.

  • Replies 150
  • Created
  • Last Reply
RM4665 Enthusiast

RM4665

Posted
Posted

Probably. I'm debating having a local shop balance the drive shaft to get the last little bit out of it, they pulled another driveshaft off a truck they had in the lot. If I wasn't tuned into it, I probably would not notice what it does now. Ill either forget about it, or it'll bother me forever. It'll cost me $200 to have it taken out, balanced and put back in.

 

Then again, what's left may not even be it. Vibrates about the same speed range.

Oli4 Enthusiast

Oli4

Posted
  • Author
Posted

So you're saying it is still there? After they replaced the drive shaft? Almost going in for my first service.

RM4665 Enthusiast

RM4665

Posted
Posted

It is, but really negligible. If you weren't looking for it you you probably would not notice it. My guess is either this driveshaft is off a little as well or there is something else going on.

C6 Doberman Enthusiast

C6 Doberman

Posted
Posted

I have the same issue at highway speed. I drove another truck on the lot and it did the same thing. My truck has a steel Driveshaft and the other truck had an aluminum shaft. Same frequency and interval with the noise.

RM4665 Enthusiast

RM4665

Posted
Posted

After the last couple days I think I'll just ignore it. I forgot to pay attention to it on the way to work this morning and didn't notice it. I'll just make a punch list for the dealer of items when I go in for service next time, hopefully its a short list.

UCR New Member

UCR

Posted
Posted

I'm new to this site. I have a new 2014 Silverado LTZ Z71. I get that same humming noise. 1 sec hum 1 sec pause and so on. I'm glad im not crazy and others have heard it as well. Took mine to the dealer today for first service. Two mechanics drove it and never heard it. But they did fix two recalls and change oil. Not sure what to do with noise. Last Chevy before this was lifted to the sky and roared I would have never heard anything but the tires. These things are just to quite of a ride so its easy to pick up on things. Other than that its a great ride and I love it. If anyone finds a answer to the hum Id love to know. I feel like with this being the newly designed trucks the bugs are going to have to get worked out.

RM4665 Enthusiast

RM4665

Posted
Posted

I'm not so sure what you're talking about is not the below, to a lesser degree after looking around a little bit, but what do I know. If the Torque Converter was bad / getting bad signals, just not as bad as the next guy, maybe you'd just get a hum noise instead.

 

brandon1282, on 14 Nov 2013 - 14:34, said:snapback.png

Update: Just was informed that GM has advised the dealership to change out the Torque converter and the Transmission Control Module. My truck should be ready on Tuesday. In the mean time they have given me another 2014 sierra as a loaner....I am interested to see if in the time I have this truck if I notice the same vibration.

 

As far as tires go, I think we may be talking about two different issues here. The problem I am experiencing (as well as some others on this thread) is intermittent at speed, not a continuous vibration that occurs above a certain speed. If the later is the case, then yes I agree, the first thing I would look at is a problem with tires (or possibly the drive shaft). The problem I am having does not occur every time I am at a certain speed or operating under the same conditions (i.e. it only seems to happen under moderate power between 50 and 65, but does not occur everytime I am under moderate power between 50 and 65).

 

As always, I'll keep you posted of the findings/results.

Just to update everyone on the rumble strip vibrations I was experiencing. I got the truck back 2 days ago and so far so good. Here is what the dealer reported:

Road tested vehicle and found possible tire/wheel vibration. Removed all four wheels and road force balanced to find one tire out of range. This tire was replaced and then vehicle was road tested again. The vibration improved but was not eliminated. Checked for TSB's and none were found that directly addressed this concern. Contacted TAC and TAC suggested to utilize TBS PIP5149B. I followed all instructions of this TSB, checking for excessive spark retardation and connecting rod oil squitter condition. There were no conditions observed. TAC then directed me to utilize DOC ID#2102430 where I checked the operation of the control solenoid within the transmission. When commended to the on position, It registered full pressure and when commanded off it registered 0 pressure. After completing all tests found that TCM could not be 'pulse-width' tested, only command on or off. With these measurements we determined that the TCM was sending an erratic signal causing the torque converter to be commanded erratically. This caused potential damage to torque converter. Therefore, I replaced the TCM (Signal) and torque converter (damaged internally). Road tested vehicle; now operating to GM specifications with no vibration when tested under the original conditions.

I have also noticed that the "floating Tac" condition I had earlier is no longer present.

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted

Hello RM4665,

I'm very happy to hear the dealership was able to get this vibration addressed for you! Let us know if anything changes.

 

If anybody else would like us to assist in getting them set up with their dealership please reach out via PM with your full name and contact information, VIN, current mileage, and preferred dealership.

Sincerely,

Jonathan A.
GM Customer Care

UCR New Member

UCR

Posted
Posted

Well I did try something I had heard on this topic. I can shift to 4wd auto and hum goes away. That's crazy and now concerns me. I would love to know how it goes when you get yours out of shop.

RM4665 Enthusiast

RM4665

Posted
Posted

It actually wasn't me, it was Brandon1282. I another post he said it fixed the proem he was having though. I quoted him.

  • 4 weeks later...
Oli4 Enthusiast

Oli4

Posted
  • Author
Posted

Here's an update from the Canadian side of the border.

I went in for my first oil change this morning.
I talked about the noise with my service department. They took the truck out for a spin and the tech heard the same noise as I did (yay I'm not loosing it). He came back, took another truck out for a spin (I assume another 5.3L). Same thing. It had the same noise.
He then called GM (I assume GM Canada) but there they had not heard of the issue as of yet.

The tech acknowledged the noise and called it a 'normal operating noise' (he even did the air quotes). The issue is now documented in my paperwork but as of now they don't want to throw parts at it. They asked me to monitor it and call them when it gets worse.

Archived

This topic is now archived and is closed to further replies.

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