Jump to content

Funky smells coming from AC vents after first service.


Recommended Posts

Posted

Brought my truck in to do first oil change at 2000 miles. Now when vent is on in truck there is a bad musty smell coming on out of the vents and when the ac is on there is a burning smell coming from the vents. I called my service guy friday, the day after I got it serviced and he never called me back.

 

Sent from my SAMSUNG-SM-N900A using Tapatalk

Posted

Try running the heater on full heat for 5 minutes or so to remove any moisture in the ducts.

Posted

probably just coincidence that it started smelling now. AC systems generate condensation and that often allows for growth of mildew and mold in the system. GM sells a spray that you simply run the AC on full and spray this into the inlet at the base of the windshield. The stuff is a disinfectant like Lysol. It may even be made by Lysol for GM with their specified scent. Buy a can of Lysol with a pleasant scent and spray in the inlet while the AC is running and it will cure it. This often takes a couple times to do the job. I have to do this about once a year on my vehicles in southern Cal. Some damp places may require doing this more often during the warm seasons. And yes, drying out the system helps. Whenever you start smelling it, spray it to keep it under control. If you let it go and it gets really bad, it's harder to get rid of. Stay on top of it. It's not a defect. All vehicles can get it. It's an environmental thing.

Posted

Never had the issue the 9 years I've owned my srt4 so was just curious or maybe I didn't notice. Lol.

 

Sent from my SAMSUNG-SM-N900A using Tapatalk

Posted

Hi 440hsp,

 

I am sorry to hear that you are experiencing a funky smell coming from the vents in your vehicle. I understand that you did reach out to your dealership and I do apologize that they have not contacted you about this issue. I am more than happy to look into this concern for you. Please private message me referencing this thread if I can be of any assistance.

 

Jennifer T.

GM Customer Care

Posted

Will do jennifer. Thank you

 

Sent from my SAMSUNG-SM-N900A using Tapatalk

  • 4 weeks later...
Posted

I had this exact same thing happen to me. I took it back to have them clean out the system and replace the cabin air filter. it seems better now. But it was awful!

Posted

Yeah it keeps happening but I've been really busy working so I havent had a chance to take it back.

 

Sent from my SAMSUNG-SM-N900A using Tapatalk

Wonder why thos is happening to a brand new truck. Weird...

 

Sent from my SAMSUNG-SM-N900A using Tapatalk

Posted

I had the same problem with my 06 Sierra. I tried all kinds of air fresheners and Lysol sprays and the only thing that worked for me was to shut off the A/C compressor about 5 minutes before I killed the engine. I do this now in my 14 as well as my 12 Camry. I have read that some Env Regulations have led to the coils not being able to be sprayed with a biocide or something and the mildew forms and you get the smell. May be something to it cause my 88 Toyota does fine and my former 2003 Accord never had the problem. I know that people with newer Camry's fuss about it to. It won't clear up instantly but it did work in my old Sierra.

Archived

This topic is now archived and is closed to further replies.

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