Jump to content

2008 Silverado 2500hd 6.0 misfire HELP!

Alan1592
 Share

Recommended Posts

Alan1592 New Member

Alan1592

Posted
Posted

So I recently purchased this 2008 Silverado from auction. It’s a 2008 2500hd 6.0. Has a cylinder 3 misfire.

Swapped the coils, injector, plugs and the misfire remains in cylinder 3.

 

I did a compression test which showed an accoasional 150psi, but most of the time it would read 75psi after 5 cranks.

 

Decided to removed the head and sent it out to get rebuilt due to some pitying on the valve and seats. Cylinder bore looked fine and the truck doesn’t burn any oil. Cam lob looked fine in cylinder 3  for both intake and exhaust. Everything in the cylinder head was replaced. Put everything back together and the truck still has a cylinder 3 misfire and remains with an occasional 150psi and now has 90-120psi most of the time. 

 

Im lost at this point and I’m getting ready to throw a new motor in this thing. It idles like crap but runs fine after that with no hesitations even under WOT. 

 

Am I missing anything? 

Supreme Pizza Senior Enthusiast

Supreme Pizza

Posted
Posted

Replacing the head is a pretty extreme measure if you have not isolated the exact cause of the problem. Replacing the entire engine seems to be even more extreme. If you are willing to throw that kind of time and money at it, I would recommend just sending it to a diagnostic shop. For a couple hundred bucks, you will have your answer. 

 

 Shot in the dark, but I would say that IF you have AFM, then that would be the place to start. 

e_schott Enthusiast

e_schott

Posted
Posted

Ok, first off I'm going to scald you for pulling a head on a hunch...let's actually try to diagnose this thing without just throwing parts and making guesses. So you swapped a known good injector, coil, wire, plug, etc. That rules out the components. However, the control side of those components could have an issue. With the compression numbers that you post, that is likely not the problem however. First things first, do you have any trouble codes and do you have a scanner that can read live data. I can try to help you out if you have that. Second, what's compression like on other cylinders on that bank? 

e_schott Enthusiast

e_schott

Posted
Posted

Sorry to double post, I am not in a place I can look it up trying to go off of memory, can you tell me if your truck has AFM? Look for option codes, I think the two option codes for a 6.0 in that year are LY6 and L76, the L76 being the AFM aluminum block. But do not quote me on that, I am going off of memory and I work on a LOT of these trucks. Let me know what I asked above and if you have AFM or not and I will be happy to assist. Private message me and I will give you my phone number and you can text me.

Alan1592 New Member

Alan1592

Posted
  • Author
Posted
34 minutes ago, e_schott said:

Sorry to double post, I am not in a place I can look it up trying to go off of memory, can you tell me if your truck has AFM? Look for option codes, I think the two option codes for a 6.0 in that year are LY6 and L76, the L76 being the AFM aluminum block. But do not quote me on that, I am going off of memory and I work on a LOT of these trucks. Let me know what I asked above and if you have AFM or not and I will be happy to assist. Private message me and I will give you my phone number and you can text me.

Sending you a PM right now! Thanks!

  • 4 years later...
Drew95a New Member

Drew95a

Posted
Posted

I have this same problem on a 03 silverado 2500hd 6.0

Wondering what came of yours?

P0306 / P0300

We've pulled and replaced spark plugs, wire set, Ignition coil, fuel injector. Good compression 125 psi. Good spark swapped coils multiple times. Checked for scoring on the cylinder walls none, valves are opening and closing. Push rods are good. Grasping at straws at this point.

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

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...