6 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHOil Guage Problem
Leading reported evidence
Replace sensor
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Replace sensor' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Clean contacts' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
Definitely replace the sensor first (it is actually the same sensor that is used on the 959), as these fail *all* the time.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Mine does it at odd intervals and I take the wires off and clean the contacts.
Replace sensor first (it is actually the same sensor
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Definitely replace the sensor first (it is actually the same sensor that is used on the 959), as these fail *all* the time.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
No perceived mechanical changes while this occurs.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
6 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Pelican Parts: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T150451Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Car: 2002 C4 Cab with 67,500
The Problem: While driving, the "oil failure" warning light comes on and the oil pressure guage drops to 0. Occurs randomly, no association with leisurely driving or going fast. Lasts about 10 seconds then returns to normal. No perceived mechanical changes while this occurs. My mechanic drove the car and couldn't get it to occur.
Does this sound like a sensor problem, or is the oil pump starting to go on me?
Thanks for the input!
Mark
I had the same problem on my 959. Whether it's a 959 or a 996, you still want to make sure it's the sensor, not the engine. So, I replaced the sensor. It's pretty easy to do - it's in the engine compartment - I have a tech article coming out on this soon. Definitely replace the sensor first (it is actually the same sensor that is used on the 959), as these fail *all* the time. We sell a ton of them.
-Wayne
It's pretty easy to access. Sits about 1/2 way along the engine (front to rear) on the right hand side. It sits up with the two wires sticking up vertical. It may be a bit of a reach, but it's relatively easy.
I agree with Wayne that failures of these seem relatively common. Mine does it at odd intervals and I take the wires off and clean the contacts. It will be fine for months, then it will start doing it again. I don't know whether it is a bad connection or whether the sensor is really playing up. I should probably buy a new one...
