WTH p0300 still ?

[whiteboyz]

Ok this might not be the right place for this. So If it is not Mod's please move this to the correct place.

Ok so I have a 6bolt bottom with a 7bolt head, with the green top cas with the harness from RRE, I also have the box checked in link for non 95/96 cas. And yet I still get the dang p0300 random misfire. So I have to cycle my key for it to go away everytime.

I thought with the harness and the box checked in link that I would not get the random misfire ? Any suggestions on why this is still happening ?

Thanks.

 

[H@xtGSX]

At what RPM does it occur?

 

[RadDsm]

Do you have the DTC box checked for the misfire?

 

[whiteboyz]

At what RPM does it occur?

Most of the time on the highway in 4th / 5th gear or crusing around town in 4th not exactly sure on the rpm's . I can check tomorrow and see at what rpm's it does it at. But it is annoying as heck especcialy when I have my kids friends int he car.


I dont think it has done it in 1st gear

Do you have the DTC box checked for the misfire?

I did not at first, Then when the misfire was going on I was not able to check what was going on with my scanner, So I just checked the dtc for misfires in link so I could see if it was that and sure enough it was a p0300

 

[RadDsm]

I mean do you have the box checked for cylinder misfire. It's the second box, it should cure your problem.

You must be logged in to view this image or video.

 

[whiteboyz]

I mean do you have the box checked for cylinder misfire. It's the second box, it should cure your problem.

You must be logged in to view this image or video.

Yes I do. When it first started to missfire. I was unsure of why as i had that box unchecked and was not able to get a CEL, Even using my mac, matco, or old red brick scanner wasnt able to pull a code. So I checked that box and drove it and pop comes a p0300. And I still have it checked.

I will try unchecking it in the morning and driving it around and see how it goes.

I think you can see the box checked in my log, I dont have the code thrown in this 1 log though