5 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHP1124 P1126 at idle
Reported repair
Replace aos bellows
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
The final thing I did was replace the AOS Bellows and that solved the problem.
Leading evidence: 'Replace aos bellows' (1 discussions report resolution; 0 report an unsuccessful attempt). Across 1 matching discussions, the most frequently mentioned possible cause is 'vacuum leak along the shared path' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Replace aos bellows' (1 discussions). For that action, 1 discussions report a resolution and 0 report an unsuccessful attempt. The most frequently reported fix is 'Replace aos bellows', 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 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
I changed the AOS and cel again came on after few miles, while sitting in traffic.
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
Originally it also included P0130 but I replaced the corresponding O2 sensor and that code hasn't come back.
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 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.
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.
5 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Pelican Parts: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 1 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T024951Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I have a new to me 99 C2 with a CEL that keeps coming on. Originally it also included P0130 but I replaced the corresponding O2 sensor and that code hasn't come back.
I can clear it and drive around for a while but if I let it idle for a couple minutes once warm the CEL light will come on.
Typical freeze frame data is coolant 205F, speed 0, rpm 740.
My understanding is that this is too lean for the computer to correct for, on both banks. So probably a vacuum leak along the shared path.
MAF is clean
hoses/connections appear OK
no whistling sounds
I don't have access to a smoke machine and I'm not willing to spray flammable chemicals on a hot engine.
I hate throwing parts at a problem that doesn't have a positive ID but I think I may have reached a diagnostic wall where I can either pay someone to diagnose it or just take it apart along the route of engine-in AOS and see what I find.
Any ideas?
I think you found your problem JrBoulder.
I had the same two codes in my 99 and it was keeping me from passing smog.
I built a smoke machine, looked all over for a leak and replaced a bunch of parts with no luck. Oil cap, gas cap, air flow meter, etc.
The final thing I did was replace the AOS Bellows and that solved the problem.
I got the bellow installed today and it was immediately noticeable how much better the car runs.
Using new spring clamps I couldn't manage to get the bellow onto the AOS. One side would always tuck under.
I ended up installing the bellow with no clamps and then putting some 20-32mm screw clamps on. Much easier.
I had the same issue. I changed the AOS and cel again came on after few miles, while sitting in traffic. I then changed the MAF and has not come on since. I recommend buying the Bosch MAF for $250 instead of $500 from dealer, since the same item.
This is a source reference. Confirm exact model applicability in the original material.
