Control Access Violation Errors

An Access Violation occurs when the software attempts to access a piece of memory that is presently inaccessible. This is commonly caused by Faulty RAM or a hardware driver, and is usually remedied by restarting Control or the host's computer. Some example error codes found in Access Violations are as follows:

  • Uninitialized Object. When a program references an object that has not been created. (The error will reference an address that starts with FFFF or 0000.)
  • Accessing a Freed Object. When a program tries to reference an object that has been deleted/destroyed and Windows has recaptured the memory. (The error will reference an address that does not start with FFFF or 0000.)

Note: When an object in uninitialized, it will ALWAYS yield an access violation. The second of these occurs more erratically than the first, because Windows often doesn't reclaim freed memory for a while. If the program attempts to access a freed object before Windows reclaims the memory, no Access Violation will occur. Hence, the second case produces more erratic errors than the first.

In the end if the same Access Violation error appears when performing the same steps, even after rebooting the machine, please contact Technical Support for further troubleshooting.

You could leave a comment if you were logged in.