Jump to content

Recommended Posts

Posted

Got a 2021 3.0L with just under 30k miles and recently started acting like it was misfiring or skipping while in gear and brakes on. Noticed it would happen while stopped or just starting to take off and would occur within a few miles of starting my trip and wouldn't matter if I had preheated the truck. Now, especially that the outside temp is in the single digits it's happening more. No codes, no check engine light. I had it in for an oil change and reported it then but of course the dealer couldn't reproduce the issue. Today it's been doing it more than normal and was able to get it on video... But still no codes. Once it's over 1k-1.5k RPMs it's clear and after I driver for at least 5 miles it won't do it until it cools back down.

 Have not found much on line about it nor other reports.. can't find anything disconnected, broken or damaged under the hood as far as vacuum lines, connections and even the air box assembly.

 

Any other reports of this?

Posted

I can't be the only one that's had this happen. Skips like it's miss firing or maybe an injector acting up. The frustrating part aside from no codes is it doesn't happen all the time even on the cold days.

Posted
8 hours ago, silveradosid said:

you should still get it scanned to see if there is any miss fires on any of the cylinders

Last time I reported it to the dealer they claimed there was no info when they scanned it.

Posted

Try pushing the onstar button when it's doing it and see if they can catch the code. 

 

 

Posted

OnStar is a sore subject... But no service with them.

 

Got my hands on a code reader and plugged it in .... All clean and no codes and it did it as I left work for the day. It seems to definitely not happen after the engine reaches 185 degrees and up to operating temp. If it is happening and I can get the RPMs over 1,500 it clears out but once I let it get back to idle it will happen until the temp comes up. Another thing I noticed is that it typically idles at about 750. When it starts acting up and it's idling smooth it's more at 850-900.

  • 3 weeks later...
Posted

So far the only other info I've been able to determine that this occured when the engine temp is about 185 or less and the ambient air temp is around 40 or less and the RPMs are slightly higher. Air\Fuel mixture or cold air intake issue possibly while the choke or choke mode is on??

Posted

If you have no codes, or past codes - Just drive it until it comes on. I don't have that issue though. When the windchill was -20F, around 0F I had the engine block heater plugged in for a few hours. Started right up. But never had any of the issues your describing. Same motor. 

Posted

Yea it's been driving me nuts with no codes and we are now going on almost 3 months of it acting daily now. I have had it stall out on me a couple of times recently and the symptoms just keep getting more pronounced. Hopefully it Will throw a code or error soon!

Posted
On 3/2/2025 at 8:55 PM, Santito said:

Yea it's been driving me nuts with no codes and we are now going on almost 3 months of it acting daily now. I have had it stall out on me a couple of times recently and the symptoms just keep getting more pronounced. Hopefully it Will throw a code or error soon!

We want to learn more and make sure we get the appropriate parties involved. Please send an email to [email protected] with your VIN, along with a history of your vehicle concerns. Please be sure to include "GMC Trucks Forum" in the subject line. By sending us a message, you consent to the information you provide being monitored and recorded by GM or those acting on GM’s behalf, subject to the GM Privacy Statement: https://www.gm.com/privacy-statement.

Posted
On 3/5/2025 at 6:51 PM, GMCustomerService said:

We want to learn more and make sure we get the appropriate parties involved. Please send an email to [email protected] with your VIN, along with a history of your vehicle concerns. Please be sure to include "GMC Trucks Forum" in the subject line. By sending us a message, you consent to the information you provide being monitored and recorded by GM or those acting on GM’s behalf, subject to the GM Privacy Statement: https://www.gm.com/privacy-statement.

Email has been sent.

  • 3 weeks later...
Posted (edited)

Well the mystery has been solved. It was found that the when the air filter was inspected at the last service, the hose was not connected to the air box correctly there was an air leak going by the mass airflow sensor. Couldn't see it from the front side of the engine.....

 

PXL_20250321_204737653.jpg

Edited by Santito

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   3 Members, 0 Anonymous, 2,173 Guests (See full list)

  • 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...