P0303 code and car runs like poopoo
Could you please explain to me in technical terms what makes you think a faulty o2 sensor would cause just cylinder #3 to misfire, yet only throw a P0303 fault and not a o2 fault?
I don't think you know how the ECU reads a misfire and how an o2 sensor works.
I don't think you know how the ECU reads a misfire and how an o2 sensor works.
lmao. i had it overnighted. i get it tomorrow/today in the morning. since its on this 35r kit all i have to do it drop the downpipe and take the o2dp from the turbo. If this doesnt fix the problem i will be seeing denver thurs/fri.
I was getting this code all weekend, Pulled plugs and the third cylinder plug was black. The others were normal. The injector had gone bad. Put new ones in and reinstalled the plugs. So far so good. No codes yet. Good luck.
I swapped my plugs to the Denso Iridium IKH24s and when I took the ones I had in the cylinders (NGK ILFR7H), the 4th one looked pretty dry as if no fuel/oil went to it where as the other 3 had fuel/oil on them. Could it be my injector #4 getting faulty? Right now my car runs like poo on a stick and has been for I'd say a month? When I floor it, it sputters / hesitates from 3.5K RPM all the way to 7K and caused the SES light to go on.. How can o2 sensors go bad? Isn't it rare for that to happen? Comments / advice / suggestions would be highly appreciated. I need my car to be back to normal like before. I had this problem before and the cause was simply the wrong plugs (Evo 8) plugs in a 9, but now the problem got way more complex and difficult to pin point so please anybody if u know what it could be, Lmk, Thanks guys!!
Back from the Dead.. Did that 02 sensor ever fix your po300/po303 SEL code?? i have a similar problem with my car. First it popped a code for P0303, then went away and popped P0300. That went away and now we're back to P0303
Thread
Thread Starter
Forum
Replies
Last Post
Decepticon1225
Lancer Engine Tech
3
Jul 29, 2012 01:58 AM





