Multiplicity crashes immediately at startup

OS Vista 32bit

When I'm booting my workstation with Vista 32bit multiplicity just immediately crashes.
Also when I try to start it mannually it crashes.
I tried to reinstall it a few times now, but it doesn't work.
In total I think multiplicity worked for 2 till 3 hours.
I got the following detailed information from Vista:

Problem signature:
Problem Event Name: APPCRASH
Application Name: multipl.exe
Application Version: 1.2.0.0
Application Timestamp: 4651c097
Fault Module Name: StackHash_4c7c
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 4c000000
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1043
Additional Information 1: 4c7c
Additional Information 2: b03eff3c0fe8b2ac45c7aef39015c51b
Additional Information 3: d1de
Additional Information 4: 62faed0f7a9690dda8d04150d51f88ff

Anyone knows what to do?
3,065 views 7 replies
Reply #1 Top
I submitted a support ticket about this weeks ago, so far I've gotten no useful feedback.

One person on these forums said it might be related to the trial version only though, you could always take one for the team and buy it and post your results
Reply #2 Top
What version of Multiplicity do you have installed?
Reply #4 Top
I also got the trial installed.
We already bought an license for someone else in the company, but I don't need the program so I'm not going to buy it.
I used it for testing, and now i wanted tot test some different configurations.
Think I'll just try to get in contact with someone of Stardock.
Reply #5 Top
If they actually provide you with some kind of solution, please post it here.
Reply #6 Top
No problem, I will.
But the problem at the moment is that I still haven't got any response on my mail

Edit: At the moment the multiplicity service is started by the local administrator account.
So far I haven't got any problems with multiplicity starting
Reply #7 Top
The only option Stardock gave me for using Multiplicity in Vista was to buy the pro version.
So I recommend that you let the service be started by the local administrator account.