kXproject 3527,28 + M-Audio driver == crash!

Alus · Jan 16, 2003, 07:46 AM

Using kXproject driver version 3526 or 3527 or 3528 or 3529 or less

:
Windows XP SP1 OR 2000 SP2
SB Audigy (SB0090) + Audigydrive
SB Live! (SB0060) + Livedrive
M-Audio Delta 410 (driver version 5.10.00.27 or beta0.5.10.00.29x12 or 5.10.00.31)

After both the kXproject driver and the M-Audio driver are installed, the SB0090 plays fine, but the Delta locks up the system when any sound is made through Directsound or ASIO.
Completely reproducable;
Install M-Audio driver, install kX, load winamp (or whatever), hit play -- locks within 1 second. (1 seconds seems to be the amount of buffer I had set on winamp)

I would call this a serious bug for users try to use both cards. (I guess that makes it a pretty small group of people, but a serious bug none-the-less). I've tried every version of the M-Audio drivers available, and both cards seem to play fine with the built-on Nvidia nForce2 chipset audio.

-Alus

p.s. Nice work on the kX drivers in general! A truly awesome piece of work! I don't suppose you'd like to write nVidia's nForce2 on-board audio drivers for them?

Alus · Feb 11, 2003, 11:09 PM

Ok, after a ton of testing, I've descovered:

Versions don't actually matter. Any version of the Delta 410 drivers combined with the kX project drivers causes one serious failure or another.

Any help on this would be greatly appriciated, I know it's an annoying sounding bug, but I'm willing to do any amount of troubleshooting / reporting.

Max M. · Feb 12, 2003, 12:34 AM

So M-Audio drivers play fine when kx driver is disabled?

Alus · Feb 12, 2003, 02:33 AM

If I remove the kX driver, and the .inf so it doesn't re-detect on reboot, then the M-Audio works fine.

Max M. · Feb 12, 2003, 07:39 AM

ok, then what about other system parameters: ACPI enabled/disabled, and especially shared interrupts. Have you tryed to move cards into different PCI slots?

Alus · Feb 12, 2003, 07:46 AM

ACPI is enabled, and actually, I can't disable it on this board. There's a choice to disable APIC, but that's not the same thing.
I have tried every different combination of cards and slots, to the exact same results. The cards are both on completely seperate irqs in all but one of those combinations, with no difference there either.

Max M. · Feb 13, 2003, 05:44 AM

yep... so that's vary hard to guess what that can be.... And what about card's manufacturers (e.g. Creative Labs) driver? Have you tried it? (i'd wish i had m-audigy and could help but... so i can even imagine what it can be...i just can guess that this is some low level hardware issue since both directsound and asio are affected (typically asio should play fine even if directsound/winmm are dead completly))...

Alus · Feb 13, 2003, 06:01 AM

I tried native drivers on the SB Live!. It worked after I installed them, but then after a reboot the same thing happened. I actually can't seem to replicate that behavior.

-Edit-- It seems that pretty randomly, the cards will work in harmony right after the drivers have been installed. After a reboot, things are back to normal (broken).

Alus · Mar 3, 2003, 09:12 PM

So, add up another variable! I made some head-way.

story:
I installed 2000, as you can see from my edits to the post above. Somewhere in doing so I accidentally set the M-Audio as my default windows device, and upon boot it tried to play the Windows Startup sound. Of course it failed, locked, and I had to reboot. However, when it came back up it said the video driver had failed! Now, mind you what I have been calling a hard-lock actually means the system freezes but keeps playing audio. So, this makes sense and it seems like the video driver, right? That was a Matrox G200 PCI, I tried the Microsoft and the Matrox driver, same difference. So I dropped in an NVidia Geforce 3 Ti300 AGP; latest NVidia driver - Same Problem. Frustrated and frankly bored, I messed with the Hardware Acceleration (Display Properties > Settings > Advanced > Troubleshooting > Hardware Acceleration) slider. Suprisingly enough, the more to the left the slider is, the more stable the whole situation ('write combining' off, of course). This is sure-fire in all configs, XP, 2000, anything.

facts:
A7N8X Deluxe
M-Audio card
CLabs card
The lower the Hardware Acceleration slider, the better.
Everything else can be variable

What does this sound like? To me, it sounds like Motherboard, specifically bandwidth issues. If I load the system down with an SB0090, SB0060, scsi card, and all the onboard NIC and audio card options, the Hardware Acceleration slider has to be lower.

So, an FYI for people who were keeping up with my story, if anyone.

Cheers.

Jan 16, 2003, 07:46 AM	#1
Alus DriverHeaven Newbie Join Date: Jan 2003 Posts: 6 Rep Power: 0	kXproject + M-Audio driver == crash! Using kXproject driver version 3526 or 3527 or 3528 or 3529 or less: Windows XP SP1 OR 2000 SP2 SB Audigy (SB0090) + Audigydrive SB Live! (SB0060) + Livedrive M-Audio Delta 410 (driver version 5.10.00.27 or beta0.5.10.00.29x12 or 5.10.00.31) After both the kXproject driver and the M-Audio driver are installed, the SB0090 plays fine, but the Delta locks up the system when any sound is made through Directsound or ASIO. Completely reproducable; Install M-Audio driver, install kX, load winamp (or whatever), hit play -- locks within 1 second. (1 seconds seems to be the amount of buffer I had set on winamp) I would call this a serious bug for users try to use both cards. (I guess that makes it a pretty small group of people, but a serious bug none-the-less). I've tried every version of the M-Audio drivers available, and both cards seem to play fine with the built-on Nvidia nForce2 chipset audio. -Alus p.s. Nice work on the kX drivers in general! A truly awesome piece of work! I don't suppose you'd like to write nVidia's nForce2 on-board audio drivers for them? Last edited by Alus; Mar 3, 2003 at 01:39 PM.

Feb 11, 2003, 11:09 PM	Thread Starter #2
Alus DriverHeaven Newbie Join Date: Jan 2003 Posts: 6 Rep Power: 0	More info on this Ok, after a ton of testing, I've descovered: Versions don't actually matter. Any version of the Delta 410 drivers combined with the kX project drivers causes one serious failure or another. Any help on this would be greatly appriciated, I know it's an annoying sounding bug, but I'm willing to do any amount of troubleshooting / reporting. Last edited by Alus; Feb 11, 2003 at 11:22 PM.

Feb 12, 2003, 12:34 AM	#3
Max M. h/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,639 Rep Power: 69	So M-Audio drivers play fine when kx driver is disabled? __________________

Feb 12, 2003, 07:39 AM	#5
Max M. h/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,639 Rep Power: 69	ok, then what about other system parameters: ACPI enabled/disabled, and especially shared interrupts. Have you tryed to move cards into different PCI slots? __________________

Feb 13, 2003, 05:44 AM	#7
Max M. h/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,639 Rep Power: 69	yep... so that's vary hard to guess what that can be.... And what about card's manufacturers (e.g. Creative Labs) driver? Have you tried it? (i'd wish i had m-audigy and could help but... so i can even imagine what it can be...i just can guess that this is some low level hardware issue since both directsound and asio are affected (typically asio should play fine even if directsound/winmm are dead completly))... __________________ Last edited by Max M.; Feb 13, 2003 at 05:53 AM.

Feb 12, 2003, 02:33 AM	Thread Starter #4
Alus DriverHeaven Newbie Join Date: Jan 2003 Posts: 6 Rep Power: 0	If I remove the kX driver, and the .inf so it doesn't re-detect on reboot, then the M-Audio works fine.

Feb 12, 2003, 07:46 AM	Thread Starter #6
Alus DriverHeaven Newbie Join Date: Jan 2003 Posts: 6 Rep Power: 0	ACPI is enabled, and actually, I can't disable it on this board. There's a choice to disable APIC, but that's not the same thing. I have tried every different combination of cards and slots, to the exact same results. The cards are both on completely seperate irqs in all but one of those combinations, with no difference there either.

Feb 13, 2003, 06:01 AM	Thread Starter #8
Alus DriverHeaven Newbie Join Date: Jan 2003 Posts: 6 Rep Power: 0	I tried native drivers on the SB Live!. It worked after I installed them, but then after a reboot the same thing happened. I actually can't seem to replicate that behavior. -Edit-- It seems that pretty randomly, the cards will work in harmony right after the drivers have been installed. After a reboot, things are back to normal (broken). Last edited by Alus; Mar 3, 2003 at 01:38 PM.

Mar 3, 2003, 09:12 PM	Thread Starter #9
Alus DriverHeaven Newbie Join Date: Jan 2003 Posts: 6 Rep Power: 0	I wish I coul change the thread name So, add up another variable! I made some head-way. story: I installed 2000, as you can see from my edits to the post above. Somewhere in doing so I accidentally set the M-Audio as my default windows device, and upon boot it tried to play the Windows Startup sound. Of course it failed, locked, and I had to reboot. However, when it came back up it said the video driver had failed! Now, mind you what I have been calling a hard-lock actually means the system freezes but keeps playing audio. So, this makes sense and it seems like the video driver, right? That was a Matrox G200 PCI, I tried the Microsoft and the Matrox driver, same difference. So I dropped in an NVidia Geforce 3 Ti300 AGP; latest NVidia driver - Same Problem. Frustrated and frankly bored, I messed with the Hardware Acceleration (Display Properties > Settings > Advanced > Troubleshooting > Hardware Acceleration) slider. Suprisingly enough, the more to the left the slider is, the more stable the whole situation ('write combining' off, of course). This is sure-fire in all configs, XP, 2000, anything. facts: A7N8X Deluxe M-Audio card CLabs card The lower the Hardware Acceleration slider, the better. Everything else can be variable What does this sound like? To me, it sounds like Motherboard, specifically bandwidth issues. If I load the system down with an SB0090, SB0060, scsi card, and all the onboard NIC and audio card options, the Hardware Acceleration slider has to be lower. So, an FYI for people who were keeping up with my story, if anyone. Cheers.