» » »

Dodge Q&A

Ask Your Question

2006 Dodge Dakota Question: Weird nosie in engine after change to synthetic oil?

 

Question

fitzbrandon, 4.7L V8, Arcadia, FL, October 06, 2009, 17:57
 Rookie

I changed the oil on my 2006 dodge Dakota v8 4.7 high output.I changed the oil and filter. I used the specified filter mopar and 5w-30 full synthetic mobile1.When I turn the key to on the engine malfunction lite and oil pressure light stays on but not while started.I began to hear a strange nosie with the synthetic so I changed over to conventional valvoline the next day. Still I swear I hear this nosie and I don't know what to do? Sounds sort of like faint rattling or knocking. But the check lights don't show unless key is in on position and stay on but not when started.Engine mileage is only 36000.I don't know what is going on and I would be happy to hear any kind of advice that you may have to offer!

1 Answer
Flag This
  • Answer #1

    patrick mannion from Greg Solow's Engine Room, October 06, 2009, 20:05
    Profile_thumbnail
     Master

    At idle the spec for oil pressure is 7psi at 3000 RPM the spec is 35 to 105 psi (which is quite a vague range from Dodge ). A noise is hard to speculate on without being able to hear it fist hand. A "ticking sound" that may go away one the engine warms up and circulates oil could be a "dirty" hydraulic lifter. Perhaps try a produce called Risolene it is a high detergentcy, low viscosity oil additive that I have had success with on other engines with hydraulic lifters.
    A noise on initial cold start up that goes away could be bad connecting rod bearings which is serious but unlikely at such low mileage. A friend of mine with a Durango had a terrible engine noise and both he and the tow truck drive assumed the engine was bad and he was going to tow it to a wrecking yard ended up being a disintegrated fan belt. He had bought a new car before I had a chance to go to his house to look at the car. He still laughs at how he and the tow truck driver jumped to conclusions on what turned out to be a simple fix.

    Reply
    Flag This
Answer Ranks