| Page 1 of 1 |
|
|
 Posted: Fri, 3rd Jun 2005 20:55 Post subject: Audigy 2 ZS Popping sound problem! |
|
 |
I got this card a few days ago and when I play games like SC3 and similar, I get an annoying popping sound every few seconds. Moreover when I play songs with winamp sometimes winamp crashes.
I've installed the latest official drivers from the creative website.
What should I do?
|
|
| Back to top |
|
|
Phluxed
VIP Member
Posts: 4911
Location: Oakville, Ontario, Canada
|
| Posted: Tue, 14th Jun 2005 05:52 Post subject: |
|
|
PCI slot is messed up or something in the BIOS. IRQ might be assigned wrong. PCI slot could be damaged. Card itself could be damaged. Try changing the slot, manually assigning IRQs and the like. If not, take the card back and get a new one. If you've still got a problem, I dunno 
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 14th Jun 2005 11:49 Post subject: |
|
|
When I had this, a reformat fixed it.
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 14th Jun 2005 16:28 Post subject: |
|
|
you reformated and fixed it? LOL This is a hardware issue my friend. Look around the web, you'll find thousands of links about creative cards and scratching sounds.
Creative sucks. Fact
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 14th Jun 2005 16:29 Post subject: |
|
|
My Audigy 2 Value does the exact same thing, solution? I use my onboard sound for Windows and only use the soundcard for Linux (which is why I bought it). Which works perfectly with the hacked, reversed engineered drivers made by people who do it for free (ALSA).
InvisibleSurfer is right, Creative sucks. They don't support their own hardware and rarely release drivers even when in dire need.
A hacked reversed engineered driver for Windows exists (It does not support Value so I don't really have any experience with it a side from learning it does not support Value) called kX
Something you may want to know is that they have not updated their download page and they have a newer version of kX on their forum: http://www.driverheaven.net/showthread.php?t=70982
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 14th Jun 2005 18:52 Post subject: |
|
|
Surfer: I had from time to time popping sounds, re installed the OS. And they are gone. Whats there more to say?
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Jun 2005 04:25 Post subject: |
|
|
Some driver was conflicting somewhere.... Is it possible when you updated the drivers it didn't wipe the old ones clean? Just an idea.
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Jun 2005 09:26 Post subject: |
|
|
Sounds more like an IRQ conflict to me, try to put the card in another pci slot.
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Jun 2005 13:05 Post subject: |
|
|
Probably the 1st time you installed the card, windows was already installed so there was some sort of IRQ-driver conflict which was resolved after re-installing windows. This doesn't mean that the actual formating solved the problem, all it means is that windows took into account if you wish the existance of a pci device and altered the IRQ config accordingly.
Nonetheless, problems like these shouldn't happen; this is clearly lame hardware drivers issue.
|
|
| Back to top |
|
|
|
|
| Posted: Sun, 19th Jun 2005 20:16 Post subject: |
|
|
Now get this! After millions (not joking) of tests I have found one solution:
When I play a game with my case opened there is no problem with the card. Once I close the case's lid, the sound crackling begins. WTF?! O_o
I mean my 9800 pro can bear the computer's heat but the small lame audigy 2 ZS can't????
|
|
| Back to top |
|
|
Phluxed
VIP Member
Posts: 4911
Location: Oakville, Ontario, Canada
|
| Posted: Mon, 20th Jun 2005 06:59 Post subject: |
|
|
Well... maybe the card is experiencing interference?
|
|
| Back to top |
|
|
|
|
| Posted: Mon, 20th Jun 2005 14:22 Post subject: |
|
|
|
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 29th Jun 2005 16:04 Post subject: |
|
|
Finally I solved the problem, and I think anyone with that problem should do this:
Take out the motherboard's battery for 10 mins and put it back. Then load fail safe defaults and everything will work fine!
(By taking out the battery, the mobo's cmos is being cleared)
|
|
| Back to top |
|
|
fisk
Posts: 9145
Location: Von Oben
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
[sYn]
[Moderator] Elitist
Posts: 8374
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 29th Jun 2005 22:33 Post subject: |
|
|
No I already loaded the fail-safe defaults before and even upgraded my firmware. None helped! Only after clearing cmos the problem was solved. There is no way to completely clear cmos through bios only by removing the battery for 10 mins and reinsert it.
|
|
| Back to top |
|
|
[sYn]
[Moderator] Elitist
Posts: 8374
|
| Posted: Wed, 29th Jun 2005 22:36 Post subject: |
|
|
*slaps head and walks away*
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 29th Jun 2005 23:08 Post subject: |
|
|
Man you didn't get it yet! Fisk said I didn't configure my bios right but it was on fail-safe from day one! I never touched anything there! Clearing cmos fixes issues which can't be solved by messing with the BIOS's settings. So saying "learn how to configure your BIOS" is wrong since no configuration settings can fix the issue.
|
|
| Back to top |
|
|
[sYn]
[Moderator] Elitist
Posts: 8374
|
| Posted: Wed, 29th Jun 2005 23:14 Post subject: |
|
|
... ill try and make this simple.
Clear your CMOS, reset it to default. Not to fail safe.
So. If you had of changed all of your settings back to how they where when the motherboard was bought. It would of worked.
*bangs head on wall lots*
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 29th Jun 2005 23:17 Post subject: |
|
|
Like I said I already did what you are suggesting!!! And the problem still occurred! Nothing fixed this issue until I removed the battery and reinserted it.
And giga-byte themselves said that by removing the battery bad data is being cleared and this cannot be done through the BIOS' configurations.
Last edited by exon on Wed, 29th Jun 2005 23:19; edited 1 time in total
|
|
| Back to top |
|
|
[sYn]
[Moderator] Elitist
Posts: 8374
|
| Posted: Wed, 29th Jun 2005 23:18 Post subject: |
|
|
|
|
|
| Back to top |
|
|
fisk
Posts: 9145
Location: Von Oben
|
| Posted: Thu, 30th Jun 2005 01:29 Post subject: |
|
|
The CMOS contains the settings you make in BIOS, clearing the CMOS (which can be done by a jumper also, normally) resets these to Factory default.
However, if you actually knew what to do with your BIOS, you could've tweaked the setting necessary to rid yourself of the same problem.
CMOS doesn't contain any magical data, just the settings of the BIOS, that can be done manually. =)
Yes, yes I'm back.
Somewhat.
|
|
| Back to top |
|
|
|
|
| Posted: Thu, 30th Jun 2005 15:04 Post subject: |
|
|
| fisk wrote: | The CMOS contains the settings you make in BIOS, clearing the CMOS (which can be done by a jumper also, normally) resets these to Factory default.
However, if you actually knew what to do with your BIOS, you could've tweaked the setting necessary to rid yourself of the same problem.
CMOS doesn't contain any magical data, just the settings of the BIOS, that can be done manually. =) |
You should tell that to the guys at gigabyte then, apparently you know better than them. For the last time by upgrading the firmware, bad data may still be stored at CMOS from previous firmware versions. For clearing this data you must take out the battery since this cannot be done through the UPDATED firmware version of the bios.
|
|
| Back to top |
|
|
fisk
Posts: 9145
Location: Von Oben
|
| Posted: Thu, 30th Jun 2005 15:08 Post subject: |
|
|
| exon wrote: | | fisk wrote: | The CMOS contains the settings you make in BIOS, clearing the CMOS (which can be done by a jumper also, normally) resets these to Factory default.
However, if you actually knew what to do with your BIOS, you could've tweaked the setting necessary to rid yourself of the same problem.
CMOS doesn't contain any magical data, just the settings of the BIOS, that can be done manually. =) |
You should tell that to the guys at gigabyte then, apparently you know better than them. For the last time by upgrading the firmware, bad data may still be stored at CMOS from previous firmware versions. For clearing this data you must take out the battery since this cannot be done through the UPDATED firmware version of the bios. |
Ok, I'm sorry - apparently they have some own standard then.
Yes, yes I'm back.
Somewhat.
|
|
| Back to top |
|
|
[sYn]
[Moderator] Elitist
Posts: 8374
|
| Posted: Thu, 30th Jun 2005 15:57 Post subject: |
|
|
|
|
|
| Back to top |
|
|
| Page 1 of 1 |
All times are GMT + 1 Hour |
