fullymatted.
Back to search
Rennlist

Weird misfire issue

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

Discussion summary

YOUR RESEARCHWeird misfire issue

Reported or suspected cause

whole bank

Reported cause

No successful repair reported for this finding.

1
Identified cause
0
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 report identifying 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.

Reported cause · Original poster

It looks like issue was with whole bank, but now it drives fine.

Weird misfire issue
Frequently discussed work

Run vehicle

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 ran the vehicle with my professional scanner and saw this codes.

Weird misfire issue
Read full discussion summary

Leading evidence: 'whole bank' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'whole bank' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Run vehicle' (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 · 14 captured posts examined · 0 partial discussions

Compare 2 other evidence results

Run vehicle

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 ran the vehicle with my professional scanner and saw this codes.

Weird misfire issue

Use factory scanner it displays a cumulative number, typically taken

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

When using the factory scanner it displays a cumulative number, typically taken after a good drive with the engine hot.

Weird misfire issue
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.

Run vehicle

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 ran the vehicle with my professional scanner and saw this codes.

Weird misfire issue

Use factory scanner it displays a cumulative number, typically taken

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

When using the factory scanner it displays a cumulative number, typically taken after a good drive with the engine hot.

Weird misfire issue
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.

whole bank

No successful repair reported for this finding.

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

Reported cause · Original poster

It looks like issue was with whole bank, but now it drives fine.

Weird misfire issue
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.

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

POST 1 / ORIGINAL POSTEROriginal post

Hello all, Yesterday about 5 minutes into driving, I received a check engine light. Sometimes it flashed and mostly it just stayed solid. Performance-wise it just felt like a standard misfire. Today I started the vehicle and did not notice any misfire. I ran the vehicle with my professional scanner and saw this codes. I was able to erase all codes with no issues. I then turned on live data showing misfire counter and drove for about 10 minutes. Counter stayed at zero. I was hoping for a simple ignition coil, but now not sure what it could be. It looks like issue was with whole bank, but now it drives fine. Can you lead me in the right direction? Thanks!

POST 2Original post

I would hone on on the P1371 fault code first, potentially an issue with your variocam actuator on that bank. What are your cam deviation numbers?

POST 3 / ORIGINAL POSTEROriginal post

Are the first two on the screen are cam deviations? or that's something else? I'll look through options on the scanner and see if I can find it there.

POST 4Original post

I'm not familiar with your scan tool but it does look like the first two are measuring camshaft deviation. Not sure if it is a live reading or cumulative over time. When using the factory scanner it displays a cumulative number, typically taken after a good drive with the engine hot. Maybe give some more details about your car? Year? Mileage? History? Any recent repairs?

POST 5Original post

What engine? 3.4 or 3.6? Do you have any tell tale indications of the coolant expansion tank leaking? White/pink residue on the bottom?

POST 6Original post

That "actual camshaft" reading should be the instantainious reading. It should jump when the variocam engauges. U should be able to graph those readings and as u bring the rpms past 3-3500 it should jump on both sides.

POST 7Original post

I see you have the 3.6, 2002. Here is P1359: https://lemon-manuals.la/Porsche/200...Above%20Limit/ P13571 https://lemon-manuals.la/Porsche/200...Above%20Limit/ Go up one directory and there is another page for each code. Here is a great video on the lifters that your car has....you could have a misfire due the lifter. You Tube I am in Port Orange if you ever need help.

POST 8 / ORIGINAL POSTEROriginal post

Quotes source post: 20723794

2002 996.2 with 121k miles. Bought it on carsandbids about 3 months ago. So far put probably under 1k miles on it. That happened first time. No repairs done yet, especially to the engine.

POST 9 / ORIGINAL POSTEROriginal post

Quotes source post: 20723875

Thanks, will need to figure out for sure whether its lifters or what it could be. Never had that issue before and starting today did not show any issues. Hopefully it won't be something that would require engine removal and work on it.

POST 10 / ORIGINAL POSTEROriginal post

Did a bit of research and I doubt it was lifters as normally when they go bad or get stuck, it would affect specific cylinder. In my case it looks like whole row was affected. Will do more research and try to carry my professional scanner with the car so that if misfire happens again I can try to pin it to a specific part.

POST 11Original post

Do you keep the car on a charger? Low batt voltage can cause odd issues with these cars.

POST 12 / ORIGINAL POSTEROriginal post

I did not and I think it was about 3 weeks since I drove it last time. Hopefully that was the issue.

POST 13Original post

Quotes source post: 20726010

3 weeks is a long time, definitely look into a charger. CTEK, Porsche white labels this for their version, or NOCCO are popular and reliable. I have the CTEK. https://a.co/d/0gTcpoZa

POST 14 / ORIGINAL POSTEROriginal post

After some research, turns out misfire would not be on same bank as cylinders on driver's side go 1, 2, 3, and passenger side 4, 5, 6. I got check engine now again and this time it is not going away. Good thing is it now points just to cylinder 1. Might do half of spark plugs and ignition coils swap first and when I get more money, buy another half and replace that side.

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