Jump to content

2005 Silverado L33 Engine Noise

RINGOz71
 Share

Recommended Posts

RINGOz71 New Member

RINGOz71

Posted
Posted (edited)

I have a 2005 silverado 1500 with the L33 motor. I've had this knocking noise since 170k miles and now it seems at times like it's getting worse, and others it sounds like it's getting better. The truck now has 215k on it now.

Truck does not seem to have a loss in power. Oil pressure sits above 40psi at idle and around 50-60 normal driving. Oil level is checked every week and Is topped off whenever its below half on the stick. Tried switching to a thicker 10-30 Penzoil high millage with no change in noise. 

 

The weird thing is, is that it seems to go away at higher speeds. You can here it get faster with higher rpms in a parking lot, but if you pull onto a main road and go, It sounds normal. I'm stumped and have been told many things from different techs at my dealer. Some say manifold bolts, some say a cracked flywheel, piston slap, rod knock, valves, lifters, you name it. I'm stumped and ready to put a new motor in it. Any insight is very appreciated!

I took a video on it

enRRqnT.mp4

 

Edited by RINGOz71
CamGTP Senior Enthusiast

CamGTP

Posted
Posted (edited)

Can you get a video of you raising the rpm slowly to 1,500-2,000rpm and back down?

 

Just set the phone or whatever on the tire and do it.

 

It's hard to say what it is but to me it's sorta valve train related. Piston slap sounds different than this video.

Edited by CamGTP
RINGOz71 New Member

RINGOz71

Posted
  • Author
Posted (edited)

First video is a cold start after sitting at work all day

2yqjGBY.mp4

second video is after driving home with the temp around 200

 

cmUd376.mp4

Ignore the exhaust leak. That will be fixed today. For some reason the magnaflow catback doesn't  like the magnaflow cats. 

Edited by RINGOz71
CamGTP Senior Enthusiast

CamGTP

Posted
Posted

I'm still going with valve train/camshaft related. It sounds like it's going half the speed of the crank.

 

Could be a worn cam bearing or even a roller on a lifter that keeps getting louder. These engines are somewhat known for eating the cam lobe off on some.

  • 4 years later...
cat eye 121 New Member

cat eye 121

Posted
Posted

I have a 2006 that sounds identical to these videos. Thought it was lifters. But sounds more like bottom. Can hear it good down by the front tire. Did OP find the problem?

davester Senior Enthusiast

davester

Posted
Posted

ringo hasn't logged onto the site in 4 years, so you aren't going to get a response from that user.

you might use a mechanics stethscope to better localize what & where the sound is coming from.

and idky you would think whatever fixed the o.p.'s issue would also fix it for you.

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

    • 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.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?
    • Snowcamo
      Replacement Radiator

      By Snowcamo · Posted

      Rockauto bud. I pass local stores for parts.   Findya something online. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...