Kernel Panics non-stop

[keithos27]

I am running the latest MacBook Air (4 GB RAM, 256 GB SSD, 2.04 GHz) with the latest build of Mac OS X (10.6) and the latest build of Parallels Desktop 6 with Windows 7 64-bit installed. I have tried this now on two identical MacBook Air machines (same configuration). Whenever Parallels Desktop is running Windows 7 my computer will intermittently:

A) Freeze up and I cannot move my mouse, or have the computer recognize a keystroke, thus resulting in me having to shut down the computer by holding down the power button.

B) Experience a Kernel Panic on the Mac OS X side again rendering my computer useless and forcing me to shut down by holding down the power button.

I reiterate that this has happened to me multiple times on two MacBook Airs (each clean installs). There is something going on with Parallels and the new MacBook Airs. I have copy/pasted the last two kernel panics into PDF documents and will paste them in as separate posts below. Perhaps someone can help me, please? I am 95% positive I'm going to have to switch to Boot Camp.

Thank you,
Keith

 

[jon boles]

I was getting kernel panics 90%+ of the time a few seconds after starting the VM, the suggestion above fixed the issue. Nice find.

 

[jon boles]

I think I spoke too soon about the boot flags mentioned in the link, but I have found that my KP's occur right after starting the VM, when the VM window with its fancy graphical effect while the VM is starting changes to the VM's BIOS screen. If I have the VM window resized to a large size (as it ends up after shutting down a VM) it will crash, but if I resize it to the smallest size it can be, it won't.

So guys try resizing your VM window to the minimum before starting it and post back whether it works for you.

Looks like you guys at Parallels may have a bug to fix

 

[mikesreach]

Kernal Panic #70

I'm not sure if Parallels is causing this, but I've had up to 4 KP's daily not even using/opening Parallels. So far, this has added up to 70 KP's since July. However Parallels does show up at the top of the list each time in the crash reports, so something is always running in the background even when Parallels is not engaged/running.

The first notice I read involving Parallels causing KP's in Lion was supposedly because of a second party virus scanner that was given out by Parallels as an optional install. However, I didn't and haven't install it.

The other "ify" .kext file extensions that are showing up are a few from AudioHyjack (e.g. sound flower) and Little Snitch. I've removed them and still am getting the panics.

I did add the bootjack text posted here... we'll see if this is the fix. But what an immense pain... so much work lost. good thing I kept Snow Leopard on my MacbookPro!!! Running 10.7.2 and the latest Parallels 7 on an iMac 24" 2.8Ghz w/4 GB RAM.

 

[Parallels User]

@mikesreach
You can try uninstalling Parallels (it won't delete your VMs or settings unless you deliberately tell it to), reboot and see if you still get Kernel Panics.

Whatever the outcome, run a permissions repair before installing PDM7 again (in case what's causing this was an upgrade that wasn't able to update all files because of bad permissions).

 

[mikesreach]

uninstaller?

I think when giving advice that requires software, a link to that software would be extremely helpful. How and where would I find an "uninstaller" for Parallels?

 

[Parallels User]

Maybe you haven't noticed the links in my signature.
And, you maybe haven't also noticed that the .dmg or cd that you used to install PDM has an uninstaller package too.

 

[JohnC]

External Monitor?

keithos27/mikesreach/ others - are you running an external monitor? P6 runs fine on my MBA until I connect an external monitor. Then I get a kp within minutes.
John

 

[FelipeMann]

Funny that you ask.

I'm trying to find the cause of the KP's on my mother's MacPro. So far i did the "Extended Apple Hardware Test" and the "memtest on single-user-mode" (memtest all) and both passed successfully.

To note:
She bought her MacPro abroad and used it abroad without any problems. She got herself a RAM upgrade abroad, went from 4GB to 8GB and still used it abroad for a few more days without any KP's or problems.

She then flew home and followed my instructions, connected it to an external monitor, so she can have more space to work. Since she got home and connected this external monitor she is having KP's, so far as i've noticed, just when she shuts down Parallels, but not always when she shuts it down.

At first i was sure it was the new RAM, but after both tests passed (see above) i am starting to look for another source. Temp is sitting at around 50c-80c max. I have also run Onyx and fixed the permissions.

And now that you asked about the external monitor, could it really be the cause of the KP's (thru Parallels)?

Panic (system crashes) log:

Source: /Library/Logs/DiagnosticReports/Kernel_2012-02-23-222825_Constances-MacBook-Pro.panic
Size: 7 KB (7,284 bytes)
Last Modified: 2/23/12 10:28 PM
Recent Contents: Thu Feb 23 22:28:25 2012
panic(cpu 1 caller 0xffffff80002c266d): Kernel trap at 0xffffff8000644ab2, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x00000001041b3000, CR3: 0x000000005b7b2057, CR4: 0x00000000000606e0
RAX: 0xfbffff8000866d90, RBX: 0xffffff802afdc900, RCX: 0x0000000000000010, RDX: 0xffffff8003cef9a0
RSP: 0xffffff81348d3a30, RBP: 0xffffff81348d3a70, RSI: 0x0000000000000000, RDI: 0xffffff802afd6400
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0xfffffe825eb8db78, R11: 0x00000000002623be
R12: 0x0000000000000080, R13: 0xffffff813566d004, R14: 0x0000000000000010, R15: 0xffffff8015d6f004
RFL: 0x0000000000010202, RIP: 0xffffff8000644ab2, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0x00000001041b3000, Error code: 0x0000000000000000, Faulting CPU: 0x1

Backtrace (CPU 1), Frame : Return Address
0xffffff81348d36f0 : 0xffffff8000220702
0xffffff81348d3770 : 0xffffff80002c266d
0xffffff81348d3910 : 0xffffff80002d7a1d
0xffffff81348d3930 : 0xffffff8000644ab2
0xffffff81348d3a70 : 0xffffff7f81b31a9c
0xffffff81348d3a90 : 0xffffff7f81b3d162
0xffffff81348d3ae0 : 0xffffff7f81b37a4a
0xffffff81348d3ba0 : 0xffffff7f81b33332
0xffffff81348d3be0 : 0xffffff8000652a5e
0xffffff81348d3c40 : 0xffffff800065341b
0xffffff81348d3d80 : 0xffffff80002a3b78
0xffffff81348d3e80 : 0xffffff8000223006
0xffffff81348d3eb0 : 0xffffff8000214829
0xffffff81348d3f10 : 0xffffff800021bb58
0xffffff81348d3f70 : 0xffffff80002aeb80
0xffffff81348d3fb0 : 0xffffff80002d8383
Kernel Extensions in backtrace:
com.parallels.kext.prl_hypervisor(7.0)[00000000-0000-0000-0000-000000000000]@0xffffff7f81b30000->0xffffff7f81b8bfff
dependency: com.apple.iokit.IOPCIFamily(2.6.8)[F63D4ABE-42DA-33EF-BADD-3415B0CB0179]@0xffffff7f80840000
dependency: com.apple.iokit.IOACPIFamily(1.4)[8B3C2276-CD6A-355B-A5F7-A09E4499594B]@0xffffff7f807cd000

BSD process name corresponding to current thread: prl_vm_app

Mac OS version:
11D50b

Kernel version:
Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64
Kernel UUID: 7B6546C7-70E8-3ED8-A6C3-C927E4D3D0D6
System model name: MacBookPro8,1 (Mac-94245B3640C91C81)

 

[FelipeMann]

I decided to do the memtest again, it failed one time out of 5 passes, does this mean one of the memory sticks is bad?

Memtest version 4.22 (64-bit)
Copyright (C) 2004 Charles Cazabon
Copyright (C) 2004 - 2008 Tony Scaminaci (Macintosh port)
Licensed under the GNU General Public License version 2 only

Log file written to /Users/Constance/memtest.log

Mac OS X 10.7.3 (11D50b) running in single user mode
Memory Page Size: 4096
System has 4 Intel core(s) with SSE
Requested memory: 7695MB (8068878336 bytes)
Available memory: 7695MB (8068878336 bytes)
NOTE: Memory request is too large, reducing to acceptable value...
Allocated memory: 7479MB (7842949696 bytes) at local address 0x0000000101000000
Attempting memory lock... locked successfully
Splitting allocated memory into 2 comparison buffers...
Buffer A: 3739MB (3921474848 bytes) starts at local address 0x0000000101000000
Buffer B: 3739MB (3921474848 bytes) starts at local address 0x00000001eabcf520

Running 5 test sequences... (CTRL-C to quit)

Test sequence 1 of 5:

Running tests on entire 7479MB region...
Stuck Address : ok
Linear PRN : ok
Running comparison tests using 3739MB buffers...
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Test sequence 2 of 5:

Running tests on entire 7479MB region...
Stuck Address : ok
Linear PRN : ok
Running comparison tests using 3739MB buffers...
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential :

FAILURE! Data mismatch at local BUFA address 0x0000000187a1bee0, BUFB address 0x00000002715eb400
BUFA Data: 0x1e1e1e1e1e1e1e1e, BUFB Data: 0x1a1e1e1e1e1e1e1e

Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Test sequence 3 of 5:

Running tests on entire 7479MB region...
Stuck Address : ok
Linear PRN : ok
Running comparison tests using 3739MB buffers...
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Test sequence 4 of 5:

Running tests on entire 7479MB region...
Stuck Address : ok
Linear PRN : ok
Running comparison tests using 3739MB buffers...
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

Test sequence 5 of 5:

Running tests on entire 7479MB region...
Stuck Address : ok
Linear PRN : ok
Running comparison tests using 3739MB buffers...
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

*** Memory Test Failed *** Please check logfile for details.
Execution time: 13188 seconds.

 

[WilliamPaul]

I too have the similar problems,really don't know what exactly happening this

 

[jelavich]

To those who have kernel panics, see this article, which explores the same failure message that I was getting, shown below the link.
http://www.embracingchaos.com/2011/...l-panics-and-coping-with-an-apple-genius.html

Kernel Extensions in backtrace (with dependencies):
com.apple.GeForce(6.4.0)@0xc5c000->0xd12fff
dependency: com.apple.NVDAResman(6.4.0)@0x96e000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
com.apple.nvidia.nv50hal(6.4.0)@0x159f000->0x19b3fff
dependency: com.apple.NVDAResman(6.4.0)@0x96e000
com.apple.NVDAResman(6.4.0)@0x96e000->0xc5bfff
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000

Engineering at both Apple and Parallels looked at the failure, and concur that this is a hardware problem, likely in the graphics subsystem. Apple needs to improve their H/W test to screen for this.

The failure would occur regardless of whether or not I was running Parallels. Interestingly, this failure (a black screen, caused by a kernel panic) would not happen happen if the computer had only 4 GB of memory. With 6GB or 8GB, it would crash. The computer was a 15" Macbook Pro 6,2 from 2011, with a 2.8 GHz dual core i7 processor. Wiping it clean and reinstalling the OS did NOT fix anything, though I had no crashes for about a day after doing this. In that time I installed Windoze, and I did get 2 bluescreens while installing Apple's drivers. Then I installed MS Word from 2008. Other than that, there was no 3rd party S/W on the computer. Next I installed Parallels 6. When I launched it it crashed. When I launched it again and resized the window, down it would go. Uninstalling Parallels and re-installing it did not fix it either.

Changing the memory to new Apple memory didn't fix it either.

Apple replaced the computer. The ordeal cost me 60 hours of time, so far. Now I need Windows 7, since the new machines won't run XP, or 10.6 either.