![]() |
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 - first time posting and a relative novice with Pro Tools. Just bought and hooked up an Axiom Pro 40 keyboard controller and recording a track using the virtual mini grand that comes with Pro Tools LE 8.0.3. When I went to add another non-instrument track I started getting the following error:
"Access violation occurred unable to read location: 0x00000000 at address: 0x182F0318 in module: M-Audio Keyboard.dll". It also completely freezes my computer (windows 7) so I have to reboot. Does anyone have any help they can provide? Much, much appreciated. |
#2
|
||||
|
||||
![]()
There's some useful information here;
http://www.wiki-errors.com/wiki-erro...iki=0x00000000 Having read it, Have you Installed/Uninstalled PT recently? Has PT ever run properly on your computer? Have you tried uninstalling Axiom Drivers(Axiom turned off) & Re-installing them (Axiom still turned off) then switching Axiom on and do you have latest drivers and Firmware to do this? http://forums.m-audio.com/showthread...-Now-Available I notice two things with the latest drivers/firmware, that may have the potential to fix this; * Changed installer to use Avid license file rather than the old M-Audio license. * Changed build to use Avid signing certificate in place of the expired M-Audio signing certificate. You may also want to try the M Audio Forum, I've found it to be extremely useful with problems I had with my Axiom Pro 61. Even though this problem is most likely a Pro Tools/Windows software related problem, M Audio may not be of much help this time but keep it in mind for if you ever need it for your Axiom. http://forums.m-audio.com/forumdispl...ces-amp-Enigma
__________________
Too much blood in my drugstream Motherboard: Gigabyte Z690 AERO D CPU: Intel Alder Lake Core i9-12900K CPU Cooler: Noctua NH-D15S RAM: Corsair Vengeance DDR5 64GB (2x 32gb 5200MHz) Drives: 2 x Samsung 980 Pro 2TB NVME PCIE 4.0 M.2 SSD (Record & Samples) 1 x Samsung 980 Pro 1TB NVME PCIE 4.0 M.2 SSD (OS Win 11 Pro) GPU:Gigabyte GeForce RTX 3060 12GB GDDR6 PCIE 4 PSU: Corsair HX Series HX850 Platinim CASE: Fractal Define XL R2 PT 11HD (v11.3.2) Omni s/pdif <> AxeFxIII HD 96I/O |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Access violation occurred, unable to read location: 0x000000003E3FFFBA | pm mastering studio | Pro Tools 11 | 17 | 05-13-2015 02:37 PM |
Access violation occurred, unable to read location: 0x00000002E0341AFD | notedmusic | Windows | 6 | 02-05-2014 06:58 AM |
Problem "An Access Violation Has Occurred" | sk8r47373 | Pro Tools SE and Essential (Mac) | 3 | 05-12-2012 01:47 AM |
Help? sudden error repeats: "access violation occurred" | jojo99 | Pro Tools M-Powered (Win) | 5 | 01-26-2009 09:20 PM |
Always Got "Access violation occurred" when start a new file | Patrrchan35 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 0 | 05-25-2002 10:02 AM |