PlanetZ forums - scopeusers.com

I have a scope 6 dsp running SnS under 4.5
.
It used to work fine in an MSI AMD Athlon 64 3Ghz PCI mobo.

I'm trying to cross grade to an MSI K9, AMD dual core 4.6Ghz.

For the first few days, it ran perfectly.
I could play synth devices (including vectron) and it played fine - no clicks, crackles or overflows.

I've come to use it a few days later and now I regularly get BSOD and it complains about missing DSP objects "inverter" and "envelope follower 2" when I try to add Vectron, etc..

I've checked my folders and I have what I think are those dsp objects
sinvert.dsp and EFSRL2.dsp.

I've now stripped back the machine and only by removing the creamware scope card will it be stable.

I've tried overwriting (and bit compared) the install with the previously working version from my old PC, but results are the same.

Any ideas, why the card can't find a file that is clearly there?

Although this mobo is mixed pci/pcie and has a high FSB (200), AFAIK the PCI slots still clock at 33Mhz, as the bios only sets the clock for the E slots.

BTW the K9N SLI Platinum uses a nvidea nforce 570 chipset.

Any ideas ???


BTW the google link I used to find this forum featured this post in prime slot....

http://www.planetz.com/forums/viewtopic ... forum=5&80

Check & see if those dsp files are set with read only or 'system' flags. If you want to make it easy on yourself try the batchfile I attached. I made it some time ago to make things easy on new users.

To troubleshoot the bsods, right click on My Computer & choose 'Manage' to open the Management Console. Go into System Tools > Device Manager in the left hand pane and then View > Resources by Type. List everything under the Interrupt Request (IRQ) section including the IRQ's. Most likely there are things that you could disable in your onboard BIOS to simplify your system's IRQ sharing.

Thanks Valis, that's very helpful !

Presumably the correct state is with none of the files hidden, system or read only then ?

You think the bsod is an IRQ conflict then ? OK I'll have a play with that.....


Huge thanks for your help!

The correct state of the files is to be neither system nor hidden/read only. This sometimes happens with installs, and is most likely due to legacy code in the installer (imho).

BSOD's with Scope cards are generally an IRQ / resource sharing conflict yes, barring some other issue with your PC of course (bad ram, overheating cpu etc).

The listing of IRQ's will help us help you.