I AM USING PULSAR2 AND SX 1.05.061 ON AN AMD SYSTEM (DETAILS BELOW)AND HAVING THE ABOUVE PROBLEMS:
1) CUBASE QUITS UNEXPECTEDLY ,WITHOUT ANY NOTICE , EVEN IN NEW PROJECT WITH NO PLUGINGS OR NOTHING
2)AS ABOUVE WITH LAST AUDIO STILL HANGING...
3)WHEN MOVING SLIDES ON PULSAR CUBASE DROPS &CRACKLS
4)SOMETIMES BLUE SCREEN "IRQ NOT LESS OR EQULE"..
SOMETIMES SYSTEM CAN WORK OK FOR HOURS AND THEN FAIL &WONT WORK EVEN AFTER RESTATING...
SYSTEM IS XP PRO /W CLEAN INSTALL .PULSAR2 AND CUBASE SX +DUNGLE)ARE THE ONLY SOFTWARE INSTALLED.
DESCRIPTION:
AMD XP 2000+
GIGABYTE 7DXR+ VIA CHIPSET 686B
1GB DDR RAM
ATI 9000 /128MB DDR
ADAPTEC 2940UW2
SEGATE BARRACUDA 60GB
IBM SCSI 10 GB
MIDEX 8
THANX IN ADVANCE FOR ANY HELP!
FUF
SX QUITS AND PULSAR CRACKLES -PLEASE HELP
This is a cucase sx related issue!On 2003-04-23 18:13, fuflet wrote:
1) CUBASE QUITS UNEXPECTEDLY ,WITHOUT ANY NOTICE , EVEN IN NEW PROJECT WITH NO PLUGINGS OR NOTHING
Try to use an older version 1.03 or change to logic.
But chrashes is new projects withot plugs?!
What kind of PSU are u using? Could be a heat problem too...
Look at shared IRQ, the error message you have gotten has got to do with to many shared IRQ's
TheDubCrew
http://www.thedubmeditation.nl
http://www.thedubmeditation.nl
irq not less or equal...
dealt with that one for months
the ONLY thing that fixed it was a clean install in standard pc mode
i am not sure, but i don't think yor board supports apic, and even if it did, you may still run into this problem.
as mrokalea said, your card is sharing irqs with other devices, and in my experience, pulsar 2 cards do not like sharing irqs, hence the BSOD you are experiencing.
the sx problem is strictly a cubase issue- welcome to cubase sx!!!!!!!!
do you know how to install in standard pc?
dealt with that one for months
the ONLY thing that fixed it was a clean install in standard pc mode
i am not sure, but i don't think yor board supports apic, and even if it did, you may still run into this problem.
as mrokalea said, your card is sharing irqs with other devices, and in my experience, pulsar 2 cards do not like sharing irqs, hence the BSOD you are experiencing.
the sx problem is strictly a cubase issue- welcome to cubase sx!!!!!!!!
do you know how to install in standard pc?
may be it could be a processor or RAM problem associated with memory/processor usage. I have 2Gb of paging file partitioned on my hard disk + 384 RAM. Also installing intel app accelorator got rid of a lot of things like crackles and pops and messages such as PCI overflow etc. SX is very temperamental, if you have virus protection disable it before installing SX. Also what is your graphics card?
Good luck
Good luck
I have the same experience with nearly the same PC-configuration. It occured first, as I put in the third Pulsar-Card (3xPulsarII connected via STDM). The three cards share IRQ5 which should not be a problem as the communicate via STDM.
Other difference is, that it occurs only, if I get "heavy traffic" on my PC. Still don't know the reason ...
Other difference is, that it occurs only, if I get "heavy traffic" on my PC. Still don't know the reason ...
-
marcuspocus
- Posts: 2310
- Joined: Sun Mar 25, 2001 4:00 pm
- Location: Canada/France
I am also suffering from this mysterious IRQL_NOT_LESS_OR_EQUAL although none of my hardware cards share any IRQs. The Pulsar cards share IRQ11 but that's ok.
I found out that it is up to the Cubase SX USB dongle. I used Cubase SX for three month and 2-3 times a week Cubase SX just quitted. After starting it again I got that blue screen with IRQL_NOT_LESS_OR_EQUAL. One time I wasn't even able to set up the dongle again cause it just said error code 10. It even destroyed my project I was working on. I lost money cause I crossed the dead line for that remix.
On the Cubase SX CD there was a exe file which to start when problems with the dongle occur. After that it worked again but since one month I am using the dongle crack I found while searching on google for a solution. You won't believe...it works!!! After 4 weeks of working with Cubase SX + dongle crack I didn't get a blue screen *still testing*.
Well...is not a real help or solution. But hopefully Steinberg does sth. Cubase SX is not a cheap software and actually customers can expect it to work.
Good night
I found out that it is up to the Cubase SX USB dongle. I used Cubase SX for three month and 2-3 times a week Cubase SX just quitted. After starting it again I got that blue screen with IRQL_NOT_LESS_OR_EQUAL. One time I wasn't even able to set up the dongle again cause it just said error code 10. It even destroyed my project I was working on. I lost money cause I crossed the dead line for that remix.
On the Cubase SX CD there was a exe file which to start when problems with the dongle occur. After that it worked again but since one month I am using the dongle crack I found while searching on google for a solution. You won't believe...it works!!! After 4 weeks of working with Cubase SX + dongle crack I didn't get a blue screen *still testing*.
Well...is not a real help or solution. But hopefully Steinberg does sth. Cubase SX is not a cheap software and actually customers can expect it to work.
Good night
About a year ago I started using pulsar2 with TDM to Pulsar1 in 256DDR 1.4Ghz AMD 7200 HD nothing as flashy as a baracuda)Athlon and dreaded VIA chipset, I say dreaded because that's how everyone else referred to them on this forum - please read on as this may be useful to you all:-
After ::---
1) installing Windows98se and Mcaffee virus scan WITHOUT ANY PULSAR CARDS PHYSICALLY INSTALLED,
2) then installing the pulsar2 card PCI slot 2 with SFP (now SFP 3.1c),
3) then installing the pulsar1 card PCI slot 3 with TDM link,
4) then installing the pulsar1 card driver from windows controlpanel system devices menu
5) and then installing cubase v5.1r1,
(never used 1st or last pci slots for creamware gear)
6) searched the pc in explorer for the csnet.ini file and edited the 'blk size'to reflect how much ram I had. plus the min and max cache values
7) AND turned off the virus scanner at bootup by excluding as many startup programs as possible - (just type msconfig in RUN on windows start menu)
Making sure DMA was ticked in HD section of CntrolPanel/Device manager.
AFTER I had done all that and not installed any more programs on the PC - (I have a dual boot setup using two separate hardrives and bootmagic), I have never experienced one pop or crackle, the PC did power itself off and reboot a couple of times but I found out very quickly that this was a power supply that lacked enough gumption to drive all the hardware. After changing it for a 400W - I have had 1 year of completely blue screen, crackle and pop free recording and my pulsar routing windows have been far from simple, with muliple midi and audio tracks being recorded in cubase and taking the 10 DSPs to the limit. Hope this helps some poor unfortunate souls.
After ::---
1) installing Windows98se and Mcaffee virus scan WITHOUT ANY PULSAR CARDS PHYSICALLY INSTALLED,
2) then installing the pulsar2 card PCI slot 2 with SFP (now SFP 3.1c),
3) then installing the pulsar1 card PCI slot 3 with TDM link,
4) then installing the pulsar1 card driver from windows controlpanel system devices menu
5) and then installing cubase v5.1r1,
(never used 1st or last pci slots for creamware gear)
6) searched the pc in explorer for the csnet.ini file and edited the 'blk size'to reflect how much ram I had. plus the min and max cache values
7) AND turned off the virus scanner at bootup by excluding as many startup programs as possible - (just type msconfig in RUN on windows start menu)
Making sure DMA was ticked in HD section of CntrolPanel/Device manager.AFTER I had done all that and not installed any more programs on the PC - (I have a dual boot setup using two separate hardrives and bootmagic), I have never experienced one pop or crackle, the PC did power itself off and reboot a couple of times but I found out very quickly that this was a power supply that lacked enough gumption to drive all the hardware. After changing it for a 400W - I have had 1 year of completely blue screen, crackle and pop free recording and my pulsar routing windows have been far from simple, with muliple midi and audio tracks being recorded in cubase and taking the 10 DSPs to the limit. Hope this helps some poor unfortunate souls.
Into every life terrential rain continuously ....
hello every one,
forst of all ,its good to know that im not alone:)
well i have a blue screen that says the same massage that mention above :
IRQL_NO_LESS_OR_EQUAL and after i restart
the computer and sfp starts everything works fine until i start SX and then its open and crash before the project comes up and it says it hase a problem with the asio driver blue screen ,ya di ia di
well,
untill today every thing worked fine but i remember that yesterday i try to reinstall the onboard soundcard that i have on my asus P4PE motherboard , and i didnt succeed so today everything go's blue
i remember that i'v install directX8.1
and maybe it cause some problems , could it?
how can i uninstall thiis directX or retern to that olderone ,if i had eny?
<font size=-1>[ This Message was edited by: Omb on 2003-07-01 18:38 ]</font>
forst of all ,its good to know that im not alone:)
well i have a blue screen that says the same massage that mention above :
IRQL_NO_LESS_OR_EQUAL and after i restart
the computer and sfp starts everything works fine until i start SX and then its open and crash before the project comes up and it says it hase a problem with the asio driver blue screen ,ya di ia di
well,
untill today every thing worked fine but i remember that yesterday i try to reinstall the onboard soundcard that i have on my asus P4PE motherboard , and i didnt succeed so today everything go's blue
i remember that i'v install directX8.1
and maybe it cause some problems , could it?
how can i uninstall thiis directX or retern to that olderone ,if i had eny?
<font size=-1>[ This Message was edited by: Omb on 2003-07-01 18:38 ]</font>
hello again
as far for now the problem still exist .
i talk today with the store that sold me my pulsar and to the guy that fix this kind of problem and he told me that the problem is with the motherboard ( asus p4pe ) and irq
sharing .
he told me to put the card in the second or fifth slot and to allocate an irq for the card in the bios but still the problem exist ,mybe ill change again the card location.
i realy hope that it will be solved soon ,
im hungry for music.
BTW
if anyone among you solved this kind of problem ,pleeeeeeeeeeeas
Omb
as far for now the problem still exist .
i talk today with the store that sold me my pulsar and to the guy that fix this kind of problem and he told me that the problem is with the motherboard ( asus p4pe ) and irq
sharing .
he told me to put the card in the second or fifth slot and to allocate an irq for the card in the bios but still the problem exist ,mybe ill change again the card location.
i realy hope that it will be solved soon ,
im hungry for music.
BTW
if anyone among you solved this kind of problem ,pleeeeeeeeeeeas
Omb
-
Guest
i had the same error using cubase sx 1.051 and pulsar2+ on a celeron 2 933. i always had this problem when using the "asio2 flt" drivers with sx. SX usually POOFS, then when i reload sx it says the ASIO scope isnt running or whatever. At this point i have to shutdown SFP and reload, then bang, i get that nasty IRQL BSOD. (All this on a standard pc with no shared irqs, os tweaked, just windows xp, sx, cooledit and some vst plugs...)
Now, i use the ASIO2 24bit drivers with SX 1.061, and it hasnt crashed once yet. I use my pc quite aggressively too. 6-8hrs at a time, cpu often maxed with crazy vst plugins and sharcs near full. Also i'm not using XP anymore, down to WIN2K Pro/SP3. I've created a windows install similar to what's being done with "WIN2000/XP Lite" (www.litepc.com), i'm currently running a basic win2k core, no IE system or any of the standard frills. Extremely fast, similar to the days of 98lite. Never again am i going to use XP!
that's my experience..nothing conclusive, but in my case i'm sure it was definitely SX or those asio drivers at fault.
anyway, here's some info based on the microsoft support site.
SUMMARY
This article discusses how to troubleshoot the following Stop error in Windows XP:
Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename
The parameters refer to the specific issues that are involved:
Parameter 1 - An address that was referenced improperly
Parameter 2 - An IRQL that was required to access the memory
Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation
Parameter 4 - The address of the instruction that referenced memory in parameter 1
This article describes troubleshooting steps to take if you receive this Stop error either during or after the installation of Windows XP.
MORE INFORMATION
Stop error 0x0000000A (Stop 0x0A) shows that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). This error usually occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.
Now, i use the ASIO2 24bit drivers with SX 1.061, and it hasnt crashed once yet. I use my pc quite aggressively too. 6-8hrs at a time, cpu often maxed with crazy vst plugins and sharcs near full. Also i'm not using XP anymore, down to WIN2K Pro/SP3. I've created a windows install similar to what's being done with "WIN2000/XP Lite" (www.litepc.com), i'm currently running a basic win2k core, no IE system or any of the standard frills. Extremely fast, similar to the days of 98lite. Never again am i going to use XP!
that's my experience..nothing conclusive, but in my case i'm sure it was definitely SX or those asio drivers at fault.
anyway, here's some info based on the microsoft support site.
SUMMARY
This article discusses how to troubleshoot the following Stop error in Windows XP:
Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename
The parameters refer to the specific issues that are involved:
Parameter 1 - An address that was referenced improperly
Parameter 2 - An IRQL that was required to access the memory
Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation
Parameter 4 - The address of the instruction that referenced memory in parameter 1
This article describes troubleshooting steps to take if you receive this Stop error either during or after the installation of Windows XP.
MORE INFORMATION
Stop error 0x0000000A (Stop 0x0A) shows that there was an attempt in kernel mode to touch pageable memory at too high a process internal request level (IRQL). This error usually occurs when a driver uses an incorrect memory address. Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software.