This error is usually related to MS Office. Here is a link to Microsoft's KB article: C0000005 ACCESS_VIOLATION - Google Search
But interestingly enough, here are some Cubase specific versions of this error: Cubase.net :: View topic - Cubase SX3 Crashes when opening a song. I have SX3 Log txt. Steinbergusers.com: Problems with loading a VST in Cubase LE I would pursue tech support from the manufacturer & user groups first, but assuming that it isn't as simple as avoiding VST plugins, here is some additional troubleshooting 'food for thought':
I presume that this same version of Cubase, was operating properly before this error started.
Does your system function properly now, apart from this Cubase error?
Can you correlate when this error began, with anything specific? Unusual websites visited or other strange computer behavior?
Any new programs installed, utilities run, email file attachments opened, etc... which correspond to when this began?
Have you booted from a write-protected media, and run any virus/malware scans? If not that would be a very good thing to do.
Here's a link to a great utility for creating a safe diagnostic environment: Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD
Any changes in hardware or drivers? Have you checked your Device Manager for any resource conflicts?
Made any changes to the CMOS configuration?
Do your Windows updates download and install automatically? It's possible that something could go wrong with this process, and you wouldn't know about it right away. At this time, let's stop and reassess again: have you contacted the manufacturer or their tech forums, etc? If not, exhaust that resource before going any further, as everything from here on in is going to be more invasive & time consuming.
When you reloaded Windows, did you boot from the RO Windows media, and DELETE the previous partition, and create a new partition, before installing the OS? That is how I would always recommend you install Windows.
But before re-installing again, there are a few other things to consider. You could have a corrupt or infected boot record, and might
benefit from restoring your boot sector. To do this you boot into the Recovery Console, and run the FIXBOOT and FIXMBR utilities. PLEASE NOTE, this is a long shot and a last ditch step, only to be used if you have already exhausted all other reasonable troubleshooting, so don't rush to run these now just because I mentioned it. But it's there if you run out of other options.
For future reference, here are links to instructions on these utilities:
FIXBOOT Microsoft Corporation
FIXMBR Microsoft Corporation
If you decide to re-install the OS (again) here is a suggestion:
Follow the partitioning steps outlined above. Then proceed only as far as the basic, fully functioning but stable OS installation. Now install your backup software. If you don't have a backup solution already, look for one that allows you to create a bootable disc, that will let you do a complete or partial restore, from your backup file or image. This makes the restore process very quick & easy. One company that makes inexpensive, but high quality utility software, (incl. backup) is Acronis.
Now install Cubase. Test it to verify that it is functioning. Now get a complete backup to that point before going any further. Label it clearly and set it aside. This 1st backup will allow you to restore your system quickly, to this stage in the proceedings (which contains a functioning Cubase installation).
Now finish all critical Windows updates. Do a 2nd backup, label, store.
Now test Cubase again. Ok? If not, restore your 1st backup and re-test. If it works again, then you know where the problem occurred (something in the Windows updates). At this point, you can decide if you want to run without Windows updates (and a connection to the internet
) or proceed downloading a few critical updates at a time... testing Cubase after each session.
When you finish this step, and still have a functioning Cubase system, do a 3rd backup.
Now finish installing all your other programs. Keep it reasonable, you don't want to use your production machine as a software testbed ... unless you are prepared to have it go belly up on you occasionally, perhaps for good. Test again. Ok? Time for a 4th backup.
Follow this procedure and you will always have a working option. Don't forget to test your backups occasionally by restoring a single file or directory/folder tree. It is also a good idea to DISABLE Windows automatic updates on a production machine, if you want to ensure that you know the state of your system at all times. By doing the updates manually, you will know when something changes, and what caused it.
Good luck - Hope this helps!