Jump to content

Quick grinding sound on cold start

Obscenejesster

By Obscenejesster
in Troubleshooting & Recalls

 Share

Recommended Posts

Obscenejesster Enthusiast

Obscenejesster

Posted
Posted

Recently, I started to notice a grinding noise after starting my '16 Silverado after its been sitting in the cold over night. It only makes this sound on cold starts. The sound occurs for roughly 1 second or less. It almost sounds exactly like turning the ignition after the engine is already running.

 

This doesn't happen on cold starts when the weather is warm. Only when it's below 40 degrees and it's been sitting all night.

 

Anyone know what this could be?

 

Sent from my LG-H932 using Tapatalk

 

 

Thomcat Senior Enthusiast

Thomcat

Posted
Posted

Mine too in cold weather/ sounds to me like the Bendix drive - the starter motor still spinning while it retracts........more energy is drawn by the starter in cold weather could account for more noise. Any noise made for a second or less doesn't bother me.

  • Like 1
Dmf10e Enthusiast

Dmf10e

Posted
Posted

I’ve got the same issue. They replaced the starter and it still happens. I also had a 2018 loaner and it too had the same issue.


Sent from my iPhone using Tapatalk

Obscenejesster Enthusiast

Obscenejesster

Posted
  • Author
Posted
I’ve got the same issue. They replaced the starter and it still happens. I also had a 2018 loaner and it too had the same issue.


Sent from my iPhone using Tapatalk
I know of 3 other people who say they experience the same issue.

I asked a local mechanic who I've dealt with for the past 15 years. He knows his stuff and doesn't depend on a computer to tell him what to do like these new age dealer mechanics.

He said it is the starter and it's due to the mechanism GM uses. I forget the technical aspects but basically it has to do with the way the ignition works. In cold weather it will stay engaged longer than it has to. He said as long as its only for a couple seconds or less, it shouldn't cause any damage.

He did say that a non OEM starter would likely fix the issue but he wouldn't personally spend the money to replace it.

Sent from my LG-H932 using Tapatalk

Dmf10e Enthusiast

Dmf10e

Posted
Posted
I know of 3 other people who say they experience the same issue.

I asked a local mechanic who I've dealt with for the past 15 years. He knows his stuff and doesn't depend on a computer to tell him what to do like these new age dealer mechanics.

He said it is the starter and it's due to the mechanism GM uses. I forget the technical aspects but basically it has to do with the way the ignition works. In cold weather it will stay engaged longer than it has to. He said as long as its only for a couple seconds or less, it shouldn't cause any damage.

He did say that a non OEM starter would likely fix the issue but he wouldn't personally spend the money to replace it.

Sent from my LG-H932 using Tapatalk


Good to know. Like I said, they replaced with a new one (so they say) and it still happens. But it’s still only for like a quick second. That’s the least of my worries.


Sent from my iPhone using Tapatalk
Obscenejesster Enthusiast

Obscenejesster

Posted
  • Author
Posted

Good to know. Like I said, they replaced with a new one (so they say) and it still happens. But it’s still only for like a quick second. That’s the least of my worries.


Sent from my iPhone using Tapatalk
Yea. Mine is only a quick second as well. It only does it on cold starts when the weather is below 45.

Sent from my LG-H932 using Tapatalk

jimbowilly1960 Enthusiast

jimbowilly1960

Posted
Posted

I just purchased a 2017 GMC 1500 Sierra Elevation. The same grinding/rattling noise comes from under the cab on the passenger side of the truck. Sounds more like emissions to me.  Stops after a few minutes.  Truck runs fine.

 

Obscenejesster Enthusiast

Obscenejesster

Posted
  • Author
Posted
I just purchased a 2017 GMC 1500 Sierra Elevation. The same grinding/rattling noise comes from under the cab on the passenger side of the truck. Sounds more like emissions to me.  Stops after a few minutes.  Truck runs fine.
 
We are talking about something else likely. The sound we are talking about only lasts a second or so.

Sent from my LG-H932 using Tapatalk

Cadzilla78 Enthusiast

Cadzilla78

Posted
Posted

I have owned a 01 Sierra, 03 Suburban, and now a 12 Sierra. They all have made that sound on a cold morning. I though it was something with the 5.3 engine and feared it was metal on metal internally (Poor oil distribution on a cold start) I have never seen anything metallic in the oil though. That makes me feel a little better if it is just the starter. 

jimbowilly1960 Enthusiast

jimbowilly1960

Posted
Posted
On 12/6/2017 at 9:24 AM, Obscenejesster said:

We are talking about something else likely. The sound we are talking about only lasts a second or so.

Sent from my LG-H932 using Tapatalk
 

Yup. Same thing. More pro dominant while standing on the passenger side of my cab. This noise lasts maybe, maybe 30 seconds?  Millions of these trucks on the road at this moment, making the same noise upon start up. Probably find out the day after my warranty runs out, it's some counterfeit part in my oil pan which was manufactured the Ukraine? 

Obscenejesster Enthusiast

Obscenejesster

Posted
  • Author
Posted
Yup. Same thing. More pro dominant while standing on the passenger side of my cab. This noise lasts maybe, maybe 30 seconds?  Millions of these trucks on the road at this moment, making the same noise upon start up. Probably find out the day after my warranty runs out, it's some counterfeit part in my oil pan which was manufactured the Ukraine? 
I think we are talking about different noises. The noise we are talking about doesn't last anywhere near 30 seconds.

The noise we're referring to lasts like half a second to a second.

Sent from my LG-H932 using Tapatalk

jimbowilly1960 Enthusiast

jimbowilly1960

Posted
Posted
31 minutes ago, Obscenejesster said:

I think we are talking about different noises. The noise we are talking about doesn't last anywhere near 30 seconds.

The noise we're referring to lasts like half a second to a second.

Sent from my LG-H932 using Tapatalk
 

Ok. So I'm at the GMC dealership right now, on Central Ave, Albany NY. I stopped by to take advantage of the free coffee and donuts. And this department manager is having a cow. He says your probably sitting at your table in a trailer park somewhere with nothing better to do than to follow threads/people on GMC related forums?  He says GMC/Chevy trucks do not make this noise period.  He was wrong!

It's 25 °F. We just started up 5 GMC pickups. 3) 2017's, 1) 2016, and 1) 2018 GMC 1500 Sierra pickups.

Everyone with the 5.3 liter engine. Each truck made the same strange noise upon start up. Each noise only varying a few seconds in duration.

The day I purchased my 2017 GMC Sierra 1500 Elevation, I started 3 different trucks without noticing this noise. Hoping this post helps? 

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

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   3 Members, 0 Anonymous, 1,554 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...