Subject:Blue screen errors with acid 3.0

Posted by: liljim

Date:4/23/2002 5:16:42 PM

When i open acid it scans for direct x plugins.As soon as the scan starts i get a blue screen:Fatal Exception 0E @ 0028-00000017.What is causing that?I formated my system,wrote zero's to the drive and still no luck.I updated every driver i could and installed direct x 8.1,still nothing.Im ready to throw the whole thing through a window so someone please help a dumb ass louisiana boy get running.

Subject:RE: Blue screen errors with acid 3.0

Reply by: xxFT13xx

Date:4/23/2002 6:34:30 PM

sounds like its hitting a plugin that wasnt properly installed/uninstalled.

-Sin

Subject:RE: Blue screen errors with acid 3.0

Reply by: SonicJG

Date:4/24/2002 3:53:08 PM

Blue Screens are often a sign that there's something wrong with hardware or their drivers. You also didn't mention what OS you're on.

It could very well be related to either your audio card, video card, or if you have a list of plug-ins, perhaps one of them IS doing something funky when it gets called.

You may want to check http://www.analogx.com/contents/download/audio/dxman.htm for a tool that can tell you what DX plugs in you have.

HTH,
Joel

Subject:RE: Blue screen errors with acid 3.0

Reply by: liljim

Date:4/24/2002 7:26:16 PM

im running 98 first edition and i went got the tool (thanks for the link) for DX plugins.I went to properties on every plugin and got illegial operations on a few.I went back and removed those that caused trouble.Still no acid.I can email you a plugin list if you think it will do any good.

Subject:RE: Blue screen errors with acid 3.0

Reply by: liljim

Date:4/24/2002 7:50:09 PM

Ok,Get this.I just got pissed and booted in safe mode.Opened Acid up and it passed the plugin scan.I ran a few loops,checking to see if the plugins actually worked and they did.I rebooted back in normal mode and ran Acid again.Guess what.....It works now.What does that mean?

Subject:RE: Blue screen errors with acid 3.0

Reply by: groovewerx

Date:4/24/2002 8:59:49 PM

sounds like you needed to reboot after removing those plugs

Subject:RE: Blue screen errors with acid 3.0

Reply by: pwppch

Date:4/24/2002 11:11:30 PM

ACID scans for all plugins when it detects a change in the number of available plugins at startup. It will attempt to connect to any and all plugins loaded on a system to see if they 1) are really installed 2) functional and 3) whether they support some useful interfaces. Many plugs hate being "asked questions" and cause all kinds of havoc. Some have kernel mode components - ie drivers. Others are copy protected and don't like being "interogated".

Typically only drivers can cause Blue screens, though it is possible for a plugin to cause this.

Since ACID made it through it successfully built its cache of available plugins. Until something installs a new plugin or changes the registry in such a way that ACID believe that a new plugin might be installed, ACID will not attempt to interrogate any plugins.

If you ever run into this problem again, the easiest solution is to uninstall all of your plugins. Then install ACID again. Begin by installing one plugin at a time. Run ACID, it should find the new plugin and add it to its cache. After installing a new plugin, if ACID crashes, your machine hangs, or any badness happens, the last plugin you installed is the culprit. Let us know which one caused the problem, and will will contact the plugin vendor and raise hell with them.

Peter

Subject:RE: Blue screen errors with acid 3.0

Reply by: liljim

Date:4/25/2002 2:50:15 AM

Thanks to all of you for the help.I'll be sure to make a note of the bad plugins next time although i hope there won't be a next time.Im going make some new tunes,catch yall later.

Jimmy

Subject:RE: Blue screen errors with acid 3.0

Reply by: BlueRajah

Date:4/25/2002 3:49:31 PM

I'd like to recommend that you update your operating system to Win98SE at a bare minimum. You can get the info on this from Microsoft's web site. It's relatively inexpensive. Second, I'd recommend that you run the diagnostics under Start/Programs/Accessories/System Tools/System Information, especially the DirectX diagnostics. And make sure you have the latest version of DirectX, which is a free download from Microsoft.