Jump to content

Recommended Posts

Posted

Ok I have 2011 GMC Sierra that has developed a ticking noise. I also have a misfire p0308 in cylinder 8 with p0300 in the history of the obd2 scan. (This tick does not happen in idle)This tick only happens when reaching 2500rpm and above and and willl increase tick speed with rpm but does not get louder only faster. And it does sound like it’s is on the passenger side coming from cylinder 8
1.i have replaced spark plug 

2.i have swapped coil pack from one side to the other along with wire (Misfire still cylinder ?

3. I have stethoscoped the injectors they all sound the same and are functioning I have even unplugged the injector and wire and ran it up to 2500 rpm still ticking 

4. I have changed oil 5w30 ac Delco filter and im currently running mmo with it. 
• I do not see any sign of exhaust leak as far as bolts or black carbon around manifold 
•all my vacuum lines seem intact and good

• MY VALVE COVER GASKET DOES SEEM IT HAD OIL CRUD AROUND THE EDGES 

—my next step is to run sea foam through the vacuum line to see if I have carbon causing a sticky valve or something 

I believe I either have a Hydraulic lifter issue cylinder 8 NON-afm cylinder smacking my cam 

or a spun bearing ,

weak or broken valve spring , maybe a rocker Arm loose, bent pushrod but I honestly don’t know when it comes to internals (THIS ONLY HAPPENS 2500rpm and ABOVE) any help thanks 

Posted





I believe I either have a Hydraulic lifter issue cylinder 8 NON-afm cylinder smacking my cam 
or a spun bearing ,
weak or broken valve spring , maybe a rocker Arm loose, bent pushrod but I honestly don’t know when it comes to internals (THIS ONLY HAPPENS 2500rpm and ABOVE) any help thanks 



Yes, yes, yes.

Time to pull the valve cover and have a look, and hope it's up there.

Have you run the stethoscope around the engine at 2500k? Hopefully, the noise is up high on one side. (Is it more 'tsk, tsk, tsk' or 'whisper, whisper, whisper'? Lifter vs bearing)
Posted

More of a tsk tsk tsk... I pulled the valve cover and cranked the motor it seemed smooth everything felt snug no spongy lifters no bent push rods so I bought two valve springs I’m gonna install them tonight. I cranked the motor by hand and one of the springs just seemed it didn’t get as high as the other and it’s had 2 or 3 shiny marks on it as if it was binding up. So my guess was if it’s not pushing all the way up then my push rod isn’t going all the way down and my lifter isn’t riding in the cam smoothly just my guess but I will start there tonight ...thanks I had a you tube video up I’m not a mechanic but I research enough to get it done myself :)

 

Posted

Well valve spring didn’t work out due to a shitty tool so I’m ordering a better one I’m gonna do these springs regardless.... I did change the pick up tube o ring today it was pretty flat. I removed the baffle to check my rods they don’t push up and down as far as the bearing clearance it’s Pretty stiff but they all move a hair side to side I’m sure that’s normal I hope but I did get a snap of my cam lobe I don’t think it was normal It was hard to tell the one I got was the lobe of my misfiring cylinder 

0AB5E7D3-19D7-4B5D-8940-B00CD346E0DD.jpeg

  • 1 month later...
Posted
48 minutes ago, barto said:

Any update on the issue? 

Yes absolutely it was a single lifter a non afm One at that the lifter roller was all nicked up and chipped  and it was eating the top of the cam lobe !!!!!! This tick never happened in low rpm so it was hard to find and also because the rocker arm was tight and had no play. So if you get a code p030(1-8) with a ticking noise that will indicate your cylinder and just to be sure the only thing that really helped me was a mechanic stethoscope the best location I found was directly on top of the (valve cover) back bolt by cylinder 8 with the vehicle revved up and I placed it directly on the VLOM Metal plate in the very back I kind of squeezed the stethoscope under the intake manifold. I hope this helps someone because everyone always talks about the afm lifter failing in a active fuel management vehicle funny thing is those lifters were all fine. I believe the cause was low and old oil also with 136,000 miles the valves needed to be adjusted for a smooth transition from v8-v4 and if you ever get that dreaded v4 vibration replace your motor mounts v4 is unbalanced and it needs those firm ac delcos it won’t happen in v8 i had broken mounts and v8 was smooth as ever and with the motor vibrating the way mine did I believe it could have also caused lifter and cam vibration just my 2 cents... good luck ? 

Posted
18 hours ago, Alonzo Nunez said:

Yes absolutely it was a single lifter a non afm One at that the lifter roller was all nicked up and chipped  and it was eating the top of the cam lobe !!!!!! This tick never happened in low rpm so it was hard to find and also because the rocker arm was tight and had no play. So if you get a code p030(1-8) with a ticking noise that will indicate your cylinder and just to be sure the only thing that really helped me was a mechanic stethoscope the best location I found was directly on top of the (valve cover) back bolt by cylinder 8 with the vehicle revved up and I placed it directly on the VLOM Metal plate in the very back I kind of squeezed the stethoscope under the intake manifold. I hope this helps someone because everyone always talks about the afm lifter failing in a active fuel management vehicle funny thing is those lifters were all fine. I believe the cause was low and old oil also with 136,000 miles the valves needed to be adjusted for a smooth transition from v8-v4 and if you ever get that dreaded v4 vibration replace your motor mounts v4 is unbalanced and it needs those firm ac delcos it won’t happen in v8 i had broken mounts and v8 was smooth as ever and with the motor vibrating the way mine did I believe it could have also caused lifter and cam vibration just my 2 cents... good luck ? 

You may have significantly helped me. 

Posted

Nice...if your doing the work yourself I don’t know if your a mechanic or not but this guy on you tube called the sundae drive breaks down a great rebuild on a 5.3 his is a gen 5 but very similar to the gen 4 and 3 or you can check out gt performance that with with a Haynes Manuel for all the torque specs helps a lot I really saved a lot of money doing it myself... hit me up if you ever got any questions or concerns 

  • Thanks 1
  • 1 month later...
Posted

Update on my issue. 2015 Yukon Denali 6.2L first owner. The valve spring and lifter on cylinder 8 need to be replaced. Had a bent push rod and cam replaced. 

 

Earlier this year I had the radiator, water pump, thermostat, and water bottle replaced.  After that the AC condenser, rear lines and rear condenser. 

 

Last year, the mag ride shocks replaced, steering column bearing twice, then eventually the steering column as a whole. None of this was covered my GM and the dealers (two of them) said sorry for your luck. That's just how these cars are... Never again. 

  • 3 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
  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • 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...