What is; Access Violation Error

thebski75 wrote on 1/15/2013, 12:26 PM

Hi

I'm using Video Pro X4 and I have just put in a new graphic card, when I go into program settings and do any thing it comes up with this Error message saying     ''Access Violation'' it also says ''Attention! The current project was saved automatically. However internal memory structures may be damaged that do not enable correct saving. It is recommended that the movies are saved with new names for further editing''

I can not work out what is going on here, the graphic card I put is working and a better one,

Can any one help?

Comments

emmrecs wrote on 1/17/2013, 5:57 AM

Since no-one else has answered your question (perhaps because we'd all be guessing)!..

It would appear that VPX has "taken exception" to something on your system - could be the new graphics card - OR its own installation has somehow become corrupted.  I have VPX4 and, in general, I find it very stable but, when it does start to display seemingly random "errors" and to behave in unexpected ways, my experience is the "best" solution is to uninstall and reinstall!  (I keep a screenshot of any customizations I've made in Program Settings or the "import" screen (links to particular folders)) and then proceed to uninstall, using Revo Uninstaller before reinstalling, re-registering and restoring all my customizations.  Yes, it is tedious and rather time-consuming but, in my experience, tends to sort out any problems I've met; the "Repair" option for me at least, rarely achieves any improvement!

HTH

Jeff

Last changed by emmrecs on 1/17/2013, 5:57 AM, changed a total of 1 times.

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

artsmith wrote on 2/13/2013, 5:03 PM

Following a recent 'Access Violation' crash, I took all the usual precautions and very carefully restored my programme after saving under another name, as a precaution. Everything is now working correctly again, EXCEPT that the 'size/position' setting in 'Zoom' under 'effects' has defaulted from'100 percent' to '90 percent' with the image in the left-hand monitor window showing a black margin surrounding it. The situation is easily able to be put-right, by selecting  each clip (together or in-bulk) and manually changing the setting to '100 percent'. There is also a horizontal offset of the image to be corrected as well. I am not vitally, concerned with my current project, as image-wise it is complete, with everything OK. What I would like to know, is will future projects be similarly affected as a result of the crash, or if I began a new project, tomorrow, would I find that the settings have defaulted to the correct '100 percent' as they ought to be? In short,  is the problem likely to be specific to the software installation, or the project-saves (including auto-saves) following the crash? Of course, I know that a re-installation will likely fix the problem; I'm just interested in alternative 'fixes', in case the problem occurs again.

 Computer is Intel i7-based and highly specified, with a top-grade graphics-card and 16gB of Ultra-fast 'Kingston' RAM.

 

 

caracasDGA wrote on 3/16/2014, 11:33 PM

caracasDGA wrote on 3/16/2014, 11:36 PM
  • arriba un link espero que te sirva esta en spanish
Scenestealer wrote on 3/24/2014, 6:26 PM

Hi

Does it mention a specific xxxxxx.dll that is causing the problem?

Are you on the latest driver from the card manufacturers website (not NVidia or AMD's website)?

Ss

Last changed by Scenestealer on 3/24/2014, 6:26 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

johnebaker wrote on 3/25/2014, 2:12 AM

Hi

Your computer specification and the new graphics card make, model and specification in addition to the other information requested will help us give you a more informed answer.

John

Last changed by johnebaker on 3/25/2014, 2:12 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

kurtis-veith wrote on 7/9/2019, 1:02 AM

i only get the access violation when i exit music maker... my songs are there and mixed. i do not get the access violation any time other than when i close music maker.. but i get it every single time i exit music maker.. never ever got one until i switched to the 2020 music maker.. it is a non issue for me because i do not lose my mix

johnebaker wrote on 7/9/2019, 3:29 AM

@kurtis-veith

Hi

You have resurrected a 5 year old topic in the Video Pro X forum - Music Maker has its own forum here - please post your issue there, including details of you computer system and Music Maker version - see this topic for what is required and the full error message text.

This topic will be closed

John EB

Forum Moderator

Last changed by johnebaker on 7/9/2019, 3:34 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.