cold start runs great for about a minute then starts skipping throwing these codes. can turn off for a minute and restart everything will be fine. can drive the rest of day with no problems. does this every cold start. 2009 dodge charger 5.7 police package 67,000 miles

 

You can visit this site and do some research on the causes and solutions to those codes.


http://www.obd-codes.com/

 

Identical issue with my 2007 Durango with 5.7 hemi. Any possible solution would be greatly appreciated.

 

If you click the link in the above thread, it will list the possible solutions.

 

Thanks for the link.

I looked at the link and the dealer reprogrammed the PCM module for me with 6 updates. Car was misfiring when I took it in and perfectly smooth after the update. I let the car cool this afternoon and took it for a drive tonight. I got the P1416 again and rough acceleration but by the time I got home the pending code P1416 had cleared itself.

Dealer did verify the MDS were all working fine which I had replaced a month ago. I don't believe it would be the oil since I have had it from new and nothing but Mobil 1 every 5-6,000 miles. Car has 152,000 miles.

All I can think is the lifter is shot and will probably pull the head. Uggh!

 

So I did the lifters and camshaft myself. Still have the P1416 code intermittently once warmed up.

Any suggestions before I head to the dealer and let them diagnose it?

 

Cylinder 6 reactivation issue. Since the cam/lifters are new..... did you change the solenoid as well?

 

Solenoid for cyl #6 was replaced twice since I figured the first one must have been defective. Both were Mopar brand.

After replacing the MDS for the second time I thought the truck was fixed since it ran perfectly from a cold start for the next 3 days. The 4 and 5th days it reverted back to the same issue of a P1416 and really rough running after 1-2 minutes of driving. Turn it off for 10 seconds and restart. It is then good for the day.

I checked the injector for cyl #6 is firing fine at idle. Two dealers are stumped without going on a multi hour trouble shooting journey which I wish to avoid.

 

Bad connection somewhere.

 

I am having the same issue you had. Did you figure out what was wrong?