*Here's a repost of something I asked about on *PCDAW, and got a couple of replies to. I have *since checked (again) DMA and some other things, *and all the settings seem to be fine:
I keep having freezes and playback problems in Windows 2000 with Nuendo and Wavelab, and when I look back at the event viewer after this type of problem, there are always a string of disk and atapi errors, applying to both hard disk controllers, and both of my audio hard disks. I also get a BSOD stop error every day or two, and the errors upon rebooting are the same types.
Any ideas? Is my mobo hosed? This happens with several different drives (I do audio with removable IDE drives), so I don't think it's them specifically. I recently did a wipe and reinstall, and I went from 10G partitions to full 80G (on my 80g drives) or two 60G (on my 120's). That's really the only difference, and the thing was stable before.
*and a couple days later, after a few answers, I *posted:
Any more input? This problem is beyond my scope of knowledge, and I'm on
the verge of buying another motherboard out of sheer frustration (plus, it's
ATA100, not 133, and it doesn't drive keyboard/mouse extensions really well.
And it only *mostly* plays nice with my Hammerfall, a known issue).
So, any ideas? I'm pretty frustrated, because I've just about exhausted all the things *I* know to do.
Thanks.
Comments
we had this problem once with removeable drive bays and found th
we had this problem once with removeable drive bays and found that we had to resolder the ide connector in the tray part of the caddy as there were quite a few dry joints.The other possibility concerns cd rom drives connected to the ide bus that are configured for bus mastering this is a known issue with nero software and is explained on their site.This problem only affects 2000 and xp . I hope this might throw a bit of light on your problem.
Wow, can you tell us what brand of removable IDE trays you got t
Wow, can you tell us what brand of removable IDE trays you got that needed that? This way we could put that in our mental archives not to get those!
I guess the question here is if he's running Nero or not.
I've been running Wavelab since at least the 2.x days and never came across any issues running in DMA mode. So I'm a bit skeptical about Wavelab being the cause here!
Opus :D
The problem with the drive trays is essentially common to all of
The problem with the drive trays is essentially common to all of them .The area of concern is the pcb that has the 40 wire idc cable that plugs into the drive.It is always worth checking to see that there are no dry joints where the ribbon meets the printed circuit board.I also recommend Pro Gold from caig labs as a contact enhancer ,this is also excellent for ram modules and pci card contacts
Funny, all the IDE trays I use are always fine. I've put them th
Funny, all the IDE trays I use are always fine. I've put them through abuse and beyond as well.
Please let us know the brand name trays you are using as it would be good to stay away from them.
Personally I wouldn't recommend telling everyone to start spraying their boards out of safety sake but if that's your thang, that's ok.
As an electronic technician myself I can't say that I have ever had to spray for contact continuity on a pc?!!
Opus :D
Just an update- one of my drives (a 120G Maxtor DiamondMax Plus
Just an update- one of my drives (a 120G Maxtor DiamondMax Plus 9) appears to have died, in a very slow and interesting way that made the entire IDE system return lots of different errors, relating to all four drives on both IDE ports. Dumped everything over (after two hours of thinking I'd lost everything- finally got the drive to recognize one last time...), put in a new one, and everything seems to be good.
It was kind of interesting, though- apparently the NTFS error correction is pretty robust, because it had to have been working overtime- it took over two hours to copy 70G or so of information between the two drives, and everything made it intact! This after the Maxtor utility just up and failed the drive completely.
Well, what happens if you leave your system on and don't do anyt
Well, what happens if you leave your system on and don't do anything. Does it give you the BSOD still?
What CPU are you using? Did you overclock it at all?
What memory and how much of it do you have? What motherboard as well.
It could be the CPU failing but not sure until I know some exact answers.
Exactly what BSOD message do you get? That will truly tell me what's going on.
Opus :D