i have no clue what that is. can you explain a lil more?

 

Here's a link to the thread he's talking about:

https://www.evolutionm.net/forums/ec...us-mrfred.html

Also, yes the periphery bits used to ignore the P0300 on the 8 are the same ones used for the 9.

 

Do you have Windows Vista? I'm assuming you do, because I had that same problem. You have to disable UAC (User Account Control) by doing this: Click Start, type msconfig into search bar, right click msconfig.exe at top of screen and select Run as administrator. At System Configuration screen, select Tools, scroll down the list until you see Disable UAC, click on launch and reboot your computer.

mrfred, if I am reading this topic right, this fix disables the ecu from detecting p0300 or does it just make the ecu less sensitive to detecting the p0300? I was talking to a dsm and transmission guru and he says I might have a major issue and that a p0300 code does not come up just for nothing and ignoring it/disabling it is a mistake, but how do I convince him?

 

Does the disable P0300 work also for P0301......P0304 ?

 

I believe it does. I had P0300 and P0304, as far as I can tell, they both got disabled.

 

Correct, all the P030X get disabled.

 

Thanks a lot

 

bump

i get this same issue. im using windows vista if that matters. anyone have any suggestions?

"cannot create the program c:/blahblahblah xml file. Make sure the path is correct"

Edit

I think I got it working. Had to download a regular XML reader/writer program which seemed to save it this time. Here goes nothing,

 

Hey guys. It may be the "user access control" (UAC) that's stopping you from doing any type of administrative work on your computer. Go to start window (hit window key) -> run, then type: msconfig to get the system config screen. It's been a while since I had Vista, but I think it's in the "tools" tab that gives you a selection to turn the UAC off. After that's done it'll ask to restart I think. Do that and try again.

 

So disabling the P0300 test will in turn stop the car from studdering in 5th gear on the highway? Can someone explain in detail how disabling a code from coming stops a mechanical issue? Doesn't the code come up due to an issue, not the issue comes up because of a code?

 

Hey Hollywood. This doesn't stop the mechanical studdering, it just stops the test from being performed by the ecu. Some of us get the 0300 even if the car is not studdering, so we shut it off. But yeah, studdering means either the plugs are bad or the head gasket Is blown and is leaking into the cylinder.

 

some people have said that when the code comes on the sputter starts. they disable the code and it no longer does that. I've been been witness to it personally.

 

I used to get a studder. Not a hiccup since I first added this. Also too much timing/lean a/f at hwy cruise can be the cause of the P0300...90% of the time it's from bigger cams.

 

I'm running stock cams. The upgraded from the 008 ROM to the 015 ROM and it doesn't seem to do it as much. I'm now also running on just the stock map, not a reflashed generic lame ***** map. Did yours studder happen on the highway?

If the head gasket was blown, i'm sure it would cause some type of an issue in all gears and all the time, not selective to 5th gear at 70ish MPH.

I posted a thread about my P0300 issue with all the descriptions of what happens, and a couple guys posted to disable the code, and that will fix it.

 

I've had only two experiences with blown head gaskets on EVO's, and they were quite different. The first of which was in my own vehicle where it sputtered here and there, then progressively became more and more apparent until there was a chuck of head missing from where the head gasket was blown. With the other vehicle the AFR's went from being 11.7 - 11.5 to being 10.2 - 9.8 however did not have studdering issues.

I also had an issue where I was spiking 26 lbs of boost with the stock head studs, at which time I also had highway studdering. It turned out that I lifted the head and warped the head studs.

Anyway, I guess disabling the 0300 works to stop the studdering, all I'm saying is that there may be a mecanical issue.

BTW: Hollywood has a good question; if disabling the 0300 stop the studdering, how does it work? I always thought that disabling the codes in the periphery's just stopped the tests for each particular device, so why would a test for an issue cause the issue?