Dakota Forumz banner
1 - 3 of 3 Posts

·
Registered
Joined
·
1 Posts
Discussion Starter · #1 ·
Hi all - have a ‘99 3.9L v6 4x4 Dakota Sport, about a week ago was driving down the road at approx 40mph when all of a sudden the engine cut out, and lights on dash went out except for a code which showed up in location marked by arrow in attached photo. Too worried about getting rear-ended plus needing to find safe place to pull over didn’t pay attention to what code was. After pulling over code was gone. Tried restarting multiple times, engine tried to turn over but didn’t. Waited about a minute, then it started up like normal and I was able to drive the remaining mile home. Have driven it a few times since, short distances no problem. No code stored in system, checked myself then had Autozone check and guy there asked me if check engine light came on when engine/power cut out - told him no, no engine light so he said that’s why there isn’t a code. Don’t know what the code was that I saw then or what most likely cause was....any ideas?
3140
 

·
Registered
Joined
·
6 Posts
Hi all - have a ‘99 3.9L v6 4x4 Dakota Sport, about a week ago was driving down the road at approx 40mph when all of a sudden the engine cut out, and lights on dash went out except for a code which showed up in location marked by arrow in attached photo. Too worried about getting rear-ended plus needing to find safe place to pull over didn’t pay attention to what code was. After pulling over code was gone. Tried restarting multiple times, engine tried to turn over but didn’t. Waited about a minute, then it started up like normal and I was able to drive the remaining mile home. Have driven it a few times since, short distances no problem. No code stored in system, checked myself then had Autozone check and guy there asked me if check engine light came on when engine/power cut out - told him no, no engine light so he said that’s why there isn’t a code. Don’t know what the code was that I saw then or what most likely cause was....any ideas?
View attachment 3140
Check the Iacv & inspect if it’s clean and has no carbon deposits then check the throttle body and get some throttle body cleaner and firmly but carefully clean it if it’s dirty with carbon deposits making sure you don’t hit the butterfly plates, to get a even better clean have someone press the gas while the truck is off to clean under the butterfly plates when it opens. Also the Tbps & Map sensor, even the air filter and make sure it’s either clean or new.
 

·
Registered
2003 RT (5.9)
Joined
·
757 Posts
As far as your (IACV) idle air control valve, I can hardly see how it would cause the symptoms you experienced.

I am going to take a guess & say that what probably showed up on the odometer portion of your speedometer said "NO BUS". I am not an expert on these things & I wouldn't offer input except you aren't getting a whole lot yet. I believe the "NO BUS" message means that the PCM is not communicating with one or some of the sensors. As I typed, I am not an expert, so hopefully some one will chime in.

When you say that the engine tried to turn over but wouldn't, I assume you mean that it turned over but wouldn't light off? Or are you saying it wouldn't even turn over?

My experience is limited, but I did have a scenario, a few years back with my '03 5.9 Dakota, in which it would intermittently shut down & after a period of time it would start & run normally & NOT store a code. It was intermittent so I found it difficult to troubleshoot, so I threw some parts at it (ASD & fuel pump relays, crank & cam position sensors). The issue devolved to being permanent (as opposed to intermittent) so I followed the troubleshooting procedure for "crank but no start" and wound up finding no signal to the coil & this led me to suspect that the PCM was at fault. I did wind up sending the PCM out to a facility where they bench checked it & repaired it & my Dakota has started & ran fine ever since.

With that typed, I am not suggesting that this is your issue, just relating my experience which seems somewhat similar to yours. As long as your issue stays intermittent, in my opinion it will be hard to troubleshoot.
 
1 - 3 of 3 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top