mean02

Made one nitrous pass at the track tonight, car started surging when i slowed down and eventually died. now I have to keep my foot on the pedal or the car will die. the SES light flashes non-stop. The scanner says it's an O2 sensor. They are both new. Any ideas? Maybe some fouled plugs? THey are new also.

mean02

anyone?

Need2gofaster

Check the metal tube connected to the front of your throttle body. I had a n2o backfire and it started leaking air form that tube and it was surging. Make sure there is still a o-ring on the tube also.

PREDATOR-Z

Probably fried the O2 sensor. Time to hoist the car or get on your back. Oh and check all you plugs too.

68birdls1

iTrader: (46)

if the comp says its the o2 sensor, then i am pretty sure thats what it is!

Predator

The computer never lies.

KGSloan

hahahaha

i've chased down many "o2" problems that had nothing to do with the o2's. check for vacume leaks all around the intake. make sure nothing blew off. it would make the car run like you describe, and possibly trigger an o2 code.

hellbents10

iTrader: (10)

Start lookin for a vacum leak. there is a million o2 codes. Just cause you throw a code for a o2 doesn't mean its a o2.

Need2gofaster

when i had my backfire it threw the same o2 code when i blew the tube out. Once i put the tube back in with the new o-ring(the old one got sucked threw the engine!) everything went back to normal

Predator

Sorry for the bad info. My experience so far is that the computer has never lied to ME, yet. I was always doubtful about codes that were thrown looking for other problems, and it always turned out that the computer was right afterall. Sometimes the problem would be INDIRECTLY related to the code, but the code was always thrown for a logical reason. Anyway, many folks here have way more experience than me, and my computer comment was based on my own experience. With that being said, I don't think it could hurt to check the O2 sensors, or something that might indirectly cause that code to be thrown.

The Juggernaut

iTrader: (7)

Might be a broken spring, causing it to run rich, throwing the O2 code.

slow trap

iTrader: (22)

how about the maf.i've heard of another car acting like that.

mean02

I checked the maf and it looks fine. I have double springs. Could the inside or outside only have broke?

KGSloan

i thought you were joking as well. sorry, didn't mean to sound like a dick. most of the o2 codes i have experienced have been indirectly related to the o2's and not the actual o2's. it seems it's allways something else that makes the computer think the o2's are messed up. once again, my appoligies for coming off harsh.

Predator

No problem man, and no offense taken.

I should have explained that I meant that even if the problem is indirectly related to the code, the computer isn't lying. The whole point was that the O2 code was thrown for a reason, and that reason can usually be traced back and integrated with the thrown code. Anyway, splitting hairs.

The Juggernaut

iTrader: (7)

Yes, the outside could break.

Happened to me(exhaust valve) and ran like yours.

mean02

Thanks for the help. I'll be on vacation next week, I'll pull her apart then.

The Juggernaut

iTrader: (7)

np....pull the valve covers and take a look

Need2gofaster

have you started the car and opened the hood and listened for a vaucume leak?