DonationCoder.com Software > Screenshot Captor

Access Violation at address 00480893

(1/2) > >>

kindageeky:
I have been getting this error for months. I was hoping the latest update would squash it, but it didn't.  Using Win 10 on a dual monitor setup. Every time I restart the computer I get this error. And it pops up over 25 times or more so I have a really aggravating amount of windows to close.

I searched the forum, but didn't get any results to show up since 2012, so I'm assuming I'm the only one with the issue.

I'd appreciate any guidance on how I can fix the error.

Access Violation at address 00480893

tomos:
a couple of questions:


* Is it portable or installed SC?
* If portable where is it -- could it be in a folder that it cannot write to?
* Did anything change 10 months ago when the problem started?

tomos:
Another thing could be the folder used for screenshots: whether that was changed; whether you have different types of files in that folder (seems to have been a problem in the past).

kindageeky:
It is installed. And yes I have changed the default save folder, which does contain multiple file types.

Can't think of anything particular that may have happened other than, I stopped being able to use the drawing features around that same time and had to edit in another application. But with the latest update, they are now working again.  :up:

mouser:
Are you using the portable version of screenshot captor or the installer version?
You say the error happens on computer startup.  If you exit Screenshot Captor and restart it manually, do you not get the error? Or does it happen whenever you start screenshot captor?

The first thing you might try is to exit SC and delete the ScreenshotCaptor.ini file to reset any of your screenshot captor options and settings, and see if that fixes it.

If you didn't install SC normally (for example if you copied it over from another machine), you might try uninstalling or deleting it and reinstalling it.

Another thing to try is to use the portable version and see if that has the same problem -- if not then we know it has something to do with where/how it was installed.

Navigation

[0] Message Index

[#] Next page