do the '05 models have the 0300 problem? If they don't, i might trade up my '04

 

I've encountered exactly the same thing. The problem is, once it occurs, it just keeps occurring constantly. This is very, very annoying.

Once it begins, the only way I've been able to interrupt it is by plugging in an OBDII code scanner. I find it very strange that the misfiring keeps occurring until the code scanner clears the codes from the computer. This makes little sense to me. Why would the ECU continue the misfiring until the code is cleared from memory? I see no logic there.

Recently this started when I was roughly 200 miles into a 400 mile trip. I simply plugged the code scanner in and left it there. I've learned that if the code scanner is left plugged, the misfire will not reoccur. Go figure.

 

Ted B - try slowing down to like 65mph - downshifting to 4th and take it up to like 90mph. After that it seems to go away. It's worked the past 3 times for me.

I need to get one of those sensors! Can you recommend where or which one?

 

If you are referring to OBDII code scanners, you can 'Buy It Now' for $35-45 here:

http://search.ebay.com/obdii-code-sc...ectZ1QQfromZR8

 

webguy - any updates?

 

Hey man, yeah I have a pretty substantial update. Mitsu pulled a fast one on us, but things are progressing. I will be able to disclose details later, but for now I think it's best to keep quiet.

All is not lost, but right now there is still no buy back settlement.

 

I'm having the exact same problem, and its since the weather changed...I'm like Ted, I just leave my ODB2 plugged in.

 

Got a question about my new Creeder OBDII code scanner. I start the car, plug it in, and it'll display LAUNCH, then the dashes (- - - -), and then just an 'E'. Then it cycles through again. I do have a SES light, but showing no code. Is the 'E' meaning there is like an error or something??

 

Possibly. You don't need to start the car, just put the ignition onto the on position and try again.

 

yeah, my obd II scanner says in bold letters dont start car.

 

i have a P304 code. Same issue as P300?

 

P0304 = misfire in cylinder #4. The codes we are getting are P0300 = random multipal cylinder misfire.


Update: Well my car was at the dealer service center for a full week and they weren't able to fix anything, infact I think its worse now then before. I used to get the code at @ 270 miles into a 360+ mile trip and it would just be a light that came on with little to no feeling of an actual misfire. Just yesterday I made the trip again but this time the code happened over half a dozen times, and everytime I was able to actually feel the car misfiring. I am going to start take matters in my own hands now cause I can't keep leaving the car at the dealer for weeks at a time only to have them put miles on her and not fix sh*t.

 

I sent an email to the guy I bought the scanner from off of Ebay. He asked me what car I drove and I told him. He sent me a note back stating it won't work on my car. What is that? Did I get the wrong kind?

(btw; he offered to reimburse me minus shipping - which is cool.)

 

so, should i not even try the dealership reflash?

 

Who would have guessed it??? I knew it was only a matter of time before the P0300 saga continued for me.

To summarize:

First P0300, 6 months ago while on vacation, dealer (#1) scratched their heads and cleared the code sending me on my way.

On my way home, P0300 again, took to a local dealership (#2). They try to blame race gas (which i have never used up to this point.) I shrug off their remarks, they clear the codes and send me on my way.

Less than a week later, more P0300 codes. I begin pulling the negative battery terminal to avoid staring at the light, which starts to become a daily routine.

A few weeks later, I take the car to another dealership (#3) for the so called "flash fix". Dealership's flash data is not up to date and they turn me away, resetting the code, which comes back on during my drive back home (naturally).

Next day I return to local dealership (#2) for the "flash fix". Car seems to be working fine and no P0300 codes for months.

8,000 miles later (yesterday), driving home from JGTC, while cruising on the highway the car stumbles slightly. I look down and see the SES light come on. I have no doubt in my mind that it is the P0300.

Today, my car is inside the garage with a scheduled service appointment at another dealership (#4) for Thursday (the soonest I can take the car in).

I am at this point seriously considering calling a lemon lawyer. The only things discouraging me are the potential out of pocket cost (which I cannot afford) and the posibility of owing money to return a lemon.

BAHHHHHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!! FKN Mitsubishi!!!!!!!!!!