MS10 access violations

Technical support and scripting issues

Moderators: JRL, Dorian (MJT support)

Post Reply
bnc1
Pro Scripter
Posts: 127
Joined: Sun Jul 31, 2005 5:10 pm

MS10 access violations

Post by bnc1 » Thu Jan 03, 2008 1:43 am

I am now getting consistent MS10.012 access violations on my Vista x64 system.The last thing I did was :
1) uncheck my group properties option to add macros to Quicklaunch
2) updated 3 individual macros properties to use Quicklaunch

Now I get "Access Violation at address 54CDCA in module msched.exe read of address 00000000" after the execution of any macro, whether via the editor or quicklaunch or hotkey. MS freezes and I am forced to kill it via task manager. This is very similar to a problem I had with MS10 beta http://www.mjtnet.com/forum/viewtopic.php?t=4281

Me_again
Automation Wizard
Posts: 1101
Joined: Fri Jan 07, 2005 5:55 pm
Location: Somewhere else on the planet

Post by Me_again » Thu Jan 03, 2008 2:51 am

Try 10.013, see this thead which appears to deal with a similar issue.

bnc1
Pro Scripter
Posts: 127
Joined: Sun Jul 31, 2005 5:10 pm

Post by bnc1 » Thu Jan 03, 2008 2:40 pm

Yes I was well aware of that thread seeing as I posted to it twice. I just didnt think it was the same problem ! duh :o . When I saw that the error address was the same I changed my mind. I tried everything short of reinstalling 10.012 but couldnt get rid of the errors. Installing 10.013 was the solution. Wierd that everything just fell apart after several days of testing. It would be nice know a little more about this problem. Did it just affect Vista x64 users ?

User avatar
Marcus Tettmar
Site Admin
Posts: 7395
Joined: Thu Sep 19, 2002 3:00 pm
Location: Dorset, UK
Contact:

Post by Marcus Tettmar » Thu Jan 03, 2008 3:11 pm

An access violation occurs when you try to read memory that isn't available, or try to read memory you don't have access to, or try to dereference a pointer to memory that was never created in the first place, etc. In this case the problem was that a memory pointer was being freed which in some cases was never created in the first place.

The issue that was fixed could affect anyone, no matter what version of Windows was in use. It was not restricted to 64 bit Vista.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar

Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts