DLL file not letting me render in Video pro x6

Xkiller wrote on 1/2/2016, 12:55 AM

Im using Video pro x6 and recently there has been a problem with rendering, it will always fail to render about 80% there and give me a fatal error

"Error in module "ntdll.dll (Load address 0x76d60000) to address 0x76daaf36

Exception 0xc0000005 "ACCESS_VIOLATION""

But when i rename/delete the avrt.dll file from system32 it would be able to render but the sound would become messed up? Anyway to fix, been trying to fix for hours.

EDIT: it also seems that it only occurs in that project, i tried rendering a test project for about 20 seconds and it worked, the other project that does not work is about 3.5 minutes. Also on the "bad" project I also did a test render on it, for about 30 seconds, it did work then fully without having to disable or do anything. Is it a length problem that screws up my computer?

Specs

Windows 7

i7-4970k

AMD R9 280x

16gb ram

2tb harddrive

Comments

johnebaker wrote on 1/2/2016, 6:34 AM

. . . . "Error in module "ntdll.dll (Load address 0x76d60000) to address 0x76daaf36

Exception 0xc0000005 "ACCESS_VIOLATION""

But when i rename/delete the avrt.dll file from system32 it would be able to render . . . .

There is some confusion here over which DLL is causing the problem.

Also do not start altering the Windows system files - this is the quickest way to wreck your computer.

You may have a corrupted Windows system so the first thing to do is to put your system back into its correct state using this procedure:

Expect this to take a couple of hours – do not skip any of the following steps
Press and hold down the Windows key and press the R key.
Type in cmd and press the Enter key
In the window that opens type in the following: sfc /scannow note there is a space between sfc and /scannow
Let this run to completion - it may take a long time
Once the checks are complete you may get a message saying some files cannot be fixed - this is OK.
Restart the computer.
If you had the message in step 6 that files could not be fixed repeat steps 2 to 7 again - do not open any other programs if you have to do this. Note you may have to do this once more though twice is usually sufficient.
Reboot the computer

Once this has been done try the exporting again.

If the export still fails then it is possible that one of the objects on the timeline is the issue.

To check this successively remove an object from the end of the timeline and try exporting.

Repeat until you find the offending object.

HTH

John EB

johnebaker wrote on 1/2/2016, 3:14 PM

Thanks for letting us know - it is useful for other members who come across the same problem.

John EB