Computer stops responding

galileo · Post by **galileo** » Thu Jan 24, 2008 3:01 pm

ok garyb, i have this:

Puerto E/S 0x00000000-0x00000CF7 Bus PCI
Puerto E/S 0x00000000-0x00000CF7 Controladora de acceso directo a memoria

IRQ 11 Controladora de vídeo (compatible VGA)
IRQ 11 Controladora Ethernet

Puerto E/S 0x00000400-0x0000047F Recursos de la placa base
Puerto E/S 0x00000400-0x0000047F Recursos de la placa base

IRQ 23 Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
IRQ 23 Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C

IRQ 16 Intel(R) 915G/P/GV PCI Express Root Port - 2581
IRQ 16 Microsoft UAA Bus Driver for High Definition Audio
IRQ 16 Intel(R) 82801FB/FBM PCI Express Root Port - 2662
IRQ 16 Intel(R) 82801FB/FBM USB Universal Host Controller - 265B

IRQ 18 Intel(R) 82801FB/FBM PCI Express Root Port - 2664
IRQ 18 Intel(R) 82801FB/FBM USB Universal Host Controller - 265A

IRQ 19 Intel(R) 82801FB/FBM PCI Express Root Port - 2666
IRQ 19 Intel(R) 82801FB/FBM USB Universal Host Controller - 2659
IRQ 19 Intel(R) 82801FB Ultra ATA Storage Controllers - 2651

Dirección de memoria 0xA0000-0xBFFFF Bus PCI
Dirección de memoria 0xA0000-0xBFFFF VgaSave

Puerto E/S 0x00000500-0x0000053F Recursos de la placa base
Puerto E/S 0x00000500-0x0000053F Recursos de la placa base

galileo · Post by **galileo** » Thu Jan 24, 2008 3:03 pm

In addition, the IRQs:

IRQ 0 Cronómetro del sistema OK
IRQ 1 Teclado estándar de 101/102 teclas o Microsoft Natural PS/2 Keyboard OK
IRQ 4 Puerto de comunicaciones (COM1) OK
IRQ 6 Controlador estándar de disquetes OK
IRQ 8 Sistema CMOS/reloj en tiempo real OK
IRQ 9 Sistema Microsoft compatible con ACPI OK
IRQ 10 Intel(R) 82801FB/FBM SMBus Controller - 266A OK
IRQ 11 Controladora de vídeo (compatible VGA) OK
IRQ 11 Controladora Ethernet OK
IRQ 13 Procesador de datos numéricos OK
IRQ 14 Canal IDE principal OK
IRQ 15 Canal IDE secundario OK
IRQ 16 Intel(R) 915G/P/GV PCI Express Root Port - 2581 OK
IRQ 16 Microsoft UAA Bus Driver for High Definition Audio OK
IRQ 16 Intel(R) 82801FB/FBM PCI Express Root Port - 2662 OK
IRQ 16 Intel(R) 82801FB/FBM USB Universal Host Controller - 265B OK
IRQ 17 Intel(R) 82801FB/FBM PCI Express Root Port - 2660 OK
IRQ 18 Intel(R) 82801FB/FBM PCI Express Root Port - 2664 OK
IRQ 18 Intel(R) 82801FB/FBM USB Universal Host Controller - 265A OK
IRQ 19 Intel(R) 82801FB/FBM PCI Express Root Port - 2666 OK
IRQ 19 Intel(R) 82801FB/FBM USB Universal Host Controller - 2659 OK
IRQ 19 Intel(R) 82801FB Ultra ATA Storage Controllers - 2651 OK
IRQ 21 Creamware Pulsar OK
IRQ 22 NIC Fast Ethernet PCI Familia RTL8139 de Realtek OK
IRQ 23 Intel(R) 82801FB/FBM USB Universal Host Controller - 2658 OK
IRQ 23 Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C OK

Post by **garyb** » Thu Jan 24, 2008 4:27 pm

well, assuming that the software is installed correctly, you have a hardware issue. i'd guess motherboard, but it may be ram or video.......

did you try disabling antivirus?

Mr-Bit · Post by **Mr-Bit** » Fri Jan 25, 2008 3:03 am

So my question is do the lower numbered IRQ's get priority over the higher ones or do they all get the same ?

motormind · Post by **motormind** » Mon Jan 28, 2008 12:22 pm

I also have a serious problem with my PC freezing up. I have a Asus M2N32-SLI Deluxe mainboard with 4 Gb of RAM. I did notice though is that it is actually the ASIO-signal that starts stuttering. Stuff played through MIDI on my Scope plugins simply keeps on running, but the system simply won't respond anymore to mouse or keyboard events. Sonar 7 also seems to have much more of an issue than Cubase SX3., although also that one tends to freeze up occasionally.

I have no IRQ conflicts anywhere, so I am really at a loss about why this is happening. I am actually thinking about re-installing my old Terratec until the new drivers come out.

Post by **garyb** » Mon Jan 28, 2008 2:20 pm

IT'S NOT A DRIVER PROBLEM!

i'm not against a driver update by any means, but as several members here can tell you, scope works PERFECTLY with the latest chipsets and processors(intel anyway, there were real problems with nforce4, but scope wasn't the only high end card to suffer from those problems, and from what i've heard, later bios versions work just fine).

properly set up computers work. i've done literally 100's of installs. EVERY one worked.

asio stutters, but that doesn't make the asio driver the cause.

motormind · Post by **motormind** » Tue Jan 29, 2008 12:38 am

garyb wrote:IT'S NOT A DRIVER PROBLEM!

i'm not against a driver update by any means, but as several members here can tell you, scope works PERFECTLY with the latest chipsets and processors(intel anyway, there were real problems with nforce4, but scope wasn't the only high end card to suffer from those problems, and from what i've heard, later bios versions work just fine).

properly set up computers work. i've done literally 100's of installs. EVERY one worked.

Well, I tried it all: installing the latest drivers, updating the bios, disabling unnecessary services. I checked the PC memory and it's all fine. The thing just freezes randomly, end of story. I can forget about trying to finish any track this way, which frustrates me to no end.

Post by **Neil B** » Tue Jan 29, 2008 8:08 am

I can understand Motormind's frustration. It's been exactly the same for me.
I have to say though that mine was an IRQ problem and since then it just runs and runs and runs as sweet as anything.
Don't think I'll ever trust it all 100% though and I save more often than perhaps I need to.

Hope you get it sorted.

Post by **garyb** » Tue Jan 29, 2008 1:04 pm

i very much understand the frustration as well. still, the computer should be stable, the issue is not the drivers. i've seen too many stable machines running scope...

disabling services is NOT a good place to start, imho, nor is it necessary for stable operation. at best it will squeeze that last drop of performance out of the system. disabling services can lead to problems, so you only want to do that with a stable system.

try removing half the ram, does it become stable? without the 3GB switch, xp is not addressing 4GB of ram. perhaps a memory issue is the source of the freeze...

motormind · Post by **motormind** » Wed Jan 30, 2008 9:17 am

garyb wrote:i very much understand the frustration as well. still, the computer should be stable, the issue is not the drivers. i've seen too many stable machines running scope...

disabling services is NOT a good place to start, imho, nor is it necessary for stable operation. at best it will squeeze that last drop of performance out of the system. disabling services can lead to problems, so you only want to do that with a stable system.

try removing half the ram, does it become stable? without the 3GB switch, xp is not addressing 4GB of ram. perhaps a memory issue is the source of the freeze...

XP can address up to 3.5 Gb of RAM, depending on the application. Anyway, there seems to be a rule in my life: as soon as I complain about something on a forum, the solution is near. I updated the BIOS and disabled all AMD features, such as Live! and virtualization. I also managed to disable High Definition Audio on my main board which somehow didn't work before. And guess what.. the system seems to be more stable now. I'll keep you guys posted about how long it lasts...

motormind · Post by **motormind** » Wed Jan 30, 2008 11:51 am

Well, it looks like I cheered too soon. After almost a whole day of working fine, my PC started freezing again... 4 times in one hour, no less.

So, is anyone interested in one of them Scope cards? They work fine, as long as you don't expect to get any work done.

Fluxpod · Post by **Fluxpod** » Wed Jan 30, 2008 11:54 am

You did the /3gb switch in the .ini ?
More info plz:) I seriously doubt its a scope driver problem somehow.

motormind · Post by **motormind** » Thu Jan 31, 2008 1:52 am

Fluxpod wrote:You did the /3gb switch in the .ini ?
More info plz:) I seriously doubt its a scope driver problem somehow.

Yeah, I use the /3Gb switch. I turned it off for a while to see what results I would get, but I still get random freezes, so I don't think it has anything to do with that setting.

I performed another Memtest and some CPU/Memory stress tests, which all came out fine. I'm totally at a loss here.

Post by **garyb** » Thu Jan 31, 2008 2:36 am

active sensing?

Jah Servant · Post by **Jah Servant** » Thu Jan 31, 2008 2:52 am

try installing older driver versions for your video card

motormind · Post by **motormind** » Thu Jan 31, 2008 3:40 am

garyb wrote:active sensing?

My Radium Midiman indeed sends out Active Sensing signals. I do notice though that both Cubase and Sonar filter out the Active Sensing signals before rerouting them to the Scope plugins... but perhaps I can still try to filter them out. Is it sufficient if I do that with Scope's MIDI filter?

Post by **garyb** » Thu Jan 31, 2008 9:58 am

yes. both Sonar and Cubase will certainly freeze if you have a controller sending active sensing and it's not filtered. the problem is overflowing midi buffers which wreck the timing of events which makes the computer freeze. it is a known weakness of the scope midi i/o. scope's midi filter cures this 99.999999 times out of 100(filtering before the midi input or turning active sensing off on the controller are better solutions), the last small percentage of controllers that just insist on polling the computer with sooo much active sensing data that the midi filter doesn't 100% cure the problem are best used with a different midi interface and then all's happy, but i doubt you'll need to go there..

the last change you made was important, but this is likely the root of your troubles. i hope it's fixed by just adding the midi filter, my guess is, yes. then hopefully you can find some enjoyment from the card....

motormind · Post by **motormind** » Thu Jan 31, 2008 10:14 am

garyb wrote:yes. both Sonar and Cubase will certainly freeze if you have a controller sending active sensing and it's not filtered. the problem is overflowing midi buffers which wreck the timing of events which makes the computer freeze. it is a known weakness of the scope midi i/o.

Sooo.. in the end I was right when I said it was probably a Scope problem. I decided to be on the safe side and installed my good old Edirol UM-1SX USB MIDI interface, which appears to filter all active sensing garbage automatically. All the "talking" to Scope now happens only through my DAW or through MIDI-OX, so it is unlikely any active sensing messages will get through.

I am curious whether this indeed solves the problem. Further bulletins as events warrant.

Fluxpod · Post by **Fluxpod** » Thu Jan 31, 2008 10:37 am

Hey Motormind, i guess you found the problem i use the scope system in my second pc as a synth/efx host only via adat+spdif and connect midi thru a rme multiface and route it thru a midisport 2x2 into the scope daw.I tried it once to plug the midikeyboard/synth(jp 8000) i use into the scope midi in directly and it gave me bluescreens and all the horrible things you described!
I really hope you can start ..well making music now.

motormind · Post by **motormind** » Thu Jan 31, 2008 11:07 am

Fluxpod wrote:Hey Motormind, i guess you found the problem i use the scope system in my second pc as a synth/efx host only via adat+spdif and connect midi thru a rme multiface and route it thru a midisport 2x2 into the scope daw.I tried it once to plug the midikeyboard/synth(jp 8000) i use into the scope midi in directly and it gave me bluescreens and all the horrible things you described!
I really hope you can start ..well making music now.

Well, sorry to burst your bubble, but... it didn't work. Cubase still froze up my PC like before... and I didn't even have my keyboard switched on!

And about making music... well, the jury is still out there whether my stuff can be described as such

But as for my Scope card, I really don't know anymore. I guess I'll be practicing playing bass and Stick until the new version of Scope comes out. I need to practice more anyway.