PT10 crashes when opening sessions

[Legion6789]

Yesterday I upgraded my interface from a ProFire 610 to a Saffire Pro 40. Unfortunately PT10 will crash randomly when I open a session. There doesn't seem to be any regularity to it. I end up having to try opening the session 3 or 4 times until it opens without crashing. The error message is below.

I'm running Win 7 x64. I've trashed prefs a few times. I've uninstalled all the m-audio drivers for the ProFire. I have the latest drivers for the Saffire.

I've noticed that when I go to open a session I'll hear a slight popping noise in the monitors, like when you first turn on an amp and then it crashes.


Problem Event Name: APPCRASH
Application Name: ProTools.exe
Application Version: 10.0.0.821
Application Timestamp: 4e97e697
Fault Module Name: StackHash_69de
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7ba58
Exception Code: c0000374
Exception Offset: 000ce653
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 69de
Additional Information 2: 69de704c6b96b386b026f62cea1ef21e
Additional Information 3: 3cd1
Additional Information 4: 3cd15ebbfb2200b0f7e2736b35c60a82

[crizdee]

Originally Posted by Legion6789

Yesterday I upgraded my interface from a ProFire 610 to a Saffire Pro 40. Unfortunately PT10 will crash randomly when I open a session. There doesn't seem to be any regularity to it. I end up having to try opening the session 3 or 4 times until it opens without crashing. The error message is below.

I'm running Win 7 x64. I've trashed prefs a few times. I've uninstalled all the m-audio drivers for the ProFire. I have the latest drivers for the Saffire.

I've noticed that when I go to open a session I'll hear a slight popping noise in the monitors, like when you first turn on an amp and then it crashes.


Problem Event Name: APPCRASH
Application Name: ProTools.exe
Application Version: 10.0.0.821
Application Timestamp: 4e97e697
Fault Module Name: StackHash_69de
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7ba58
Exception Code: c0000374
Exception Offset: 000ce653
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 69de
Additional Information 2: 69de704c6b96b386b026f62cea1ef21e
Additional Information 3: 3cd1
Additional Information 4: 3cd15ebbfb2200b0f7e2736b35c60a82

Hi,

So was everything running solid before you changed interfaces?

Does the interface work with other apps on your computer? Any other Daw's installed you can test with?

Does pro tools run ok using the computer built-in sound card?

Does sound like the interface could be at fault! Or just the driver got corrupt or something.

Chris

[Legion6789]

Everything was solid with the M-Audio ProFire 610 with PT9. Then I upgraded to 10 and started getting access violation errors. They would happen occasionally during a session, but usually when closing one.

With the Saffire Pro 40 I get AppCrash errors when I try to open a session. But I haven't had any access violation errors yet. The AppCrash errors happen about 75% of the time, the Access Violation errors occurred only 25% of the time.

[Legion6789]

No suggestions?

[TOM@METRO]

Does this happen with new sessions?

Have you tried opening sessions without loading plug-ins? (shift+open)

[Legion6789]

This happens with new sessions too.

[Legion6789]

Just got a new error trying to open a session "Pure virtual function call". None of these sessions are complex. They top out at 12 tracks max, some of them have 1 or 2 VIs (EZDrummer and Kontakt Scarbee Bass).

[Legion6789]

I reverted back to PT 9.0.6 and I still get the AppCrash errors when opening/creating a session. It's always preceeded by the popping sound in the monitors before it crashes. Makes me think it's loading/unloading the driver or something.

[Legion6789]

I have a theory now. I noticed I'd get the same popping sound briefly when I'd go to play music in winamp for the first time. I had the saffire mix control open and I saw that it was changing the sample rate from 44.1kHz to 96kHz. This was because I had the default format in windows set to 24 bit 96kHz so when winamp would start, it would switch the sample rate. I think this may have been occurring in pro tools when I'd open/create a session. Windows and Pro Tools may have been fighting over the sample rate setting. I've reverted back to 44.1kHz for default and the problem hasn't happened since. We'll see if this keeps up.