Jump to content

Pulsing or flickering headlights for 2010 1500 Silverado 5.3L

Chev80
 Share

Recommended Posts

Chev80 New Member

Chev80

Posted
Posted

Hello, I’m new to the forum and was wandering if anyone has had an issue with flickering pulsing headlights/dash lights? So far I have replaced a list of components and still have the same results. I have replaced the main ground wire off the battery. Replaced battery and alternator. Checked all the body grounds and most of the wiring on the truck from bumper to bumper. I know it has to be something simple that I have overlooked and can do myself in my garage. I figure I would check here to see if someone had the same problem and was able to fix.

dna9656 Enthusiast

dna9656

Posted
Posted

I'm going to assume you  have checked the head light control and dash dimmer switches already.
How do you know you have checked ALL grounds? There many, many grounds on a modern vehicle, GM publishes a location guide as part of the service manual, some forums offer free downloads of factory service manuals but seldom a full set.

Get some electronic spray cleaner (de-tox is one) and check all the connectors in the problem circuits; pull them apart and look at the terminals, check for corrosion, especially if the plugs are under the carpet and you live in a place the carpet is wet much of the time. This happened to me in Alaska, snow from my boots would melt and the water would soak into the carpet. The water traveled under the seat and soaked a connector for the rear outside lights, I got the seat out lifted the carpet and there was a flat wide connector; I pulled it apart and it was full of green corrosion. I cleaned it and pushed Di-electric grease into the little holes where the connections are made. I also removed the carpet, pressure washed it and hung it out to dry in the almost 24 hour sunshine Alaska has during summer. I also bought floor mats that wouldn't allow water to get on the carpet. I don't know if a relay could be involved but I'd get a good schematic and find out, this sounds like it could be a relay that's tired or has an intermittent connection.

Would like to read about how you fixed it!

Good luck and good hunting!

Dna

jmann8686 Enthusiast

jmann8686

Posted
Posted

not sure if you found the issue.  I no you said you replaced the alternator.  I was just dealing with this myself.  Not sure where you got the alternator from.  But I went through two from Orieliys and they were bad in 3 weeks one was reman and after I got it installed I was having the issue.  I got them to warranty it even though it tested fine on their machine for a brand new one and it did the same thing. It was over charging my system.  The alt was pushing 15+ volts.  I picked up a reman from Napa got it installed and it looks like hopefully that fixed my issue.  So don't rule out new product depending on where you got it from.  I also did the big three chanced down and clean grounds.  unplugged my light bar and crawled around looking for things that could be wrong.  So don't rule out new electronic.  Just my .02 

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,770
    Total Members
    8,960
    Most Online
    Paul8556
    Newest Member
    Paul8556
    Joined

  • Who's Online   4 Members, 0 Anonymous, 592 Guests (See full list)

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      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? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      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. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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