Initializing kx Mixer Freezes XP System

_pF_ · Sep 28, 2005, 12:00 PM

[SOLVED: I saw in a similar bug report that an IDE device in PIO mode caused the poster's problem.

Sure enough, XP had reset my secondary slave to PIO mode. This is a dodgy disk I use for scratch.

Reinstalling the IDE channel reset it to DMA and all is now well.

Why, I don't understand.]

When I start the kx mixer my XP sp2 system freezes, and only a hard or soft reset will recover it.

A few ctrl-alt-dels will reboot, so the keyboard is functional.

The kx 3538i drivers themselves are loaded and working properly.

Indeed, until recently I've had the whole kx 3538i (and h, and 3537) system -
including mixer - working flawlessly, but none work now. I've spent a lot of time checking-out and rationalizing my hardware, memory, bios, software, services and drivers.

Incidentally the problem is not connected with the ATI radeon drivers.

A forced Kernel crash dump points to i8042prt.sys and I don't know whether that is helpful or not.

The mixer displays the graphical 'expanding the potential' logo, then hangs. This is what happens before the freeze:

kxmixer: add-on: registering 'c:\windows\system32\kxaddons.kxa'
ikXplugin: get_count():load library failed. [7e]
kxmixer: registering skins...
kxmixer: adding start menu items
kXsetup: shGetSpecialFolder result: C:\Documents and Settings\All Users\Start Menu\Programs
ModLoad: 76fd0000 7704f000 c:\windows\system32\CLBCATQ.DLL
ModLoad: 77050000 77115000 c:\windows\system32\ComRes.DLL
ModLoad: 76980000 78988000 c:\windows\system32\LINKINFO.DLL
ModLoad: 76990000 769h5000 c:\windows\system32\ntshrui.DLL
ModLoad: 76b20000 76b31000 c:\windows\system32\ATL.DLL
ModLoad: 5b860000 5b8b4000 c:\windows\system32\NETAPI32.DLL
ModLoad: 769c0000 76a73000 c:\windows\system32\USERENV.DLL
(764.768): unknown exception - code 000006ba (first chance)
kXsetup: shGetSpecialFolder ][ result: C:\Documents and Settings\Peter\Start Menu\Programs
kxmixer: reset global settings finished
ModLoad: 10000000 10043000 c:\windows\system32\cmax20.DLL
ModLoad: 7b3b0000 763f9000 c:\windows\system32\comdlg32.DLL
ModLoad: 755c0000 755ee000 c:\windows\system32\mscftime.DLL
ModLoad: 708f0000 70903000 c:\windows\system32\asyncfilt.DLL
kxmixer: general pr-device [0/CT470 10k1 [a400]] first-time initialization
kxmixer: resetting settings for '0' device

***************** At this point the system freezes **************************

Can anyone suggest how I may proceed?

**dj_stick** · Sep 28, 2005, 12:23 PM

have you tried using system restore to restore to a point prior to the issue occuring?

_pF_ · Sep 28, 2005, 12:41 PM

Quote:

Originally Posted by dj_stick

have you tried using system restore to restore to a point prior to the issue occuring?

That might have got me up and running, but would not have solved the core problem.

As it was, I've been making extensive changes to my system and had no suitable restore points.

isilldur · Nov 10, 2005, 03:41 PM

Hi guys,

similar problem on my side. Just installed my new sata hdd. After I enabled my sata controller in bios, kx-mixer fails to load at startup and system freezes.

Whenever I disable my audigy or my controller everythings runs smoothly again.
Already tried several reinstalls of the controller, but no positiv effect. They do share the same IRQ (11). Im not sure if that could be the cause.

When I start Windows with a disabled audigy and than enable it after the startup it runs normally. I can than even start kx-mixer without any problems.

The controller is a SIS 3112 on a n-force 2. Unfortunatley, I couldn´t find any other driver than the one Im using.

Would be real gratefull for any suggestions

Doug W · Nov 11, 2005, 03:01 AM

Quote:

They do share the same IRQ (11). Im not sure if that could be the cause.

Looks like a good place to start troubleshooting. Can you change the IRQ of your sound card?

Here are the devices that use the same IRQ on my work computer, which doesn't seem to give me any trouble. That is not to say that your problem isn't caused by an IRQ conflict, since computers are basically unknowable and operate on a totally mystic, chaotic plane with only 2 or 3 shared ground rules.

(ISA) 9 Microsoft ACPI-Complient System
(PCI) 9 AC'97 Driver for Intel(r) 82801AA Controller
(PCI) 9 HCF 56K PCI Modem
(PCI) 9 Intel(r) 82801AA USB Universal Host Controller
(PCI) 9 kX 10k1 Audio - Model CT4830 Value
(PCI) 9 Realtek RTL8139(A) PCI Fast Ethernet Adapter

_pF_ · Nov 15, 2005, 03:29 PM

At the time of my problem with the kX initialization my computer was behaving very strangely: in particular, by running very slowly. On rebooting after my DMA 'fix', kX again failed to initialize.

I eliminated all of the obvious potential causes - spyware, viruses, hardware and bios, bad and unnecessary services, interrupts, etc.

One of the last things I tried was to remove all of my uncertified kernel drivers, viz. skype and daemon tools; that almost did the trick. The computer was still running too slowly though, but it was much better.

I noticed that, strangely, neither cpu was running flat-out. I played a movie and watched the cpus in Process Explorer. CPU 1's usage was pulsating in an unnatural way - if you'll excuse the expression. Reinstalling ffdshow resolved this last problem. My boot-time decreased by a minute.

Now kX initialized perfectly.

So I think that the problem is not specifically down to DMA or kX drivers, but to various uncertified drivers' conflicting - and perhaps other software interactions. I recommend you first remove any uncertified drivers and see if kX works then.

Sep 28, 2005, 12:00 PM	#1
_pF_ DriverHeaven Newbie Join Date: Jun 2005 Posts: 7 Rep Power: 0	Initializing kx Mixer Freezes XP System [SOLVED] [SOLVED: I saw in a similar bug report that an IDE device in PIO mode caused the poster's problem. Sure enough, XP had reset my secondary slave to PIO mode. This is a dodgy disk I use for scratch. Reinstalling the IDE channel reset it to DMA and all is now well. Why, I don't understand.] When I start the kx mixer my XP sp2 system freezes, and only a hard or soft reset will recover it. A few ctrl-alt-dels will reboot, so the keyboard is functional. The kx 3538i drivers themselves are loaded and working properly. Indeed, until recently I've had the whole kx 3538i (and h, and 3537) system - including mixer - working flawlessly, but none work now. I've spent a lot of time checking-out and rationalizing my hardware, memory, bios, software, services and drivers. Incidentally the problem is not connected with the ATI radeon drivers. A forced Kernel crash dump points to i8042prt.sys and I don't know whether that is helpful or not. The mixer displays the graphical 'expanding the potential' logo, then hangs. This is what happens before the freeze: kxmixer: add-on: registering 'c:\windows\system32\kxaddons.kxa' ikXplugin: get_count():load library failed. [7e] kxmixer: registering skins... kxmixer: adding start menu items kXsetup: shGetSpecialFolder result: C:\Documents and Settings\All Users\Start Menu\Programs ModLoad: 76fd0000 7704f000 c:\windows\system32\CLBCATQ.DLL ModLoad: 77050000 77115000 c:\windows\system32\ComRes.DLL ModLoad: 76980000 78988000 c:\windows\system32\LINKINFO.DLL ModLoad: 76990000 769h5000 c:\windows\system32\ntshrui.DLL ModLoad: 76b20000 76b31000 c:\windows\system32\ATL.DLL ModLoad: 5b860000 5b8b4000 c:\windows\system32\NETAPI32.DLL ModLoad: 769c0000 76a73000 c:\windows\system32\USERENV.DLL (764.768): unknown exception - code 000006ba (first chance) kXsetup: shGetSpecialFolder ][ result: C:\Documents and Settings\Peter\Start Menu\Programs kxmixer: reset global settings finished ModLoad: 10000000 10043000 c:\windows\system32\cmax20.DLL ModLoad: 7b3b0000 763f9000 c:\windows\system32\comdlg32.DLL ModLoad: 755c0000 755ee000 c:\windows\system32\mscftime.DLL ModLoad: 708f0000 70903000 c:\windows\system32\asyncfilt.DLL kxmixer: general pr-device [0/CT470 10k1 [a400]] first-time initialization kxmixer: resetting settings for '0' device *************** At this point the system freezes ************************ Can anyone suggest how I may proceed? Last edited by _pF_; Sep 28, 2005 at 12:37 PM. Reason: Fixed: solution.

Nov 10, 2005, 03:41 PM	#4
isilldur DriverHeaven Newbie Join Date: Feb 2005 Posts: 1 Rep Power: 0	Similar problem but with sata Hi guys, similar problem on my side. Just installed my new sata hdd. After I enabled my sata controller in bios, kx-mixer fails to load at startup and system freezes. Whenever I disable my audigy or my controller everythings runs smoothly again. Already tried several reinstalls of the controller, but no positiv effect. They do share the same IRQ (11). Im not sure if that could be the cause. When I start Windows with a disabled audigy and than enable it after the startup it runs normally. I can than even start kx-mixer without any problems. The controller is a SIS 3112 on a n-force 2. Unfortunatley, I couldn´t find any other driver than the one Im using. Would be real gratefull for any suggestions

Nov 15, 2005, 03:29 PM	Thread Starter #6
_pF_ DriverHeaven Newbie Join Date: Jun 2005 Posts: 7 Rep Power: 0	Uncertified Drivers At the time of my problem with the kX initialization my computer was behaving very strangely: in particular, by running very slowly. On rebooting after my DMA 'fix', kX again failed to initialize. I eliminated all of the obvious potential causes - spyware, viruses, hardware and bios, bad and unnecessary services, interrupts, etc. One of the last things I tried was to remove all of my uncertified kernel drivers, viz. skype and daemon tools; that almost did the trick. The computer was still running too slowly though, but it was much better. I noticed that, strangely, neither cpu was running flat-out. I played a movie and watched the cpus in Process Explorer. CPU 1's usage was pulsating in an unnatural way - if you'll excuse the expression. Reinstalling ffdshow resolved this last problem. My boot-time decreased by a minute. Now kX initialized perfectly. So I think that the problem is not specifically down to DMA or kX drivers, but to various uncertified drivers' conflicting - and perhaps other software interactions. I recommend you first remove any uncertified drivers and see if kX works then.