|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#11
|
|||
|
|||
Re: Access violation occured,unable to read location
Of course.
|
#12
|
|||
|
|||
Re: Access violation occured,unable to read location
It's loading plugins when it happens so the obvious thing is to start uninstalling plugins, start with the most recent and keep going till it works...
|
#13
|
|||
|
|||
Re: Access violation occured,unable to read location
I just ran into the same problem today, specifically "Access violation occurred, unable to read location: 0x0000000000000010" causing a crash as Pro Tools launches. It happens while plugins are loading, but it's NOT a plugin problem. I tried removing all plugins, and I also reinstalled Pro Tools and updated my iLOK manager as some other Access Violation errors require.
The problem for this specific error is a corrupted/damaged MBox driver - as soon as I reinstalled the MBox drivers (with the same installer I used previously) it went away. |
#14
|
|||
|
|||
Re: Access violation occured,unable to read location
Alian82, Going to give you a recommendation, but I got to tell you - its a shot in the dark. Something I would say look into, make the change and if it fixes your issue, keep the the change, if not, change it back to what you have now.
I am curious if when you said you were working well in PT, was it version 10.something? and maybe 11 is having this issue? Here is what I am getting at: PT11 is a 64bit massive rewrite for AVID. There is a motherboard bias setting called "Hyperthreading". Before version 11 came out, I use to nail this motherboard option in the "Off" position. And when I had that enabled under version 10, it was pretty horrible. I had access-violations left and right, I would run out of CPU with maybe 3 tracks of audio and 1 VI. So under v10, having this feature shut off was the right answer. Now keep in mind, I have heard the exact opposite from some on this forum. So a little experimentation might go a long way.. Now along comes version 11, a 64 bit app and total rewrite, I started seeing these same access-violations and CPU issues with my motherboard continuing to have hyperthreading OFF. So just last week, I loaded a song that had about 28 tracks plus 1 VI, For me, it seems doing an offline bounce really asks a lot of PT, so I focused on that. I kept Hyperthread off, and the offline bounce seemed to ALWAYS choke on me. access violations, and CPU issues showed. I then reboot my PC, went into BIOS, set Hyperthread ON for my V11.3 and the same song has worked perfect for me.. Its a coin toss, may not help you, every system is a little different and your hardware especially, we both have different stuff.. But experimenting with this would cost you nothing.. Hope this helps.. |
#15
|
|||
|
|||
Re: Access violation occured,unable to read location
Hello guys
I've got PT12 yesterday and I just ran into the same problem, specifically "Access violation occurred, unable to read location: 0x0000000000000000" causing a crash as Pro Tools launches. It happens while plugins are loading. My iLOK manager has no errors and the avid application manager is fine. I'm working on a MacBook Pro with Windows 8.1 (64Bit). What can I do now? Thanks. |
#16
|
|||
|
|||
Re: Access violation occured,unable to read location
Hi,
I'm having an issue loading any plugins with Pro Tools 12.4 and I receive this error message, every time: Could not complete the Open Session... command because Access violation occurred, unable to read location: 0x0000000000000000 I've recently installed Pro Tools 12.3.1 Win and updated to 12.4 on my WIndows 10, 64 bit, Asus laptop computer (I'm on a project site and away from my recording studio, running Pro Tools setup at home). I have tried to re-install Pro Tools, re-booting, running Pro Tools using the Administrator and further, my iLOK, Avid Application Manager, computer drivers, software, windows updates are all current and yes, I have a Advanced Systemcare to take care of my registry links etc. etc. If anyone has found a solution to this issue, please could you share with me. Thanks.
__________________
Coxxie 28” Samsung UHD (4K) Video Monitor HD7750 Graphics Card Intel Xeon E5-2630V3 Processor ASUS LGA2011 XEON MB Motherboard 16GB DDR4 RAM 1 x 500GB SSD HDD (Operating System) 1 x 1TB SSD HDD (Audio Files) Corsair AX760I PSU Windows 10 Pro, 64 bit Focusrite (Scarlett) 18i20 Audio Interface Pro Tools 12.4 Win (With Upgrade & Support Pack) AIR Instruments Bundle 12.0 First AIR Effects Bundle 12.0 Win First AIR Instruments Bundle 12.0 Win Xpand II 12.0 Win |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Unable to launch Pro Tools- Access violation, unable to read location 0x000000008 | JaydenLoone | Pro Tools 10 | 11 | 11-13-2021 11:26 AM |
Access violation occured, unable to to read location: 0x0000... | mandal | Pro Tools HDX & HD Native Systems (Win) | 5 | 06-30-2014 06:22 AM |
Access violation, unable to read location. | Soul El | Windows | 3 | 04-22-2013 06:36 PM |
Access violation occured, unableto read location;0 times00000004 and 0 times00000B31 | Ofentse Morris | Windows | 0 | 09-07-2012 07:00 AM |
Access violation occured, unable to read location 0x00000010 | shamanrock | Windows | 0 | 04-03-2011 04:03 PM |