Jump to content

Recommended Posts

Posted

350 TBI. Truck has about 74000 miles on it. I bought it new. Gave it to my son last fall. Had been acting up some. Last week he took it to the dealer and they found the fuel was shot which I had suspected for quite awhile. Truck ran good for him. Couple days later ago he took it out for a longer drive and barely got it back to town. Couldn't pull itself up a hill it was so bad. He parked it along the highway and I picked him up. The coolant reservoir was still full but it seemed to be overheated. He had added some antifreeze to it a while back. We went back later and managed to get it to the dealer. I followed him back to town and didn't notice any white smoke. Next day they checked it out and said it's got a blown head gasket. I had the intake gaskets and radiator replace about 3 years ago for the 2nd time since I owned it. How common is it for them to blow a head gasket? Could it be the intake again? They haven't torn it down yet. With all the trouble with the fuel pump that had been going on for quite awhile, running lean, having trouble getting started I can't see any reason why that would have contributed to it blowing a head gasket.

Posted

Running lean causes enough excess heat to melt pistons so it could be a contributing factor. Any coolant in the oil? If it was the intake again the coolant in the radiator would be low but the reservoir may still be full and it would have overheated

Posted (edited)
15 hours ago, richard wysong said:

Running lean causes enough excess heat to melt pistons so it could be a contributing factor. Any coolant in the oil? If it was the intake again the coolant in the radiator would be low but the reservoir may still be full and it would have overheated

Yeah, with all the trouble we had getting it back to town I never thought to check the dipstick till later after I was home.. Also thought about the coolant actual level in the radiator but there was no way I was going to crack that cap unless it was completely cooled off. This afternoon my son and I will go by and see what they found. I think they are tearing it down today. It's a dealership I have dealt with for many years. I actually was a mechanic there 50 years ago for the owner's father and grandfather and I know and trust the mechanic they have on it so that's a plus. Told my son last year when I gave it to him, he would have to spend some money on it. I was pretty sure about the fuel pump but didn't see the head gasket problem coming. If I was younger, I might have torn into myself but the last few years I've been sticking to the small stuff like an alternator, starter, battery's, you get the idea. Son's no mechanic, takes no interest.

 

UPDATE: Talked to mechanic. He said the head gasket is leaking between I believe he said #3 & #5 cylinders. Said it's a common problem with that engine. Didn't ask about other years but he has seen it a lot. Always the same place on the same side the way he talked. Oil was clean and wasn't low on antifreeze. He didn't thing he got it that hot. Wasn't torn down yet so won't know if needs to be machined or what.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Edited by DRS 95 Silverado
Posted
On 7/22/2024 at 11:10 AM, DRS 95 Silverado said:

Yeah, with all the trouble we had getting it back to town I never thought to check the dipstick till later after I was home.. Also thought about the coolant actual level in the radiator but there was no way I was going to crack that cap unless it was completely cooled off. This afternoon my son and I will go by and see what they found. I think they are tearing it down today. It's a dealership I have dealt with for many years. I actually was a mechanic there 50 years ago for the owner's father and grandfather and I know and trust the mechanic they have on it so that's a plus. Told my son last year when I gave it to him, he would have to spend some money on it. I was pretty sure about the fuel pump but didn't see the head gasket problem coming. If I was younger, I might have torn into myself but the last few years I've been sticking to the small stuff like an alternator, starter, battery's, you get the idea. Son's no mechanic, takes no interest.

 

UPDATE: Talked to mechanic. He said the head gasket is leaking between I believe he said #3 & #5 cylinders. Said it's a common problem with that engine. Didn't ask about other years but he has seen it a lot. Always the same place on the same side the way he talked. Oil was clean and wasn't low on antifreeze. He didn't thing he got it that hot. Wasn't torn down yet so won't know if needs to be machined or what.

 

 

 

Bad news, the head gasket was bad exactly where he thought but it had gouged into the head and the block. He said he never had seen one that bad. I took a look at it myself. Pretty bad gouge in the block. Must have been leaking through for quite a while.  Head was bad also. If would have just been the head, no problem but the block is shot. Deciding between a new GM long block or a remanufactured one.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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
  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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...