Jump to content

06 gmc 4.3 died while driving now wont start

Doubleseveneleven
 Share

Recommended Posts

Doubleseveneleven New Member

Doubleseveneleven

Posted
Posted

Hello first time on here. 

 

I have a 06 gmc sierra 2wd WT 4.3.  Was driving and it just died.  Now it doesn't start.  Just cranks and cranks and will back fire out of intake.  I changed icm and did same thing.  I changed cap and rotor wires and plugs.  Same thing.  They needed changed anyways.  

Tested codes.  Have the following codes

P00053 ho2 bank 1 sensor 1

P00054 ho2 bank 1 sensor 2

P00059 ho2 bank 2 sensor 1

P00060 ho2 bank 2 sensor 2

Also have P00449 which I think is gas cap.

 

 

Did fuel pressure test and I get 54psi at check point when the engine is turning over.  Also holds there really good/no fall off.

 

Please help not sure what to do next

Could it be doing this with just low fuel pressure?

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

That is plenty of fuel pressure, no issues there.

 

I'd want it on a scan tool to make sure it has both a crank and camshaft signal.

Sharpz Enthusiast

Sharpz

Posted
Posted
On 8/11/2021 at 5:37 PM, Doubleseveneleven said:

Hello first time on here. 

 

I have a 06 gmc sierra 2wd WT 4.3.  Was driving and it just died.  Now it doesn't start.  Just cranks and cranks and will back fire out of intake.  I changed icm and did same thing.  I changed cap and rotor wires and plugs.  Same thing.  They needed changed anyways.  

Tested codes.  Have the following codes

P00053 ho2 bank 1 sensor 1

P00054 ho2 bank 1 sensor 2

P00059 ho2 bank 2 sensor 1

P00060 ho2 bank 2 sensor 2

Also have P00449 which I think is gas cap.

 

 

Did fuel pressure test and I get 54psi at check point when the engine is turning over.  Also holds there really good/no fall off.

 

Please help not sure what to do next

Could it be doing this with just low fuel pressure?

a few things to try. 1) test your fuel, make sure the gas is good, and doesnt have a bunch of water in it.  2) since you obviously have good pressure unplug your fuel pump fuse/relay do a dry crank.  Then after a few dry cranks spray non chlorinated brake cleaner into your intake.  If your truck runs this way, you are going to want to look into vacuum lines, and your timing. 

Josh07 New Member

Josh07

Posted
Posted

I had something like this happen on mine. I was driving on the interstate and it just died suddenly while going 70+ mph. Mine ended up being something super easy. The coil wire had gotten a hole rubbed in the sheathing and was arcing out. Put some electrical tape over it and it fired right up. Worked until I got the replacement wire set. 

  • 2 months later...
smitty28 New Member

smitty28

Posted
Posted

dont know if there the same but had a 1995 sierra that happened to me and it was electronic spark control under distributer cap cost about 60 bucks or bad coil.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...