Check a VIN

2004 Dodge Durango engine complaints

Page 11 of 20: complaints 281 to 310 of 575, newest first, as owners wrote them.

See the summary of 2004 Dodge Durango engine problems: which part fails, at what mileage and related recalls.

Filed Feb 24, 2013 · Engine, Transmission · 125,000 miles · KY

Had driven truck earlier in day had no issues at all. Drove and sounded like it always did!! Went to start it that evening to get daughter from school event and it made a horrible noise and wouldn't start! Mechanic said it was starter. After 2 days of waiting for a starter that noone keeps in stock! Put it on and nothing! Mechanic said it was stuck flywheel. He got it to turn over but the motor was knocking very loud!! Now I'm without a car because I do not have the money for a new motor!!

Filed Feb 22, 2013 · Engine · 115,000 miles · VA

Tl* the contact owns a 2004 dodge durango hemi. The contact stated that while driving at various speeds, the 4x4 light illuminated without warning. The vehicle started to shake violently and then there was a loud noise. The vehicle was towed to the contact's home where it was inspected by an independent mechanic, who advised that a rod had blown through the engine. The manufacturer was contacted and offered no assistance. The failure and current mileages were approximately 115,000. The VIN was unavailable.

Filed Feb 20, 2013 · Engine · 106,000 miles · NJ

Tl* the contact owns a 2004 dodge durango. The contact stated that while driving approximately 55 MPH, the vehicle stalled. The vehicle was towed to the dealer for diagnostics. The technician stated that the engine would have to be replaced because the connecting rod had detached from the engine. The vehicle was not repaired. The approximate failure mileage was 106,000.

Filed Feb 18, 2013 · Engine, Transmission · 90,533 miles · PA

Vehicle started to run a little rough. Wife was at a stop light accelerated upon green and heard a loud noise and a jerk. She nursed it home about a mile or so. Pulled into the driveway and shut it off and oil was everywhere. I looked around and discovered a hole in the engine block behind the passenger side tire about the size of my fist. Have had the durango since it was brand new. Its always ran great. We love our durango. Very upset that this happened. We do not have much money to spare at months end, but we needed a car so we were forced to go buy another. Would like to maybe get the durango fixed. But that might take a little while to get the money now. Be nice if chrysler could send me a new engine or something. I have owned a total of 5 chrysler brand vehicles.

Filed Feb 15, 2013 · Engine · 94,000 miles · NC

Went grocery shopping night before. Woke up next morning to go to breakfast. Went to start durango. Heard loud knocking and then it stalled got out and oil was spewing from under the engine. Took it to mechanic and had to get a $5500 loan to replace the entire engine due to a thrown rod.

Filed Feb 13, 2013 · Engine · 71,000 miles · VA

Tl* the contact owns a 2004 dodge durango. The contact started the ignition and a loud noise emitted from the engine area. The vehicle was towed to an authorized dealer for diagnosis where they advised the contact that the connecting rod fractured, which caused internal damage to the engine. The vehicle was not repaired. The manufacturer was notified of the problem and did not offer any assistance. The approximate failure mileage was 71,000. ..updated 03/18/13 *bf the consumer stated there had been no prior problems other than a check engine light, which the dealer maintained was a vaccuum leak. There was also a rough running problem that the dealer attempted to repair by changing plug wires. That problem was not repaired. Updated 04/26/2013

Filed Feb 13, 2013 · Engine · 100,000 miles · VA

Went to start it for work on day and it started making a horrible noise. I got it looked at by a mechanic, was told that the engine had blown.

Filed Feb 12, 2013 · Engine, Transmission · 125,000 miles · MO

Similar to all other complaints I read. Was driving the vehicle during rain, engine started ticking. Stopped and had it towed to mechanic. Bent rod and busted piston.

Filed Feb 10, 2013 · Electrical, Engine · 118,523 miles · NY

Went to the repair facility to have car looked at code p2302 came up when checking the computer was informed that would need a new PCM replaced with a new factory one and about 3 weeks ago light came back on and when trying to clear it the light blinks and just stays on both times the code p2302 came on the ignition coil for that cylinder was cracked and the plastic was melted.

Filed Feb 5, 2013 · Engine · 110,000 miles · MI

I bought the vehicle 9-25-12. It ran great until 1-29-13 when went to start it to go to work it made a loud crack like metal snapping. Turned out to be to be it snapped a rod and ruined the motor. Chrysler is not taking any responsibility for this problem even though it is happening to hundreds of people. This is obviously a motor defect and needs to be addressed. Hundreds of people are losing thousands of dollars, most of which can't afford a new vehicle or the cost of the repair. Good luck to everyone with this problem. Hopefully dodge will do something about this situation and stand behind their vehicles.

Filed Feb 5, 2013 · Engine · 119,000 miles · MI

Tl* the contact owns a 2004 dodge durango. The contact stated that an engine rod failed. The contact was trying to reverse from a residential driveway when the failure occurred. The contact took the vehicle to a dealer where it was confirmed that the engine rod had failed. The dealer advised that the engine needed to be replaced and also advised that the failure was uncommon for such low mileage. The vehicle was repaired. The failure mileage was 119,000 and the current mileage was 130,000.

Filed Jan 31, 2013 · Engine · 111,000 miles · NJ · fire

Tl* the contact owns a 2004 dodge durango. The contact stated the vehicle made a loud popping noise while she proceeded through an intersection and smoke emitted from underneath the hood causing the vehicle to stall. The vehicle was towed to a local mechanic who stated that a defective rod made a in the engine and the engine needed to be replaced. The vehicle was not repaired. The manufacturer was not made aware of the failure. The failure and current mileage was 111,000. Updated 03/01/13*lj updated 03/07/13

Filed Jan 24, 2013 · Engine · 136,000 miles · GA

I crunk up my vehicle (dodge durango 5.7l) and it threw an rod that busted my engine block and oil pan.

Filed Jan 23, 2013 · Engine · 117,000 miles · VA

The vehicle drove fine on 01/15/2013. I went out to start it on 01/16/2013 and there were a really loud metal on metal sound. It sounded like there were rocks in the engine. I quickly shut the engine off. I had it towed to a local repair shop and I was told that the engine failed. A rod broke and put a hole in the block. The vehicle has been serviced regularly and there were no prior issues. No warning light at all.

Filed Jan 23, 2013 · Engine · 63,000 miles · IL

Tl* the contact owns a 2004 dodge durango. The contact stated that while driving 55 MPH, the vehicle began to sputter and within one hundred feet the vehicle stalled. The failure recurred every time it rained, snowed or when being driven through a car wash. The vehicle was taken to a dealer for diagnosis and the contact was informed that there was a misfire on cylinder number 3. The vehicle was not repaired. The manufacturer was notified but they offered no assistance. The failure and current mileage was 63,000.

Filed Jan 22, 2013 · Engine · 127,500 miles · NJ

Tl* the contact owns a 2004 dodge durango. The contact stated that when the engine was started, it emitted an unusual noise. The contact powered off the vehicle and attempted to restart but to no avail. The vehicle was not taken to a mechanic and was not repaired. The failure was diagnosed by the contact as having a seized engine. The manufacturer was contacted about the failure. The failure and current mileages were approximately 127,500.

Filed Jan 16, 2013 · Engine · 180,000 miles · NJ

Went out to start in the am and the motor was making a loud banging sound and the whole car was shaking. Had it towed to my mechanic and was told the engine blew. Now having it towed to another place to put in a jasper motor is going to cost 5000.00. After reading up on this it seems to be a problem that should be looked into.

Filed Jan 15, 2013 · Engine · 73,000 miles · PA

I was driving my 2004 dodge durango 5.7 hemi and all of the sudden I heard a loud clanking noise coming from my engine. I turned it off and called a tow truck to have it towed to a garage. I was told by the mechanic that the engine was dead and it had blown a rod and could not be fixed. It has been maintained at the dealership where I bought it in 2004 up until two weeks ago when I had it inspected and the oil changed. This seems to be a common problem with these engines and something has to be done about it.

Filed Jan 11, 2013 · Engine · 120,000 miles · TX

Tl* the contact owns a 2004 dodge durango. The contact stated that while backing out of her driveway, a loud strange noise could be heard and the vehicle stalled. The vehicle was towed to an independent mechanic who informed the contact that the number eight rod fractured and the engine needed to be replaced. The vehicle was not repaired. The manufacturer was contacted and offered no assistance. The failure and current mileages were approximately 120,000.

Filed Jan 11, 2013 · Engine · 92,000 miles · MI

Tl* the contact owns a 2004 dodge durango. The contact stated while driving 70 MPH, the vehicle stalled without warning. The contact coasted to the side of the road. The vehicle restarted within a few minutes; however, the failure recurred. The contact stated the failure occurred whenever it rained. The vehicle was taken to the dealer for inspection and was advised that the wiper cowl needed to be replaced. The vehicle was not repaired. The manufacturer was notified but provided no assistance. The failure mileage was 92,000.

Filed Jan 3, 2013 · Engine · 142,000 miles · MO

Tl* the contact owns a 2004 dodge durango. The contact stated that when driving during inclement weather, the vehicle would stall without warning. The contact took the vehicle to a local mechanic, who advised him that the engine rod penetrated the side of the engine block. The mechanic also advised that the engine would need replacing. The contact called the manufacturer to report the failure but provided no assistance. The failure mileage was 142,000.

Filed Jan 2, 2013 · Engine · 102,500 miles · WA

My wife started up the vehicle to take our kid to school. When she started it, it was making a horrible clunking noise and vibrating vigorously. She immediately killed it and told me what happened when I got home from work. I started it up and I immediately knew that the engine was gone. The next morning I noticed an oil sheen on the ground in front of the durango. I have read many things online about this problem and would like for dodge to fix my vehicle. I have kept the oil changed in it regularly and done all required maintenance. I am in the military and need this vehicle for my wife. I cannot afford to fix this out of pocket.

Filed Jan 1, 2013 · Engine · 81,000 miles · SC

Started my durango as I had the day before, to a sound similar of rocks having been thrown into the motor. I immediately turned it off thinking there was something, animal or stick, stuck in motor or fan. Open hood only to find nothing visibly seen to cause such a noise. Started again to the same horrible sound and turned off immediately. Called a very reputable neighbor with lifetime experience and working experience in the motor vehicle field. Upon starting he immediately knew the problem...that my 81,000 fully maintained dodge durango that I owe 4 months payments on yet, drive 1/2 mile to work daily,with no warning whatsoever had a blown motor due to the fact that a cheap part, below previous dodge quality had been installed and caused this to happen.we had planned on driving out of town to get my daughters eyes checked the day before but was unable to afford the gas during this time of year due to being unemployed losing home and having to take a job three times less pay than previous. Thank god daily that we did not because the outcome could have been much worse knowing we could have been traveling on interstate and had this happen. My family has always bought and supported dodge/chrysler vehicles but from this point forward we will no longer support due to the lack of support, quality and care of the dodge/ chrysler industry today! Paid for your buyout again!

Filed Dec 28, 2012 · Engine · 140,000 miles · KY

I have had my truck since feb of this year and have not had any major problems with it. The only issue that I have had is that when it rains or when we go through the car wash it stalls and acts like it wants to cut off. I informed the dealership where I purchased the car from and was told it was not a major issue and to bring in after the holidays and it was ok to continue to drive it. I have kept the maintenance current and just recently got an oil change. On christmas night, I took my father home who lives about 30 miles away from me and came straight back home and parked the truck. No issues or problems. Later the next night, I went out to start it to go to the store and it would not start. It had rained earlier that day and it was cold so I just thought that maybe I needed a jump. It was late so I didn't worry about getting one from anyone. The next morning I got up early to try to start it again and still nothing, so I asked my neighbor for a jump. When he tried to jump my truck it made a horrible noise so we stopped and I called the dealership and told them what happened. They sent two of their mechanics over to my house to try and jump it and they was shocked by the noise they heard. They initially thought it may be the starter and they also verified that all my fluids were full. They ended up towing my truck back to their dealership and a few hours later they called and told me my engine locked up....this was so devastating for me to hear because they told me the repair would be $3000. I have not had the vehicle a year yet and am a single mother of two kids. This problem is very common with the same truck that I have with the hemi engine. I traded my blazer in for this one to be able to have something reliable and really love the truck but cannot believe that there has not been a recall since there have been so many of the same problems.

Filed Dec 20, 2012 · Engine · 138,792 miles · WA

Started vehicle and heard a loud banging noise from the 5.7 hemi engine. Took to a certified mechanic and learned that it had thrown a rod causing fatal damage to the motor. After conducting research this is a common issue that has not been addressed by dodge. Supposedly they used insufficient metal quality when building this engine. They need to be held responsible for this well documented issue. I'm worried that others could experience an engine failure while driving resulting in a possible casualty. Please advise others of this issue.

Filed Dec 19, 2012 · Electrical, Engine · 96,000 miles · NE

Truck cut out would not restart had stopped at an intersection needed to roll to the side of said intersection with no power steering brakes or engine.

Filed Dec 17, 2012 · Engine · 150,000 miles · TX

How many more dodge durango 2004 is it going to take to investigate. Chrysler is recalling 2012 vehicles for the same problem, what most of the complaints are about, engine failure, blown rod . Is it going to taking someone getting killed to wake you up? Seems like someone is not doing their job . Doesn't anyone read the complaints other than other 2004 dodge owners?

Filed Dec 16, 2012 · Engine · 124,200 miles · OR

I have a dodge durango 2004 hemi with approximately 124k miles on it. The car was driving fine for me and my family until this morning when I tried to start my car, it was making a loud noise like there was rocks in the engine. It doesn't start up like normal and if it does you can't even drive it. Sounds like the engine is in pieces. I've heard a lot of dodge hemi owner's had a lot of problems with their engine seizing up while they were driving at high speeds and everything just completely shut off on them(very dangerous). A lot of forums that I read online has the exact same problem that I'm having.

Filed Dec 11, 2012 · Engine · 137,000 miles · NJ

Tl* the contact owns a 2004 dodge durango. The contact stated that she started the vehicle and heard a loud noise that sounded similar to several rocks being thrown around under the hood. The vehicle was towed to an independent mechanic for diagnosis and the contact was informed that the engine would need to be replaced. The manufacturer was notified but offered no assistance. The VIN was unavailable. The failure and current mileage was 137,000.

Filed Dec 10, 2012 · Engine · 95,000 miles · RI

This morning I went to start my dodge durango and there was a loud bang from the engine. A connecting rod failed on the vehicle and now the engine is not repairable anymore. This is a big safety concern because this could have happened on the highway or in any other every day dangerous situation where the car would be inoperable. Such a failure should not happen to a vehicle that has 95k on it. I feel that dodge should own up to a design flaw on the engine, because I have read a number of complaints on the internet about this exact failure at around the same mileage. I have gotten no support from dodge on this issue even calling their customer care only to hear that my car has too many miles for them to help me out.

VIN decoder

See the problems and recalls for an exact car

Buying a used 2004 Dodge Durango?

Check the exact car before you pay: accidents, salvage or flood titles, odometer readings and previous owners.

Check its history