Workaround for "Could not complete your request because Access violation occurred....

[wdaweb]

Just thought I'd toss this out there in case it helps someone else. I was having an issue with PT 2018.1 throwing an error "Could not complete your request because Access violation occurred unable to read location: 0x0000000000" when I'd try to add a plug-in or modify one, and then when I'd try to exit it would give me a similar message saying it could not complete the exit due to an access violation ... ending in 38.

I'm running PT 2018.1 on a Win10 64 bit machine with 16G ram and an I7. I also have an AMD Radeon 7700 graphics card and an Intel HD Graphics 4000 built into the motherboard. I have a Slate Raven MTI2, and Dell Monitor on the AMD card, and a nice Samsung monitor on the Intel. It's never once hiccupped while I was a Sonar Platinum user.

After going through the Avid Windows 10 Optimizations and Troubleshooting document, I still had an issue. I saw something elsewhere about intel graphics cards and a patch for PT, but I don't have the card the article referenced. It still turns out that if I had certain plug-ins (instrument or effect) visible on the Samsung monitor (intel card), I'd run into the problem and have to re-install the plug-ins and go back to a saved session back up that was auto-saved at a point in time prior to putting something on the Samsung monitor. I developed a routine where I could duplicate this every time.

My work around is to simply not place anything on the Samsung Monitor. I have gone over 100 hours of use so far without this issue happening before posting this, and decided to try to duplicate the error again to test my theory. I backed up my current session and tried moving AD2 to the Samsung, and it threw the error and messed up the project.

I found I did not have to re-install anything. I just had to go back to the session I had backed up after trashing the preferences, and all was well. Obviously I also have to refrain from moving anything from within PT onto the monitor connected to the Intel card.

I have the latest drivers for the cards from the Intel and AMD websites since Dell doesn't have official Win10 driver for this box. Anyway, I know a lot of people are having similar issues and hopefully this will help some people work around it.

[The Weed]

Try running both monitors off the AMD and disable the Intel Graphics in BIOS.