Jump to content

6.0L Low Oil Pressure Issue

Matthew Walz
 Share

Recommended Posts

Matthew Walz New Member

Matthew Walz

Posted
Posted

As this issue comes up a lot, I can't seem to find my specific situation. 

 

My 2009 chevy 3500hd with the 6.0 had low oil pressure. Around 35 or so I figured it was the pump. Did that and the o ring and nothing. (Did it once before on another 6.0) 

 

My mechanic replaced cam phaser, timing chain(had other issues), oil pump, some other stuff in that region, new valve springs, new heads and new lifters. 

 

Engine was also generating a lot of heat although wasn't overheating. Replace the oil pressure sensor behind the intake too. Was within spec while driving (20psi) or idle (6 or 7psi I think), but now the oil pressure light is going off and dinging. Engine runs perfect, idles perfect, with no lifter noise. 

 

Is it possible its the cam bearings? We are running 10w 40 oil and Lucas to thicken it up but still has no effect. 

 

Want some opinions before diving in further.

Sharpz Enthusiast

Sharpz

Posted
Posted

It does sound like warn bearings.  If your 6.0 is a high mileage motor, it is likely the culprit.  I am pretty sure  your truck has a filter under the oil pressure sensor too.  I didnt see where you said you changed that.  You might want to replace it if you havent.

Dustoff87 Enthusiast

Dustoff87

Posted
Posted

On my 5.3 there is a small filter element under the oil sending unit. If you're not getting any knocking noises which indicate actual low oil pressure that filter element might be clogged. That's what my problem was. $7 fix for my issue.

Sent from my SM-G892U using Tapatalk

  • 4 weeks later...
Matthew Walz New Member

Matthew Walz

Posted
  • Author
Posted

Update, sorry its been a while. there was no screen in the 6.0 engines, we did install a new sensor which seemed to help. After running 2 quarts of lucas stabilizer and 10 30 oil, pressure does not ding when it gets low as often. Taking it to a more experienced mechanic today and if the mechanical gauge reads good then we will check out the gauges, the rpm gauge has been messing up. If it shows low pressure, I'm taking it to a dealer and trading it in. Not worth putting more money in to and I don't have the money for an engine.

  • 11 months later...
Vanaj Enthusiast

Vanaj

Posted
Posted

The 6.0 did have a problem with a sticky oil pressure relief valve (sticking open partially) in the oil pump housing at one time.

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   3 Members, 0 Anonymous, 2,173 Guests (See full list)

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...