Code UO1000, randomly car shuts off

I have seen this a number of times. This code is set basically when another module is expecting some information from the PCM but it never gets it due to it shutting off.

There are a couple things that could cause this. So when you replaced the plugs, what brand plug did you use? If you used a split fire of something else then that will cause this.

However, if you used a Champion plug then more then likely you have a PCM or crank sensor issue.

What happens is when these start to fail they are susceptible to excessive electrical interference. So if it were me, I would make sure the plugs are Champion and then replace the Crank sensor before you replace the PCM.

https://www.2carpros.com/articles/crankshaft-angle-sensor-replacement

I am attaching the info below on this code. Please run through this info and let us know what you find with this. Thanks

Sounds great. Thanks for the update. We will wait to hear back from you. Thanks

Is this code always active or does it go stored and you can clear it until it cuts off again?

If so, does your scan tool say what module is actually setting this code? Basically we are trying to work through the steps that I attached before so we are going to have to find this info or we may have to just replace the PCM without confirming it.

Lastly we need to confirm this is the only code you are getting when this stalls. So it is important to know if this code was just there one time or it has been cleared and comes back each time it stalls.

Thanks

Okay. That code is telling you that some other module like the transmission controller or ABS or drivetrain control module (4WD) was not able to communicate with the PCM when it needed to. So it is not going to name it in the title of the code. It is going to be in the scan tool that says something like ABS - U0100- PCM/ECM "A" lost communication. This means the ABS is what lost communication with the PCM. However, your tool may not give this level of detail at which point we should ignore it.

If this code is active when this happens then the module that set the code against the PCM would be the issue. However, if it is stored and it not there each time it stalls then it is not related or at least not causing the stall.

That means we have a rough idle and stall with no codes. That means we most likely have a based engine issue. So does your scan tool monitor the o2 sensor data?

If so, what does it read while you are driving and when it stalls?

I am concerned with either the short term fuel trims or o2 sensor voltages. They are not the easiest to watch when driving so either have someone else drive or just set your phone up to record about 15-20 second video when it is idling rough and then what it does if you can catch it stalling.

However, I think we need to chase down a vacuum leak and just eliminate that as that would be the likely cause of something like this.

Here is a guide that will help find it:

https://www.2carpros.com/articles/how-to-use-an-engine-vacuum-gauge

Did the car stall when this happened? If not, then we need to start a new post as this is most likely a different issue. I understand that the check engine light came on but there are 1,000 reasons this could happen.

Basically we need to keep each post to one issue and this was the U code and stalling so if we have a different code and no stalling then we need to start a new issue.

https://www.2carpros.com/questions/new

Sorry for any inconvenience but others will not find the solution to this issue if it is under this post.

Thanks

No apologies needed. We are here to help but our goal is to not only help you but make it so that others can find your solution so they can do what you did if they have the same issue. So that is the only reason we need to do that.

Thanks for using 2CarPros.