Jump to content

Recommended Posts

Posted (edited)

I've got a 2015 6.2 with ~82k miles on it.  Recently, about 2 weeks ago, I noticed the engine was making a much louder ticking sound than it used it, but I only notice it once the engine is warmed up (haven't heard it on a cold start yet).  The noise does vary with rpm, but there does not seem to be any loss of power or mileage.  Any recommendations of easy things to check or should I just bring it in to the dealer?  We really only drive it on weekends, and I've put maybe 500 miles on it since I first noticed the tick.

 

Thanks.

 

Edit: I forgot to mention that the noise is much more noticeable from the passenger side of the engine bay, and that I cannot hear it at all inside the cab when driving, but the ticking is definitely considerably louder than the engine used to be.

Edited by kojimep
Posted

Go get a mechanical stethoscope from the auto parts store.  They are like 10 bucks.

 

put it to the valve cover on the drivers side. If it’s lifter tick you’ll hear it really loud.  If not there put it all over the engine bay.

 

a long screw drive works to if you put it on the valve cover then put your ear in the screw driver.  But for 10 dollars I would just buy a stethoscope 

Posted
10 hours ago, kojimep said:

I've got a 2015 6.2 with ~82k miles on it.  Recently, about 2 weeks ago, I noticed the engine was making a much louder ticking sound than it used it, but I only notice it once the engine is warmed up (haven't heard it on a cold start yet).  The noise does vary with rpm, but there does not seem to be any loss of power or mileage.  Any recommendations of easy things to check or should I just bring it in to the dealer?  We really only drive it on weekends, and I've put maybe 500 miles on it since I first noticed the tick.

 

Thanks.

 

Edit: I forgot to mention that the noise is much more noticeable from the passenger side of the engine bay, and that I cannot hear it at all inside the cab when driving, but the ticking is definitely considerably louder than the engine used to be.

Vacuum pump?

Posted
17 hours ago, JONBLARC7 said:

Go get a mechanical stethoscope from the auto parts store.  They are like 10 bucks.

 

put it to the valve cover on the drivers side. If it’s lifter tick you’ll hear it really loud.  If not there put it all over the engine bay.

 

a long screw drive works to if you put it on the valve cover then put your ear in the screw driver.  But for 10 dollars I would just buy a stethoscope 

Getting one today and I'll check it out tonight after work.  Would you hear a lifter tick through the valve cover, or would it have to be on the head directly?  Also on the short list is the vacuum pump like JimCost2014 recommended.

Posted (edited)

yes to all BUT the vacumm pump it on the lower driverside on the engine bay.  My bad lifter ticked all the time and went up with RPM.  

Edited by JONBLARC7
  • 1 year later...
Posted

Kojimep did you ever figure out what the issue was?? I am currently having the same issue. I have a 2017 Silverado 4x4 4.3. I took it to a dealer and they said it was normal. However, the ticking is only after warm up. I didnt realize that before taking it in. I have been in contact with Chevy Trucks via messenger and they actually helped me with some other issues that were corrected. I had read somewhere that it could be a purge valve but nothing definitive. Thanks in advance.

Posted
22 hours ago, Poncho_ said:

Kojimep did you ever figure out what the issue was?? I am currently having the same issue. I have a 2017 Silverado 4x4 4.3. I took it to a dealer and they said it was normal. However, the ticking is only after warm up. I didnt realize that before taking it in. I have been in contact with Chevy Trucks via messenger and they actually helped me with some other issues that were corrected. I had read somewhere that it could be a purge valve but nothing definitive. Thanks in advance.

 

I was not able to ever pin point where it was coming from.  Even with a mechanic stethoscope the trick always sounding the same everywhere around the engine.   But the common ones I had checked for were:

 

*Any injectors louder than the others

*High pressure fuel pump area

*Approx location of each cylinder on the valve cover

*fuel feed hose that goes into the high pressure fuel pump (supposedly a check valve in there that can get noisy?)

*vaccum pump

*exhaust manifolds and pipe going to the back of the truck

 

I could hear the tick at every one of these locations, and none were ever any louder than another.

 

That said, a few weeks it started misfiring continuously on cylinder 4 @ 102k miles, found a bent push rod, collapsed and spun lifter, wiped cam, and damaged block.  Had to replace the engine.  I don't know that the two are related at all, but after the lifter had collapsed I didn't seem to hear to that tick anymore.  Definitely hope you don't have my poor luck with this though.

  • 2 weeks later...
Posted
On 7/29/2022 at 2:23 PM, kojimep said:

 

I was not able to ever pin point where it was coming from.  Even with a mechanic stethoscope the trick always sounding the same everywhere around the engine.   But the common ones I had checked for were:

 

*Any injectors louder than the others

*High pressure fuel pump area

*Approx location of each cylinder on the valve cover

*fuel feed hose that goes into the high pressure fuel pump (supposedly a check valve in there that can get noisy?)

*vaccum pump

*exhaust manifolds and pipe going to the back of the truck

 

I could hear the tick at every one of these locations, and none were ever any louder than another.

 

That said, a few weeks it started misfiring continuously on cylinder 4 @ 102k miles, found a bent push rod, collapsed and spun lifter, wiped cam, and damaged block.  Had to replace the engine.  I don't know that the two are related at all, but after the lifter had collapsed I didn't seem to hear to that tick anymore.  Definitely hope you don't have my poor luck with this though.

WOW, that really sucks. Sorry to hear that result. Thank you for the info. I will check into that list. I am planning on a visit to the dealer as soon as I get my wife's vehicle fixed. I will update after it gets looked at. Thanks again.

  • 2 weeks later...
Posted (edited)

source of the problem is your running factory engine t-stat, and probably using 0w-20 oil, i doubt you change oil before 5000 miles. , who knows what engine loading your put the motor under while in such a vulnerbal state.

 

next time run race oil minimum 10-30wt, get a 170 t-stat, and add and engine oil cooler. this will support the weak components to live longer

Edited by pokismoki
Posted (edited)

just curious , did the ticking sounds begin after a recent oil change?  only reason i ask is GM has two oil filters that will fit our trucks, one is low pressure bypass, and the other is much higher pressure.  just curious if everyone knows this? and if your running the correct filter?

you have to have the correct bypass pressure to match up with the new variable oil pumps on these gen5's

 

running the wrong filter can increase wear on the valve train components 

Edited by pokismoki

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...