access violation at address 00C88640 in module dvdpro.exe. Read of address 000042F3

is the error I keep getting, usually upon startup. Sometimes I get the message "Stopped at setting Collection type." I'm on my 6th clean install (deleting everything including databases), 7th database repair, 2nd computer reboot, and a system file checker (Windows found and fixed some errors). I re-loaded my collection including pictures from my online collection. Yet I still get the above error message. It may be time to find other software, I guess. I've usually been able to overcome errors like the one mentioned above through db repairs, but to no avail this time around. It started Friday night (June 21st). Incredibly frustrating.

Eric

Two observations:

Hardware issues:
This could very well be a memory problem. While Windows has it's own memory test, it's not entirely reliable. I know from personal experience. I had a memory problem. Windows memory test did not find it. I had to use memtest86 to locate the problem.

Uninstalling:
The regular uninstallers that come with programs usually only uninstall whatever the installer created, but not anything that was created by the program in question itself. So to be sure that you have uninstalled everything, you need a third party uninstaller. I use Revo Uninstaller. Just make sure that you have a backup of your database (and keep it in a "safe" folder, e.g. not one of DVD Profiler's folder that Revo might uninstall).

So if the memory test shows everything is OK, then do a complete uninstall and re-install, preferably from a freshly downloaded installation file, just to be absolutely sure.

If neither ObiKen's suggestions or the above finds the problem, then I'm at a loss.

I like the advice given by ObiKen and if necessary follow with GSyren's. Report after that, and we can go from there. Quickest way to eliminate hardware issues is to temporarily install on a different machine if possible.

I fully expect Ken's method to work, if the others didn't, but just in case:

(1) Start with a clean database
(2) Install BulkEdit
(3) Tools > Scrapegoat allows you to see any user's online
(4) Download your own database skeleton. This is different from the Invelos version. Bulkedit creates a database of new blank profiles using the profile IDs from the online.
(5) Then refresh the database from the online. If it still crashes, you should be able to figure out which profile it crashed on and delete it. Corrupt profiles are often due to bad data in the overview.

Well, you got it done, that's what matters.