18 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHCan 996s take hard runs?
Leading reported evidence
Replace twice in the last 4 months
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
I've just had the MAF replaced twice in the last 4 months!
Leading evidence: 'Replace twice in the last 4 months' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'front wheel' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check done' (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 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
you'll need to find out which one first, put probably a front wheel.
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
(See not technical, probably the wrong name for it) But sorted the problem and it has not re-occured for 12 months.
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.
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.
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.
18 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Porsche Club GB: 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: 20261027T175704Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
This morning I took my Beast for a very hard run, pushing especially hard around alot of corners. After about two-three minutes of hard cornering I noticed that the 'PSM OFF' warning light had switched on as well as the 'ABS' warning light. Pretty much as soon as I saw this I switched the car off for about a minute then turned it back on and all of the warning lights had stopped glowing. Then it happened again, after about two minutes of hard driving they switched back on.
Does anybody have any idea of what the problem may be?
Paul
PSM gets signals from the ABS sensors so that it knows what each wheel is doing. Similarly, it reads the brake light switch, and data from other sensors around the car. The reason a MAF sensor problem will trigger a PSM fault is that the CAN bus circulates data between the DME, PSM, PCM, Instrument Cluster, etc. If the MAF gives an implausible output, it causes a fault in the PSM module.
Get your fault codes read. It should have registered and stored a fault code.
Hi ,
sorry but not technical in any way however I had the same problem on and off for 10 months in my 996 Turbo. Porsche replaced many sensors, etc then identified the problem as being an electric brace? (See not technical, probably the wrong name for it) But sorted the problem and it has not re-occured for 12 months. Although the computer system on the car stored and showed a 'fault' it was not specific enough to allow repairs. Might be something worth considering?
Good luck.
"...and those magnatrusses have got to go as well, then there's the oil in your paint that has to be changed - that'll be £5k please Sir" [/Service Guy]
[
]
