10.3.6 Locking up

[jimst57]

EDITED:

(I changed the title of this post after discovering that the freezing seems related to the new Mbox 1.1.8 driver)


Since my upgrade to 10.3.6 on Windows 8 I'm getting system lockups at random times. The whole system freezes, and has to be rebooted. 10.3.5 was fine.

This is a tough one to troubleshoot because it freezes compleatly. Also I upgraded to the new Eleven Rack driver, and MBox3 driver at the same time.

So I'm just wondering if anyone else is having this lockup problem?

Thanks.

[albee1952]

Not seeing this here, but I am on Windows 7. If you don't NEED 10.3.6, I would roll back to 10.3.5. My 10.3.6 install is on its own system drive(with PT11) and I swap back to 10.3.5 to get work done.

[DAWgEAR]

I am using the demo (my upgrade box will arrive later this week) and I have experienced some lockups and instances where error messages appear as soon as soon as I try to open projects with 10.3.6. Killing PT via task manager or even a hard shutdown sometimes is required.

Usually this is preceded by a slower than usual launch and and my system has not loaded the HD Native driver. It also tends to be exacerbated by alternately launching PT 10.3.6 and PT 11.0.

I also had some unable to find iLok, or ilok found but only certain licenses reported as missing, issues which I do not believe were part of the broader iLok episode.

At the moment, rebooting and subsequently relaunching PT whilst holding down N to get to the playback engine dialog and then reselecting my interface seems to fix the situation.

Other things I did: uninstall/reinstall iLok manager and PT 10.3.6 and 11.0 and I transferred all of my ilok assets to another iLok 2 (I suspect my iLok issues were unrelated and due to a bad/failing iLok 2 key). The new iLok is still occasionally not found however. Reinserting it physically seems to fix this.

It should be noted that PT HD 11.0 is not officially supported on Win 8, so I am living on the edge. Vanilla PT 11 is supported.

Maybe none of this helps your particular situation, but I am tossing it out just in case.

[ron_from_RIFAS]

I've had this issues in the past but it was related to missing an SLI driver that my motherboard needed. I was running Pro Tools 8 then so I doubt your issue is PT related. PT is provably just the catalyst.


Sent from my HTC 8X using Tapatalk

[jimst57]

Well I've discovered that it isn't 10.3.6. It's something to do with the new Mbox driver 1.1.8.

I've tried several combinations of Pro Tools versions, Mbox drivers, Eleven rack drivers and have found that this combination works:

Pro Tools 10.3.6 / Pro Tools 11
Eleven Rack driver 1.1.6
Mbox driver 1.0.22

As soon as I load the box driver 1.1.8, and run Pro Tools, the machine freezes at random times. Doesn't take long, but the entire machine freezes and needs a reboot.

All is fine with both Pro Tools 10.3.6 and Pro Tools 11 with the older driver 1.0.22.

[ron_from_RIFAS]

Not ideal but sounds like a win.


Sent from my HTC 8X using Tapatalk

[SlicerSounds]

I just posted on the PT10 forum but I'm also experiencing a complete freeze with 10.3.6. This happens when loading a session as the ""Some paths were made inactive because they could not be assigned to existing path definitions" message appears. I got this message all the time anyway in 10.3.5 (since changing interface from fastrack pro to LS56) but never resulted in complete freeze and need to reboot like now with 10.3.6.

Glad to hear you fixed your glitch jimst57!! if I can't solve then will just go back to 10.3.5 until all my plugs/VIs go AAX 64 bit - hopefully by the end of the summer!! - as I've already upgraded to PT11

[jimst57]

Originally Posted by ron_from_RIFAS

Not ideal but sounds like a win.

Yes but no.

I tried to change the title of the thread but had no luck.

Just to be clear here, the issue is not with Pro Tools 10.3.6 or 11.
Both work fine as long as I use the old Mbox 1.0.22 driver.

When I use the new 1.1.8 driver on Windows 8, Pro Tools runs for a little bit and then locks the whole machine up. It just instantly freezes.

It would be better if the new driver worked, as I understand there are performance improvements in it.

Just guessing, but I don't think it's a machine issue here because things are fine until the new driver is loaded.