[Darryl Ramm]

How about starting at "Help us help you" up the top of each DUC web page, and post a SiSoft Sandra report for your computer. Standard optimization and troubleshooting steps are there. You probably should have looked at troubleshooting on your old system.

You should be doing basic troubleshooting including excluding (temporarily removing the .aaxplugin files from the plugin folder) all third party plugins when you suspect CPU issue. And putting .aaxplugin files back in batches trying to triangulate on the bad plugin(s). With CPUY problems *always* assume plugins are likely to be the the problem and exclude them early on. You could have done that on the old system before upgrading. Do those old plugins even claim to be compatible with Pro Tools 10 on Windows 7?

What sample rate, what IO buffer size are you running at?

Corrupt sessions can also cause run away CPU use... what happens when you start with an new totally empty session? (not a template or copy of another session). And plugin denormalization issues can also cause run away CPU use, including with the transport stopped. Back in the day DVERB and Sansamp were notorious for that, but many suffered from it. You can search for demoralization on DUC for an explanation. But you can fish for problem plugins by looking for plugins that are getting a very low/no signal level, try removing suspect plugins from the inserts, and/or sticking a dither plugin in front of the suspect plugin.

There are CPU priority and affinity settings folks are worrying about with recent Pro Tools on Windows 10 but your issues are likely to be more fundamental plugin problems.