![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
|
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
![]()
Hi
I'm currently getting the following error whenever I attempt to open Pro Tools "Access violation occurred, unable to read location: 0xFFFFFFFFFFFFFFFF" Sometimes the code changes to 0x000000000000010 or 0x00000000000000008 I recently updated my USB port drivers, as they were showing up as an unknown device in device manager, so it may have something to do with that, but I'm not sure as every other program seems to be working fine Thanks in advance for the help. Here's my setup PT: PT 2024.10.2 PC: Alienware Aurora R6 Desktop 64GB Ram Intel 17-7700 Nvidia GeForce GTX 1060 6GB OS: Windows 10 Home 64-Bit |
#2
|
|||
|
|||
![]()
That's a null pointer or close to it exception (all those memory addresses close to 0x000...0 like that are invalid and cause the same system trap as an actual null pointer), this will be caused by an internal coding error or something overwriting memory, certainly possible to be caused by a bad driver, or many other types of Windows problems as well as bugs in Pro Tools or plugins, it's an open field...
If you updated the USB drivers, the first thing I would try is to use Windows 10 to roll back those changes. Google how to do that if not sure. I'd also try removing all other USB devices possible and rebooting the PC then testing again. What exact audio interface are you using? Hopefully it supports ASIO (not using ASIO4ALL)... if so what exact version of the ASIO driver do you have installed? You can try holding down the "N" key on the keyboard after launching Pro Tools and you should see the Pro Tools playback engine dialog appear. Make sure you are selecting the correct ASIO interface there... if that does not work try selecting a different output like the (WASAPI) Windows Audio output device just to test to see Pro Tools does not crash. Still stuck: what does the Pro Tools log file show? They are fairly cryptic. C:\Users\<user>\AppData\Local\Avid\Logs\Pro_Tools* .txt Post a log file online somewhere and post the link here. Still stuck: open a support case with Avid support, get them any log and crash files. Post the case/incident number here. |
#3
|
|||
|
|||
![]()
Thanks so much for the help!
It turned out to be an issue with my audio interface. I think when I updated my USB drivers it may have thrown the audio drivers out of whack. I disconnected the audio interface from the PC and pro Tools was running. I tried a few different things, but when I uninstalled the audio drivers and then reinstalled them everything was fine again. Thanks again for your help. I hope you have a great weekend! |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Getting "Access violation occurred-unable to read location" error in 2019.10 | Jasconito | Pro Tools 2019 | 3 | 11-03-2019 02:59 PM |
Meaning of: "Access violation occurred, unable to read location: 0x0000000000000368" | taylor4814 | Pro Tools 2019 | 3 | 06-09-2019 05:17 AM |
Access violation occurred, unable to read location | JasperEads | Pro Tools 11 | 6 | 10-10-2017 02:16 PM |
Access violation occurred, unable to read location: 0x0000000000000008 | timcat | Pro Tools Express on Windows | 0 | 10-09-2017 02:21 PM |
Access violation occurred, unable to read location: 0x00000000341CFEF2 | live4live | Pro Tools 11 | 2 | 05-28-2014 09:23 AM |