Overloading CPU That Once Was Fine...

[Brian Storm]

I have a digi002 rack on XP Pro... Intel mboard D865PERL... 2GB RAM... c: and Daudio) SATA... 3.2 P4...

Everything was fine... then one day I decided to put a 3rd SATA drive in...

I immediately lost performance on my CPU... strangely... after a reboot it works fine... and for songs without many pluggins its fine... but some songs, which previously were fine, spiraled the CPU to crashing point... all subsequent playbacks made the CPU go way high until next reboot...

I took the 3rd SATA back out and ghosted back to before this but the problem has remained ever since...

I should also mention that I have reinstalled the motherboard CD... reinstalled to Protools 7.3.1 ... re-installed all of my Waves pluggins (since it seems to be the L3 which trips the CPU overloads)... the next step I guess is reinstall windows but I'm not convinced that this amount of work will work - yet...

It's interesting that after I reboot a toublesome song plays fine sitting at 30% CPU until about 2-3 mminutes in when I see the CPU go up to 97%... after this has happened I lose all performance even on small songs that never give a problem all day (as long as they were the only ones I opened)... after the CPU has "tripped" like this I can close the song - open it up again and just leave it without any keyboard or playback... the CPU will start climbing up to 97% all on it's own... if I do this on a troublesome song after a reboot though the CPU just sits at 30% - it's fine...

[Gez]

Hello,

You do not mention if you're recording onto this 3rd external hard drive. I think it is generally discouraged to record onto an external hard drive. I prefer to store old sessions or backup sessions onto my external Seagate drive. For recording I try and keep my secondary internal drive fairly empty and record onto this.
cheers and beers, hope that helps a little
Gez

[sunburst79]

Posting a Sisoft Sandra Report would be helpful.

You shouldn't have the problems your having just from installling a drive.

The fact that its doing it after you ghosted it back would kind of tend to indicate that its perhaps a BIOS or system configuration problem.

[DarylBham]

thats all i particularly record too is my external drives, I never use my internal drive, considering i primarily used a laptop