- November 12: Chrysler 300 and Dodge Charger Door Panels Warp: Lawsuit news | 8 days ago
- November 8: Chrysler Pacifica Hybrid Class Action Lawsuit is Paused news | 12 days ago
- November 7: Dodge Hornet Hybrid and Alfa Romeo Tonale Hybrid Recalled recalls | 13 days ago
- October 8: Enel X Way Closure and JuiceBox Charger Fires Investigated investigations | 43 days ago
- September 14: Ram 1500 Electric Power Steering Problems Cause Lawsuit news | 67 days ago
Engine Stalls/Shuts Off While Driving
2015 Chrysler 200 (Page 3 of 5)
This problem may be covered under warranty. Ask your Chrysler dealer.
CarComplaints.com Notes: The 2015 Chrysler 200 carries the torch of "never buy the 1st year of a new vehicle generation" with pride.
The 2015 model year is the first year of the Chrysler 200's 2nd generation. It has been plagued by problems from the start. Transmission failure at extremely low mileage, many recalls, problems stalling while driving... the list goes on. Maybe Chrysler should have stuck with the 1st generation.
9.1
really awful- Typical Repair Cost:
- $1,130
- Average Mileage:
- 35,950 miles
- Total Complaints:
- 95 complaints
Most Common Solutions:
- not sure (76 reports)
- they can't fix the problem they don't know what's wrong with (6 reports)
- loose wire to power box (3 reports)
- the car has been returned to me and is working so far (3 reports)
- chrysler buying back (2 reports)
- oil seeped into the map sensor, shorting out the vehicle (1 reports)
engine problem
Helpful websites
- No one has added a helpful site for this 2015 200 problem yet. Be the first!
A D V E R T I S E M E N T S
It started innocently enough. For a couple weeks, when I was turning a corner and going up hill, the car's bell would occasionally sound and the dash readout would say "Press OK for KMH." Then, one morning on my way to work, as I was turning left and heading up a steep hill (I live in the City of Hills), my engine stopped entirely. After a brief moment of panic, I was able to restart the car. The next day, the exact same thing happened (twice!). I tried to get an appointment after the first incident at my local Chrysler dealership (where I had tried the week before to purchase a new car to replace my husband's Jeep but was met with such ineptitude I resolved that I would seek out different brands after being a loyal Chrysler/Jeep customer in my home state for at least a decade -- leasing new vehicles, on average, every 18 months). The dealership was unable to get me in for two weeks, even though my car has a serious fault that could be deadly. I called Chrysler to see what my options were and received no satisfaction. I was told I could take it elsewhere but they couldn't tell me until after I had the work done whether I could be reimbursed or not. I asked to speak to a supervisor and was told I would get a call back in one business day and if I hadn't heard from someone by Tuesday at 8pm I should call back. I was given a case number for follow-up. No call came in and on Wednesday morning I called again using my case number and was told no request was put in for a supervisor to call me and that if they did, I would receive the exact same answer. So, I have a car I can't safely use and Chrysler will do nothing about it. When this lease is up, I will not lease another Chrysler.
Update from Jul 28, 2017: After a two-week wait (with my car tucked in my garage for safety) I was finally able to get into a dealer for repairs. The dealership ordered and replaced the steering angle sensor. Upon return, when I was driving down the same hill on which I encountered the previous problems while driving up it, the car went absolutely berserk. It felt like the car shifted down and I could not accelerate above 24 MPH. The dash flashed a warning about the variable transmission not being available at this time and then lit the engine light, the traction control light, and a big red lightning bolt. After stopping and restarting the car, the engine light remained on and the odometer continuously flashed. I returned it for repair and was told the software hadn't completely updated the day before and that it has now been properly updated. We will see . . .
- shellywho, Oneonta, US