Software problems of the 2007 Jeep Commander

Final drive control module (fdcm). Vehicle had n23 and p73 recalls completed. Sometime later, lost 4wd low. Returned to dealer for re flash per fca recall for life. Upon investigation, they cannot access fdcm due to a short; part needs replaced. Called fca multiple times and they will not cover as its hardware as opposed to software recall. There are many instances, in my research, where their recall causes the loss of 4wd low. Fca knows their "fix" was for a hardware issue and they fail to cover it. Owned Jeeps a long time and I'm done. I have six children so they maybe they can do the math on what this will cost them over generations!.

After a schedule tune up, where two coil packs were replaced, and a pcm software update was performed our 2007 Jeep Commander began stalling at slow speeds. Usually under 20 mph or at a stop when the engine is at or near idle speeds, the engine will obruptly stall without warning. There is no check engine light and no error code. Our local Jeep dealer has made several repair attempts including replacing the pcm, and shielding the engine wiring harness with aluminum foil. The problem continues. The key must be cycled to the 'off' position to restart the engine. The engine has stalled at high speeds a few times making for a very dangerous situation.

Tl- the contact owns a 2007 Jeep Commander. The contact stated that the key remained stuck in the ignition. The contact also stated that the vehicle stalled on several occasions. The vehicle was taken to a dealer where the ignition switch was replaced and the failure recurred. The vehicle was taken back to the dealer, who replaced the ignition cylinder and recoded the cylinder. The contact stated that three months later, the engine rpms increased and the engine warning light illuminated. The vehicle was taken to a dealer where the ignition switch was replaced and code was cleared but the failure persisted. The contact stated that the check engine warning light illuminated and the vehicle jerked. The vehicle was taken back to the dealer where the software was updated and a new computer was installed but failed to remedy the failure. The manufacturer was notified of the failure. The approximate failure mileage was 32,520. Djr.

I own a 2007 Jeep Commander at about 10,000 miles it started to stall and turn off. Dealer did not replace any parts only flushed the on board computer and updated the software. Months later it started to do the same thing. Dealer did not find anything wrong and performed the same task of flushing the computer and updating its software. Two years and 23,000 miles and the car is having the same problem. I have an extended warranty so I'm going back to the dealer, but I don't think they we fix the problem . Tr.