16 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH2004 996 C2 Intermittent loss of power
Reported repair
Repair car
Reported resolution
1
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 report a fix
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 fix
I just fixed a car that wouldn't stay running after starting.
Leading evidence: 'Repair car' (1 discussions report resolution; 0 report an unsuccessful attempt). Across 1 matching discussions, The most frequently discussed action is 'Repair car' (1 discussions). For that action, 1 discussions report a resolution and 0 report an unsuccessful attempt. The most frequently reported fix is 'Repair car', supported by resolution reports in 1 discussions. 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 report a fix
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 report a fix
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 fix
I changed all of the rear tail light bulbs and it fixed the problem.
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 troubleshooting a car, I always check the common/free/easiest possible causes first.
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
I just fixed a car that wouldn't stay running after starting.
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
It started after driving 3+hrs, in the Sierras near Yosemite (between 7000-8500 ft) with outside temperatures in the mid 80�s and the car running flawlessly at around 210F.
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
Yep it SHOULD throw a code if the specified MAF( calculated from RPM and throttle angle) is too far away from the actual MAF value,but in reality we have seen cars run VERY poorly from a faulty MAF value and not set a code, although not as bad as described by the OP as in complety shutting off.
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.
16 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: 20261026T091943Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I�m trying to diagnose an intermittent loss of engine power while driving. It happened for the first time today and continued to happen intermittently for over an hour. It started after driving 3+hrs, in the Sierras near Yosemite (between 7000-8500 ft) with outside temperatures in the mid 80�s and the car running flawlessly at around 210F. While on throttle (light or heavy) the engine would just quit. If I put the clutch in it would stop completely as if the ignition were switched off. After 2-10seconds the engine would kick back on at whatever throttle level was set, as if nothing was wrong, and continue on for between 30sec to several minutes before it would happen again.
The issue finally seemed to stop after we coasted down a grade for about 5 miles (engine braking the whole way). Over the distance of the grade the coolant temperature came back to a more normal 185f.
The issue would happen in any gear, at any speed and even if the clutch was depressed. It died at a stop once also, but started right up with the key. No codes were thrown for the OBD2 system and no warning lights flickered or came on.
This is a base 996 C2 with no
PSM
.
Any help is appreciated!
I ran the car this morning, hard, and it performed flawlessly over the 40min drive with RPM�s kept between 4000-6000. The temperature of the coolant never got above 190, and the air temperature is in the mid 70�s. ...still around 8000� of elevation.
Fuel, spark and air
At elevation air could be a contributor but with our modern cars not likely. Low fuel and a combination of high elevation?
Fuel pump struggling on twisty road if fuel low could be the cause.
Thanks for the fuel pump suggestion. It was slightly above half a tank when the issue occurred, but I�ve had it above 3/4 full since then.
I wouldn�t think vapor lock would be an issue with this type of EFI, but have others reported this type of fuel cut?
It�s a sudden off-on with no hesitation or reduction in power.
You're welcome, matz. Before my fuel pump gave the ghost, my car intermittently stalled. Turning the ignition key would usually fire up the engine right away. Those symptoms occurred for a couple days before I was not able to start the car at all. Fuel pumps are easy to remove and test when there is no ignition. The intermittent symptoms you are experiencing make diagnosis more difficult because the car still runs most of the time.
With the loss of power at speed for an extended amount of time, 2-10 seconds, and NO CEL/CODES,you can eliminate a few things. You can eliminate the CPS sensor or any sensor that is monitored while running. You may also can elliminate the fuel system, as running lean/no fuel for 2-10 seconds SHOULD produce a lean running/fuel trim code.(although this should be verified by watching it with an ODB2 device while it is happening)
The LOGICAL explanation would be a loss of power/potential of the ignition switch/DME relay/wiring to the DME.. Interruption of this circuit would cause the same as just turning off the switch, and cause NO CODES.
First thing I would check is your intake setup. Make sure the hose clamps are tight and there aren't any leaks.
I had the same issue with my 240SX. The intake tube was not on tight.
...improbable to happen only after extended driving I say and it would throw codes, wouldn't it?
The opposite to unmetered air as in too little or none could be causing power loss when the rubber intake hose collapses at higher engine compartment temperatures and low engine load/high vacuum conditions. But I have never heard of that related to 996.
I am with you on your earlier post though: It's electrical.
@matz73z
Anything that causes a sudden loss of supply voltage to the DME like a faulty relay, ignition switch, loose battery cable or ground wire.
Yep it SHOULD throw a code if the specified MAF( calculated from RPM and throttle angle) is too far away from the actual MAF value,but in reality we have seen cars run VERY poorly from a faulty MAF value and not set a code, although not as bad as described by the OP as in complety shutting off. I agree it's improbable for extended driving to exacerbate the symptoms, but not impossible.
The factory intake hose is thick and ribbed, I don't see it collapsing even with a very restricted/stopped up air filter and high temperature. The aftermarket intake hoses are thinner and more flexible, I could see them collapsing under high temperature for an extended amount of time with also having a restricted/stopped up air filter.
When troubleshooting a car, I always check the common/free/easiest possible causes first. It has served me well.
I bought two cars where the previous owners thought the engines were blown. Fixed one for $30. The other with an oil change and cranking it for 30 seconds.
I had another car that kept blowing the rear tail light fuse. I changed all of the rear tail light bulbs and it fixed the problem.
I just fixed a car that wouldn't stay running after starting. No CEL. Lots of people told ne it couldnt be the IACV because of no codes. Was the common stuck Idle Air Control Valve. Fixed for free.