1999 Dodge Durango Doesn't want to run

  • 5.2L
  • V8
  • 4WD
  • 215,000 MILES
So I have a 99 Dodge Durango 5.2 v8 it has 215000 miles on it and I bought it about four or five months ago. It threw a catalytic converter code and about two weeks after it did that I started it one morning and it just wouldn't run right like its misfiring. I cut the converter out and it ran great for about a day then I went to start it to take it to school on Monday and it was surging when it idled. I took it on the freeway and it started to run fine, then when I got off the freeway it started to act up again like cutting out and dying on me I have no idea what's going on with it. Please help
Do you
have the same problem?
Monday, October 26th, 2015 AT 1:22 PM

1 Reply

You aren't going to be able to diagnose this until you reinstall the catalytic converter. The Engine Computer uses the oxygen sensor behind the converter to monitor its efficiency. With no converter to clean up the exhaust, the rear oxygen sensor will report that no change is taking place to the gas as it passes through. That will cause a diagnostic fault code to set after a short period of time related to "catalytic converter efficiency". Since there is a known problem, that can't be relied on as a reference for other tests, so those will be suspended. The Engine Computer may not detect a malfunction that would lead you to the circuit or system that needs further diagnosis. Without those fault codes or test results, you could spend weeks trying to figure out where to start looking.

Misfiring is usually due to worn spark plugs and wires, especially when the problem is intermittent. A spark-related misfire will result in raw fuel going into the exhaust where it will burn inside the catalytic converter and cause it to overheat. If the catalyst melts, it will stop working and could be the cause of the original fault code. This is where ignoring a minor problem can turn into an expensive one. That's also what can happen when the "converter efficiency" code is set which turns on the Check Engine light. Since the light is already on, you'll never know if another, totally unrelated code sets that is related to something else that could turn expensive if ignored unintentionally.
Was this
Monday, October 26th, 2015 AT 7:33 PM

Please login or register to post a reply.

Recommended Guides