P0300- Misfire code
#1
On The Tree
Thread Starter
iTrader: (9)
Join Date: Feb 2004
Location: Florence, AL
Posts: 158
Likes: 0
Received 0 Likes
on
0 Posts
P0300- Misfire code
Yea, my car is throwing that code
Had it tuned back at the end of July 06 after swapping in a cam. Is the best idea to just call the guy who tuned my car? I read that many things can contribute to a cylinder misfire.
Also, is it okay to drive the car?
Had it tuned back at the end of July 06 after swapping in a cam. Is the best idea to just call the guy who tuned my car? I read that many things can contribute to a cylinder misfire.
Also, is it okay to drive the car?
#2
TECH Enthusiast
iTrader: (16)
Join Date: Nov 2004
Location: Birmingham, AL
Posts: 577
Likes: 0
Received 0 Likes
on
0 Posts
Have the tuner turn it off, and no I don't mean clear the SES light. If he doesn't know what your talking about, find a new tuner. I drove my car for 2 weeks with that code being thrown with no problems.
Last edited by ls1muscle; 01-14-2007 at 07:34 PM.
#4
Do you know if the tuner modified any of the knock settings? Yes, I would contact the tuner. Many tuners will update the tune at no charge particularly when there have been no other modifications. That 111LSA could definitely trip the sensors at idle or low RPM. You should double check the plugs and wires just for peace of mind.
#5
On The Tree
Thread Starter
iTrader: (9)
Join Date: Feb 2004
Location: Florence, AL
Posts: 158
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by 2001NBMZ28
My car has thrown P0300 a couple times over the years, I just reset it - why not try just clearing the code first and see if it comes back?
#7
On The Tree
Thread Starter
iTrader: (9)
Join Date: Feb 2004
Location: Florence, AL
Posts: 158
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by John-SDPC
Do you know if the tuner modified any of the knock settings? Yes, I would contact the tuner. Many tuners will update the tune at no charge particularly when there have been no other modifications. That 111LSA could definitely trip the sensors at idle or low RPM. You should double check the plugs and wires just for peace of mind.
What bothers me is that it has just now started doing it. Never got it the first few months
Trending Topics
#9
TECH Regular
iTrader: (2)
Join Date: Nov 2001
Location: Mims, Florida
Posts: 456
Likes: 0
Received 0 Likes
on
0 Posts
I had the P0300 mis-fire code a bit more than one year ago. After doing alot of coil swaps, spark plug swaps, and more, it turned out to be a broken valve spring. Very strange, it was not what anyone would typically expect. I changed the valve spring and clear the code. The code has never come back.
#14
Originally Posted by DustinWS6
Ugh! I cleared it and it came back this morning. Car idles and run fine though. Could my loose exhaust clamp causing my duals to rattle cause it to throw the code?
#15
On The Tree
Thread Starter
iTrader: (9)
Join Date: Feb 2004
Location: Florence, AL
Posts: 158
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by John-SDPC
People have definitely had issues with stuff 'banging' around and causing false misfire codes. Not for sure about a rear exhaust clamp doing this (assuming you're talking about something back around the catback). More likely that 111LSA.
So you think it's because of my 111LSA cam? It does shake pretty good