hello, i have a serious problem, i am experiencing since 6 months a strange bluescreen, that occours randomly when i play or when i record more than 1 track at the same moment. it could be go bluescreen after 1 minute when i hit record or play or after 1 or 2 hours or even three. it seems to have no rules...
my setup is: P4 2800 P4S800 MOTHERBOARD 1GIG RAM, MAXTOR HD, SOME KIND OF GEFORCE VIDEO CARD. i use sonar 4 producer edition.
i report the text of the bluescreen
DRIVER_IRQL_NOT LESS_OR_EQUAL
STOP: 0X000000D1 (0XF88C5000, 0X00000002, 0X00000000, 0XF8030686)
Scope.sys - Address F8030686 base at F8024000, Datestamp 3d25e31f
i have checked everything from hardware to software that could cause the problem....whitout results.... every time i have the computer in bluescreen and the audio project sometimes lost......
please help me!
thank you
frustrating Scope.sys random Bluescreen while playing or rec
the "chipset" is the part of the motherboard that controls the flow of data on the motherboard. the motherboard you have has a chipset made by SIS. it is a cheapie, poor quality chipset. better to get an intel or nvidia chipset as performance will be more reliable and robust. the sad thing is, that it's only about $40 more for a good(for audio) motherboard than a bad one. the motherboard you have is by a very reputable company and is not a bad product at all for internet or game use.
if you want to stay with asus, i suggest a model with an intel 865 or 875 chipset. i usually reccomend the intel d865perl motherboard as it can be found for about $90u.s. and it is very reliable and stable with very good performance.
obviously, the mobo you have is o.k. and it should work, it's all just a matter of degree....
if you want to stay with asus, i suggest a model with an intel 865 or 875 chipset. i usually reccomend the intel d865perl motherboard as it can be found for about $90u.s. and it is very reliable and stable with very good performance.
obviously, the mobo you have is o.k. and it should work, it's all just a matter of degree....
Perhabs you try other things before start to reconfigure you computer.
Are the cards inserted correctly in the slot.
Are SDTM connector correct?
Clean the contacts with alcohol.
Make sure everthing else in your computer has good contact. RAM, IDE, Power etc.
My first pulsar1 had similar problems. It was broken and CW replaced it. Problem solved.
Normally CW stuffs do not crash with blue screens. It freezes sometimes but without blue screen.
Are the cards inserted correctly in the slot.
Are SDTM connector correct?
Clean the contacts with alcohol.
Make sure everthing else in your computer has good contact. RAM, IDE, Power etc.
My first pulsar1 had similar problems. It was broken and CW replaced it. Problem solved.
Normally CW stuffs do not crash with blue screens. It freezes sometimes but without blue screen.
that wouldn't make much sense. scope is VERY stable in the proper environment. it is the single most expensive and the most powerful part of the computer. why wouldn't you put it in an environment where it was happy? chances are that the cwa card isn't even the cause of the problem. more likely, since the scope app is intensive, it is showing up a problem in your machine that is very solvable. as i stated earlier, that motherboard is automatically suspect because of the sis chipset.
that stated, have you checked in programs/accessories/system tools/system information to find out about resource sharing and irq allocation information in your computer? if not, please check it. the information in the device manager that sez "no conflicts" is not very helpful as your scope card could be sharing an irq with something and that could be fine in windows' estimation, but not at all good for the card in some situations. also, this type of blue screen could be caused by a faulty or badly written driver, make sure that you have the latest drivers for your vid card and motherboard resources. it is kinda strange that the problem is at 48k ONLY, i've never seen this, perhaps someone with programming experience would have an idea why, still, it should work. really there are many reasons why 44.1k is a better choice if you are going to end up on a cd, but 48k SHOULD work. i would like to be more help, but at least i can tell you that i've done a number of installs and they all run great. if worst came to worst, a clean install should fix everything(if it is done properly). you might try reinstalling sonar(over the top of the old install). maybe a critical file is corrupt.
i have NEVER lost audio from a crash so i have always been able to reconstruct after a crash, but really, i rarely see crashes(one every 2 months or so) and i am usually the cause of them. do you have "write behind caching" enabled for your hds? if so, disable it. it can cause data loss in the event of a crash.
that stated, have you checked in programs/accessories/system tools/system information to find out about resource sharing and irq allocation information in your computer? if not, please check it. the information in the device manager that sez "no conflicts" is not very helpful as your scope card could be sharing an irq with something and that could be fine in windows' estimation, but not at all good for the card in some situations. also, this type of blue screen could be caused by a faulty or badly written driver, make sure that you have the latest drivers for your vid card and motherboard resources. it is kinda strange that the problem is at 48k ONLY, i've never seen this, perhaps someone with programming experience would have an idea why, still, it should work. really there are many reasons why 44.1k is a better choice if you are going to end up on a cd, but 48k SHOULD work. i would like to be more help, but at least i can tell you that i've done a number of installs and they all run great. if worst came to worst, a clean install should fix everything(if it is done properly). you might try reinstalling sonar(over the top of the old install). maybe a critical file is corrupt.
i have NEVER lost audio from a crash so i have always been able to reconstruct after a crash, but really, i rarely see crashes(one every 2 months or so) and i am usually the cause of them. do you have "write behind caching" enabled for your hds? if so, disable it. it can cause data loss in the event of a crash.
i did everything you said before, no results... the problem is still there, i changed also the motherboard and i have that shitty random error every time... my creamware pulsar 2 does not share irqs with anything!!! i'm having serious problems.... i have had this problem with sonar 3 and now with sonar 4.... with scope 4.0 and with scope 3.1 with a different motherboard, with different ram, with different video card...... nonsense.....
i've tried everything and now i have the solution. its not hardware-software.... i tried to use the asio drivers in sonar for the first time and the computer worked perfectly... i was working with wdm/ks that caused this problem. now, with 24-bit asio i have no problems.... FOR 6 MONTHS I TRIED, AND NOW EVERYTHING'S OK... strange.... seeing this problem (driver irql not less or equal) i thought that had something to do with irqs.... asio... bah!!!
bye and thank you
bye and thank you