Jump to content

2004 2500 6.0 Alternator Whining

hatch182
 Share

Recommended Posts

hatch182 Enthusiast

hatch182

Posted
Posted

I just purchased a 2004 GMC 2500 with a 6.0. The truck has 130k miles on it. The guy I bought it from told me the alternator needed to be replaced because it had a whine that would come through the radio. He had replaced the radio because he thought it was bad...but the whine did not go away. I replaced the alternator, but had the same issue. I then took the original alternator to be bench tested, and it tested good. I put it back in, but the alternator has a whine when accelerating and it comes through the radio. 


To troubleshoot, I unplugged the wiring clip while running...and it makes zero whine under the hood. If I reconnect the the wiring, it starts making an audible whine that sounds just like the sound coming through the speakers over whatever music may be playing.

 

It is driving me crazy...has anyone else had this issue?

Formulabruce Enthusiast

Formulabruce

Posted
Posted

The problem lies with whats called a Ground loop. The radio, for lack of a better term, is using the speakers as a ground.

 Pull the radio. If you used an adapter pigtail, make sure you Solder the power and ground leads.

 Check the ground wire size, make sure its same as power. Check the ground wire ( truck off, key out) coming to the radio, to truck ground with a ohm meter. I turn on the beep on my meter, so I don't have to look at the resistance.

 Probably a NEW ground wire from the chassis of the radio, to a GOOD truck ground, ( possibly one of the 2 cigar /12 volt outlets below) will do the trick. Good luck!

hatch182 Enthusiast

hatch182

Posted
  • Author
Posted

Thanks for the advice! I pulled the radio and ran a new ground to the chassis, it was a 12gauge wire. 

 

Here is the odd thing, the loudest part of the whining is coming from the actual alternator. 

It completely goes away if I unplug the electrical connector while running...and instantly comes back. 

I checked all of the body grounds, as well. 

 

Its the strangest thing I've ever seen!

asilverblazer Senior Enthusiast

asilverblazer

Posted
Posted
Quote

Here is the odd thing, the loudest part of the whining is coming from the actual alternator. 

 

Do you hear the whining under the hood at the alternator, or is only coming through the audio system?

hatch182 Enthusiast

hatch182

Posted
  • Author
Posted

Both. 


I can turn the radio up and hear the hum.

I can then turn the radio off,  and go pop the hood and the same noise is coming form the alternator. 
If I unplug the connector on the alternator while running, it goes quiet. 
The whining comes back when the electrical connector is plugged back in (while running).
The alternator doesnt make any bearing noise and is fully bench tested. 
It even made the noise with the new alternator. 

Formulabruce Enthusiast

Formulabruce

Posted
Posted

Adding a capacitor ( noise suppressor) is an old trick that used to work well, and may just fix this.

( credit to Pizza)

 The Body control module ( all cab functions) GROUND is UNDER the truck, on the DS, right under the DS door

on the CAB mount Extension facing the REAR of the truck. These ground wires need to be removed and cleaned well,

and frame cleaned. After put some waterproof GREASE on it..

 Did you do this ground?

  • 1 month 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   5 Members, 0 Anonymous, 2,186 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...