2010 LT 5.3 V8 Flex Dying Randomly HELP!!

[LTHoe52]

Have a 2010 LT 270K that dies randomly while driving no warning no signs no triggers could be months apart or days apart complete loss of power, I Pop the negative cable off and it fires back up no problem sometimes with a engine light that vanishes within a couple of minutes.

Also run into a random won’t start with no signs no warnings no check engine light, how power to controls but doesn’t try to start/crank at all no sounds no motion. I can pop the negative off and it fires up fine could be months before it happens again or a couple of days… throws a service stabilitrak service 4wd then will die if cranked and sitting in park

I’ve replaced the computer and tighten the fuse box down where it sits (like a big plug)

Running out of options…

Mainly…
U0100
P013E
P0138

 

[Joseph Garcia]

Welcome to the Forum from NH.

Lots of knowledgeable folks here who freely share their knowledge, experiences, and perspectives. Knowledge is power.

I hope that you will become a participating member in the Forum's discussions.

Pics of the truck, please.


Simple Google search yields the following:

The U0100 code indicates a lost communication with the Engine Control Module (ECM) or Powertrain Control Module (PCM). This means there's a problem with the communication network (CAN bus) that allows different vehicle systems to talk to each other. Symptoms can include a check engine light, difficulty starting, and poor engine performance.
The P013E code signifies an O2 sensor delayed response from rich to lean in Bank 1, Sensor 2. This means the Powertrain Control Module (PCM) is detecting a delay in the O2 sensor's response to changes in exhaust gas composition. Common causes include a faulty downstream oxygen sensor, wiring issues, or a catalytic converter problem.
The OBD-II code P0138 indicates a high voltage in the oxygen sensor (O2 sensor) circuit for Bank 1, Sensor 2. This code typically means the O2 sensor is either faulty or has a wiring issue that's causing a high voltage.
Do you have, or have access to, a quality bi-directional scanner? This would be very helpful as you could troubleshoot the O2 sensor operation to see if/where the source of that issue is. If the O2 sensors are old or original, it may be time to replace them. They are a relatively cheap item to replace, and be sure to replace them with genuine GM O2 sensors (aftermarket ones tend to produce issues).
I would also check the battery with a bench load test to be sure the the battery is in good shape, as low voltage as can cause major issues in the truck's electrical network.

Other members of this Forum much more knowledgeable than me in this area will chime in.

 

[LTHoe52]

Welcome to the Forum from NH.

Lots of knowledgeable folks here who freely share their knowledge, experiences, and perspectives. Knowledge is power.

I hope that you will become a participating member in the Forum's discussions.

Pics of the truck, please.


Simple Google search yields the following:

The U0100 code indicates a lost communication with the Engine Control Module (ECM) or Powertrain Control Module (PCM). This means there's a problem with the communication network (CAN bus) that allows different vehicle systems to talk to each other. Symptoms can include a check engine light, difficulty starting, and poor engine performance.
The P013E code signifies an O2 sensor delayed response from rich to lean in Bank 1, Sensor 2. This means the Powertrain Control Module (PCM) is detecting a delay in the O2 sensor's response to changes in exhaust gas composition. Common causes include a faulty downstream oxygen sensor, wiring issues, or a catalytic converter problem.
The OBD-II code P0138 indicates a high voltage in the oxygen sensor (O2 sensor) circuit for Bank 1, Sensor 2. This code typically means the O2 sensor is either faulty or has a wiring issue that's causing a high voltage.
Do you have, or have access to, a quality bi-directional scanner? This would be very helpful as you could troubleshoot the O2 sensor operation to see if/where the source of that issue is. If the O2 sensors are old or original, it may be time to replace them. They are a relatively cheap item to replace, and be sure to replace them with genuine GM O2 sensors (aftermarket ones tend to produce issues).
I would also check the battery with a bench load test to be sure the the battery is in good shape, as low voltage as can cause major issues in the truck's electrical network.

Other members of this Forum much more knowledgeable than me in this area will chime in.

Thank you sir!!

 

[Dustin Jackson]

@LTHoe52 Since you mentioned that popping the negative battery cable off fixed the problem I am pretty certain the negative battery cable is your problem. They are known to go break internally in these tahoes and the 2015-2020 tahoes. Next time it happens, instead of removing the negative battery cable just push it back towards the firewall and see if that fixes it, that would confirm the problem is within the cable and not by removing it from the negative battery post.

 

[LTHoe52]

@LTHoe52 Since you mentioned that popping the negative battery cable off fixed the problem I am pretty certain the negative battery cable is your problem. They are known to go break internally in these tahoes and the 2015-2020 tahoes. Next time it happens, instead of removing the negative battery cable just push it back towards the firewall and see if that fixes it, that would confirm the problem is within the cable and not by removing it from the negative battery post.

My man I appreciate it I will give it a try!

 

[LTHoe52]

My man I appreciate it I will give it a try!

I got in it yesterday and it threw a service stabilitrak and service 4wd popped the cable and back to normal, would the cable be the reason it dies sometimes while driving I get a loss of communication code.. computer is new

 

[Dustin Jackson]

@LTHoe52 I think so, doing the test I suggested will help us pinpoint if the problem is fixed by discharging the electrical system or if adjusting the negative battery cable is enough to get it going. Depending on what your results are it could just be a bad battery cable or it could be something else that is fixed by resetting the computer (disconnecting the negative battery cable from the battery)

 

[LTHoe52]

@LTHoe52 I think so, doing the test I suggested will help us pinpoint if the problem is fixed by discharging the electrical system or if adjusting the negative battery cable is enough to get it going. Depending on what your results are it could just be a bad battery cable or it could be something else that is fixed by resetting the computer (disconnecting the negative battery cable from the battery)

Thanks brother!

 

[htowntahoe]

Not that it may be related to your issue but I had a brand new 2016 Sierra 5.3l and within months of owning it it did exactly as you described. Most likely a failed Chassis Control Module or Engine Control Module. Also have you changed the plugs lately?

 

[LTHoe52]

Not that it may be related to your issue but I had a brand new 2016 Sierra 5.3l and within months of owning it it did exactly as you described. Most likely a failed Chassis Control Module or Engine Control Module. Also have you changed the plugs lately?

Never changed CCM or Plugs.. New ECM though