PDA

View Full Version : Protools 9.0.1 Crash after Normalizing Regions


daslicht
01-15-2011, 04:49 AM
After Normalizing some audio Regions Protools crashed with the following message:

http://ansolas.de/public/avid/protools901/Normalize%20%20Region%20by%20Region.PNG

How do I get Protool 100 % stable working?

daslicht
01-15-2011, 05:28 AM
http://ansolas.de/public/avid/protools901/Normalize_Region_by_Region.PNG

This 'only'(until now) happens when overwriting files (destructive normalizing)

daslicht
01-15-2011, 05:48 AM
I have a project where I can 100% reproduce the crash

daslicht
01-15-2011, 06:14 AM
Hello,
I have created a project where I can 100% reproduce the 'Destructive Normalizing Region by Region Crash'

anyone like to try it, if you also can reproduce this, please?

Here is how you can reproduce it:

1.) Open the Project
2.) AudioSuite/Other/Normalize
3.) settings: overwrite Files, Region By region, Level on Each Chan/Track
4.) Continue with Destructive Normalize

The result is always:
http://ansolas.de/public/avid/protools901/destruct.PNG

Problem signature:
Problem Event Name: APPCRASH
Application Name: ProTools.exe
Application Version: 9.0.1.41
Application Timestamp: 4d1c06ed
Fault Module Name: FFmt.dll
Fault Module Version: 9.0.1.41
Fault Module Timestamp: 4d1c2ad1
Exception Code: 40000015
Exception Offset: 002c86e8
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0273
Additional Information 2: 027333e70af5c707ec71dc376ff3e0b6
Additional Information 3: 00f4
Additional Information 4: 00f41fb4ce75e1ce26c10ef87e219543



Let me know how to fix this issue ?

Here is the Project:
http://ansolas.de/public/avid/protools901/hope.zip

daslicht
01-15-2011, 03:20 PM
I tried now some BIOS settings and I modified th following:

set SATA mode to IDE and disabled no-execute memory protection.

After rebooting the error was gone.

To make sure those setting were really the cause of the crash I canged all settings back as they were before,
but after a reboot it was still working.

Really strange I still don't know why it was crashing.

:confused: