Sound Blaster X-Fi and Windows 7 64-bit

Anonymous
2009-10-23T03:31:55+00:00

I have a Sound Blaster X-Fi on a Dell XPS 710.  Installed Windows 7 64-bit.  Everything went great.  Downloaded and installed the new drivers from Creative for this sound card and Windows 7/64.  It installs but I get a staticy echo sound to everything.  Is there a fix?  The drivers are dated 6/2009.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2009-10-29T22:07:34+00:00

: WORKAROUND:

I claim NO responsibility if you mess this up but you can use this as a temporary work around until it is resolved by creative labs without removing memory... physically.

First run MSCONFIG

select the boot tab

select advanced options

under max memory select 3990 (or any value under 4 GB is fine IE anything less than 1024 * 4)

This will reduce the amount of memory that the PC uses which will allow you to hear the audio.  There is also BETA testing of newer drivers from Creative (the most recent batch of BETAS did not resolve the issue) that I am a part of.  When there is a working beta I will respond so we can all utilize our 64x machines.

Was this answer helpful?

10 people found this answer helpful.
0 comments

75 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2011-12-25T12:47:46+00:00

    I installed the drivers from the megaupload link but i also need the working THX console for this to setup my speakers right. The one from the supportpack 2.5 doenst work with that drivers. Wich one do i need?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2011-12-04T22:08:21+00:00

    They may work a treat immediately after you install them (most drivers do), but how long do they continue to do so? 1 month? 2 months? even 3 months? When I see a set of drivers that continue to work after more than 6 months, then I will start to believe it's probably fixed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2011-12-04T16:38:02+00:00

    I mis-spoke previously, linked the wrong drivers...The ones I am currently using were created by: Daniel Kawakami - Below is a link to the install I use. You can install the latest Creative driver, to get all the APPS (If you like the APPS), then run the setup.exe from this driver. It will prompt you and ask if you want to over-write your current driver or not.

    Currently I just have the driver installed and none of the creative applications and am working 100% with no crackling or popping.

    http://www.megaupload.com/?d=1T2FY414

    Hope it works for you too!

    Motherboard: ASUS M2N-E SLI

    OS: Windows 7 x64 Ultimate

    RAM: 4GB

    Sound Card: X-FI XtremeMusic

    These Work a treat buddy, thankyou

    xFi xTreme Gamer

    6GB ram

    ASUS Crossfire II

    Win 7 x64 Ultimate

    K

    Was this answer helpful?

    0 comments
  4. Anonymous
    2011-11-14T11:01:51+00:00

    Again, a bit more information since my post in April.

    I've tried 3rd party drivers, but they fail after a while in just the same way.

    I enrolled on a CL beta test program - the first beta driver clean install worked for about 6 weeks and then failed.

    I've installed the original MS generic 64-bit drivers and so far so good. They may not have all the bells and whistles of CL drivers, but I can't tell the difference on that score other than they work and continue to do so (so far!!). I just have to make sure that Windows Update doesn't "upgrade" them to the CL version.

    There is a very similar bug, often associated with mechanical drives and possibly the use of headphones. The output device changes from the speakers to SPDIF after the headphones have been plugged in and out. The speakers become greyed out and won't go back till the driver is reinstalled.

    I believe that there is also a time element to the problem, it takes several weeks or even months before the problem shows up after a clean install. Which leads me to believe that some sort of information the driver stores (registry?) changes / grows over time until it causes the problem. Maybe it's some sort of time-out during the driver initialisation.

    Was this answer helpful?

    0 comments