Crashes with Scope Project + Scope Professional

Leper · Post by **Leper** » Fri Mar 28, 2008 7:49 pm

Hello,

I am using a Scope Project and Scope Professional, and have been getting a lot of crashes and not ideal behaviour.

I have the two cards hooked up via STDM. When my sequencer crashes (usually after 1-3 hours of working on a track, Scope keeps playing an endless loop of the last half second of audio, and then the computer restarts without warning, within 1 minute of the crash. Then, when I start up the same Scope project and sequencer project, I usually get crashes/reboots soon after.

Another effect I've seen is sometimes when I load a device, the scope interface freezes just after loading the device. It still makes sound if I play through my MIDI keyboard, but the entire scope software is frozen and I need to reboot to use it again. (If i terminate it within task manager and start it again, then either ASIO drivers dont work anymorer for my sequencer, or it reboots my computer).

My sequencer is energyXT 1.4

My computer is:
Asus K8V Deluxe motherboard
Athlon 64 3200+ CPU
GeForce 7800
2 gb ram

Please help me... I've tolerated this problem for about a year, but now It is becoming extremely painful to work on any music. I love the Scope system but I haven't been able to finish any songs in -months- because of the constant crashes or freezes.

I'm willing to buy new hardware if needed, in case my computer is not compatible with the Scope hardware.

kyunghwee · Post by **kyunghwee** » Fri Mar 28, 2008 9:09 pm

Does your system only crash after it's been running for 1-3 hours? Just stabbing in the dark here but perhaps overheating problem? I'd try running with the case open to see if it's related to heat problem.

Leper · Post by **Leper** » Fri Mar 28, 2008 10:15 pm

Thanks for the reply.

Hmm, well my system never crashes normally - only when making music and using Scope. I have a large Antec server case with very good cooling/ventilation.

I always have SFP open (its my main audio driver) and the computer runs fine for days playing games or running regular windows apps, etc. But when I start making music, I start getting crashes and freezing.

Post by **garyb** » Fri Mar 28, 2008 11:16 pm

have you used a midi monitor to check for active sensing being transmitted by your controller? if so, and if you have active sensing, have you tried turning it off in the controller or used a midi filter?

H-Rave · Post by **H-Rave** » Sat Mar 29, 2008 7:10 am

And of course the the classic scope/graphic irq conflict don't forget that one.You didn't mention them in your post.Having said that I have some problems in xtc mode??

Good luck

Leper · Post by **Leper** » Sat Mar 29, 2008 4:58 pm

Hello! Thank you all for your replies. I have some hope

I have checked my midi controller and active sensing is OFF.

Here is my IRQ settings:

There is my ethernet controller (motherboard's network card) sharing IRQ with my Scope Professional. Could this be causing a problem? How can I move it to a different IRQ?

Note: I tried setting my HAL to Standard PC a few months ago but it completely screwed up my whole system and I had to do a System Restore to get it functioning again.

Leper · Post by **Leper** » Sat Mar 29, 2008 5:00 pm

I should note that i did not have crashes when i only had a Pulsar 2 and energyXT. It ran very solid. Then when I bought the Scope Pro I started seeing these issues.

Post by **garyb** » Sat Mar 29, 2008 5:48 pm

yeah, it could be the shared irq.
moving to the other slot might help, so might disabling unused ports and devices...