Jump to content

2015 Duramax: Cold Oil Pressure Bounces Off "0"


Recommended Posts

Posted

Hey folks -

 

Within the last month or so, my 2015 Duramax has been behaving a bit strangely when cold.  The definition of "cold" in this case is merely anywhere between 10-25*F, give or take.  After a cold start, the oil pressure bounces right up to where it should be during idle.  However, shortly after I put it in gear, drive down the road, and round a corner, the pressure bounces off "0".  It usually happens twice in quick succession and I get the requisite "TURN YOUR ENGINE OFF, YOU MORON!!" alarm.  After each bounce off 0, the pressure shoots right back up to where it needs to be, and all is good.

 

This only happens when the truck is cold.  After that point, I have no more issues with it until it sits in the cold for a few hours.

 

My last oil change receipt says they used 10qts (which is correct) and they used the appropriate 15W40 oil, which for these temps in Northern VA should be perfectly fine.

 

Bad sensor that doesn't like to be cold, maybe?  Should I just have them change the oil and do it again?  The oil level seems correct based on my last "HOT" check this weekend, so I'm not losing any.  Any other thoughts?

  • 2 weeks later...
Posted
1 minute ago, avalonandl said:

I would say you have a oil pickup issue.

Pardon my ignorance, but wouldn't that result in some potentially disastrous engine problems?

Posted

Yes I would say so.

 

Look at the facts- it happens only when VERY cold and not fully warmed up: 

This means pressure is dropping: one choice is oil is too thick and not flowing, one is bad sensor, another is low oil-you checked that. Oil pick up is another, your pumping cold oil into the top of the engine and it hasn't drained back and pickup is sucking air.

 

Warm the truck up is another choice.

Posted

A guess, but maybe be a sensor or harness connection that once it's warm enough tightens the joint so it reads correctly?? 

 

Regardless it needs to get fixed.

Especially if it's not the sensor or sensor circuit. 

 

I've had years of dmax 'starts' at those temps and lower, using 15W-40, and have never had one do that.

 

 

  • 3 months later...
Posted
1 hour ago, Boots said:

I have the same problem, did you find out what the issue was??

Not yet; I haven't had the opportunity to have my dealer look into it thoroughly.  An "off-the-cuff" guess from him was one of the sensors was bad but he wasn't sure.

Posted
On 2/10/2019 at 10:37 AM, avalonandl said:

I would say you have a oil pickup issue.

He says it only happens when he goes around a corner. Agree. Or one very very loose oil pressure sensor wire, but that should also read 0 oil pressure on bumps.

  • 3 months later...
Posted

Sorry for the long delay in reporting back in; I just had the truck serviced.  I've been busier than a 1-legged man in an ass-kicking contest.

 

Diagnosis: pressure sensor was FUBAR'd.  And there was a teensy bit of oil leaking around it, too.  Which is interesting because there's nothing on my garage floor.  They replaced it and I noticed an immediate change in the oil pressure reading.  Prior to the change it was always on the higher side, but not at maximum.  Now it just generally floats around between 1/4 and mid pressure.

 

The annoying thing: they claim this swap was NOT covered under the 5/100 power train warranty.  Even though it's a sensor attached to the power train, apparently it's part of the (expired) 3/36.  Hm.  That seems suspect, but I didn't press the issue because I wanted it fixed.

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • 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.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...