Jump to content

Strange Chirping Noise in Cab

Stonewall11

By Stonewall11
in Troubleshooting & Recalls

 Share

Recommended Posts

Stonewall11 Enthusiast

Stonewall11

Posted
Posted

Hey guys just checking to see if anyone else has had a problem/noise like this.

 

I drive an 2014 Crew Cab LTZ with roughly 10,000 miles. In case this info will help.

 

Now it doesn't always happen but when it does, it doesn't start until I am going roughly 30 mph. It sounds like a high chirping, or like a cricket is in the cab. It also seems like it's coming from the passenger side. Bumps don't affect this noise like the noise I have in my sunglasses holder. Only the speed does.

 

Anyways I love my truck and it wouldn't be a deal breaker, but if I could fix it that would be awesome.

 

Also thanks in advance anyone and everyone who shares their input or personal experience.

Stonewall11 Enthusiast

Stonewall11

Posted
  • Author
Posted

I am currently heading out to dinner with my family and it will not let me listen on my phone. Will listen when I get home and let you know. Thanks!

20L8TSierra24 Senior Enthusiast

20L8TSierra24

Posted
Posted (edited)

Its 100% the flapper valve just behind the muffler on your exhaust. It chirps when your truck transition's from v4-v8.

 

Put a bolt and nuf through it or a hose clamp and clamp of open. OR... Have the dealer replace your exhaust.

Edited by 20Bowtie14
jdg24 Enthusiast

jdg24

Posted
Posted

Its 100% the flapper valve just behind the muffler on your exhaust. It chirps when your truck transition's from v4-v8.

 

Put a bolt and nuf through it or a hose clamp and clamp of open. OR... Have the dealer replace your exhaust.

That's what I was thinking. The noise in my video is from the flapper valve

Stonewall11 Enthusiast

Stonewall11

Posted
  • Author
Posted

And do you hear it in the front on the passenger side as well? I'll still listen when I arrive home.

jdg24 Enthusiast

jdg24

Posted
Posted

And do you hear it in the front on the passenger side as well? I'll still listen when I arrive home.

yip

Stonewall11 Enthusiast

Stonewall11

Posted
  • Author
Posted

That sound is much more consistent than mine, and mine doesn't keep a constant chirp going in that way. I'll have to upload a clip of my trucks noise. Although it may just sound different on video. But I'll have to do some testing and comparison as that could be it.

Trza Enthusiast

Trza

Posted
Posted

I'd put money on the Flapper Valve as well.

 

I took my truck in over the winter complaining of the noise. The shop foreman at the time went on a ride along and couldn't figure it out and told me to book an appointment so that they can do a thorough assessment. I waited till after winter, in which during this time, I scoured the forums and came across this Flapper Valve issue. As well, the chirp in that time got worse and would actually chirp every time I stepped on the throttle...it was quite embarrassing.

 

I recently just took it in for an oil change and told them that I'm positive that my flapper valve is the reason for the noise. Later that day, they call me to tell me that it wasn't the flapper valve and that it was my rear leaf springs that needed to be lubed up as per some bulletin...I took their word for it, drove it home...fast forward a couple days and the chirping was back! I made another appointment, took the (new) shop foreman for a spin and he agreed that it was in fact the flapper valve. They replaced my exhaust with part # 23219691, which is the exhaust, resonator and tail pipe ( work order: 4051980 exhaust muffler with resonator, exhaust and tail pipe replacement)...he even warned me that it might come back as he's had similar experiences with other owners. ***Sigh***

 

Prior to installation, I tried making a deal with him to carry over the cost of the new exhaust and put it towards the GM Borla one. He said he couldn't do it...now that this new exhaust that they put on is starting to chirp, I'm definitely going to strong arm them into something.

 

Coles Notes: It's your Flapper Valve.

Fishingbear Enthusiast

Fishingbear

Posted
Posted

It's your flapper valve in the exhaust system and is related to the Active Fuel Management feature. It happens every time your engine switches from V4 to V8. I complained about this in my 2015 SLT 5.3 Sierra months ago and was told that there is no fix and to turn up the radio so that I don't hear it.

 

It's very frustrating and unacceptable. I've had passengers in my truck think that my transmission was on the fritz. I complained again when I had my oil changed three weeks ago and my service adviser put it on the service ticket but my receipt when I picked up my truck said that it was "operating as designed."

 

Waiting for GM to come up with a fix.... this did not happen in my 2007 Sierra with Active Fuel Management.

Stonewall11 Enthusiast

Stonewall11

Posted
  • Author
Posted

I'm going to set up a service appointment and see if I can get that checked out. Seems as though that's the problem as everyone knows what it is just from explanation. I'll let you guys know how I make out.

  • 5 years later...

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

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

  • Latest Articles

  • Posts

    • Chuck FB
      summer road trips in the 2026 2500HD

      By Chuck FB · Posted

      I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...