PlanetZ forums - scopeusers.com

Hi there,

I'm having some serious issues with bluescreening right now that I'm linking to Scope

Information:

PC running AMD Athlon 64 x2 6000+, ASUS M2N32 PRO mobo, Seagate 500GB SATA II hard drive
Windows XP pro (sp3)
Pulsar project card
Sonar 6 producer
Scope 4

I've had it hang and bluescreen several times in the last two days.
I've only just set up this new PC, but I've noticed I get these problems since moving to 24bit recording and 48khz

I'm getting the following message when it bluescreens:


DRIVER_IRQL_NOT_LESS_OR_EQUAL

Stop 0x000000D1(0xBA502000, 0x00000002, 0x00000000, 0xB9C5D686)
SCOPE.SYS- ADDRESS B9c5D686 BASE AT B9C51000, DATASTAMP 3D25E31F

Unfortunately I need to fix this issue urgently as I have studio time booked out already (Thursday) and if it cannot be resolved, I will have wasted a lot of time and money.

Please advise as best you can. Thank you for all your help guys!

John

cool, thank you for that. where can I find cset.ini to change the latency?

apologies for the potentially silly question.

In:
scope_v45/app/bin

cheers

unfortunately, bluescreens usually indicate hardware issues, usually motherboard, graphics card or memory.

what are your irqs? is your scope card sharing an irq with anything?

Check that your card is propely in its pci socket, I took mine out to dust them dow the other day and the same thing happened.

yes., take it out, clean the plugs and put it in another pci slot as well! i get weird errors when i insert my card in a certain pci slot. u'm guessing its an irq problem..

or maybe a driver problem.
I had the exact same error message on my labtop when i updated my soundcard drivers ( not scope!)..

but first. take the card out, clean it, and put it in another slot.

if you clean the contacts, DON'T use rubbing alchohol. if you use alchohol it must be 99% or purer...

Hey guys, here's an update:

Nothing we've tried has worked so far.
- there were IRQ conflicts (with our NVIDIA graphics card), but thanks to XP it's been a chore to change them. finally though after some disabling of IRQ hogging items, we got the Creamware card on a solitary IRQ. Still bluescreening though.
- we do not have another PCI slot on the motherboard.
- we're using scope 4, so we haven't got the "scope_v45/app/bin" file structure.
- I did a search for the "cset.ini" file name and got nothing.
- I've changed the latency within sonar and still nothing.
- am just about to clean the card. will update you I'm sure.


I'm booked into a studio tomorrow morning and have already wasted a massive amount of recording time with my guitarist with this issue... not totally sure what to do.

My next thought would be to get a new video card as I suspect it's still conflicting.

thank you for all your help so far guys, but... help!
J

hi there, thanks for the help (again)

I found the cset.ini file but cannot see "intBlksize" or anything relating to the latency within the file. (nor "hw")

we're also not using ULLI. (our setting is 23ms @ 48khz)

One thing I should also mention is that it's not an immediate bluescreen that happens. I've been able to do an amount of recording but randomly it crashes/bluescreens.
this can happen anything between 3 / 4 hours through to as soon as we start using sonar.

Cheers!

Erm no I don't have a 1st generation card... I have Pulsar 2 - the ULLI setting is the lowest setting I could use (changed in an attempt to get a stable machine!) there are lower settings.

Well the computer is still crashing...I'm going ahead with recording with this computer even though it's giving me "blue screens" at random intervals! If anyone can offer any more help that would be great!!! I'll still be checking for solutions while I'm in the studio.

Thanks for helping!!

J

have you checked advice with proper fits in slot?
bluescreen scope is normaly when card is not fully in the slot at one point;
exat the behavior you said;
---------

this happens when you see f.e. one side of the pci goldcontacts minimal more up than the other if screwed to thight on case;

good vibes

That's just a driver problem.
Try deleting then reloading pulsar drivers.

back for more guys!

have cleaned the card and made sure it's sitting in the slot ok:
still bluescreening.

have deleted and reinstalled drivers several times.
still bluescreening.

smacking my head against wall.
still bluescreening.

bad hardware....motherboard, memory or video card...

Test your RAM.

Has this just begun to appear or is it an immediate problem?

Music Manic wrote:Test your RAM.

Has this just begun to appear or is it an immediate problem?

it's been intermittent.

was fine for several hours of testing when we first got it up and running...
then started bluescreening and hanging throughout a day of recording guitars with about 3 hours of work in between.
it got a bit worse.... and then I came into the studio and found that by switching from 48k to 44.1 it seemed to clear the issue up. (our mackie d8b was having issues syncing and then playing back.)

I went most of yesterday (about 9 hours), without any bluescreens or crashes. Then towards the end of the session it REALLY started slowing down...
sonar seemed to take forever to render the just recorded tracks.
I figured I should restart and did so... then I started bluescreening again. badly.
I've also found that every now and again we get some spiking from the mackie not syncing correctly to the pulsar.

I done no work at all since 10pm yesterday and this studio time is costing us...

not been able to check the memory yet... any suggestions of programs?

any more thoughts? this is driving me mad.

cheers again guys!
J

if you test the ram(use a program like memtest, you can get it free if you google the name), and it's good, you might try reseating the i/o plate on the card(just be careful it's held in place by 4 plastic screws). i'd also use compressed air to blow out the adat ports if you're using them.

the way to be sure that the problem isn't in the card is to put it in a different computer, be sure that it soesn't share irqs and see if it bluescreens there....

Could be a heat problem if you are running it trouble free for that length of time.