this is pretty strange,
I didn`t do anything, but since some time, I m having clicks when recording asio signal.
The clicks do not appear on the scope analog out, so it seems to be a software issue.
I am working at lowest latency setting, 44,1Khz
with higher latency it works fine, but I remember, lowest latency worked fine with my system some time ago.
So it seems to be a setup issue.
I don`t know what I have changed.
The last days I did a new xp installation, which diddn`t solve the problems...
change the card slots scope<->pulsarII didn`t help too.
I have optimized the xp installation for background tasks....
Is there anything I could do to solve these new problems?
could it be the new forceware grafics driver I am using?
any other tips?
recording ASIO -> clicks
I`ve tried doubledawg but it didn`t help.
mhh that really sucks, now I work over 1 year without any problems and now whats going on?
I think it could be a problem with irq and that stuff, but my motherboard doesn`t feature a clear_nvram setting. (all my other boards had this feature.)
So the scope always sits on IRQ 19 and the pulsarII always on IRQ 16, some sort of random IRQ assignment could probably solve the problem.
I did take out the scope cards some time ago, to check out an usb card, maybe this mixed up my nvram and now the scope boards are assigned to other IRQs which may get in conflict with other components. ( but thats just one of my ideas, what could be the problem)

I mean there are no signs of conficts in system managment, but you never know with this irq sharing.
mhh that really sucks, now I work over 1 year without any problems and now whats going on?

I think it could be a problem with irq and that stuff, but my motherboard doesn`t feature a clear_nvram setting. (all my other boards had this feature.)
So the scope always sits on IRQ 19 and the pulsarII always on IRQ 16, some sort of random IRQ assignment could probably solve the problem.
I did take out the scope cards some time ago, to check out an usb card, maybe this mixed up my nvram and now the scope boards are assigned to other IRQs which may get in conflict with other components. ( but thats just one of my ideas, what could be the problem)

I mean there are no signs of conficts in system managment, but you never know with this irq sharing.
maybe..... normally I do not write down the IRQ numbers of the nvram.
but it could have been like this:
scope IRQ ? lets say 14
pulsar IRQ ? lets say 15
now I exchanged scope card with usb card and maybe the usb card was fixed to a new IRQ
And finally after replacing the usb card back with the scope card they are adressed by new IRQs which may cause problems.
but It seems I have located a problem, I get very short cpu peaks which seem to cause the record bug.
how can I find out what causes the cpu spike.
I mean my whole system is running at 0-2% and sometimes it has a very short spike ....
there is a small conflict somewhere, but I don`t know how to find out whats causing it.

but it could have been like this:
scope IRQ ? lets say 14
pulsar IRQ ? lets say 15
now I exchanged scope card with usb card and maybe the usb card was fixed to a new IRQ
And finally after replacing the usb card back with the scope card they are adressed by new IRQs which may cause problems.
but It seems I have located a problem, I get very short cpu peaks which seem to cause the record bug.
how can I find out what causes the cpu spike.
I mean my whole system is running at 0-2% and sometimes it has a very short spike ....
there is a small conflict somewhere, but I don`t know how to find out whats causing it.
thank you stardust,
concerning the background task, keep in mind I did a new install after deinstalling the usb card.
so there shouldn`t be any unwanted drivers on my system right now.
I only installed newest chipset drivers and forceware for 6600gt and amd cpu driver.
the rest is a very clean os with sp2. So I`m pretty sure its a bios related problem.
concerning the background task, keep in mind I did a new install after deinstalling the usb card.
so there shouldn`t be any unwanted drivers on my system right now.
I only installed newest chipset drivers and forceware for 6600gt and amd cpu driver.
the rest is a very clean os with sp2. So I`m pretty sure its a bios related problem.