13 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHTwo Random CELs
Leading reported evidence
Check with the
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.
Performed · outcome unconfirmed · Original poster
Checked with the on-board displayed which said no errors saved(or something similar).
Leading evidence: 'Check with the' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check " function in computer of the car really' (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
I smoke tested the vehicle and found a vacuum leak.
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
What exactly is the "check" function in computer of the car really for?
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
Don't have none of them there fancy check'n thangs!
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
A bit of research indicates it could be connected to the PSM and ABS lights popping up every few days or weeks (I went 3 weeks without them after cleaning the MAF, but now like wet Gremlins they are back).
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
A bit of research indicates it could be connected to the PSM and ABS lights popping up every few days or weeks (I went 3 weeks without them after cleaning the MAF, but now like wet Gremlins they are back).
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.
13 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 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: 20261026T130754Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
2005 996 C4S
Started car today, backed out of garage, waited for air pump to shut off and drove gently off. After @ four blocks never above 35mph nor above 3,000rpm. Stopped at stop light, pulled away on green still gently then about two blocks further the chime goes off, CEL is on and cpu says "drive to service facility" or something like that. Oil pressure normal, water temp(still low), no unusual noises noted and charging just under 14v...all normal for this car. Stopped to turn left and go back home when warnings go off. Went straight @ another half block and same warning-same gauge results. Turned left to go home and everything went off. Drove the nine or so blocks back home without further excitement. Parked in garage, jumped out everything sounds and smells normal at idle. Don't have none of them there fancy check'n thangs! Checked with the on-board displayed which said no errors saved(or something similar).
Opinions?
I had a CEL come and go a few months ago, codes P1128 and P1130. I smoke tested the vehicle and found a vacuum leak. Replaced PN 996-110-151-52 and haven't had the CEL come back since. $18 and 5 minutes. Hope yours is as easy!
So the Innova tells me:
Two separate records:
P0300 Random Misfire Detected
P0306 Cylinder 6 Misfire Detected
The coil guess's could be coming true. Car had sat in garage for about one week as the security receiver had gone to sleep. It was hot and humid plus numerous thunderstorms during this period. Makes sense that if #6 coil has a crack or cracks it could have taken some moisture sitting in a cooler than outside temperature garage. Also makes sense that the trip back home was uneventful as some heat had been generated by driving. So I guess we will see. Approx. 54k miles so might be time for a new set of coils plus spark plugs, as well.
A code reader is the key to lower levels of panic when you get the dreaded CEL. I had one on the way to the office yesterday, but everything was running/operating fine so I drove home in a quite sedate manner, pretty much holding my breath (I have been thru the IMS thing twice). The Werewife was waiting with her code reader; we soon saw P2096. A bit of research indicates it could be connected to the PSM and ABS lights popping up every few days or weeks (I went 3 weeks without them after cleaning the MAF, but now like wet Gremlins they are back). She cleaned the MAF today and I have a new one due tomorrow from Pelican. We'll see if that does the trick. Could be an o2 sensor or xxxx, but I'm starting with the easier, pull out / plug-in, less expensive options.
I must admit it was calming when the code reader whispered "Listen to Ahsai...he is correct!"
What exactly is the "check" function in computer of the car really for? Does it display only something currently troubling or what? At least it wasn't this...
I had the scariest ever CEL pop up on the GT3 after a f-up exhaust mod by a local indy whose shop I pray will fall down upon his head some day soon without harming any of the cars inside.
Basically it said Drive to repair facility NOW ****! It was a Code Brown inducing event. Happily it was just a "Achtung, we are running way too rich, o2 sensors can't figure out what you did, fixen shnell!" thing and was
an easy fix.
