Jump to content

Recommended Posts

Posted

Hello I have a 2000 GMC Sierra 5.3 4x4, it has been sitting for 6 months. First thing I did was change the oil, next I drained the old gas and put new gas in. The truck would crank but not turn over. I replaced the fuel filter, and replaced the fuel regulator. Prior to replacing the fuel regulator I had no fuel pressure, gas was leaking through the diaphragm of the regulator into the intake manifold. Once I replaced the above items fuel pressure was up to 50psi with key in start position. The truck fired right up no problem but, there was a very loud ticking sound that sped up and got louder when I pushed on the gas. I immediately shut it off. I checked the oil and the dipstick smelled like gas. I drained the oil and there was a lot of gas mixed in with the new oil. I replaced the oil filter and filled it with new 5W-30 Mobile 1 high mileage synthetic oil. It fired right up again and the loud ticking sound was still there. Oil pressure was good I let it idle for a few minutes and the ticking got a little bit quieter but, still loud. Check engine light was on and the codes were P0300 and P0200. I hooked up a Noid light to each injectors wiring harness at idle and every one was firing. I removed the fuel injectors and cleaned them, did OHM test on each one and all of them had consistent readings. I do not know what else to do from here? Any help, direction, or advice would be greatly appreciated. Thank you for taking the time to read this.

My truck has 245,000 miles on the original engine.

 

Posted (edited)

We've got a terminology barrier here. If it cranked, it's "turning over". I think what you meant to say is it was a "crank, NO START" prior, correct? Just want to make sure we're on the same page, since internet diags are difficult enough.

 

The P0300 (random, multiple cylinder miss) is probably intake gaskets given its age, mileage, and the fact it sat parked half a year. The P0200 indicates you've got some wiring issues related to the injectors. Probably just unplugging them and plugging them back in after your testing "fixed" that code, I would guess.

 

Oh and the tick was from gas dilution of the oil, as you found. You may have to do one or 2 more oil changes. And since you live in CA where it's warmer than most places, I'd run 10w-30 full synthetic in that. Will quiet it right down. I run it up here in MA, all winter long, too.

 

Edited by Jsdirt
Posted
On 5/25/2021 at 5:25 PM, Jsdirt said:

We've got a terminology barrier here. If it cranked, it's "turning over". I think what you meant to say is it was a "crank, NO START" prior, correct? Just want to make sure we're on the same page, since internet diags are difficult enough.

 

The P0300 (random, multiple cylinder miss) is probably intake gaskets given its age, mileage, and the fact it sat parked half a year. The P0200 indicates you've got some wiring issues related to the injectors. Probably just unplugging them and plugging them back in after your testing "fixed" that code, I would guess.

 

Oh and the tick was from gas dilution of the oil, as you found. You may have to do one or 2 more oil changes. And since you live in CA where it's warmer than most places, I'd run 10w-30 full synthetic in that. Will quiet it right down. I run it up here in MA, all winter long, too.

 

 

Posted
On 5/25/2021 at 5:25 PM, Jsdirt said:

We've got a terminology barrier here. If it cranked, it's "turning over". I think what you meant to say is it was a "crank, NO START" prior, correct? Just want to make sure we're on the same page, since internet diags are difficult enough.

 

The P0300 (random, multiple cylinder miss) is probably intake gaskets given its age, mileage, and the fact it sat parked half a year. The P0200 indicates you've got some wiring issues related to the injectors. Probably just unplugging them and plugging them back in after your testing "fixed" that code, I would guess.

 

Oh and the tick was from gas dilution of the oil, as you found. You may have to do one or 2 more oil changes. And since you live in CA where it's warmer than most places, I'd run 10w-30 full synthetic in that. Will quiet it right down. I run it up here in MA, all winter long, too.

 

Thank you very much for replying Jsdirt. Yes, you are correct it would crank but, no start prior. 

I picked up intake and valve cover gaskets yesterday. Right now I have the intake manifold off and the valve covers off. On the drivers side 2 of the valves are open, the pushrods are all the way up. The rocker arms for these are in an opposite position than all the rest. The are right next to each other but, are for different cylinders. Do you know how I can close them so all the rocker arms are in the same position? I really do appreciate your time. 

  • Like 1
Posted

I hope you checked the gaskets before buying them. That might not be your problem - it was just a suggestion. You've got to check these things before winging parts at it.

 

A squeeze bottle of water poured along the gasket area while it's idling will usually reveal any intake leaks, especially with a cold engine. If the leak is small, it can be hard to detect. Watching fuel trims on a scan tool while doing the test might reveal a smaller leak. 

 

As far as the rockers go, I just rotate the engine around and loosen the ones with no tension.

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...