I can't give you a fix. Someting in your app is trying to read, or more probably, write into the part of memory that Windows reserved for itself at startup.
Users are not allowed to mess with OS tables, lists, queues, stacks, etc.
Might you have a size or location problem ?
Usually when I create a new project I'll rename the form shortly after, whenever I add a new form I'll give it a new name right away (in the create form dialog box) so it gets created with a meaningful name. If I need a new form that basically does what one of the projects existing forms already does, then I'll opt to tweak the existing one rather than creating a whole new one, but that's not a strict rule for me because if the existing form needs to have a lot of things changed on it to become dual/multi-purposed then I'll just create a new form (or make a copy of the existing one into a new form), I do that to make testing easier. These are just things I personally do, but giving forms (and controls on the forms) meaningful names is a must, you'd be surprised at how much of those details you forget after not working on it for 6 months (or longer).
Access violation exceptions almost always indicates either a virus or faulty hardware. Or some corruption in system files. I would just reformat and run stress tests to see if it still happens. If it does it's a hardware problem.