11 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHFault could diagnosis help
Leading reported evidence
Check cables and did not see anything loose
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 checked all the cables and did not see anything loose.
Leading evidence: 'Check cables and did not see anything loose' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check cables and did not see anything loose' (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.
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 by autozone to check the codes and forgot to clear them.
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
I ran by autozone to check the codes and forgot to clear them.
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
Check too the intake system didn't develop a leak from the off and while you are there check the exhaust doesn't have a leak either.
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.
11 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: 20261026T165820Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Recently had an off during a DE that cracked the driver's front radiator. I went ahead and installed 2 new radiators. We started the car up and received 9 fault codes. All codes are regarding misfires and O2 sensors. I could use some help with ideas as to what would be causing them.
Codes are:
P0300
P0301
P0302
P0303
P0304
P0305
P0305
P0130
P0150
I'm not sure if something came loose during the spin. I've checked all the cables and did not see anything loose. Any ideas?
Can’t think of any good reason why these faults would be associated with what happen. Are you sure they were not present before? With a PST2 you see when the fault code was recorded. Have you cleared the codes to see if they come back? Also, you can connect a PST2 or Durametric while the engine is running to see if the o2 sensors are working and if is it misfiring.
It is idling rough, but I don't detect a miss when revs increase. I ran by autozone to check the codes and forgot to clear them. I'm confident there is something to the codes. I'll probably take it down to RAC tomorrow. I wonder if it is safe to drive or should it be trailered?
Check again. P0130/P0150 point to the #1 sensors on bank 1 and bank 2.
Check too the intake system didn't develop a leak from the off and while you are there check the exhaust doesn't have a leak either.
Let us know what it turns out to be. Durametric is relatively inexpensive and would be great to diagnose this type of problem.
Also, did you get a high engine temp or low coolant level warning after the incident? Hs the coolant level dropped after you made the repair?
