Jump to content

Front End Popping About To Drive Me Crazy

plainvanilla
 Share

Recommended Posts

Spurshot Senior Enthusiast

Spurshot

Posted
Posted

My 08 1500 started doing this last fall. I took it to a frontend shop I've been using for over 30 yrs. He checked the balljoints and steering and said it's not those things and that GM trucks had a little gremlin that can be fixed by tightening the "crossmember bolts". I don't know which ones, A-arms or other?

  • Replies 40
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

ilmk123
ilmk123

Check A frame bolts. Mine had the popping sound and when I tightend them up all I could move them was a1/4" with two half inch breaker bars. It did stop the popping sound....scott

asilverblazer
asilverblazer

Mine does this too, been doing it for the last 40k miles, no better no worse. Make me think its not the ball joints, they should be getting worse by now if it was them. If I manage to remember I'll go

imollison Enthusiast

imollison

Posted
Posted

I have had this popping noise aswell in my 2008 2500HD 4x4 gaser with 40,000 kms on the clock, the last 4 months. Only happens while braking, on the drivers side, but does not happen all the time. Hard to replicate the noise.....will happen every time I stop for a day then go away for a week or two. Not feeling it in the steering wheel, so do not think it is the intermediate steering shaft....also don't think it is the cross member as it is coming from up front near the suspension.

 

Sealership said to bring it in when it is doing it again, and when it is dry so the tech can have a look.....like that is going to happen here in Ottawa before the summer.....

 

Also having problems with the input/ output seals on the transmission....weeping some fluid...again told to bring it in after a few more miles and when it is dry out so the the tech can see the problem.

burnthefurniture Enthusiast

burnthefurniture

Posted
Posted

For what its worth, I finally determined the cause of my front end popping noise. It was not body bushings, it was not the crossmember, it was not tie rods, or ball joints. My mechanic determined my steering rack bushings were worn out and when I cycled my steering, my entire steering rack would move 1/4-1/2 of an inch. For what its worth, my truck is a 2wd. I don't know if the 2wd steering on the 07+ trucks are the same, but I was told I have to replace the entire rack to replace the bushings and fix the noise. Not worth 500 dollars in my opinion...

  • 6 months later...
Fenn Enthusiast

Fenn

Posted
Posted

bringing this back up.

 

I've been having this problem for some time. I did the body mount TSB and still had the noise. Tonight I re torqued the upper control arm bolts and so far it solved the issue.

CapitalTruck Senior Enthusiast

CapitalTruck

Posted
Posted

I have had to retorque my upper control arm bolts a couple of times. They have pretty high torque specs, use a torque wrench. I was getting some noise also. I think the torque spec. is like 150 or something.

  • 3 years later...
Explorer Enthusiast

Explorer

Posted
Posted

That issue on my 4x4 wound up being the front hub and bearing assembly. Everything checked out fine till I grabbed the CV joint and was able to move it side to side about a 1/16". Easy fix, but a real bear to get the old one off.

BlackZ71Silverado Senior Enthusiast

BlackZ71Silverado

Posted
Posted

Have you guys with the front end pop checked your front sway bar end links ond sway bar bushings?

Sway bar cantact will make a pop/clunk sound and can be hard to find.

 

 

Sent from my crappy iPhone 6

using Tapatalk

  • 3 weeks later...
fattiresc New Member

fattiresc

Posted
Posted

Have you guys with the front end pop checked your front sway bar end links ond sway bar bushings?

Sway bar cantact will make a pop/clunk sound and can be hard to find.

 

 

Sent from my crappy iPhone 6

using Tapatalk

I have had this for a few months, replaced sway bar linkage and bushings. While doing so I saw where the passenger upper A arm rear bolt was loose and moving under load. I took new parts vck off, drove it with neither on and had the same problem. Apparently when I had the truck aligned mid April, the dealer didn't tighten that bolt after loosening. Nutz. I just tightened it down and no issue now. Going to dealer Monday morning to make it right.

 

Sent from my SM-G920V using Tapatalk

BlackZ71Silverado Senior Enthusiast

BlackZ71Silverado

Posted
Posted (edited)

^^^^^^

I hope they are ready to replace your tires if they show any irregular wear. If I were you, I would check them over really good. Those genius 'certified tech's' at the dealership should be responsible for cost of tires, mount & balance, and new alignment.

 

Glad you found the issue.

 

Yet another example of why to stay away from stealership service departments. Most of those clowns can't even do regular maintenance properly, proven again.

 

 

Sent from my crappy iPhone 6

using Tapatalk

Edited by BlackZ71Silverado
  • 7 years later...

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

    • 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?
    • Grumpy Bear
      OCI, not when but why?

      By Grumpy Bear · Posted

      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. 
    • revmanii
      Looking at ordering a '26 WT because I want a std cab, std bed

      By revmanii · Posted

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