The (0xc0000005) error is often associated with a driver conflict. Recommend you launch Sacred 2 in safe mode. If it works from there, the conflict is probably driver related, usually in terms of video or audio drivers. Might also be beneficial to launch Sacred 2 using Windows Xp compatibility mode.
Additional suggestions here
on how to deal with (0xc0000005):
So, what is an access violation, a C0000005? This is the translated #GP code the fault handler raises, which the operating system displays as an 'Access Violation', whos numerical form is c thousand 5. Its the operating system telling you that a program has malfunctioned and tried to reference no mans land. It has nothing specific to do with any particular program, or a brand of software, this is straight from the CPU and kernel of the operating system.
You now need to determine which program is throwing the exception. It may be several, thats certainly possible. Use Start->Run Drwtsn32 and see whats in the exception handler log. Use the event viewer, if you prefer. Once you've identified the application that is faulting, the next time it crashes on you, note where it stuck the dump (probably \windows\minidump\3279272.dmp or in C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp) and run it through the dump data analysis tool in my signature, and ill tell you why it blew up, and try to recommend what to do to fix it.