Will this solve your problems? Click n pop and Squeeli

Question

Hi everyone,I'm new here. I've been reading about all of the problems everyone has been having with their X-Fi's. I realise how everyone must feel that they spent ?XX or ?XXX getting a brand spanking new soundcard that claimed to be the best money could buy. I'm here to try and get this sorted for you. Let me explain. I'm a computer enthusiast. I, like a lot of you, have an awesome computer. However, i don't have an X-Fi (one is on the way to me though). I'm not here to show off my specs. I'm here to try and offer a solution. I've been thinking about this. And i thought, why don't we, as a community, make some modified drivers, or, some application that can read the BIOS chip on the X-Fi (i assume they have some sort of BIOS chip, like most GPU's). I don't have much experience in reading system data, but i do know about programming. Or perhaps some sort of system patch? The "Screech of death" and the "cracking and popping" seems to happen on a wide variety of system configurations, but does seem more prevalent on Asus boards. I have a theory that it occurs due to the FSB/HTT being too high. Perhaps someone could try this for me:?) Go into BIOS and change your HTT or FSB Multiplier down one step. So if you have set it at 5X, set it to 4X. Then, try and see if you can replicate the problem. If it reoccurs, then try lowering it one more just to be sure. If it doesn't reoccur, then we have one part of the problem solved. If it does, then we can remove that. Next, IRQ's. I realise this has been posted a lot around here. But, this is for those of you with some sort of Onboard audio (which are a lot of you i imagine). I've done a bit of research with my own system (Epox EP9NPAJ SLI motherboard, which is NF4 SLI Chipset) and i've discovered that the onboard audio, is sharing with the Primary?PCI IDE Controller. Now, even though IRQ Sharing is part of the PCI specification, has anyone thought of disabling onboard audio? Or completely disabling that IRQ? Now, if you don't have an FDD, you could potentially try assigning IRQ 6 to the X-Fi as IRQ 6 is a uni'versal IRQ that is used for the FDD. If that doesn't work, perhaps you could try the following:?) You need to disable your onboard LAN and all references to LAN and NVidia in your BIOS.2) In IRQ's, assign the NVidia Netbus IRQ to the X-Fi. Ususally, this is IRQ 22, but you should check this in Device manager in Windows (View ---> Resources by Type ---> Interrupt Request ---> Nvidia Network Bus Enumerator). Obviously, this means you lose networkability, but if it solved your problem, you can always buy a PCI network card. If not, then reassign the IRQ to the Nvidia Netbus to reenable networking. Next one, PCI Slot. Again, i know this has been mentioned a lot, but try changing?the PCI slot that the X-Fi is in. If it still causes problems, then try one or more of the steps above. Next, memory. I don't know if this has been mentioned or not, but it may help. Try this, go into your BIOS and loosen your memory timings. So, if you have memory timings of 3-3-3-5-T, try adjusting it to 3-3-3-5-2T. If this solves your problem, good for you! If not, then try changing it to 3-3-3-7-T or 3-3-3-7-2T. Again, if this solves your problem, well done! If not, readjust your timings to what they were before. You could also try using a lower memory divider. So if you have 200 divider, try 83, or even 66. Solved your problem? Nice! Not solved? Sorry. I realise that people are very stressed about the problems, but i would appreciate it if you didn't flame me. I am not here to interfere, i'm simply here to try and provide my knowledge to you as best i can (i'm currently studying for Network+, A+, Customer Support (ITSST: Information Technology Systems Support Technician) at college). I do have a background in Computers, and even though i'm only 7, i know about things like this. No, i don't work for Creative. I am not part of their team, neither support, technical or software. I just want to work towards a solution. Let me know if there are any problems, or if you have any suggestions or any case studies i could use. Perhaps you could also post the following for me at the bottom of your message (please press the enter key first and then write the information in bold):?Motherboard Manufacturer (E.G. Asus, Epox, Etc.)Chipset on that board (E.G. NF4 SLI, Via K8T900, Etc.)Single VGA Card, SLI or CrossfireMemory Type (E.G. DDR DIMM, DDR2 DIMM, Etc.)Speaker Setup used (E.G. Multimedia/2.0, 2., 5., Etc.)Problems you have experienced with relation to the X-Fi (E.G. Squeeking, Popping, Etc.) Write all that apply to you. That's all i need to know. It should help me come to a solution and i plan to present a case study to both the community, the motherboard manufacturers that are affected most, chipset manufacturers that are affected most and Creative themselves. Like i said earlier, please don't flame me. I realise that almost all of you have been in contact with Creative. I also plan to present the case study to them along with possible causes and solutions. Please do not flame me for planning to do this as i am only here to try and help you out. If we, together, as a community can get to the bottom of this, then we can let the whole world know that we know what's wrong and how it can possibly be solved. Thankyou,Scott Pritchard.Message Edited by DJKahuna on 02-28-200708:50 PM

Answer 1

You may find my take on this of interest:
http://forums.creative.com/creativel...ssage.id=84078
It does not apply to squealing behaviors.
-Dave
?[email protected]