Installed build 4124 this morning and Parallels keeps crashing!!!!!

Robster · Jun 7, 2007

This is the first build of Parallels I have had significant problems with.

I launch the new build and try to install the new drivers but Parallels crashes every time.

Here is the crash log (or as much as I can post anyway) in case it is helpful but build 3188 was working rock solid......

Date/Time: 2007-06-08 07:02:52.384 +0100
OS Version: 10.4.9 (Build 8P2137)
Report Version: 4

Command: Parallels
Path: /Applications/Parallels/Parallels Desktop.app/Contents/MacOS/Parallels
Parent: WindowServer [84]

Version: 3.0 (3.0 Build 4124.0)

PID: 480
Thread: 0

Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000002
Code[1]: 0x00000000

Thread 0 Crashed:
0 com.apple.Foundation 0x9281847f _NSRaiseError + 227
1 com.apple.Foundation 0x9283f23f +[NSException raise:format:] + 57
2 com.apple.Foundation 0x928c74be -[NSObject doesNotRecognizeSelector:] + 123
3 com.apple.Foundation 0x927eb34b -[NSObject(NSForwardInvocation) forward::] + 184
4 libobjc.A.dylib 0x90a5aba1 _objc_msgForward + 49
5 com.apple.CoreFoundation 0x908105a8 CFArrayGetCount + 97
6 com.parallels.desktop 0x00345a03 0x1000 + 3426819
7 com.parallels.desktop 0x00347edd 0x1000 + 3436253
8 com.parallels.desktop 0x00348079 0x1000 + 3436665
9 com.parallels.desktop 0x00348313 0x1000 + 3437331
10 com.parallels.desktop 0x00348c9c 0x1000 + 3439772
11 com.parallels.desktop 0x001345cd 0x1000 + 1258957
12 com.parallels.desktop 0x0037ac9b 0x1000 + 3644571
13 com.parallels.desktop 0x003aad6e 0x1000 + 3841390
14 com.parallels.desktop 0x000ed7c0 0x1000 + 968640
15 com.parallels.desktop 0x00370915 0x1000 + 3602709
16 com.parallels.desktop 0x003758ff 0x1000 + 3623167
17 com.parallels.desktop 0x00387e20 0x1000 + 3698208
18 com.parallels.desktop 0x005fea8b 0x1000 + 6281867
19 com.parallels.desktop 0x005ab0bb 0x1000 + 5939387
20 com.parallels.desktop 0x005ab1d4 0x1000 + 5939668
21 com.parallels.desktop 0x00388d5d 0x1000 + 3702109
22 com.parallels.desktop 0x00041dc9 0x1000 + 265673
23 com.parallels.desktop 0x00006792 0x1000 + 22418
24 com.parallels.desktop 0x000066b9 0x1000 + 22201

Thread 1:
0 libSystem.B.dylib 0x9000a077 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082c2b3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x9083d188 CFRunLoopRun + 60
3 ...yousoftware.desktops.helper 0x1ffba7e3 MDHelperEntry + 157
4 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 2:
0 libSystem.B.dylib 0x9000a077 mach_msg_trap + 7
1 com.apple.CoreFoundation 0x9082c2b3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x9082bace CFRunLoopRunInMode + 61
3 com.apple.audio.CoreAudio 0x9145f41e HALRunLoop::OwnThread(void*) + 158
4 com.apple.audio.CoreAudio 0x9145f239 CAPThread::Entry(CAPThread*) + 93
5 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 3:
0 libSystem.B.dylib 0x900270fc kevent + 12
1 ...ple.CoreServices.CarbonCore 0x90cb6cb4 PrivateMPEntryPoint + 51
2 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 4:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 ...ple.CoreServices.CarbonCore 0x90cb6e59 MPWaitOnQueue + 198
2 com.apple.DesktopServices 0x9270c953 TNodeSyncTask::SyncTaskProc(void*) + 143
3 ...ple.CoreServices.CarbonCore 0x90cb6cb4 PrivateMPEntryPoint + 51
4 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 5:
0 libSystem.B.dylib 0x90049257 semaphore_timedwait_signal_trap + 7
1 com.parallels.desktop 0x0045465d 0x1000 + 4535901
2 com.parallels.desktop 0x0045508c 0x1000 + 4538508
3 com.parallels.desktop 0x003b6836 0x1000 + 3889206
4 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 6:
0 libSystem.B.dylib 0x90037ed7 mach_wait_until + 7
1 libSystem.B.dylib 0x9003a5a2 usleep + 82
2 com.parallels.desktop 0x00648b7a 0x1000 + 6585210
3 com.parallels.desktop 0x0064baac 0x1000 + 6597292
4 com.parallels.desktop 0x0043b9e2 0x1000 + 4434402
5 com.parallels.desktop 0x003b6836 0x1000 + 3889206
6 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 7:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 8:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 9:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 10:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 11:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0065f63c 0x1000 + 6678076
2 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 12:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 13:
0 libSystem.B.dylib 0x9011174f semaphore_timedwait_trap + 7
1 com.parallels.desktop 0x00724f9c 0x1000 + 7487388
2 com.parallels.desktop 0x00659e24 0x1000 + 6655524
3 com.parallels.desktop 0x0096b45b QList<TGDev>::append(TGDev const&) + 379
4 com.parallels.desktop 0x007251d1 0x1000 + 7487953
5 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 14:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 15:
0 libSystem.B.dylib 0x9011174f semaphore_timedwait_trap + 7
1 com.parallels.desktop 0x00724f9c 0x1000 + 7487388
2 com.parallels.desktop 0x00659e24 0x1000 + 6655524
3 com.parallels.desktop 0x0096b45b QList<TGDev>::append(TGDev const&) + 379
4 com.parallels.desktop 0x007251d1 0x1000 + 7487953
5 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 16:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 17:
0 libSystem.B.dylib 0x9011174f semaphore_timedwait_trap + 7
1 com.parallels.desktop 0x00724f9c 0x1000 + 7487388
2 com.parallels.desktop 0x00659e24 0x1000 + 6655524
3 com.parallels.desktop 0x0096b45b QList<TGDev>::append(TGDev const&) + 379
4 com.parallels.desktop 0x007251d1 0x1000 + 7487953
5 libSystem.B.dylib 0x900245c7 _pthread_body + 84

Thread 18:
0 libSystem.B.dylib 0x90024c67 semaphore_wait_signal_trap + 7
1 com.parallels.desktop 0x0064bdd8 0x1000 + 6598104
2 com.parallels.desktop 0x003b6836 0x1000 + 3889206
3 libSystem.B.dylib 0x900245c7 _pthread_body + 84

HumanMedia · Jun 7, 2007

Mine crashes everytime also, and corrupts my virtual machines.

Ive lost my Vista VM completely, but luckily had a backup of my XP VM.

Ive completely uninstalled, set the vm to 1024x768 and restarting windows before running parallels tools, but Parallels tools crashes EVERYTIME and takes the parallels mac host app down with it.

Ive wasted a day trying everything, Im giving up and Ive comeback here to report and download 2.x.

Very disappointed. (yes I know its a beta, but it corrupts so consistently and violently that im fed up)

Robster · Jun 7, 2007

Nope NOT a beta this is SUPPOSED to be a GA product!!!!!!!!!!!!!

My issues are not quite as bad as yours as my VM does not appear to be corrupted.

Does anyone have download of 3188 as I seem to have deleted mine and need to revert before things get too bad.

Cheers.

Robin

ciparis · Jun 8, 2007

Maybe it's a good thing the $39 option wasn't extended. Looks like it may have saved me some headaches.

pointybeard · Jun 8, 2007

I've had the same problem. Upgraded to 4124, from a fully functioning stable installation of the previous version, and as soon as the conversion process was done I recieved a kernel panic. After restarting, my XP VM was no longer readable.. and, in my infinite wisdom, didn't make a backup.

I thought the kernel panic problems for iMacs were long gone, guess I was wrong, and right now, I'm far from impressed. I'd be able to cope with just the kernel panic and a simple downgrade in the mean time, but to have a corrupted VM, losing a bunch of data (nothing too important luckily), is frustrating to say the least. I really hope this is fixed soon.

Robster · Jun 8, 2007

After about 6 quits during the VM Tools installation and reboot process I have now had this release running without a quit for 90 minutes.

LUCKILY I did not get a corrupted VM during these multiple Parallels crashes but I am very unimpressed with the reliability of this version so far.

Robin

kastorff · Jun 8, 2007

I'm having similar issues with Parallels Tools.
http://forum.parallels.com/thread12484.html

This is a very shaky release. I'm reverting to 2.5 as I write.

Olivier · Jun 8, 2007

Could this be related to some machines models? I may be lucky but I'm only positively impressed by this 3.0 version since I installed it 6 hours ago. I had not a single problem. Everything I tested worked (well). I use a MacBook Pro of the first generation (bought it beginning of April 2006). It has 2 GB RAM. I had no issue when installing the Parallels Tools.

Olivier · Jun 8, 2007

Robster said:
After about 6 quits during the VM Tools installation and reboot process I have now had this release running without a quit for 90 minutes.

Did you reboot your Mac after installing Parallels itself and before starting your VMs? This is absolutely required for a safe and correct upgrade or installation.

Robster · Jun 8, 2007

Olivier said:
Did you reboot your Mac after installing Parallels itself and before starting your VMs? This is absolutely required for a safe and correct upgrade or installation.

THREE TIMES.

Initially before doing ANYTHING and then again after the first crash and again after a couple of other crashes.

Robin

ATXP · Jun 8, 2007

Goddamnit! Why do I have to call Microsoft twice to reactivate my Windows XP in BootCamp and Parallels via BootCamp?

pointybeard · Jun 8, 2007

Could this be related to some machines models?

Perhaps. I know in the past the kernel panics were a common problem with the new iMacs. Im on a 24" one.

Did you reboot your Mac after installing Parallels itself and before starting your VMs?

Of course. There is an alert box after installation requesting you restart, and like all good citizens, I did so.

Goddamnit! Why do I have to call Microsoft twice to reactivate my Windows XP in BootCamp and Parallels via BootCamp?

Now that I have lost my XP VM, I will have to go through the whole routine with MS activations. Joy.

fbronner · Jun 8, 2007

Everyone,

Make absolutely sure all of your VM machines were shutdown properly before doing the upgrade. If your XP session was suspended before you did the upgrade you will run into problems.

If you do not let you XP -VM shutdown properly before doing the upgrade, you will run into the problems you described.

So procedure is make sure everything has been shutdown properly. Then do the upgrade. Reboot you Mac. Then you can start up those VM and upgrade them.

Robster · Jun 8, 2007

fbronner said:
Everyone,

Make absolutely sure all of your VM machines were shutdown properly before doing the upgrade. If your XP session was suspended before you did the upgrade you will run into problems.

If you do not let you XP -VM shutdown properly before doing the upgrade, you will run into the problems you described.

So procedure is make sure everything has been shutdown properly. Then do the upgrade. Reboot you Mac. Then you can start up those VM and upgrade them.

Well just to be clear I DID all the above.

Shutdown (and backed up my VM).

Installed V3.

Rebooted.

Updated VM.

Booted XP - CRASH of Parallels while installing new VM Additions.

Restarted Parallels, rerun VM Additions AGAIN Parallels crashed.

Rebooted Mac........etc............

Robin

kastorff · Jun 8, 2007

fbronner said:
Everyone,

Make absolutely sure all of your VM machines were shutdown properly before doing the upgrade. If your XP session was suspended before you did the upgrade you will run into problems.

If you do not let you XP -VM shutdown properly before doing the upgrade, you will run into the problems you described.

So procedure is make sure everything has been shutdown properly. Then do the upgrade. Reboot you Mac. Then you can start up those VM and upgrade them.

Oh come on. I made precisely sure that the VM was shut down properly (and backed up, thank goodness). And rebooted after installing 3.0 before I even opened the VM. This assumption that people did something wrong or were careless during the upgrade is crap. This build is buggy. Very buggy.

tkatz · Jun 8, 2007

I'm having the same problem on both of my VM's (XP and Vista). I made sure both were fully shut down (and up-to-date patch wise). I even uninstalled the tools, shut down, rebooted and attempted an install. I also tried installing under safe mode (saw that suggestion in another post), but just like with the other attempts both VM's crashed near the end of the tools install. On the last attempt of installing on XP the crash corrupted a lot of files in the VM (to the point where I dont have at least keyboard and mouse support, watched those driver files along with many others get truncated during the boot process). I have a backup but will attempt a fresh install later today and see if that goes better.

I'm running this on a MBP 2.33ghz w/ 3gb ram (fully up-to-date OSX) if that matters..

drumbo · Jun 8, 2007

Similar issues here. My original VM crashed continuously (especially when activating coherence). So I created a completely fresh XP VM (just got zonelabs running), got coherence to work once, now it causes a BSOD.

Strange thing was when I first upgraded my parallels install to v3, I shut down as required, however I got to a blue screen with a spinning dial (not the ball), at the bottom/middle of the screen. This stayed there for 20 minutes before I gave up waiting and (force) powered off my macbook pro. When I booted up again, it took far longer to boot than normal (just the once)(about 3-4 minutes whereby I normally boot in about 1 minute). When I logged in, all my startup items had gone - ie. everything I have set to load when I log in.

aaronlyon · Jun 8, 2007

blue screen of death

I have a similar problem. I installed 4124 yesterday and got it working properly using a 15-day trial key. Then this morning I got my real key from element5 and activated Parallels. But now every time I try to launch my XP virtual machine, it starts to load, then flashes the blue screen of death (BSOD) too quickly to see, then returns to the Stopped dialog. I can't get it to boot any more!

Sheppy · Jun 8, 2007

Parallels is crashing every time I try to install the Tools. Including on a fresh VM I created using 3 just today. It also gets into modes where I can only see the bottom left corner of the screen, locks up my Mac, and generally is 100% unusable. This update has been the first one that hasn't worked flawlessly for me, and it's quite a doozy.

davidaf · Jun 8, 2007

I've had my second Kernel Panic since the 3.0 upgrade. This on a Mac Pro, so it's not just an iMac issue. Unfortunately i'll be away from my office for 3 days so I can't even restart the box to find out if the VM is corrupt.

pointybeard said:
I've had the same problem. Upgraded to 4124, from a fully functioning stable installation of the previous version, and as soon as the conversion process was done I recieved a kernel panic. After restarting, my XP VM was no longer readable.. and, in my infinite wisdom, didn't make a backup.

I thought the kernel panic problems for iMacs were long gone, guess I was wrong, and right now, I'm far from impressed. I'd be able to cope with just the kernel panic and a simple downgrade in the mean time, but to have a corrupted VM, losing a bunch of data (nothing too important luckily), is frustrating to say the least. I really hope this is fixed soon.