Jump to content

Recommended Posts

Posted

I've got the same noise. I would have bet a weeks pay it was the belt. But after reading this thread I have my doubts. Quits by the time I back to the end of the driveway.

  • 3 weeks later...
Posted (edited)

My brand new 2024 3500hd SLE has the same problem since I bought it. Squeals on startup and  acceleration. Dealer says they don't want to explore the problem, but rather wait for a recall. Horseshit.

Edited by MikeDJohnson
Posted
On 9/10/2024 at 10:12 PM, MikeDJohnson said:

My brand new 2024 3500hd SLE has the same problem since I bought it. Squeals on startup and  acceleration. Dealer says they don't want to explore the problem, but rather wait for a recall. Horseshit.

We regret to hear of this concern with your vehicle and would like to take the time to investigate further on our end. Please send us an email to [email protected]. Be sure to include your Username and Forum name in the subject line with additional details. We look forward to hearing from you. 

Posted
6 hours ago, GMCustomerService said:

We regret to hear of this concern with your vehicle and would like to take the time to investigate further on our end. Please send us an email to [email protected]. Be sure to include your Username and Forum name in the subject line with additional details. We look forward to hearing from you. 

What about the rest of us with the same problem?

 

Posted

My truck has a short squeals for 5-6 seconds upon start up and basically stops when I put it in drive to leave my garage. Its done it since new and hasn’t  changed duration so I don’t care. 

  • 2 weeks later...
Posted

Took the truck in again to the dealer.  They are still at a loss of what it is.

 

Dealership is going to order an intake and see what that does.  They basically told me they will bust out the parts cannon and keep throwing parts at it until GM stops paying for warranty work.

  • Like 1
Posted
On 9/21/2024 at 2:53 PM, MudMonkey said:

Took the truck in again to the dealer.  They are still at a loss of what it is.

 

Dealership is going to order an intake and see what that does.  They basically told me they will bust out the parts cannon and keep throwing parts at it until GM stops paying for warranty work.

We are sorry to hear that you are still facing ongoing concerns with your vehicle and would like to take the time to investigate further. To get started, please send us an email to [email protected]. Be sure to include your Username and Forum name in the subject line with additional details. 

  • 1 month later...
Posted
On 9/21/2024 at 2:53 PM, MudMonkey said:

Took the truck in again to the dealer.  They are still at a loss of what it is.

 

Dealership is going to order an intake and see what that does.  They basically told me they will bust out the parts cannon and keep throwing parts at it until GM stops paying for warranty work.

Mud Monkey

Any news on the parts cannon solution?

Posted

Per usual Gm, one of the parts is on back order.  I did hear a whistle noise while climbing on a mountain pass today.  The rpm’s were around 2500 when I could hear it.  Almost sounded like a faint turbo whistle.

 

i thought I seen a post about something similar.  I can’t remember if it was on a gasser or diesel.

 

Maybe the two sounds are related.

Posted (edited)

I also have been dealing with this noise, exactly as described in this post. 2024 2500HD gas. Mostly on start-up, louder when put into R or D and on light acceleration when driving or in a drive-thru, etc.

 

Had two different dealers look at it. First dealer couldn't replicate it and when I picked it up and pointed out the noise they said they don't hear an issue. Second dealer it did it very loud when I dropped it off, after a day they called and said it's a normal sound for this truck. I've given up on dealer service, my 2019 Colorado spent a ton of time at the dealer for 8 speed issues and 4x4 issues and the dealers were always trying to get out of doing anything or telling me nothing is wrong.

 

It has slowly gotten worse and I told them my new truck shouldn't sound like the old S10 I drove in school but they stuck to their answers. 

 

Ordered a mechanics stethoscope coming in the mail but I'm no mechanic, even a backyard one so not too hopeful. If I can't get a fix for it Im debating just getting exhaust work to make the truck louder and drown it out 😂

 

Hope everyone keeps at it and gets some answers!

 

Edited by Big Timber
  • Like 1
  • 4 months later...
Posted
14 hours ago, Tracker48 said:

This could be the noise mentioned in this thread.
Well at least this is what I'm going with.
https://www.gm-trucks.com/gm-62l-66l-v8-engine-noises-normal-explained/

Now that I've read that article, I can almost convince myself that the sound I'm hearing is kinda like a spark knock you'd hear under load/acceleration... kinda.

 

Almost.

Posted

I use midgrade gas.  I wonder if premium would make the noise go away.  I will try this out and see what happens.

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

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...