When I first installed and tried to run RSLogix 5000 on my new Windows 10 laptop, I was met with the following ugly Fatal Error for an EXCEPTION_ACCESS_VIOLATION:
I searched through several forum posts and tried several solutions, but what solved the problem for me was running the program as administrator.
To change this setting, first right-click the RSLogix 5000 shortcut and click Properties:
In the Shortcut tab, click Advanced…
Check Run as administrator, then hit OK on both dialogs to commit the changes.
For me, this was all it took to fix the RSLogix 5000 EXCEPTION_ACCESS_VIOLATION on Windows 10! Still having issues? Leave a comment with your situation, or check out this forum post on PLCS.net for some other things to try.
Are you ready to take the next step in your industrial automation career?
If so, the Industrial Automation Connection is here to help connect you with opportunities to advance yourself.
Let us put you in touch with organizations that are looking for people like you.
With IAC, this service is always free, and it takes only a few moments to register. Click one of the buttons below to get started!
Was this post helpful for you? Take just a few seconds below to sign up for our newsletter, and we’ll keep you posted whenever new content is available. Thanks for reading!
Thank you very much. Saved me a phone call to tech support and hours of research and re-installing.
Glad to hear it, Derek. Is there any content you’re hoping someone will cover?
thanks so much! what an easy fix
Thank you so much for your time in putting together this fix. Easy fix.
Thank you so much for yours help .i fixed it.
Glad to hear it helped! Are you having any other issues?
Thank you very much, this was very helpful and worked fine on my computer.
thanks very helpful and easy!
When some one searches for his vital thing, therefore he/she wants to be available that in detail, so that thing is maintained over here.
This did not work for me. This error did not pop up until I changed from 20.01 to 20.05. For a particular processor, this is the latest I can run. I was having issues accessing the processor via the LAN. Linx could connect but 5000 “did not recognize” the processor. Had to use the 232 port. Too slow. Hoping 20.05 would fix that issue. Wonderful working with legacy products.
Hi David,
Sorry to hear it didn’t work for you. If you happen to think of it, let me know what solved your problem and if possible, what was different in your situation that prevented this fix from working.
Yes, we’re doing some legacy conversions and it’s loads of fun. 🙂