The car will almost stall, randomly, when stopped at a stop sign or light. it has now started to act like it is going to stall when we start it. the car hesitates, randomly, when you go to accelerate. this has happened to us many times. entering the interstate it acts like it stumbles before it will respond. we have pulled out onto a busy street where acceleration is a necessity and the car hesitates and almost caused an accident. most recently, switching lanes on the interstate we lifted our foot off accl. to allow a car to pass us when we went to accelerate again the car would not respond, a car came up on us in our lane and almost rear ended us. (this was on the way to the dealership for the problem) the dealer has been unable to duplicate the issue and nothing was recorded on the computer. many complaints about this issue on chrysler 200 forums. we have had a blk box installed and no feed back from dealer was provided even when requested in writing and verbally. we have an attorney, chrysler has put a low value on the complaint and we are not going to settle case at this time. i hope we do not have an accident while collecting data! *tr *js
When going into a stop or a slow down, the engine stalls; this is now the 3rd time chrsyler is looking into it. car is a 2012 chrysler convertible s purchased in feb of 2012 w/ 100 miles. 1st. happened at ~5k 2nd happened at ~7k in july 18,2012 3rd happened at ~12k oct 8th, 2012 this last time the car died on my 4 times in 5 minutes. dealer was able to reproduce the error. they are saying it is caused by a asd(v) circuit in which the relay is broken. 1st time they reprogrammed the computer. 2nd time they replaced the part containing the relay. 3rd it is the relay again. it is a major safety concern as i almost got rear ended by a van this time as i was making a legal u-turn. *tr
Took car in to dealership years ago to have head rest and airbags fixed. received a notice by inputting my vin that these fixes were incomplete . also discovered that the 3.6 pentastar engine from the factory had substandard engine bearings which could result in the engine seizure and the remedy was for the factory to replace the engine. my 2012 chrysler 200 was manufactured during this time frame, yet was never notified by the manufacturer of this dangerous condition.
Car continues to have a speed impediment; it hesitates or stalls at 10, 20, 30, and 40 mph increments and also at various times with acceleration from a low speed to a higher speed such as entering a highway from an "on ramp". chrysler tells the owner to continue to just drive it and the computer will adapt to the car. car stalls, hesitates or maybe experiences a seizure. in shop for more than 4 times with no resolution. think this needs to be investigated as a safety recall. dealer service man was asked if there was a recall and this question was met with an answer that there have been no recalls. *tr
This car was bought new with approx 300 miles brought from a dealer's inventory in kokomo, in to one in northern kentucky, where it was bought 11 may ,2012..it had been on the previous dealer's lot, as part of inventory, i believe since sep,2011. in total it has stalled while stopped at a light 2 separate times..twice it has either quit while slowing or downshifted causing quite a violent throw forward of persons in their seats while at a relatively slow speed coming to a stop...in the old days it would be the jerk you get while popping a clutch to get a car started with a bad battery.. the third time it stalled was backing out of our driveway...we are now approaching 1000 total miles on the car with less than a month of ownership...made first visit to a dealer service 30 may 2012,..pcm code was updated,but could not duplicate problem..have had one jerky downshift since then ..this has been the recurring theme of many of these instances written up on blogs concerning this model over last 2 years.. side note..this car has remote start capability on the key fob..i noticed a recall last year for some vehicles where they noticed the circuit board inside a fob had vibrated loose, and somehow was sending signals to some component in the car which was causing it to stop...ie. no codes associated with a malfunction like that...might be something to look at too. twice also, the hint of an electrical smell has been detected...same smell i experienced when the pcm on my 1993 ford van cooked itself a couple years ago..at first i wrote it off as a new car thing..but combine that with present and past experiences...well, the connection may not be coincidental. *tr