BSOD with SFP 4 and Sonar 3

[PaulSh]

OK, after 30 years in the computer industry I should know better, but I wanted to play with my new toys. I made the real bad mistake of updating my Pulsar II to SFP 4.0 and installing Sonar 3 (now updated to 3.1.1) at the same time. Before, my system was rock solid - now when I click on Play or Record in Sonar, I sometimes get a BSOD in scope.sys with IRQL_NOT_LESSTHAN or whatever it is. Sonar locks up sometimes too, and when I kill it with Task Manager I get the same error.

WinXP Home, Single Intel CPU, MSI Mobo. Yes, I have ACPI, and yes, my Pulsar card shares an IRQ with something else, but I've never had any problems like this before.

<font size=-1>[ This Message was edited by: PaulSh on 2004-05-26 14:49 ]</font>

[valis]

Move your creamware card to a new slot.

[PaulSh]

I guess that's a fairly standard reply to this type of problem, but why am I seeing it now all of a sudden? I'd understood that Scope 4.0 was really more of a smoke and mirrors update than anything really significant

[BingoTheClowno]

Do you have an external keyboard that is transmitting clock MIDI messages? If yes, then more than likely that's the problem.

[at0m]

On 2004-05-26 16:59, PaulSh wrote:
I guess that's a fairly standard reply to this type of problem, but why am I seeing it now all of a sudden?

I'd rather say you were very lucky it worked all these years sharing IRQ's. Try to put the cards on their own, that's the first thing on the list when you get IRQ_NOT_LESS_OR_EQUAL BSOD's.

[PaulSh]

OK, I've managed to free up an IRQ by disabling a USB controller I'm not using, so in theory if I move my Pulsar from PCI slot 5 to slot 3 it won't be sharing an IRQ any more. I'll give it a try.

[PaulSh]

Well, I guess it wouldn't really surprise anyone to know that moving the card so it had its own IRQ fixed the problem. Thanks, all.

[hubird]

convinced