Well, since MItsu doesn't have a final resolution to our problem, i just bought a OBDII reader which reads the error codes and clears the codes. I got mine for $50 and its called Creader

 

Well guys, here goes nothing. First of all... knock on wood. After a full transmission rebuild, replacing diff's and a lot of "coercing" I have been almost 4000 miles with no SES light. I still have a slight vibration around 60-70 mph but it is almost negligible compared to how it used to be. No stumbles, no major vibrations, no nothing. The service tech was really cool about letting me know what was going on. He showed me the tranny gears and showed me there was some slipping and grinding in 4th and 5th gears. he says this vibration caused my knock sensor to be set off. He also notice a major wobble in the rear diff. so he replaced it too. I checked my warranty info and I got the 10yr/100k mile warranty (yay!!) so I told him I would be back if anything acted up. I was kinda hoping it does so I could justify lemoning it and getting an MR. (pipe dream i guess). the service tech listed my VIN as having these issues with Mitsu. He said that way Mitsu would let him know if anything new is found out about the p0300 issues, and if there are more problems I will find out about them. So.. no more mustang for me I am cruising again and still loving my car.

If any more problems pop up tho. I am definately going with the buyback option. After all... the Evo MR is near.
-Phrostie

P.S. I had a grinding when trying to put the car into first gear under any speeds at all. The dealer in FL said this was normal for the EVO so I let it go. In Cali the service tech said my first gear synchro was jacked up so he went ahead and replaced it while he was at it. (I really like this guy)

 

I hope replacing the transmission fixes the problem. I just got the code recently at 14500 miles. Also, a friend of mine has the code since 4000 miles.

 

EEEeekkk..

Well, so far I've got 600 miles on the car with the new flash and it appears to be OK with no SES light. I'm gonna give 'er another full tank of gas before I put my cat delete back in for the real test. heheh

 

Will getting a aem standalone fix this. My xede did.

Phil

 

well add my name to the list of people having the p0300 SES. On my way home from work just crusing in 5th I felt a studder and then the SES light came up. A trip to autozone confirmed that is was a random multipal cylinder misfire. Monday I'll call the dealer and schedule an appointment for a reflash.


Without reading the entire 21 page post can anyone tell me if the reflash actually fixes the problem??

Thanks

 

i got the code for the first time after leaving a respectible tunning shop (wont say which one right now) but i think they told me it was a misfire in clylinder #4, never had this code or any other code in 20000 mile, you think it might be just a bad plug, or they messed up somewhere.

 

i guess people are sick and tired of this thread, and the p0300 situation. don't blame you.

 

Unfortunately....
There is no ONE answer to your question.....

The remedy has worked for some...
The remedy has not worked for some....

For me... it turned out I had a bad #1 seal and piston and had them and the injectors replaced (engine basically disassembled and rebuilt).

Car was out of my hands for 3+ weeks. No cost to me.... No SES light since.... been a couple thousand miles now. Engine running strong no issues.

 

i hope they wouldn't have to tear down my engine to fix the problem... if the reflash doesn't work i'll just get a scan tool and clear it myself, my last daily driver threw random multiple cylinder misfire codes all the time but they were false signals probably from the knock sensors.

Its a pita to have to run to the dealer for every little thing.

 

It's more about making a road trip without your car f#cking up every 30 seconds, but yeah.

 

I started a poll on this in an attempt to collect fixes and non-fixes:

https://www.evolutionm.net/forums/sh...d.php?t=109179

 

This is exactly what I'm experiencing. I've been trying to diagnose the problem and blame it on one of my recent mods (though it was the DV, but not). What's weird is this didn't pop up until about a month ago - at 15,000 miles.

I've been reading what everyone has been doing to try and remedy the situation, but seems like a mis-match of efforts and no one real solid fix. I'm going to keep clearing code myself - using the old fashioned battery remedy - and will stay tuned.

 

I would like to thank everyone for the help. I would not have had I clue and may have been strung along forever. . read all the post and you will learn what has been tried. you may choose to live with the problem and just clear it yourself with a code reader. Good Luck and

THANKS for the internet!

 

my P0300 code turned out to be 2 fouled spark plugs, dealer replaced them but now I'm bucking when I get on/off the throttle.