Jump to content

Recommended Posts

Posted (edited)

I wouldn't let what you read here deter you completely. Use this info to make informed decisions and test drive thoroughly, but don't be fooled into thinking this is wide spread. This forum represents a very small percentage of buyers. I, along with many others, don't have any issues. There's a valid reason your dealer didn't know about the problem.

I would love to believe this is not widespread, because that implies that there is something "wrong" with our vehicles compared to the rest. Which further implies that "defect" can be identified and fixed. Unfortunately, that really hasen't happened. I can only think of three reasons why....

 

1. GM isn't smart enough to figure it out. Hmmm - not a comforting notion.

2. GM doesn't give a crap to figure it out because only a small percentage of customers are complaining about it (note that the number of complaints and the actual number of vehicles with the issue may not be the same! Some folks may not even notice).

3. There is no fix. All these vehicles are the same and they all do it. (I realize there are lots of folks reporting on this forum that they do not have the problem. I also know that "noise" is a very subjective thing. Everyone has a different sensitivity to noise. A different threshhold of what they hear, and more importantly what "bothers" them. One person will be driven nuts by a noise, and someone else won't even hear it. And I'm sure GM is counting on that!!)

 

I can't say for certain that all vehicles have this issue. But, when you look at the number of views of this thread (well over 50,000!!), tells me there are alot of folks looking for information on the topic. I've never seen a thread so popular!! Can't be a coincedence.

 

But, there is noting I would like more then to be proven wrong with a solid, repeatable, permanent fix from GM. Until then, the jury is still out....

Edited by Wrench589
  • Like 1
Posted

Hey Sub, your truck had the issue without roof racks? You had roof racks installed and it went away? Is that accurate? I am getting desperate for a solution before I start a buy back again. I really want to love this truck...

 

To add to this, Anon has 2 or 3 of these vehicles and none of them exhibit the issue. He confirmed the first 2 have cross bars, but didnt say about the third.

 

I recently rode in a Tahoe LT that has cross bars, and I can definitely hear the noise and feel the pressure. So, not to encouraged to think the cross bars will solve it. That said, both cross bars were near the back of the vehicle, so it is possible there is an optimal location. Worth playing around with....

Posted

More reports of 'vibration' described on carcomplaints.com. No reports of 'pressure' - unsure if they are referring to the same problem.

 

--

Marc

 

Actually, I think this link is absolutely referring to the same problem. I maintain mine has the same "rough" ride and vibration, and like was said on that site, "you feel every pebble and bump" on the road. I also observe that when the road is extremely smooth, the vibration goes away and so does all the annoying noise and pressure sensation. Lastly, someone on that other site mentioned "reverberation" - definitely referred to sound/noise.

Posted

I would love to believe this is not widespread, because that implies that there is something "wrong" with our vehicles compared to the rest. Which further implies that "defect" can be identified and fixed. Unfortunately, that really hasen't happened. I can only think of three reasons why....

 

1. GM isn't smart enough to figure it out. Hmmm - not a comforting notion.

2. GM doesn't give a crap to figure it out because only a small percentage of customers are complaining about it (note that the number of complaints and the actual number of vehicles with the issue may not be the same! Some folks may not even notice).

3. There is no fix. All these vehicles are the same and they all do it. (I realize there are lots of folks reporting on this forum that they do not have the problem. I also know that "noise" is a very subjective thing. Everyone has a different sensitivity to noise. A different threshhold of what they hear, and more importantly what "bothers" them. One person will be driven nuts by a noise, and someone else won't even hear it. And I'm sure GM is counting on that!!)

 

I can't say for certain that all vehicles have this issue. But, when you look at the number of views of this thread (well over 50,000!!), tells me there are alot of folks looking for information on the topic. I've never seen a thread so popular!! Can't be a coincedence.

 

But, there is noting I would like more then to be proven wrong with a solid, repeatable, permanent fix from GM. Until then, the jury is still out....

Well said, and I think point 2, followed by point 3 are the most likely. I can't imagine many people test driving a vehicle(s), noting such a prominent issue and signing on the dotted line anyway. I sure wouldn't have. Sales of these things aren't slowing down and for good reason. I hope you guys get a resolution soon but I really think your 2nd point is why GM isn't running for their life here. My main point is that there is a difference, at least I beleive there is, between the affected Vehicles (minority) and the unaffected (majority). That in of itself would suggest a solution.

Posted

Hi all, new to forum, but not new to Chevys. I am in the market for a new tow vehicle for a new boat I have coming in the spring. I have had a 2007 ltz Tahoe and now a 2011 ltz suburban, both of which have been excellent high mileage vehicles for me. I am / was in the market for another ltz suburban but this thread has me completely freaked out over potential next purchase. I drove one today trying to hear what others on here have experienced, I did not replicate it with the one I was driving. My question is are the ones prone to this born with it so to speak and you hear the issue from day one, or does something "break" over time. The one I drove did not have the issues spoke of on this forum at present, but not sure if they will develop and admittedly the one I drove (build date of October 30 2014) does not have all of the options (and color) that I would like to have....any input on this is greatly appreciated as to what I might expect next.....thanks in advance for your guidance!!!!!!

From what we experienced, in October 2014 - we test drove 2 of the 2015 Yukon Denalis. One of them absolutely had the buffeting and it was so bad we couldn't continue the test drive. The 2nd one did not have it at all. We then test drove and bought the 2015 Escalade ESV and it did NOT have it. This was October 28th, 2014. However, on January 7th, 2015, the Escalade was left outside all day from approximately 7:00 AM until around 9 or 10 PM. The day was an extremely cold Illinois day, temperatures in the single digits. The ride home that evening was horrible - I attributed it to the cold tires as the tire pressure was extremely low. As the tire pressure came up, the buffeting did not go away, and from that day forward, the buffeting has been terrible. My current status is that my local dealer test drove it, noticed the buffeting and agreed to the roof fix, but we have not heard back that the parts have arrived so that it can be scheduled. So to answer your question, while I think they may be prone to it, something definitely happened to ours on January 7th, 2015 that caused this (My guess is the cold temperatures may have caused the separation) Prior to that date, the vehicle was silent on the inside.

Posted

From what we experienced, in October 2014 - we test drove 2 of the 2015 Yukon Denalis. One of them absolutely had the buffeting and it was so bad we couldn't continue the test drive. The 2nd one did not have it at all. We then test drove and bought the 2015 Escalade ESV and it did NOT have it. This was October 28th, 2014. However, on January 7th, 2015, the Escalade was left outside all day from approximately 7:00 AM until around 9 or 10 PM. The day was an extremely cold Illinois day, temperatures in the single digits. The ride home that evening was horrible - I attributed it to the cold tires as the tire pressure was extremely low. As the tire pressure came up, the buffeting did not go away, and from that day forward, the buffeting has been terrible. My current status is that my local dealer test drove it, noticed the buffeting and agreed to the roof fix, but we have not heard back that the parts have arrived so that it can be scheduled. So to answer your question, while I think they may be prone to it, something definitely happened to ours on January 7th, 2015 that caused this (My guess is the cold temperatures may have caused the separation) Prior to that date, the vehicle was silent on the inside.

Yes! I agree there is a variable in the vehicle that is causing some sort of "trigger" to the buffeting. My current Denali (1st was repurchased due to the problem you describe) was perfect for the first 250 miles or so. I know the sound and I know the feel. It was not there when I first got the vehicle...I would not have accepted delivery if it was present. Now, 1200 miles in, it is back with a vengeance just like my first one. Starting at the same exact speed as my first one...38mph. Coincidence? I doubt it.

 

Is it the frame? It really is the only true common denominator between the Tahoe, Yukon, and Escalade. While some have more features than others, or different sized tires, the frame is the same for all. Is it too rigid, then "breaks in" causing it, or the other way around? I don't know, I am not a car guy. I just play a very pissed customer on TV...

 

Either way, don't waste your time getting the roof repaired. It will make the same sound after the "repair." The only difference will be the greasy finger prints left all over your interior liner. Trust me, I know.

Posted

Yes! I agree there is a variable in the vehicle that is causing some sort of "trigger" to the buffeting. My current Denali (1st was repurchased due to the problem you describe) was perfect for the first 250 miles or so. I know the sound and I know the feel. It was not there when I first got the vehicle...I would not have accepted delivery if it was present. Now, 1200 miles in, it is back with a vengeance just like my first one. Starting at the same exact speed as my first one...38mph. Coincidence? I doubt it.

 

Is it the frame? It really is the only true common denominator between the Tahoe, Yukon, and Escalade. While some have more features than others, or different sized tires, the frame is the same for all. Is it too rigid, then "breaks in" causing it, or the other way around? I don't know, I am not a car guy. I just play a very pissed customer on TV...

 

Either way, don't waste your time getting the roof repaired. It will make the same sound after the "repair." The only difference will be the greasy finger prints left all over your interior liner. Trust me, I know.

Now you have my attention as well....... 38 MPH is the EXACT same speed that we have the most notable production of the buffeting. I about fell out of my chair just now when I was reading your post and noted the MPH. However, as for the fix, I really don't see a better way to negotiate with GM unless we allow them to attempt to fix the vehicle first. I have not taken the issue any farther than my local dealership at this point. If the fix doesn't correct it, then I fully intend on taking the issue to the next level. As I disclosed earlier, I am an Attorney in Illinois. That doesn't make me any better than anyone else, just a heck of a lot easier to cause some real problems that won't cost me a lot of real money.

Posted

I've been in the vibration playing a significant role camp since first finding this thread. If I'm not mistaken the suburban, Yukon, escalade all share the same platform with the new Silverado/Sierra introduced with the 2014 model. Just do a search for Silverado vibration and you'll find a bunch threads and videos. I actually drove a 2014 Silverado and it had similar buffeting. Then a buddy got a brand new 2015 and it had zero. They were the same trim level but the difference was night and day. The 2015 drove like a caddy!

 

Sent from my Nexus 5 using Tapatalk

Posted

38 mph (60 kph) is definitely where mine really starts to be noticeable. But it persists up to 80 kph, diminishes somewhat, seems real bad at 100 kph again, then diminishes again by 120 kph.

 

I too am thinking more and more that the vibration is totally related to the noise/pressure. They feel/sound completely in sync when it's 'rocking and Rollin' at its worst.

 

I find Romanbasi's story totally fascinating. Thinking back, I do recall an extremely cold day here about a month after we got it. The vehicle is always parked in our heated garage, but we took the kids to skating lessons and it sat outside for a spell. I remember the day because it didn't start all that great and I was thinking "oh, oh, I hope this isn't going to be an issue" now that I think about it, it is possible,I first started to notice the noise/pressure around that same time. Can't claim as distinct an observation as Romanbasi, but maybe.....

 

Observations like this, that show a distinct change in the behaviour, are incrediably crucial in determining a root cause of this issue. This is extremely helpful. Thank to both Romanbasi and Jasondenali15. Thanks guys!

 

As for taking it in to the dealer for the roof fix, yea. Pretty hard to avoid giving them a chance to fix it. I think most lemon laws give them several attempts. We don't have any lemon laws in Canada. The Ontario government was going to pass one, but the big three petitioned them not to, offering to set up an "independent" group to arbitrate these issues, funded by the automobile industry. Since it wouldn't cost the government any money, they agreed to it. So that's what we got stuck with!!

Posted (edited)

I've been in the vibration playing a significant role camp since first finding this thread. If I'm not mistaken the suburban, Yukon, escalade all share the same platform with the new Silverado/Sierra introduced with the 2014 model. Just do a search for Silverado vibration and you'll find a bunch threads and videos. I actually drove a 2014 Silverado and it had similar buffeting. Then a buddy got a brand new 2015 and it had zero. They were the same trim level but the difference was night and day. The 2015 drove like a caddy!

 

Sent from my Nexus 5 using Tapatalk

 

Yes, this vibration/noise problem is reported on all product on that platform:

 

The temperature trigger is interesting as it would make test drives irrelevant. I'll love to be able to take a poll of the viewers of this thread to see how many of those affected live in the colder climates. I've spoken with 2 dealerships in southern Ontario and neither were aware of any issues.

[fixed links above]

[added links below]

More references to the same problem...

--

Marc

Edited by FogDucker
Posted

I've got a 2015 Yukon Denali and have experienced the buffeting noise as well. I found that when it starts buffeting i set the cabin thermostat up 1 degree to get the heat/air to kick in. As soon as the heater fan kicks on (low) the buffeting is gone. It has to be a cabin pressure issue for me. I'm currently stationed in Grafenwoehr Germany where the weather today was 27F.

Posted

You guys can go back and read my earlier post to review my issues, but here is an update. Apparently there was a regional meeting yesterday for all service managers in my area. GM is aware of this issue and they have some type of machine they are sending out to all the dealers. They are doing training on this machine and it detects vibrations and noise to determine its origin. The regional GM service liasion drives a yukon and is experiencing the same issue. Apparently most service shops are now acknowledging the problem. We will see if this helps find the cause and an eventual solution to each case. They obviously have multiple items causing the problems. This release of this machine only tells me they don't have one solution or one root cause. I will keep you guys posted on what happens to mine. I've patiently waited to see what action my dealer takes and they told wait till after this meeting to proceed. I appreciate you guys trying to solve this issue but I don't have the time or expertise. I'm going to leave it up to the dealer to solve it or they can have it back. We like the Yukon XL but cant drive it this way. Mine is more of an annoyance than anything and there is no way I can continue to drive on longer trips. Mine is really noticeable at 45mph.

Posted

In regards to temp being a possible issue for theses vehicles, I'm in Houston, Texas. I started driving and trying to purchase in the spring on first release and throughout the summer. It was never below 70 degrees. Btw - we have followed up with 2 dealers which we do business and have friendships with and they are very aware of the issues. Their words "it's a mess!"

Posted

In regards to temp being a possible issue for theses vehicles, I'm in Houston, Texas. I started driving and trying to purchase in the spring on first release and throughout the summer. It was never below 70 degrees. Btw - we have followed up with 2 dealers which we do business and have friendships with and they are very aware of the issues. Their words "it's a mess!"

It might be an issue of differential temperature. Cold outside, warm inside with the heat on. Or, hot outside, cold inside with the AC on. Or, any exteme temp, hot or cold, from the temp during assembly (I've seen this at work many times on industrial machinery).

  • Like 1
Posted

I've got a 2015 Yukon Denali and have experienced the buffeting noise as well. I found that when it starts buffeting i set the cabin thermostat up 1 degree to get the heat/air to kick in. As soon as the heater fan kicks on (low) the buffeting is gone. It has to be a cabin pressure issue for me. I'm currently stationed in Grafenwoehr Germany where the weather today was 27F.

Interesting. I've observed on mine that the noise and buffeting occur when the heater fan is on. I also turned the hvac system completely off and didn't seem to make any difference, but I might play around a it more with that if someone else has seen an affect.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   7 Members, 0 Anonymous, 1,646 Guests (See full list)


  • Latest Articles

  • Posts

    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...