9 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHNew to me C4S Cluster and Spoiler issues
Leading reported evidence
Replace ignition switch
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
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.
Performed · outcome unconfirmed · Original poster
So far I have replaced the ignition switch but am trying not to throw parts at it.
Leading evidence: 'Replace ignition switch' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'damp has caused issues' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check almost everything' (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 · Original poster
I ended up using a factory Porsche part thinking that was best.
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
As your other issues are cluster based, I suspect damp has caused issues.
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
Indeed, I’m afraid you’re right- just going to have to check almost everything.
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
Maybe start by removing it and checking connectors for corrosion.
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
Battery ground to frame is good- although there is the slightest little spark when reconnecting the negative battery cable- which I was always told that meant there was a bad connection somewhere.
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.
9 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261026T212127Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi everyone- new Porsche owner here….
I recently inherited a 2004 C4S with about 21,000 miles on it that has been sitting for about 6-7 years. It starts right up and drives fine, but I have quite a few issues with the instrument cluster.
1. The cluster will sometimes show KPH and sometimes show MPH, it is never the same and sometimes switches midstream.
2. The high beam indicator light will illuminate even when the headlights are not on.
3. The lower cluster - mileage, time, mph will stay on after I shut off the car- as long as an hour before I finally have to disconnect the battery.
Occasionally it will go off normally, after 3-5 minutes, but most of the time its long enough that I have to disconnect the battery.
Additionally, the rear spolier stays up, even after the car is shut off. A diagnostic reader shows some sort of communication error to the spoiler.
I know some of this might be in previous threads, but I looked and could not find any that spoke to my particular issues- so I apoligize in advace if I missed them.
So far I have replaced the ignition switch but am trying not to throw parts at it.
Help!
Thanks!
Certainly on the earlier cars, the spoiler control is done by the instrument cluster, as the speed determines when it goes up or comes down. As your other issues are cluster based, I suspect damp has caused issues. The cluster is easy to remove, I think it's just 2 screws, but Google will throw up loads of videos.
Maybe start by removing it and checking connectors for corrosion.
Does it have after market HIDs by any chance, I worked on a 996 once which had irrational cluster and spoiler behaviour which was resolved by ripping out the aftermarket hid kit.
Also on another car the lower cluster reading staying on was indication of a faulty ignition switch as it didn't fully turn off (common on 996s) a vw replacement part was the fix if I remember correctly.
Unfortunately, no aftermarket lights of any sort. I did replace the ignition switch already- which is not fun for a guy my size. I ended up using a factory Porsche part thinking that was best. I suppose I could have got a bad switch. I’m pretty bummed- at only 20k for mileage, it seems early for an issue like this. I’ll keep searching- thank you for the suggestions!
It's not the mileage , it's age related and like someone has said, it could be from being stored in a damp building and corrosion has gotten to a few things. You're just going to have to work through it methodically I'm afraid.
Indeed, I’m afraid you’re right- just going to have to check almost everything. Battery ground to frame is good- although there is the slightest little spark when reconnecting the negative battery cable- which I was always told that meant there was a bad connection somewhere. I’ll keep trying. Thanks everyone for the suggestions- all very helpful, especially for a newbie.
This is a source reference. Confirm exact model applicability in the original material.