3536 spontaneously reboots

meroveus · Oct 31, 2003, 03:36 AM

Hi Eugene,

I have been using W2003, and before yesterday had never seen a blue screen or suffered a reboot.
While trying the 3536a drivers though, it happened twice in an hour.
Both times, while playing an mp3, the screen suddenly went black, and the system rebooted.
The first time it happened when changing a DSP layout.
The second time it happened while I was checking the Analyser.
For a split second, every single voice showed up in multiple colours, then the sytem rebooted.

To make matters worse, even though I went back to 3534, ASIO has disappeared, and cannot be used.

It was working fine until I tried the 3536 drivers.
I have uninstalled and reinstalled the drivers, cleaned out the registry, and removed the registered plugs and skins, but still I cannot use ASIO.

When I select 'Settings/ASIO Control Panel' in the menu, nothing happens.

Although KX ASIO is available in my soundcard settings for my audio apps, if I select it, I get the message 'Failed to initialize ASIO driver'

If I persist with this selection, the app is unresponsive and refuses to play or record sounds.

I've tried 'Reset Settings' and 'Reset Global Settings' with no change.

I'll try 3536b later and report whether it works for me.

**Eugene Gavrilov** · Oct 31, 2003, 11:44 PM

turn off 'automatic reboot' feature (somewhere in control panel->system) and watch if there's any additional information displayed

as for asio, don't forget to set the hardware acceleration (since it might have got reset)

/E

meroveus · Nov 1, 2003, 09:04 AM

Hi again Eugene,

I've turned off the auto reboot.
I reinstalled the latest KX project drivers , but still no ASIO.

So I had a closer look in the registry.
It seems I didn't clean it out properly for I found hundreds of old KX settings.
After about an hour of deleting registry keys I gave up.

But the good thing is, when I did reinstall the KX drivers, I got my ASIO back.
It seems your unistallers don't delete any KX registry entries.

And that Windows becomes confused with the multitude of ASIO keys and entries!

I have just downloaded and tested about half a dozen registry monitoring apps.
The best one I have found which did the job was Active Registry Monitor from http://www.ntutility.com.
I think I'll buy it.
All the others either barfed at various times, or didn't display the information in an easy to understand way.

I know you are extremely busy and all, but it would be nice if your future uninstallers could delete the registry entries which were created.
It is essential to remove the old entries, especially when installing an updated version every week or so.

In the meantime, I will write a script to remove the registry keys.
Can't do a great deal though until my exams are over.

You have done a great job with these drivers, but you definitely need help Eugene.

I may not have much money to contribute, but after November will definitely be able to contribute a lot of time.
Installing the drivers a number of times I have found a number of small mistakes and anomalies, which can be easily corrected.
Once the installing and uninstalling procedures have been perfected, it will be easier to upgrade drivers.
Then I will be free to give a hand on helping with Soundfont issues.

BTW, every time I install the drivers, even the very first time when my system was fresh and clean, I get a number of notification boxes saying "Error initializing secondary DirectSound". The last time I installed, I got five of these boxes in a row.
What are they about?

cheers

-m

RIV@NVX · Nov 1, 2003, 12:53 PM

Have you maximized HW acceleration in Control Panel and dxdiag?

meroveus · Nov 2, 2003, 02:15 AM

Yes, I have checked both.

Oct 31, 2003, 03:36 AM	#1
meroveus DriverHeaven Junior Member Join Date: Jul 2002 Posts: 63 Rep Power: 0	3536 spontaneously reboots Hi Eugene, I have been using W2003, and before yesterday had never seen a blue screen or suffered a reboot. While trying the 3536a drivers though, it happened twice in an hour. Both times, while playing an mp3, the screen suddenly went black, and the system rebooted. The first time it happened when changing a DSP layout. The second time it happened while I was checking the Analyser. For a split second, every single voice showed up in multiple colours, then the sytem rebooted. To make matters worse, even though I went back to 3534, ASIO has disappeared, and cannot be used. It was working fine until I tried the 3536 drivers. I have uninstalled and reinstalled the drivers, cleaned out the registry, and removed the registered plugs and skins, but still I cannot use ASIO. When I select 'Settings/ASIO Control Panel' in the menu, nothing happens. Although KX ASIO is available in my soundcard settings for my audio apps, if I select it, I get the message 'Failed to initialize ASIO driver' If I persist with this selection, the app is unresponsive and refuses to play or record sounds. I've tried 'Reset Settings' and 'Reset Global Settings' with no change. I'll try 3536b later and report whether it works for me.

Nov 1, 2003, 12:53 PM	#4
RIV@NVX Freedom is a feature. Join Date: Jul 2002 Location: Croatia, Rijeka Posts: 4,476 Rep Power: 0 System Specs	Have you maximized HW acceleration in Control Panel and dxdiag? __________________ -- Vedran

Oct 31, 2003, 11:44 PM	#2
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,119 Rep Power: 75	turn off 'automatic reboot' feature (somewhere in control panel->system) and watch if there's any additional information displayed as for asio, don't forget to set the hardware acceleration (since it might have got reset) /E

Nov 1, 2003, 09:04 AM	Thread Starter #3
meroveus DriverHeaven Junior Member Join Date: Jul 2002 Posts: 63 Rep Power: 0	Hi again Eugene, I've turned off the auto reboot. I reinstalled the latest KX project drivers , but still no ASIO. So I had a closer look in the registry. It seems I didn't clean it out properly for I found hundreds of old KX settings. After about an hour of deleting registry keys I gave up. But the good thing is, when I did reinstall the KX drivers, I got my ASIO back. It seems your unistallers don't delete any KX registry entries. And that Windows becomes confused with the multitude of ASIO keys and entries! I have just downloaded and tested about half a dozen registry monitoring apps. The best one I have found which did the job was Active Registry Monitor from http://www.ntutility.com. I think I'll buy it. All the others either barfed at various times, or didn't display the information in an easy to understand way. I know you are extremely busy and all, but it would be nice if your future uninstallers could delete the registry entries which were created. It is essential to remove the old entries, especially when installing an updated version every week or so. In the meantime, I will write a script to remove the registry keys. Can't do a great deal though until my exams are over. You have done a great job with these drivers, but you definitely need help Eugene. I may not have much money to contribute, but after November will definitely be able to contribute a lot of time. Installing the drivers a number of times I have found a number of small mistakes and anomalies, which can be easily corrected. Once the installing and uninstalling procedures have been perfected, it will be easier to upgrade drivers. Then I will be free to give a hand on helping with Soundfont issues. BTW, every time I install the drivers, even the very first time when my system was fresh and clean, I get a number of notification boxes saying "Error initializing secondary DirectSound". The last time I installed, I got five of these boxes in a row. What are they about? cheers -m

Nov 2, 2003, 02:15 AM	Thread Starter #5
meroveus DriverHeaven Junior Member Join Date: Jul 2002 Posts: 63 Rep Power: 0	Yes, I have checked both.