Community Forums Archive

Go Back

Subject:Fatal Exception error with Acid Pro 3.0 demo
Posted by: coose
Date:10/31/2001 1:35:52 AM

Hello all, I've been racking my brain on this one.
I downloaded the Acid Pro 3.0 demo and installed it and when it scans for audio plugins I get the following blue screen

Fatal Exception 06 has occurred at 0028:00000017

I hit enter to terminate the Acid Pro 3.0 demo and then a few mins later the application loads. I have uninstalled Acid Pro 3.0 demo rebooted, uninstalled directx rebooted, reinstalled directx 8a rebooted and reinstalled Acid Pro 3.0 demo and rebooted and I still get this error. I have also downloaded the other demos in the Acid family to see if this still occurs and it does not. The one thing that I have noticed is that the other demos do not scan for audio plugins at application start up so I am thinking it has something to do with that.
I am running Windows 98 on an AMD 1.4 ghz cpu with 1 GB ram and a 15 GB harddrive with 10 GB of free space. My sound card is intergrated into my motherboard it is the ECS K7AMA the sound card driver is ALi Audio Accelerator WDM driver. I have a GeForce 2 MX 400 64mb with TV out if this is also a concern. I am running the latest detonator drivers from Nvidia for this.

Hope this helps, btw this system is only a few months old and otherwise has no problems.

Thanks in advance. :)

Subject:RE: Fatal Exception error with Acid Pro 3.0 demo
Reply by: coose
Date:10/31/2001 8:24:58 AM

I think I have it narrowed down some, it defintly has to do with directx and display drivers. I haven't narrowed it down completely yet, but I will keep you updated.

Subject:RE: Fatal Exception error with Acid Pro 3.0 demo
Reply by: coose
Date:11/4/2001 2:33:22 AM

Just wanted to let you know that I have resolved my issues. There apparently was something wrong with my install with DirectX. I uninstalled all of my media playing applications and completely uninstalled DirectX and cleaned up my registry files and reinstalled windows then reinstalled DirectX 8 and my problem is solved now (I have created another problem with my display drivers and have to narrow that down now, heh, but I won't get into that).

Go Back