Screen Freeze - Plug-ins periodically become 'corrupted'

[dave911]

The DPC looks good.
Outside of reinstalling PT you could run a disk check and defragmentation on your drives.
Don't run the defrag. with PT running!
Scheduled defrag should be turned off for a PT system.
Also, running "sfc/scannow" at a admin. DOS prompt will check for bad system files

[Drywsef]

Thanks, Dave911. I'll give it a shot and report back tomorrow. Another update for now: I tried performing a full uninstall and reinstallation of 10.3.7 and the same problem persists today.

[Drywsef]

I tried defragmenting the drives and running that command. I have attached the result. The problem still persists; however, the last few times PT froze/crashed, the DYN III plug-in was inactive. I can no longer attribute this to the DYN III plug in. With no plug-ins activated, the issue will not occur. However, if I only activate my 3 VIs, (Battery, Absynth, and Kontakt), the freeze will come on. I really ask for it when I try to save. That usually brings the freeze/crash on. Memory related, perhaps??
About ready to pull out my hair.

[guitardom]

Check your task manager when your running and see where your system ram is during the session. For best results to check this, temporarily turn off disk cache to check. If your hitting around 3.5gb of memory usage, your in trouble territory.

[Drywsef]

Originally Posted by guitardom

Check your task manager when your running and see where your system ram is during the session. For best results to check this, temporarily turn off disk cache to check. If your hitting around 3.5gb of memory usage, your in trouble territory.

Thanks for this. Am I looking to see how much RAM the entire system is using, or just Pro Tools?

[Darryl Ramm]

Originally Posted by Drywsef

Thanks for this. Am I looking to see how much RAM the entire system is using, or just Pro Tools?

Pro Tools.

[guitardom]

Originally Posted by Drywsef

Thanks for this. Am I looking to see how much RAM the entire system is using, or just Pro Tools?

This will give the system total, but the app total is also viewable in here. With only PT running, it would be maxing out around here somewhere. I am guessing this could be the issue. To bad you did not have PT 11 to verify.

[Drywsef]

Originally Posted by guitardom

This will give the system total, but the app total is also viewable in here. With only PT running, it would be maxing out around here somewhere. I am guessing this could be the issue. To bad you did not have PT 11 to verify.

I do have PT11 to verify. What exactly am I verifying? To see if PT11 uses more RAM with the same session?

[Darryl Ramm]

Originally Posted by Drywsef

I do have PT11 to verify. What exactly am I verifying? To see if PT11 uses more RAM with the same session?

You would be confirming that Pro Tools 11 does not suffer from the problem you are seeing. The suspicion here is you are hitting a 32 bit related limit in Pro Tools 10, Pro Tools 11 being 64 bit does not have that limitation.

Darryl

[dave911]

Also, have you reinstalled the MOTU drivers?

Besides running out of memory in PT as others suggested you may have a memory leak. So you want to watch the memory usage from boot up and see if it is high before you start PT.