PT9HD CPU(Rtas) drops to 0 after about a minute.

[scicom]

I'm hoping someone can shed some light on what's going on. I've tried just about everything and can't seem to solve it.

I'm on PT9HD. When I load a native effect (altiverb) I'll see the meter on CPU bump, to about 9 or 10. Things will work great for about 2 minutes, and then suddenly the cpu will just drop to zero. No peaks or overloads or anything, it just drops to zero. If I change a buss setting or output/input, it pops back in. Same thing if I put a dverb on that buss. Cpu will register 2 or 3, but about two minutes in will drop to zero and I have to do something that engages the cpu (switch heat on/off, or chose any input/output setting)

I've gone through bios settings, gone through the optimization recommendation, made sure there's no start-up processes running, tried every combination of settings, and I even reinstalled the whole shabang, and I'm still getting the drop out.

someone please rescue me from this frustration.


SiSoftware Sandra

ID
Host Name : DESKTOP-4EK8L87
Workgroup : WORKGROUP

Computer
Model : GigaByte X58A-UD3R
Chassis : GigaByte Desktop
Mainboard : GigaByte X58A-UD3R
BIOS : Award (OEM) FB 08/24/2010
Total Memory : 24GB DIMM DDR3

Processors
Processor : Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz (4C 8T 3GHz/3.1GHz, 2.16GHz IMC, 4x 256kB L2, 8MB L3)
Socket/Slot : FC LGA1366

Chipset
Memory Controller : Gigabyte X58 I/O Hub 2x 2.43GHz (4.86GHz)
Memory Controller : Gigabyte Core Desktop (Bloomfield) UnCore 2x 2.43GHz (4.86GHz), 3x 8GB DIMM DDR3 1.08GHz 192-bit

Memory Module(s)
Memory Module : Crucial CT51264BA1339M16F 4GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Crucial CT51264BA1339M16F 4GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Crucial CT51264BA1339M16F 4GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Crucial CT51264BA1339M16F 4GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Crucial CT51264BA1339M16F 4GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-25 4-34-10-5)
Memory Module : Crucial CT51264BA1339M16F 4GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-25 4-34-10-5)

Video System
Monitor/Panel : SEK SE42UM
(3840x2160, 32.0")
Monitor/Panel : Hewlett Packard HP V242h
(1920x1080, 24.0")
Video Adapter : AMD Radeon R9 200 / HD 7900 Series (32CU 2048SP SM5.1 925MHz/1GHz, 16kB L2, 3GB DDR5 5.5GHz 384-bit, PCIe 3.00 x16)
Video Adapter : AMD Radeon R9 200 / HD 7900 Series (32CU 2048SP SM5.1 925MHz/1GHz, 16kB L2, 3GB DDR5 5.5GHz 384-bit, PCIe 3.00 x16)

Graphics Processor
OpenCL GP Processor : AMD Radeon R9 200 / HD 7900 Series (2048SP 32C 925MHz/1GHz, 16kB L2, 3GB DDR5 5.5GHz 384-bit)
Compute Shader Processor : AMD Radeon R9 200 / HD 7900 Series (2048SP 32C 925MHz/1GHz, 16kB L2, 3GB DDR5 5.5GHz 384-bit)
OpenGL Processor : AMD Radeon R9 200 / HD 7900 Series (2048SP 32C 925MHz/1GHz, 16kB L2, 3GB DDR5 5.5GHz 384-bit)
OpenGL Processor : AMD Radeon R9 200 / HD 7900 Series (2048SP 32C 925MHz/1GHz, 16kB L2, 3GB DDR5 5.5GHz 384-bit)

Storage Devices
TOSHIBA DT01ACA300 (3TB, SATA300/600, 3.5", 7200rpm) : 3TB (D:)
Mushkin MKNSSDEC512GB (512.1GB, SATA300/600, SSD) : 477GB (C:)
TOSHIBA DT01ACA300 (3TB, SATA300/600, 3.5", 7200rpm) : 3TB (E:)
SMI Feiya Technology Memory Bar (16.2GB, USB2) : 15GB (G:)
SONY DVD RW DRU-V200A (ATA66, DVD+-RW, CD-RW, 2MB Cache) : N/A (F:)

Logical Storage Devices
Development (D:) : 3TB (NTFS, 4kB) @ TOSHIBA DT01ACA300 (3TB, SATA300/600, 3.5", 7200rpm)
System Reserved : 350MB (NTFS, 4kB) @ Mushkin MKNSSDEC512GB (512.1GB, SATA300/600, SSD)
Libraries (E:) : 3TB (NTFS, 4kB) @ TOSHIBA DT01ACA300 (3TB, SATA300/600, 3.5", 7200rpm)
ESD-USB (G:) : 15GB (FAT32, 8kB) @ SMI Feiya Technology Memory Bar (16.2GB, USB2)
Hard Disk (C:) : 476GB (NTFS, 4kB) @ Mushkin MKNSSDEC512GB (512.1GB, SATA300/600, SSD)
Hard Disk : 450MB (NTFS, 4kB) @ Mushkin MKNSSDEC512GB (512.1GB, SATA300/600, SSD)
Optical Drive (F:) : N/A @ SONY DVD RW DRU-V200A (ATA66, DVD+-RW, CD-RW, 2MB Cache)

Peripherals
LPC Hub Controller 1 : Gigabyte LPC Interface Controller
LPC Legacy Controller 1 : ITE IT8720F
Audio Device : ATI (AMD) Tahiti XT HDMI Audio [Radeon HD 7970 Series]
Audio Codec : ATI (AMD) HDMI Audio
Audio Device : AVID Tech 56361 Audio I/O Controller (MIDI)
Disk Controller : Gigabyte 4 port SATA IDE Controller
Disk Controller : Gigabyte 2 port SATA IDE Controller
Disk Controller : Gigabyte 88SE91A3 SATA-600 Controller
Disk Controller : Gigabyte JMB36X PCIE-to-SATAII/IDE RAID Controller
Disk Controller : Gigabyte JMB36X PCIE-to-SATAII/IDE RAID Controller
USB Controller 1 : Gigabyte USB UHCI Controller #4
USB Controller 2 : Gigabyte USB UHCI Controller #5
USB Controller 3 : Gigabyte USB UHCI Controller #6
USB Controller 4 : Gigabyte USB EHCI Controller #2
USB Controller 5 : Gigabyte USB UHCI Controller #1
USB Controller 6 : Gigabyte USB UHCI Controller #2
USB Controller 7 : Gigabyte USB UHCI Controller #3
USB Controller 8 : Gigabyte USB EHCI Controller #1
FireWire/1394 Controller 1 : Gigabyte TSB43AB23 1394a-2000 OHCI PHY/link-layer Controller
SMBus/i2c Controller 1 : Intel ICH SMBus

Printers and Faxes
Printer : Microsoft XPS Document Writer v4 (600x600, Colour)
Printer : Microsoft Print To PDF (600x600, Colour)
Printer : HP Officejet Pro 6830 (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)
Printer : Brother Laser Type2 Class Driver (600x600)

Scanners and Cameras
Scanner : Microsoft HPE2C73A (HP Officejet Pro 6830) (Scanner, USB)

Peripherals
Media Player : SMI USB DISK (15.1GB)

Network Services
Network Adapter : Realtek PCIe GBE Family Controller (Ethernet, 1Gbps)

Operating System
Windows System : Microsoft Windows 10 Professional 10.00.10586
Platform Compliance : x64

[Darryl Ramm]

Sounds like classic badly witten/behaving plugin denormalization. But is this causing you any actual problem? If not ignore it, if it is then use a plugin that goes not suffer from denormalization, use TDM plugins instead of RTAS, or put a dither plugin in front of those that do. You can find denormalization discussed many hundreds of times on DUC.

What is the actual problem impacting work here? CPU "drop out" is when things are not running away with denormalization, or are you having audio drop outs? Make sure "ignore errors" is *not* checked and start with the number of RTAS CPUs equal to one less than the number of physical (not virtual/hyperthreading) cores, limit of 99%.

Please do not post the same question in multiple threads, that just wastes other people's time, and is against the DUC guidelines.

[scicom]

It's happening with any RTAS plug used. Any and all. I listed altiverb and dverb in the post, as I figured they were pretty staple. Anything that is using the CPU, as opposed to tdm, it mutes after a minute or so, unless I 'kick' the cpu by reselecting any input, output or buss setting. I don't get any error or anything, it just mutes.


SiSoftware Sandra added to OP.

*Apologies on the cross post, I couldn't seem to find a way to delete it.

[Stig Eliassen]

Originally Posted by scicom

*Apologies on the cross post, I couldn't seem to find a way to delete it.

No worries. I removed it for you.

[Top Jimmy]

The only thing I can point out here is that Win10 is most definitely not approved for PT9HD nor will it ever be. It is highly recommended that you follow the compatibility document for PT9 if you want the best guarantee of a properly performing system.
http://avid.force.com/pkb/articles/e...ility/en380535

[scicom]

It was the same issue in Win7. Also the same issue under PT10. I run PT10HD at work, so borrowed the dongle and installed PT10HD at home under Win7, and then tried PT10-Win10, just to see if I could observe any sort of change in behavior. There were moments when I thought it went away, 10 or 12 minutes would pass, but then the drop would occur, and back to the <3min frequency. I landed back at PT9HD/Win10 by the tail, and that's currently where it sits. OS didn't seem to make an impact, at least not on the problem at hand. But, yes, i'll align to the recommended set-up so as to eliminate variables.

I also swapped out the video card, just to check that. Same issue. Though, both cards are AMD and not nvidias. current Drivers.

The fan on the CPU kinda sounds like it's starting to struggle, but temperatures report in the normal 45-50 range... unless it's doing some sort of power suck. I'm not sure that would hijack cpu, unless it's related to fan regulation. It _feels_ like it's timebombing to some sort of hardware or system call.

I monitored the task manager to see if there was any sort of process that was popping up to coincide with the loss of native cpu... but nothing unusual aligns.

I'm running PT9 HD6 in a Magma PE6Ri, if that matters. All software is 100% legit, and PT is pretty much all that's on the machine. And, as i moved to fresh installs I went lean on plugs, only those to test with.

I guess I'll go through the BIOS again tonight and drill on that. I discovered there is a BIOS update, so I'll give that a shot. It's about the only thing I haven't tried.

[Top Jimmy]

Originally Posted by scicom

I'm running PT9 HD6 in a Magma PE6Ri, if that matters.

Yes this does matter and could play a part here. Take the core card out of the chassis and put it in the PC and see if the issue goes away. I suspect it will. If this proves to be the case, you could try moving the expansion chassis PCIe card into a different slot in the PC. Also update the Magma firmware if possible.

[scicom]

Do I run with just the core, and magma disengaged? Or is it ok to have both the core in the PC and the accels in the Magma while testing?

[Top Jimmy]

Remove the Magma card so the chassis is not attached when you test the core card alone.

[Darryl Ramm]

Originally Posted by scicom

It's happening with any RTAS plug used. Any and all. I listed altiverb and dverb in the post, as I figured they were pretty staple. Anything that is using the CPU, as opposed to tdm, it mutes after a minute or so, unless I 'kick' the cpu by reselecting any input, output or buss setting. I don't get any error or anything, it just mutes.

OK any plugin is an issue, just the two you mentioned can have denormalization problems, which explain CPU spikes/excessive CPU use, but still that will not cause an audio mute, it can cause a DAE CPU error.

I have no idea what is going on, but make sure the playback engine settings are what I suggested while you do other troubleshooting.

I would also try to test with a non-HD/Digilink interface.