fullymatted.
Back to search
Rennlist

Drain Bramage??? :-(

Add to repair workspace
Open repair workspace
Original source
4 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHDrain Bramage??? :-(

Reported or suspected cause

may be having the same sort of computer problem

Suggestion or failed attempt

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
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 suspect a cause
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.

Suspected cause

My $100 Actron reader works fine on my 99 996, but won't work on my 00 M5, which I suspect may be having the same sort of computer problem.

Drain Bramage??? :-(
Frequently discussed work

Check codes and let me know what they were

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

So I asked the service manager to check the codes and let me know what they were.

Drain Bramage??? :-(
Read full discussion summary

Leading evidence: 'may be having the same sort of computer problem' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'may be having the same sort of computer problem' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check codes and let me know what they were' (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.

Read captured replies

1 matching discussions · 4 captured posts examined · 0 partial discussions

Compare 2 other evidence results

Check codes and let me know what they were

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 · Original poster

So I asked the service manager to check the codes and let me know what they were.

Drain Bramage??? :-(

Run same as always

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 · Original poster

The car seemed to run same as always.

Drain Bramage??? :-(
Frequently discussed actions (2)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Check codes and let me know what they were

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

So I asked the service manager to check the codes and let me know what they were.

Drain Bramage??? :-(

Run same as always

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

The car seemed to run same as always.

Drain Bramage??? :-(
Reported and suspected causes (1)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

may be having the same sort of computer problem

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect a cause
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.

Suspected cause

My $100 Actron reader works fine on my 99 996, but won't work on my 00 M5, which I suspect may be having the same sort of computer problem.

Drain Bramage??? :-(
Coverage and how to read this overview

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.

4 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: 20261027T173940Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

So I take my 99 C2 Cab out Saturday night and the check engine light comes on. The car has just under 40K miles and has been a gem. No engine problems since I have owned it and no check engine lights either. The car seemed to run same as always. Luckily I was scheduled this morning to take it in to have my ROW M030 suspension installed. So I asked the service manager to check the codes and let me know what they were. I don't take it to the dealership because it is out of factory warranty and the shop I use is a very experienced private Porsche shop here in Raleigh. Long story short I get a call when the car is done and the service manager tells me that my 996's computer will not talk to their DME to read the codes. He tells me that he has seen this a lot lately with early 996s and that it often means the cars computer needs to be replaced. He says it's like a 2K job and that I will have to take it to the dealer to see if that is actually what the problem is. Questions: Has anyone else heard of this as a common problem with early 996's? Also what is the warranty on something like that? Since the computer monitors many of the emissions systems on the car can it be considered as part of the emisssions system? I think most emissions parts these days are warranted for 80K by law. I may be wrong on that though. Luckily I bought extra warranty through the dealership so if its not covered by Porsche hopefully it will be covered by the extra warranty. Thanks in advance for any information you all can give... Oh...and the ROW M030 is amazing. I highly recommend it to anyone considering it!

POST 2Original post

My $100 Actron reader works fine on my 99 996, but won't work on my 00 M5, which I suspect may be having the same sort of computer problem. Uber

POST 3Original post

Try another shop to read the code. If not, go to dealer to read the code. Until the code is read, you won't know what sensor failed. Did the dash display any error message besdies the CEL? Besides O2 sensor, other possible culprit can be MAF and many other sensors. I doubt if o2 sensors are part of emission warranty but I could be wrong. Usually it's just the cat and muffler.

POST 4Original post

Could be a loose gas cap...or NOT. Get the codes read at the dealer

This is a source reference. Confirm exact model applicability in the original material.