Audigy and KT266A ?

[DrZone]

I've heard of audigy having problems with older via mobos. But does it have any issues with the KT266A ?

 

[CyNics]

i'm using Epox kt266a board and my audigy has been working great, no problems ever..no slowdown or lock up

 

[RanDum72]

Yup, there still a lot of issues with the Audigy and KT266A chipsets, the worst is corrupted Audigy firmware due to ACPI. Just browse the Creative web site and their forums (especially the European one). My KR7A ate two Audigy's before I decided to go with the Santa Cruz on that machine. My friend's MSI board did the same. Weird thing is, my Epox 8KHA+ seemed to work just fine.

 

[Mem]

No problems with my Audigy & Epox 8KHA+(KT266A board) ,btw I`ve read that some of the problems with the Audigy go away with clean install of drivers,it seems old sound card drivers can cause problems,maybe that`s why I had no problems since I did a clean install of OS.

 

[DrZone]

Thanks for the responses.

I got an audigy and installed it into a fair clean install of winXP. But after a few days, i did a driver update and all went to hell. I restalled the drivers and tried a few things but no good. My box wouldnt reboot! It wouldnt even reboot when i formatted the comp.

I'm using the ASUS A7V266-E. I took out the audigy and did a bios update and a total re-install of XP. I popped the audigy back in and it seems to be fine now - no more messing with the drivers !

 

[DrZone]

Anyone else experience issues here ?

 

[Mac]

I just recently built a new system, from scratch using an Abit KR7A-R133, 1600 XP+ and the Audigy on Win98SE. It seemed to come up fine at first but then things became real weird after adding a NIC and a SCSI controller. The Audigy was in the 4th (from the AGP) PCI slot. So, I uninstalled the Audigy and attempted to reinstall. During boot, the Win would "find" a multi-media card and the 1394 fire wire port, but per, Creative's instruction, I would skip past the "looking for drivers". When I tried to run the install program from the SB CDROM, it came back with an error message saying it could not detect an Audigy card. I figured the card just went bad so returned it to BB, got an exchange and started over.

I spent the better part of this last Saturday, trying to get the Audigy to work. This time the card was recognized properly and seem to install properly. Then everything started going bad again. Really bizarre stuff. After uninstalling and reinstalling several times, I think I found a pattern. After running the installation program, you are prompted to restart the system. The system would boot up properly and seem to run fine until the system was restarted. The system would then crash during Win startup, BSOD's and would continue until I reran the install program again. Would seem to run OK once, then BSOD during the next reboot.

I finally gave up an reinstalled an old SB Live card. Don't know what to do but if anyone can point me to any threads or FAQ's which may help, would sure appreciate. The FAQ's on Creative sites are pretty useless.

 

[DrZone]

Try a bios update. The bios update *seemed* to have solved the problem with my audigy and ASUS A7V266-E

 

[Anubis]

i have an Audigy on my 8KHA+ 266A mobo and it workf fine. when i installed it i just took my ole SB live card out and put the audigy in and reinstalled soem drivers. has worked flawlessly sence then

 

[RanDum72]

I just recently built a new system, from scratch using an Abit KR7A-R133, 1600 XP+

Thats one of the issues I'm talking about. Some KT266A mobos corrupt the firmware of the Audigy, so it installs as a "emu10k" sound device instead of Audigy. When you try to update the drivers, it won't find the sound card. The Audigy is basically trashed from then on. You can reformat the harddrive, do clean re-installs of WinXP and remove all cards except the Audigy and the video card, it won't help. Sometimes, the computer won't even turn on when the Audigy is plugged in. The scary thing is everything seems to be random. Some mobos from the same manufacturers (same model) work, some don't.