need to reinstall scope if change cpu?

[SonicTransportSystem]

Hi,
I decided to change my cpu from 2.4g to 3.2g. But then when i work with scope and cubase sx3 the pc crashes and need to rebbot pressing the button on the pc. Do you think that maybe need to reinstall scope and cubase cause of the new cpu?

If someone have some idea please help me!

Thanks a lot

Pedro

ww.myspace.com/sonictransportsystem

[valis]

No you don't need to reinstall the applications for a new cpu.

Is the RAM ok with the current cpu speed/multiplier?
CPU, System temperatures & PSU voltages ok?
Do you have a hardware keyboard/controller attached to the midi input of the Scope card ( = possible active sensing conflict )

[SonicTransportSystem]

No you don't need to reinstall the applications for a new cpu.

Is the RAM ok with the current cpu speed/multiplier?
CPU, System temperatures & PSU voltages ok?
Do you have a hardware keyboard/controller attached to the midi input of the Scope card ( = possible active sensing conflict )

I have made all the tests on the computer shop and everything was ok! Im getting crazy with this problem! And what about the active sensing conflict? If its that who i fix it? I already update the firmware for the mainboard

[valis]

http://www.techpowerup.com/downloads/13 ... ckage.html
Download the trial (that's an official mirror) and check your machine if you're unsure.

Also check & see if you've got an IRQ conflict.

And exactly what cpu did you install (Everest can help answer that too).

As for the 'active sensing', do you have a keyboard attached to the computer?

Troubleshooting is about eliminating obvious possibilities before moving to obscure ones, and if you require assistance we need to have information that's a bit less frantic

[SonicTransportSystem]

http://www.techpowerup.com/downloads/13 ... ckage.html
Download the trial (that's an official mirror) and check your machine if you're unsure.

Also check & see if you've got an IRQ conflict.

And exactly what cpu did you install (Everest can help answer that too).

As for the 'active sensing', do you have a keyboard attached to the computer?

Troubleshooting is about eliminating obvious possibilities before moving to obscure ones, and if you require assistance we need to have information that's a bit less frantic

Well, the new cpu its a pentium 4 with 3.2 ghz, xp home, i have a midi keyboard attached to my scope home card but i must say that the computer crashes without play the midi keyboard, just listen to some of my projects and then the computer just frezes! Im going to make the test you send me the link, and then i say something....how i check if i have an irq conflict?

Thanks a lot

[SonicTransportSystem]

http://www.techpowerup.com/downloads/13 ... ckage.html
Download the trial (that's an official mirror) and check your machine if you're unsure.

Also check & see if you've got an IRQ conflict.

And exactly what cpu did you install (Everest can help answer that too).

As for the 'active sensing', do you have a keyboard attached to the computer?

Troubleshooting is about eliminating obvious possibilities before moving to obscure ones, and if you require assistance we need to have information that's a bit less frantic

I already made a test a send it to Everest, i hope they understand cause i install it on portuguese language

[valis]

You don't need to send it to them, just look under Computer > Sensor and check your temps, voltages etc when you have Scope running (in case its power draw is at issue).

What kind of keyboard do you have attached to the Scope midi input?

[SonicTransportSystem]

You don't need to send it to them, just look under Computer > Sensor and check your temps, voltages etc when you have Scope running (in case its power draw is at issue).

What kind of keyboard do you have attached to the Scope midi input?

Its an Yamaha cs2x....a friend of mine told me to change the scope slot... can be cause of irqs. I already change and things are really strange...the asio test said that is not ok...im going to reisntall again the scope software and see whats happen

cheers

[valis]

Yamaha cs2x does indeed send active sensing messages, which are known to cause problems with Intel P4 cpu's with hyperthreading enabled. Before you try anything further, disconnnect (or power off) the cs2x and try working for a bit. I'm willing to bet this is the problem.

If that does indeed turn out to be the fix for you, your options are either to filter out the active sensing messages (an external filter is ideal, filtering in scope works "ok" but not always) or to get a usb midi interface instead.

[garyb]

the midi filter in Scope will probably fix it. it's in the midi menu in the Scope routing window. as Valis said, an external filter is better, but the Scope filter should work.

also, go to start/programs/accessories/system tools/sytem information/hardware resources/conflicts-sharing and tell me what, if anything, is shariung an irq with your card.

[SonicTransportSystem]

Yamaha cs2x does indeed send active sensing messages, which are known to cause problems with Intel P4 cpu's with hyperthreading enabled. Before you try anything further, disconnnect (or power off) the cs2x and try working for a bit. I'm willing to bet this is the problem.

If that does indeed turn out to be the fix for you, your options are either to filter out the active sensing messages (an external filter is ideal, filtering in scope works "ok" but not always) or to get a usb midi interface instead.

I change the soundcard slot to try if it was cause of irqs and it seems its ok...but im going to still trying if something happens i say something....about the cs2x i use it has midi controler since a lot of time and he always worked ok

Thanks a lot for your help

cheers

pedro

[valis]

The c2sx is sending active sensing messages, these have been known to cause Scope to 'freeze' the host computer when used with a Pentium-4 era cpu that has hyperthreading enabled (which is what your new cpu appears to be).

[SonicTransportSystem]

the midi filter in Scope will probably fix it. it's in the midi menu in the Scope routing window. as Valis said, an external filter is better, but the Scope filter should work.

also, go to start/programs/accessories/system tools/sytem information/hardware resources/conflicts-sharing and tell me what, if anything, is shariung an irq with your card.

Realtek RTL8139 Family PCI Fast Ethernet NIC is sharing IRQ 22 with my soundcard...but i think this is the mainboard soundcard and was disabled at the Bios.

[SonicTransportSystem]

The c2sx is sending active sensing messages, these have been known to cause Scope to 'freeze' the host computer when used with a Pentium-4 era cpu that has hyperthreading enabled (which is what your new cpu appears to be).

but my old cpu was a Pentium 4 too and never happens this kind of things....the diference is just more 800 mhz

[valis]

Realtek RTL8139 Family PCI Fast Ethernet NIC is sharing IRQ 22 with my soundcard...but i think this is the mainboard soundcard and was disabled at the Bios.

Onboard networking chip (not a soundcard). You're in ACPI mode so they may or may not be sharing at the hardware level. Before moving the card again though, go into your BIOS again and make sure you have anything unnecessary disabled (parallel, serial, floppy if you don't have one etc). After that (or if you've already done that) find the 'reset ESCD data' option and use it, then save & reboot. That will clear the information stored for IRQ sharing and you may get different sharing on reboot. If that doesn't work you can try moving the card again.

The c2sx is sending active sensing messages, these have been known to cause Scope to 'freeze' the host computer when used with a Pentium-4 era cpu that has hyperthreading enabled (which is what your new cpu appears to be).

but my old cpu was a Pentium 4 too and never happens this kind of things....the diference is just more 800 mhz

It's easy to test. Unplug the keyboard, work in your project for about an hour. If it hasn't crashed, you identified the problem & know the solutions from this thread. If it does crash then it's something else, and you've eliminated a possibility. It's been crashing on you while working anyway it seems like...just remember to save frequently and protect your monitors.

Most importantly, when you test I would test each thing at a time. Or better yet, unplug the keyboard for now and work on the IRQ sharing. When you can successfully run a Scope+Cubase project without crashing, try hooking the keyboard back up and see if the crashing returns.

[SonicTransportSystem]

Realtek RTL8139 Family PCI Fast Ethernet NIC is sharing IRQ 22 with my soundcard...but i think this is the mainboard soundcard and was disabled at the Bios.

Onboard networking chip (not a soundcard). You're in ACPI mode so they may or may not be sharing at the hardware level. Before moving the card again though, go into your BIOS again and make sure you have anything unnecessary disabled (parallel, serial, floppy if you don't have one etc). After that (or if you've already done that) find the 'reset ESCD data' option and use it, then save & reboot. That will clear the information stored for IRQ sharing and you may get different sharing on reboot. If that doesn't work you can try moving the card again.

The c2sx is sending active sensing messages, these have been known to cause Scope to 'freeze' the host computer when used with a Pentium-4 era cpu that has hyperthreading enabled (which is what your new cpu appears to be).

but my old cpu was a Pentium 4 too and never happens this kind of things....the diference is just more 800 mhz

It's easy to test. Unplug the keyboard, work in your project for about an hour. If it hasn't crashed, you identified the problem & know the solutions from this thread. If it does crash then it's something else, and you've eliminated a possibility. It's been crashing on you while working anyway it seems like...just remember to save frequently and protect your monitors.

Most importantly, when you test I would test each thing at a time. Or better yet, unplug the keyboard for now and work on the IRQ sharing. When you can successfully run a Scope+Cubase project without crashing, try hooking the keyboard back up and see if the crashing returns.

you said to go to Bios, but that is something that i dont know how to do, usually is the guy from the computer shop that do that kind of things...about the cs2x...when the problem happens i am never playing it..its rare to use it almost the time i use the pencil and write notes on the piano roll...the cs2x is more to receive midi messages than to send...when the problem starts and always that happen im never playing the cs2x. but im going to try disconnect the cs2x to try if something changes

[SonicTransportSystem]

I found something that can help...when i open Absynth or other vsti in standalone option and i go to preferences to change midi port if im using scope midi the preferences tab needs a lot of time to appear but if i change to my other midi port where i have attached a nord modular appears in 1 second...to see if the problem is about cs2x i connect the nord to scope midi and the something happens so it seems the problem is the scope midi and not cs2x....what you think about that?

[SonicTransportSystem]

I found something that can help...when i open Absynth or other vsti in standalone option and i go to preferences to change midi port if im using scope midi the preferences tab needs a lot of time to appear but if i change to my other midi port where i have attached a nord modular appears in 1 second...to see if the problem is about cs2x i connect the nord to scope midi and the something happens so it seems the problem is the scope midi and not cs2x....what you think about that?

i forget to say something...when i use absynth standalone has i said with scope midi port absynth crashes, note keys freezes it seems doesnt have note of

[SonicTransportSystem]

Realtek RTL8139 Family PCI Fast Ethernet NIC is sharing IRQ 22 with my soundcard...but i think this is the mainboard soundcard and was disabled at the Bios.

Onboard networking chip (not a soundcard). You're in ACPI mode so they may or may not be sharing at the hardware level. Before moving the card again though, go into your BIOS again and make sure you have anything unnecessary disabled (parallel, serial, floppy if you don't have one etc). After that (or if you've already done that) find the 'reset ESCD data' option and use it, then save & reboot. That will clear the information stored for IRQ sharing and you may get different sharing on reboot. If that doesn't work you can try moving the card again.

The c2sx is sending active sensing messages, these have been known to cause Scope to 'freeze' the host computer when used with a Pentium-4 era cpu that has hyperthreading enabled (which is what your new cpu appears to be).

but my old cpu was a Pentium 4 too and never happens this kind of things....the diference is just more 800 mhz

It's easy to test. Unplug the keyboard, work in your project for about an hour. If it hasn't crashed, you identified the problem & know the solutions from this thread. If it does crash then it's something else, and you've eliminated a possibility. It's been crashing on you while working anyway it seems like...just remember to save frequently and protect your monitors.

Most importantly, when you test I would test each thing at a time. Or better yet, unplug the keyboard for now and work on the IRQ sharing. When you can successfully run a Scope+Cubase project without crashing, try hooking the keyboard back up and see if the crashing returns.

I think that when the computer shop guy update the mainboard drive for the new cpu after that when computer reboot the mainboard clear all the information..even i remember that Realtek was unable and i ask him to disabled.

Thanks a lot again for you help

[SonicTransportSystem]

Already filtered active sensing with scope midi filter and some problem happens...just try it with absynth standalone...but i think is all part of the same problem...