Originally Posted by mfr122887

So you cut each value in half? And just to make sure I have the right definition, in table 1 they are all 0's right?

Originally Posted by Smogrunner

Interesting. Switching from 94170008 to 94170015 cured the p0300 for me.

Originally Posted by DCsleeper

Correct you are. The main change from the older series ROM 94170008 and series 94170014 was a change to one of the knock filter tables. I think it was the first or second table. Would have to go back and compare to be sure. When I had the flash performed by mitsubishi years ago the frequency of the error dramatically dropped. Later I flashed my ECU with the latest ROM in the series 94170015 to see if it would cure the problem for good. Unfortunatly it did not, but again lowered the frequency of occurance. Between 94170014 and 94170015 I was not able to see any changes in the tables currenlty viewable in ECUFlash.

From what I have read there seems to be several causes of this code. For me, I have to believe that it is due to a vibration caused by the trans. The reason I know this is I have tried everything else over the past 3 years to get rid of the annoying code (new injectors, ignition amplifier, reflashed ECU, and new exhaust hangers to prevent the exhaust from hitting anything).

I really wish that someone good with disassembling code would just find the p0300 error code and disable it. This is the only code I ever throw and it is incredibly annoying. For me, only occurs in low/med load conditions about 3500 rpms in 5th gear no boost (about 75 mph cruising).

Originally Posted by spdracr

between this and the phantom knock when pulling from a stop is driving me nuts lol

Originally Posted by Smogrunner

Interesting. Switching from 94170008 to 94170015 cured the p0300 for me.

Originally Posted by Jazzie604

It appears that there may be 2 common causes for the P0300-idle issues that may have been adjusted by the reflash, and mechanical issues at cruising speed. I have recently had problems with the cruising issue. Sometimes the light comes on with no noticable cause, and sometimes I get a definite dead-hole stutter. Has anyone else had the light come on after the stutter, or is it always on before you feel a miss? I plan to do some datalogging for myself, but I want to find out if the miss is a result of the code changing engine performance, or if the code is the result of an actual miss.