scope hangs.
You've tried fresh install of XP (ie format drive and new install)? It happens when scope is the only app loaded (nothing else, no sequencer, no midi)? I just find it unlikely the motherboard could be the problem unless there is an actual manufacturing fault. I guess I would try a clean windows install with just scope installed, nothing else (USB disabled, no NIC,etc etc) and see if it still happens.
Stuart.
brown stuff
tom ,thats it.brown stuff on one of the tubes!
i suppose this is fatal?
i suppose this is fatal?
the single item is relatively 'easy' to repair, but ...
if you've never done it before (or are unfamiliar with a soldering iron),
it's most likely not the only wornout cap,
you don't have replacement parts laying around in the closet
these things are rather expensive in single quantities ($2-4)
there's significant risk to damage the board
... so it's not exactly worth the effort
these parts really do age - and if the 5 years included some periods of heavy use, there's nothing wrong with this.
The most evil part of the symptoms is their precise faking of typical software and configuration errors...
they have tons of mobos on ebay that don't fit the current gamer anymore - or you could get a brand new one, preferably a CoreDuo version in case you have a significant amount of native processing beneath Scope. Otherwise you can spare that (or take one of the entry CPUs)
cheers, Tom
if you've never done it before (or are unfamiliar with a soldering iron),
it's most likely not the only wornout cap,
you don't have replacement parts laying around in the closet
these things are rather expensive in single quantities ($2-4)
there's significant risk to damage the board
... so it's not exactly worth the effort
these parts really do age - and if the 5 years included some periods of heavy use, there's nothing wrong with this.
The most evil part of the symptoms is their precise faking of typical software and configuration errors...
they have tons of mobos on ebay that don't fit the current gamer anymore - or you could get a brand new one, preferably a CoreDuo version in case you have a significant amount of native processing beneath Scope. Otherwise you can spare that (or take one of the entry CPUs)
cheers, Tom
new computer
i think a core 2 duo e6600
would you recommend asus p5b ,its more available in these parts?
would you recommend asus p5b ,its more available in these parts?
Hang on, the computer runs fine until you work with scope right? So that little cap must have a grudge against Creamware! 
Are you sure it's not just glue? Sometimes you'll see blobs of glue to help keep components stable against the board so they don't move about. Or maybe the cap is indeed faulty. Does it look like the capacitor (tube) has leaked. Can you tell us what is written on the tube so we can ascertain that you are indeed looking at a capacitor?
Wouldn't you expect to see symptons no matter what you are using on the computer not just scope?
Are you sure it's not just glue? Sometimes you'll see blobs of glue to help keep components stable against the board so they don't move about. Or maybe the cap is indeed faulty. Does it look like the capacitor (tube) has leaked. Can you tell us what is written on the tube so we can ascertain that you are indeed looking at a capacitor? Wouldn't you expect to see symptons no matter what you are using on the computer not just scope?
Stuart.
all black tubes on that board are capacitors, so they are impossible to be messed 
you're correct that some dusty, heated glue might look similiar - the brown electrolyte sauce is more like dried Cola visually.
These caps buffer and smooth the supply lines of integrated circuits, and in particular Ram. The result is more or less just a bit changing it's value erroneously now and then.
I've had it on an I815 board and was absolutely convinced that my Ram was broken, so strange (yet convincing) were the symptoms.
I moved thePulsars to a different system and only remembered the board when the story about MSI using wrong caps for a complete series of boards was published.
Wasn't that an MSI box ? So I picked it from the attic - and right : 2 bulky caps, pretty small ones btw. Ripped the parts from another board and in fact - it could be revitalized. It was pure curiosity and nothing to loose anyway.
Since I made it work again it's used to browse the internet occasionally - and it still does produce graphic errors (a few bits aren't refreshed, a short screen flicker, it sometimes needs a 2nd boot attempt etc).
For browsing the net it doesn't matter, but I wouldn't prepare a tax balance on it
Scope always loads more or less into the same memory region (because it loads under the same circumstances) and so it looks as if only Scope has a problem.
I must admit that my Pulsar box has been tortured really badly
it was a tiny office thing about the size of a vinyl cover and 2 rack units high with 2 Pulsar Ones on a riser card (on one of them a cap had to be transplanted to the backside, as it would stick into the CPU fan otherwise...)
3 fans running on 5V provided some airflow - temperature was 50/75 Celsius
It even survived (running idle) 1-2 hours without CPU fan, when I forgot to reconnect that.
It was rather (but not perfectly) quiet and more of a technical challenge than a real system - but it was very reliable (I hardly switched it off) until the fried caps seeked attention.
cheers, Tom
you're correct that some dusty, heated glue might look similiar - the brown electrolyte sauce is more like dried Cola visually.
These caps buffer and smooth the supply lines of integrated circuits, and in particular Ram. The result is more or less just a bit changing it's value erroneously now and then.
I've had it on an I815 board and was absolutely convinced that my Ram was broken, so strange (yet convincing) were the symptoms.
I moved thePulsars to a different system and only remembered the board when the story about MSI using wrong caps for a complete series of boards was published.
Wasn't that an MSI box ? So I picked it from the attic - and right : 2 bulky caps, pretty small ones btw. Ripped the parts from another board and in fact - it could be revitalized. It was pure curiosity and nothing to loose anyway.
Since I made it work again it's used to browse the internet occasionally - and it still does produce graphic errors (a few bits aren't refreshed, a short screen flicker, it sometimes needs a 2nd boot attempt etc).
For browsing the net it doesn't matter, but I wouldn't prepare a tax balance on it
Scope always loads more or less into the same memory region (because it loads under the same circumstances) and so it looks as if only Scope has a problem.
I must admit that my Pulsar box has been tortured really badly
it was a tiny office thing about the size of a vinyl cover and 2 rack units high with 2 Pulsar Ones on a riser card (on one of them a cap had to be transplanted to the backside, as it would stick into the CPU fan otherwise...)
3 fans running on 5V provided some airflow - temperature was 50/75 Celsius
It even survived (running idle) 1-2 hours without CPU fan, when I forgot to reconnect that.
It was rather (but not perfectly) quiet and more of a technical challenge than a real system - but it was very reliable (I hardly switched it off) until the fried caps seeked attention.
cheers, Tom
Well I hope you are right for Karls sake. In that case to me it seems more likely that the supply is affecting the scope card producing spurious results when the scope card draws power to do calculations. The scope cards may be less forgiving of an unclean supply? I'm just trying to understand why it only happens when Karl does stuff in the scope environment.
Karl does the audio freeze as well or is it just the video?
Karl does the audio freeze as well or is it just the video?
Stuart.
black tubes
one black tube looks like an old aa battery leaking,others look like they are close to leaking.
when it hangs,audio continues,and needs to be stopped in cubase.if i was to wait, cpu returns to 15%,but everything is even less stable.
i have given up all hope with this mobo.
you guys could make a lot of money in ireland! i had a big problem finding DP965LT,Intel Core 2 Duo E6600 / 2.4 ,combination,plus case,psu etc.i dont want to assemble every thing,so one company wanted 500 euros for a technician for a day.
new computer ordered:
Processor - 1 x Intel Core 2 Duo E6600 / 2.4 GHz ( 1066 MHz ) - LGA775 Socket - L2 4 MB - Box
Intel Desktop Board DP965LT - Motherboard - ATX - iP965 - LGA775 Socket - UDMA133, Serial ATA-300 - Gigabit Ethernet - FireWire - High Definition Audio (6-channel)
Kingston ValueRAM - Memory - 512 MB - DIMM 240-pin - DDR II - 800 MHz / PC2-6400 - CL5 - 1.8 V - unbuffered - non-ECC
2 gig corsair on order
Seagate Barracuda 7200.10 - Hard drive - 250 GB - internal - 3.5" - SATA-300 - 7200 rpm - buffer: 8 MB
Antec SmartPower 2.0 SP-400PGB - Power supply ( internal ) - ATX12V 2.0 - AC 115/230 V - 400 Watt
Antec Solution SLK3000B - Mid tower - ATX - black
ASUS EN6200LE TC256/TD - Graphics adapter - GF 6200LE TC supporting 256MB - PCI Express x16 - 64 MB DDR - Digital Visual Interface (DVI) - TV out
Sony AW-G170A - Disk drive - DVD±RW (±R DL) / DVD-RAM - 18x/18x/12x - IDE - internal - 5.25" - black
do you think its ok, they only charge 60 euros to assemble
when it hangs,audio continues,and needs to be stopped in cubase.if i was to wait, cpu returns to 15%,but everything is even less stable.
i have given up all hope with this mobo.
you guys could make a lot of money in ireland! i had a big problem finding DP965LT,Intel Core 2 Duo E6600 / 2.4 ,combination,plus case,psu etc.i dont want to assemble every thing,so one company wanted 500 euros for a technician for a day.
new computer ordered:
Processor - 1 x Intel Core 2 Duo E6600 / 2.4 GHz ( 1066 MHz ) - LGA775 Socket - L2 4 MB - Box
Intel Desktop Board DP965LT - Motherboard - ATX - iP965 - LGA775 Socket - UDMA133, Serial ATA-300 - Gigabit Ethernet - FireWire - High Definition Audio (6-channel)
Kingston ValueRAM - Memory - 512 MB - DIMM 240-pin - DDR II - 800 MHz / PC2-6400 - CL5 - 1.8 V - unbuffered - non-ECC
2 gig corsair on order
Seagate Barracuda 7200.10 - Hard drive - 250 GB - internal - 3.5" - SATA-300 - 7200 rpm - buffer: 8 MB
Antec SmartPower 2.0 SP-400PGB - Power supply ( internal ) - ATX12V 2.0 - AC 115/230 V - 400 Watt
Antec Solution SLK3000B - Mid tower - ATX - black
ASUS EN6200LE TC256/TD - Graphics adapter - GF 6200LE TC supporting 256MB - PCI Express x16 - 64 MB DDR - Digital Visual Interface (DVI) - TV out
Sony AW-G170A - Disk drive - DVD±RW (±R DL) / DVD-RAM - 18x/18x/12x - IDE - internal - 5.25" - black
do you think its ok, they only charge 60 euros to assemble
I have seen this effect a few times. It used to happen to me reasonably often. I moved to a new computer and sometimes saw the same thing again. But it was very rare so I gave up trying to solve it. Now, it never happens - no idea why. (Both machines used Asus mobos though).
That's no help, but at least you're not alone. I suspect its some older driver somewhere which I've since updated and which has now eliminated the problem....
That's no help, but at least you're not alone. I suspect its some older driver somewhere which I've since updated and which has now eliminated the problem....
new computer
new computer is great,much more stable,no hanging, 512 ram but 2 gigs more next week will be better.
moving windows rapidly, still causes huge cpu spikes on both cpus,though its not so critical now,is this normal?
also,scope is sharing irq 21 with usb controller and smbus contoller.how do i give scope its own irq?i saw nothin in bios
moving windows rapidly, still causes huge cpu spikes on both cpus,though its not so critical now,is this normal?
also,scope is sharing irq 21 with usb controller and smbus contoller.how do i give scope its own irq?i saw nothin in bios
i'd move the card to get off of the smbus controller's irq. the smbus won't really make any problems, though, the usb controller will. to get rid of the usb controller(after you move the card you'll still be sharing an irq with a usb controller), look at the usb controller's name, i.e. 2DEY7 or similar. open the device manager, find the usb controller with that name and then disable it(highlight and then choose disable at the top of the window OR right click and choose "disable"). recheck for irq sharing. it should be gone(after closing and then reopening system information).
mobo cables
tried to change to different slot but scope pro card is too big,too many plugs on mobo,sata cable etc,to be honest im lucky it fits any slot.
i disabled usb controller,so now just sharing with smbus.
on the positive side,it seems to be working smoothly.time will tell.
i disabled usb controller,so now just sharing with smbus.
on the positive side,it seems to be working smoothly.time will tell.
thanks for all your help
new cosair ram arrived.everything seems fine.
thanks for all your help
maybe i should post this elsewhere, but i have this problem.
when i load sts 5000 i get error message: cant find dsp file recording vxb.
when i load minimax it says unexpected dsp overload
i tried a reinstall.
thanks for all your help
maybe i should post this elsewhere, but i have this problem.
when i load sts 5000 i get error message: cant find dsp file recording vxb.
when i load minimax it says unexpected dsp overload
i tried a reinstall.
-
Zero Creative Music
- Posts: 24
- Joined: Tue Nov 07, 2006 4:36 am
- Location: Netherlands
- Contact:
sts is fine now
sts is fine now ,replaced Trec.vxd file in vxd folder,no problems.
i found midi configurations are treacherous with sts.that might be your problem.best of luck.
karl
i found midi configurations are treacherous with sts.that might be your problem.best of luck.
karl
good point, Karl
given the fact there is a 'midi leak' (invisible) somewhere within the device, it would have the full potential to crash Windows out of the blue
I have no proof for this, but just can't help the strange feeling there is something like that in SFP (or within certain devices) that acts like a midi loop (by overflowing or falsely allocated buffers).
As I'm lazy I usually feed sequences from a DX200 which is generally fine, but from time to time there are those infamous hanging notes. Under Win98 it's easy to recover, but under W2K or XP I'd probably have crashes, too.
cheers, Tom
given the fact there is a 'midi leak' (invisible) somewhere within the device, it would have the full potential to crash Windows out of the blue
I have no proof for this, but just can't help the strange feeling there is something like that in SFP (or within certain devices) that acts like a midi loop (by overflowing or falsely allocated buffers).
As I'm lazy I usually feed sequences from a DX200 which is generally fine, but from time to time there are those infamous hanging notes. Under Win98 it's easy to recover, but under W2K or XP I'd probably have crashes, too.
cheers, Tom