Parallels 3.0 == Kernel Panic City

I installed Parallels 3.0 on 19 August. In the year and a half before installing 3.0 I had a total of 5 kernel panics on this machine. In the week and a half since installing 3.0 I've had 10. I've tried builds 4560, 5060, and 5122; I ran 3188 without problems. Parallels causes a kernel panic reproducibly (100% of the time) on shutting down the VM. But I'm also seeing random panics, even when not running Parallels (note that the Parallels drivers (kexts) run all the time). The stack traces are variable; often they involve the apple NTFS driver (see http://forums.parallels.com/thread15507.html for trace). This is very frustrating.

-c

Mon Mar 20 10:47:26 2006 crashdump[105]: crashdump invoked as panicdump
Mon Feb 5 15:15:54 2007 crashdump[160]: crashdump invoked as panicdump
Tue Jul 10 10:56:03 2007 crashdump[103]: crashdump invoked as panicdump
Tue Jul 24 12:00:37 2007 crashdump[109]: crashdump invoked as panicdump
Sun Aug 5 18:30:42 2007 crashdump[94]: crashdump invoked as panicdump
Sun Aug 19 16:29:04 2007 crashdump[86]: crashdump invoked as panicdump
Sun Aug 19 19:26:07 2007 crashdump[94]: crashdump invoked as panicdump
Sun Aug 19 22:46:40 2007 crashdump[140]: crashdump invoked as panicdump
Mon Aug 20 07:22:33 2007 crashdump[127]: crashdump invoked as panicdump
Mon Aug 20 12:37:25 2007 crashdump[85]: crashdump invoked as panicdump
Mon Aug 20 13:44:19 2007 crashdump[177]: crashdump invoked as panicdump
Mon Aug 20 22:15:00 2007 crashdump[146]: crashdump invoked as panicdump
Sat Aug 25 21:36:37 2007 crashdump[115]: crashdump invoked as panicdump
Mon Aug 27 13:55:20 2007 crashdump[97]: crashdump invoked as panicdump
Tue Aug 28 14:03:25 2007 crashdump[85]: crashdump invoked as panicdump

 

I should note that this is on a Macbook Pro Core Duo 2Ghz with 2GB of RAM and 10.4.10; I
've allocated 500-750 MB to the Windows VM. I've run Apple Hardware Test (including the extended test) with no problems. -c

 

Have you tried this solution - http://kb.parallels.com/entry/21/235/?

 

Not so much.

Immediately after performing the above procedure, even before Parallels had completed booting Windows XP SP2, I got the following kernel panic, my 11th in the week and half since installing Parallels 3.0.

-c

panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00ed5000, CR4: 0x000026e0
EAX: 0x00000000, EBX: 0x00000000, ECX: 0x00008000, EDX: 0x00020000
CR2: 0x00000000, EBP: 0x253d35b8, ESI: 0x3af3d000, EDI: 0x00000000
EFL: 0x00010206, EIP: 0x00196316, CS: 0x00000008, DS: 0x36c40010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x253d3318 : 0x128d08 (0x3cc0a4 0x253d333c 0x131de5 0x0)
0x253d3358 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x253d3468 : 0x19aeb4 (0x253d347c 0x14d7688 0x0 0xe)
0x253d35b8 : 0x973007 (0x0 0x0 0x20000 0x0)
0x253d3658 : 0x972215 (0x0 0x0 0x0 0x20000)
0x253d3718 : 0x972339 (0x9fad800 0x5188200 0x80 0x0)
0x253d3768 : 0x974c94 (0x394f900 0x9fad800 0xa09a9c4 0x0)
0x253d3ad8 : 0x1e839e (0x394f900 0x3ff439c 0xbffffbe0 0x0)
0x253d3b28 : 0x1d5ada (0x394f900 0x3ff439c 0xbffffbe0 0x0)
0x253d3f58 : 0x37ad83 (0xa09a9c4 0x4356af8 0x4356b3c 0x0)
0x253d3fc8 : 0x19b28e (0x4165d60 0x0 0x202 0x384533c) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffffe98
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.ntfs(1.2.1)@0x970000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

 

Here's another:


panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x01798000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x0457c200, ECX: 0x05091b00, EDX: 0x05acc004
CR2: 0x00000000, EBP: 0x25b13358, ESI: 0x00000000, EDI: 0x25b133c0
EFL: 0x00010202, EIP: 0x0019a4b6, CS: 0x00000004, DS: 0x25b1000c

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25b13198 : 0x128d08 (0x3cc0a4 0x25b131bc 0x131de5 0x0)
0x25b131d8 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x25b132e8 : 0x19aeb4 (0x25b132f8 0x25b1330c 0xe 0x48)
0x25b13358 : 0x19a51d (0x0 0x457c200 0x4 0x5b1be70)
0x25b13378 : 0x3df3cff3 (0x0 0x457c200 0x5acc6a4 0x0)
0x25b13ad8 : 0x1e839e (0x5091b00 0x0 0xbffff24c 0x0)
0x25b13b28 : 0x1d5ada (0x5091b00 0x0 0xbffff24c 0x0)
0x25b13f58 : 0x37ad83 (0x577c1f4 0x546d6f0 0x546d734 0x0)
0x25b13fc8 : 0x19b28e (0x56395f8 0x0 0x19e0b5 0x56395f8) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffffd38
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.smbfs(1.3.7)@0x3df34000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

 

My kernel panic = memory problem

Hello,

I cannot say if this is the same problem, but all of my memory panic issues were solved by replacing memory. Parallels caused kernel panic after I upgraded memory to 3Gb. I have not reall had Mac crash while Parallels were nto running, so I suspected the software... But then I got free memtest, booted in single user mode and run memtest. Some tests failed. Got replacement memory from cdw and swapped. Memtest did not fail and I have yet to see kernel panic... It's month later BTW...

Memtest is free, may take little bit of time, but will provide robust test on memory...

Jan