fullymatted.
Back to search
Planet-9

Troubleshooting my 986's Random Shutdowns

Add to repair workspace
Open repair workspace
Original source
1 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHTroubleshooting my 986's Random Shutdowns

Leading reported evidence

Replace so far

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

What I've replaced so far:

Troubleshooting my 986's Random Shutdowns
Read full discussion summary

Leading evidence: 'Replace so far' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Replace so far' (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 · 1 captured posts examined · 1 partial discussions

Frequently discussed actions (1)

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

Replace so far

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

What I've replaced so far:

Troubleshooting my 986's Random Shutdowns
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.

1 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • Planet-9: 1 discussions

0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.

1 acknowledgements have no verified action link; they do not establish a repair result.

Outcome without a verified action link

Engine temp really makes no difference.

No unique explicit quoted action; no causal link assigned

Generation: 20261026T174436Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1Original post

At the end of last year, I drove the car from ID to NC with two quick stalls/misfires going over a mountain in Montana. The rest of the trip, it was perfect. I had serviced it before leaving my parents' home there, as it had spent a good bit of time in storage. Now, when I'm on the road, it will occasionally completely shut down the engine. I roll to the side of the road, then can get it started after four or five tries (it always cranks). Engine temp really makes no difference. Occasionally, I can kill it immediately if I engage the a/c compressor at idle. What I've replaced so far: Idle Air Control Valve MAF Fuel Pump Fuel Pump Relay Coil/O2/injection relay (rear panel) DME relay (rear panel) Battery (my stepdad had the wrong one in there) Accessory drive/serpentine belt Air filter Crank position sensor I did locate an old mouse nesting spot between the rear trunk carpet and the firewall (near where the coolant hoses go through). That's all been cleaned up and I couldn't spot any chewed wiring, etc. Interesting development with this car today. I went to start it up to point it the other way in the garage. When I went to position 1 with the key (where I always pause to glance at the oil level), a rapping noise started coming from the area of the right rear wheel well..."rat-a-tat-tat-tat-tat-tat". Like muffled automatic rifle fire. As it was happening, the cluster lights were flickering. I shut it off, then tried again. It didn't happen again, but it did take ten or so attempts to start the car (it did crank every time). Once I got it going, textbook idle with no problems. I engaged the a/c compressor, idle adjusted as designed. I've made room for ignition switch replacement gymnastics (for this 6' 3" guy) tomorrow, and will hook up the laptop (Durametric) as well. In the meantime, any thoughts or ideas are more than welcome. Thanks, all.

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