Access Violation 0x00000000 when loading Pro Tools 10.3.9 HD | Native
 

I have PT 11, which works perfectly fine, and PT 10 that I use for older client sessions while I transition everything into 11. After installing the latest 11 update, 10 freezes with error during plugin scan.

See attached screen shot for exact error message. It occurs whenever I attempt to load version 10.3.9 of PT. After clicking "OK" on the error pop-up, Pro Tools hangs indefinitely and must be closed manually using Ctr-Alt-Del and ending the process.

Here is what I've tried already:
-removed ALL AAX 32 and 64 bit plugins from the PT 10 directory, and left only the RTAS plugs. Still no load.
-made sure all plugins are up-to-date
-gave admin access to PT 10 during setup and launch
-did clean uninstall of PT10 before installing upgrade
-performed all Win 7 optimizations
-disconnected all USB peripherals
-disconnected Ethernet cable
-tried running PT10 in compatibility mode Win XP SP3
-ran some kind of command prompt "fix" I found on a forum thread related to this issue, where all entities are given "OptIn" to some parameter. Wish I could remember exactly what or where I found it, but whatever it was it said "operation successful"; however this didn't fix the issue I'm having at all.


On the screen shot, you will see the error pop-up during the Absynth scan; however, if I remove Absynth from plugin directory, the error simply appears on the next plugin. Even the Avid AiR plugins cause this error to happen. I went through just about every plugin I have, one by one, and PT still hangs during the scan on all but Xpand.

I can only get Pro Tools 10 to load when removing ALL other plugins from the RTAS and AAX directories.

-All my plugs are up to date.
-I have PT HD|Native v11.1.3 and v10.3.9
-My OS is Win 7 Ultimate 64-bit SP-1

I/O Hardware:
Avid 8x8x8
Lynx Aurora 8 via AES
Burl B2 via AES encl


SANDRA report:
SiSoftware Sandra

ID
Host Name : PowerhouseIII-A
Workgroup : WORKGROUP

Computer
Model : OEM P5E3 Deluxe
Serial Number : System Ser**********
Chassis : Desktop
Mainboard : ASUS P5E3 Deluxe
Serial Number : MS1C7AB********
BIOS : AMI (OEM) 1409 02/02/2009
Total Memory : 8GB DIMM DDR3

Processors
Processor : Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz (4C 3GHz, 2x 6MB L2)
Socket/Slot : FC LGA (Socket T)

Chipset
Memory Controller : ASUS X38 Processor to I/O Controller 4x 333MHz (1.33GHz), 2x 4GB DIMM DDR3 1.33GHz 128-bit

Memory Module(s)
Memory Module : Corsair CM3X2G1333C9D 2GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CM3X2G1333C9D 2GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CM3X2G1333C9D 2GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-24 5-34-10-5)
Memory Module : Corsair CM3X2G1333C9D 2GB DIMM DDR3 PC3-10700U DDR3-1334 (9-9-9-24 5-34-10-5)

Video System
Monitor/Panel : ACR S200HQL
(1600x1200, 19.4")
Monitor/Panel : XXX L24
(1920x1200, 30.6")
Video Adapter : ATI Radeon HD 3800 Series (320SP SM4.1 670MHz, 1GB DDR2 800MHz 256-bit, PCIe 2.00 x16)

Graphics Processor

Storage Devices
WDC WD1500HLFS-01G6U0 (150GB, SATA300, 3.5", 10000rpm, 16MB Cache) : 140GB (G:)
WDC WD3000HLFS-01G6U1 (300GB, SATA300, 3.5", 10000rpm, 16MB Cache) : 279GB (I:)
WDC WD3000GLFS-01F8U0 (300GB, SATA300, 3.5", 10000rpm, 16MB Cache) : 279GB (C:)
ASAP (515.8MB, USB2) : 492MB (F:)
TSSTcorp CDDVDW SH-S202N (ATA66, DVD+-RW, CD-RW, 2MB Cache) : N/A (D:)
SAMSUNG CD-ROM SC-148C (ATAPI, CD-R, 128kB Cache) : N/A (E:)

Logical Storage Devices
Slave 1 (G:) : 140GB (NTFS) @ WDC WD1500HLFS-01G6U0 (150GB, SATA300, 3.5", 10000rpm, 16MB Cache)
Alt Master (I:) : 279GB (NTFS) @ WDC WD3000HLFS-01G6U1 (300GB, SATA300, 3.5", 10000rpm, 16MB Cache)
Master (C:) : 279GB (NTFS) @ WDC WD3000GLFS-01F8U0 (300GB, SATA300, 3.5", 10000rpm, 16MB Cache)
Removable Drive (F:) : 121MB (FAT) @ ASAP (515.8MB, USB2)
Optical Drive (D:) : N/A @ TSSTcorp CDDVDW SH-S202N (ATA66, DVD+-RW, CD-RW, 2MB Cache)
Optical Drive (E:) : N/A @ SAMSUNG CD-ROM SC-148C (ATAPI, CD-R, 128kB Cache)

Peripherals
LPC Hub Controller 1 : ASUS (ICH9) LPC Interface Controller
LPC Legacy Controller 1 : Winbond W83627DHG
Audio Device : ASUS (ICH9) HD Audio Controller
Audio Device : Gammagraphx, Inc. (or missing ID) Radeon HD 3870 Audio device
Serial Port(s) : 1
Disk Controller : ASUS (ICH9) 4 port Serial ATA Storage Controller 1
Disk Controller : ASUS (ICH9) 2 port Serial ATA Storage Controller 2
Disk Controller : ASUS JMB36X PCIE-to-SATAII/IDE RAID Controller
USB Controller 1 : ASUS (ICH9) USB Universal Host Controller
USB Controller 2 : ASUS (ICH9) USB Universal Host Controller
USB Controller 3 : ASUS (ICH9) USB Universal Host Controller
USB Controller 4 : ASUS (ICH9) USB2 Enhanced Host Controller
USB Controller 5 : ASUS (ICH9) USB Universal Host Controller
USB Controller 6 : ASUS (ICH9) USB Universal Host Controller
USB Controller 7 : ASUS (ICH9) USB Universal Host Controller
USB Controller 8 : ASUS (ICH9) USB2 Enhanced Host Controller
FireWire/1394 Controller 1 : ASUS IEEE 1394a Firewire Controller
SMBus/i2c Controller 1 : Intel ICH SMBus

Printers and Faxes
Printer : Amyuni Document Converter 400 (2400x2400, Colour)
Printer : Microsoft XPS Document Writer (600x600, Colour)
Printer : HP LJ300-400 color MFP M375-M475 PCL 6 (600x600, Colour)
Printer : HP Photosmart D110 series (1200x1200, Colour)
Printer : HP Photosmart C5200 series (1200x1200, USB, Colour)
Printer : HP Photosmart 7960 series (600x600, USB, Colour)
Printer : HP Photosmart 7960 series (1200x1200, Colour)
Fax : Microsoft Shared Fax Driver (200x200)

Peripherals
Media Player : ASAP (120.82MB)

Network Services
Network Adapter : Realtek PCI GBE Family Controller (Ethernet, 100Mbps)
Network Adapter : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller (Ethernet)

Operating System
Windows System : Microsoft Windows 7 Ultimate 6.01.7601 (Service Pack 1)
Platform Compliance : x64

Windows Experience Index
Current System : 5.9

Re: Access Violation 0x00000000 when loading Pro Tools 10.3.9 HD | Native
 

Hi, A few things come to mind. An access violation could indicate a bad stick of RAM. I would run some diagnostics on them. Doing a quick search, looks like there's a Windows Memory Diagnostic tool that may be good - I'm sure there are others.

Also, you could try completely removing Pro Tools 10 and 11 and then reinstall just Pro Tools 10 and see if any plugins work. My pc likes to have 10 installed first, then 11 - at least there are less errors when doing so.

Beyond that, you could try removing PT10 and running a defrag and/or checkdisk on the system drive before reinstalling.

When all else fails, you could try a System Restore, restore your system drive from backup, or reformat and reinstall Windows 7 as a last resort. :eek:

Re: Access Violation 0x00000000 when loading Pro Tools 10.3.9 HD | Native
 

Re: Access Violation 0x00000000 when loading Pro Tools 10.3.9 HD | Native
 

Thanks for the tips cwsand.

Fortunately, after about a week of trying different things, I got v10 working again by doing the following:

1.) Full uninstall of PT10, including HD drivers and all settings/profiles.

2.) Full uninstall of all RTAS plug-ins, including air virtual instruments collection. (Turns out the AAX plugs were not the issue, but all the dpm and rsr style plugs had to be uninstalled (not just moved).

3.) Full reinstall of PT10.

4.) Full reinstall of all RTAS plug-ins.

5.) Full update of all reinstalled RTAS plug-ins.

*Make sure to reboot between each step.

Recap:
It seems, this particular access violation error, for whatever reason, was a result of all my RTAS plugins in PT10 becoming corrupt after installing the latest version of PT11.

Key point in solving:
Simply updating the plug-ins did NOT work for me.
I had to clean uninstall all my RTAS plugs, then reinstall them, and the finally, update them.

Luckily, the steps above solved my problem. I did not end up having to check memory, run defrag, discheck, reformat my OS, or do a full clean and reinstall of 11 either.
I will, however, make a restore point now that everything is playing nice!

Re: Access Violation 0x00000000 when loading Pro Tools 10.3.9 HD | Native
 

I've had that happen when the system was in external sync but the converter was powered down.