PlanetZ forums - scopeusers.com

Ok, ok, not in flames, but still...

From time to time, and always while working with scope (recording, mixing, etc'), the entire machine crush down.

Everything, including the mouse, simply freeze on screen, escorted by a high-pitched pulsing static noise. It sounds like a constantly repeating corrupted audio buffer.

The only way to end this acoustic nightmare is to disconnect the computer off its power source.

Any help or tips that will illuminate this strange and agressive phenomenon will be highly appreciated.

configuration:
AMD 2800, 512RAM, PulsarII, Scope 4.0, WinXP SP1, 2 IDE HDs.

Thanks in advance,
ds-sound


_________________
<FONT SIZE="-2"> ["...and yet I always fail to notice, that I'm still heading for the ground..."]</FONT>

<font size=-1>[ This Message was edited by: ds-sound on 2005-05-03 03:56 ]</font>

hm , how many times i heard this before ?
i had similar problems some time ago, but once there were one post about changing to 3.1a driver, which fantasticly works for me, can't be sure for other setups,
and i have all things which people don't recommend enabled;
like multi acpi
ht enabled
usb enabled
1394 port for firewire enabled

i have p4 2.8ht, asus p4c800de, 1mb ram, ide hdd 80gb, ati radeon 9600,, winxp sp2

i get time to times blue screen, but mostly when running modular in sfp, but i remember that behaviour before in my diferrent setup,
but i don't have any freezes anymore, which i had before,
and i can still use sfp4, but with sfp3.1a drivers ...

hm, i wonder why, but the point is , that now i can work all day without freezes, which is the most important thing here,

no tension, no high blood pressure, no sweating ....





matej

<font size=-1>[ This Message was edited by: fidox on 2005-05-03 06:21 ]</font>

<font size=-1>[ This Message was edited by: fidox on 2005-05-03 06:21 ]</font>

Did you installed ASPI?

i had your same problem... i take the replies to my post and the replies to your post and my pc from 1 hour doesnt crash

read this:

http://www.planetz.com/forums/viewtopic ... forum=1&11

Many thank-you's to you all.

I am having a similar problem but I am using SONAR 4 as a sequencer. If I disable MIDI in Scope 4 (or in SFP 3.1c- it happens there as well), and also disable MIDI in/out in SONAR the problem goes away. But I need MIDI.

Any ideas on a fix?

Thanks in advance.

It keeps crashing... i don't know what to do, i know itãs not midi related as it is sfp which crash not cubase. I have installed 3.1c . On the thread above fidox says 3.1a but on a different thread 3.1c. Please let me know cause i have really a problem. It can crash anytime fullloaded but also with just dynamic mixer loaded... I can work for 4 hours and the next time it can crash in 10 minutes.
I donãt know how to disable my graphics card from bus mastering but i know that itãs not that. There isnãt any irq sharing... Aby ideas.
The funny thing is that i configured a friend of mine system with the same mobo (d865perl) and he says that itãs not crashing!
What reallly makes me anxious is that most of the times the system restarts, itãs realy a hard crash and when a blue screen appears it says "driver corrapted"

this is not normal for scope. are you sure that you don't have faulty memory or a problem with the xp install? how about the power supply? 3.1c never crashed for me and 4.0 is rock stable as well....

actually, gary, it's quite common.
I've seen (and heard) it happen more than once over several machines.

freezes in cubase, maybe. freezes from hardware, common. freezes in scope alone? not so common.

I got this problem recently...I have pulsar 2 for six month and it just happened as I tried to use the STS 5000 It's one more nail in this crapy sampler...

Cubase SX2...no xtc P4 3.0 1.5g ram

again, if the computer is right, scope rarely crashes, it's VERY stable. i am quite sure that the freezes and crashes described are happening, just not for the reasons often postulated and given....

it's not scope that crush and freeze, it's the entire machine.
"VERY stable"? I beg to differ... You can't argue with facts, can you?

I'm more interested in solutions, however.

SFP IS very stable if you have your pc setup right.
Configuration issues aren't Scope's fault

I know you all mean well, but these kind of reply are'nt really helpful.
If proper configuration is required, what should be adjusted?

not knowing what you have done, the quality and model and brand of your parts, whether it was a fresh install of the os, whether you properly installed the motherboard drivers from the start(i suspect fra77's problem), whether you have a midi controller that is transmitting active sensing(a common cause of freezes) or any one of a thousand other computer issues, it's so very hard to just say, "do this".

first off, what motherboard are you using?
second, what if anything, is sharing an irq with your scope card?

more information, less smarty sarcasm and maybe i can help. NONE of the computers that i have set up have any of these problems. most of the regulars here can say the same. there is no audio software available that is more stable than scope(that i have seen).

if you have cheap, poor quality parts and you are trying to use high-end audio apps and hardware like scope, you WILL have serious problems. there is no more resource intensive activity that you can do with a comnputer(for the most part). the price difference between good parts and bad parts is minimal too, upping the cost of the pc by about $200, a pittance considering the cost of a scope card(i'm not saying that you have bad parts, just ranting....). so, what motherboard, what ram, what irqs, did you do a complete fresh install of everything when you installed the card?

My appologies if I appeard as smarty and sarcastic, I assure you I bare much respect to you, as well as to all planet-z users.
English is not my mother language, and therefore misunderstandings happen from time to time, as certain subtleties are lost along the way.

Back to SPF:

The Computer was tailored and optimized by Bobis (Shay Shezifi). He's a close partner of Red-Muze (Adern, Flexor), and accounted as one of the No.1 experts here at the holy land. I trust he knows what he's doing.

The detailed configuration is as followed:

CPU: AMD Athlon XP (2800)
CPU Cooler: zalman cnps6000-cu
Mother Board: Gigabyte GA-7VT600 1394 (With Firewire interface
Memory: Kingston DDR400, 512mb
Hard Drives: 2 Seagate Baracuda 7200RPM
Display card: Matrox Millennium G550
Case: Hec/Compucase CI6919
CD: Asus X52 or Creative X52 ot Teac X52
Burner: Teac X52
Floppy: Teac

I'm affraid I'm too novis to answer your IRQ question...

If there's anything else you'd like to know in order to assist, I'll be more than happy to provide additional details.

thankfully yours,
ds-sound

<font size=-1>[ This Message was edited by: ds-sound on 2005-05-29 12:35 ]</font>

for irq info go to start/programs/accessories/system tools/sytem information/hardware resources/ conflicts-sharing and tell me what's there.

as to the motherboard, it's probably not the source of your problem, but the via chipset is probably not a good choice....

is that the cheap kingston valueram? if so, replace it with a high quality stick...

what power supply are you using?

System Information including CW related lines:

IRQ 18 Creamware Pulsar2
IRQ 18 Realtek RTL8139/810x Family Fast Ethernet NIC

All parts are about a year old, all of the highest quality available at that time.

IRQ 18 Creamware Pulsar2
IRQ 18 Realtek RTL8139/810x Family Fast Ethernet NIC


there is almost certainly your problem. try moving the card to another slot and then check system info again. your computer is not set up properly. the cwa card must not share an irq with anything.