Panic kernal trap

Hi my macbook came up with this, please help!
Anonymous UUID:
F870381A-1949-A1A5-FD11-2785C6DDCF97
Sat Jul 12 21:30:47 2014
panic(cpu 0 caller 0xffffff800f2dbf5e): Kernel trap at 0xffffff800f2c68c0, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000000, CR3: 0x00000000756d7050, CR4: 0x00000000001606e0
RAX: 0xffffff800f8d4a28, RBX: 0xfffffea34d992fe8, RCX: 0x0000000000000000, RDX: 0xfffffea140000000
RSP: 0xffffff811214ba20, RBP: 0xffffff811214ba80, RSI: 0x0000000000000060, RDI: 0x00000000001a5d14
R8: 0xffffff811214bb40, R9: 0x000000012fd06000, R10: 0x0000000000080040, R11: 0x0000000000000206
R12: 0x00007fff77a90000, R13: 0xffffffffffffff9f, R14: 0xffffff801fb53280, R15: 0x00630059005a0062
RFL: 0x0000000000010246, RIP: 0xffffff800f2c68c0, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff811214b6b0 : 0xffffff800f222fa9
0xffffff811214b730 : 0xffffff800f2dbf5e
0xffffff811214b900 : 0xffffff800f2f3456
0xffffff811214b920 : 0xffffff800f2c68c0
0xffffff811214ba80 : 0xffffff800f290c6b
0xffffff811214bd80 : 0xffffff800f28a3fb
0xffffff811214be50 : 0xffffff800f289627
0xffffff811214bf20 : 0xffffff800f5d4e83
0xffffff811214bf50 : 0xffffff800f640653
0xffffff811214bfb0 : 0xffffff800f2f3c56
BSD process name corresponding to current thread: firefox
Mac OS version:
13D65
Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide:
0x000000000f000000
Kernel text base: 0xffffff800f200000
System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)
System uptime in nanoseconds: 172544437854133
last loaded kext at 172033309529496: com.apple.driver.AppleIntelMCEReporter    104 (addr 0xffffff7f912cd000, size 49152)
last unloaded kext at 172183613264694: com.apple.driver.AppleIntelMCEReporter    104 (addr 0xffffff7f912cd000, size 32768)
loaded kexts:
com.parallels.virtualsound    1.0 18
com.apple.filesystems.smbfs    2.0.2
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleUpstreamUserClient    3.5.13
com.apple.iokit.IOBluetoothSerialManager    4.2.4f1
com.apple.driver.AudioAUUC    1.60
com.apple.driver.X86PlatformShim    1.0.0
com.apple.driver.AGPM    100.14.15
com.apple.driver.ApplePlatformEnabler    2.0.9d1
com.apple.driver.AppleHDA    2.6.1f2
com.apple.iokit.IOUserEthernet    1.0.0d1
com.apple.driver.AppleLPC    1.7.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport    4.2.4f1
com.apple.driver.AppleSMCLMU    2.0.4d1
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleHWAccess    1
com.apple.driver.AppleThunderboltIP    1.1.2
com.apple.driver.AppleCameraInterface    4.26.0
com.apple.driver.AppleBacklight    170.3.5
com.apple.driver.AppleMCCSControl    1.1.12
com.apple.driver.AppleIntelHD5000Graphics    8.2.6
com.apple.driver.AppleIntelFramebufferAzul    8.2.6

That doesn't look like the entire kernel panic log, but I agree with OGELTHORPE in that you should delete the parallels.virtualsound startup item. It look as if you had Parallels Desktop installed at one time, but - somehow - tried to delete all of it, but didn't succeed.
That's not the current version of the Parallels virtual sound kext, anyway.
Clinton
MacBook Pro (15-inch Late 2011), OS X Mavericks 10.9.5, 16GB Crucial RAM, Crucial M500 960GB SSD, 27” Apple Thunderbolt Display

Similar Messages

Unresolved kernal trap

My eMac had been running well and doing as it should. Within the past few weeks it has started to freeze up with the screen shadowed and a message appearing in the center saying "Your computer needs to be restarted. Hold down the power button for a few seconds or press restart."
When I restart it asks if I want to send a report, which I always do. The report begins with the words "Unresolved kernal trap" followed by code. Once in a while it alters and begins with the word "Panic" followed by code.
It seems to be doing it more and more, now two or three times a day. It sometimes happens when I am in the middle of something and it gets very irritating.
Any suggestions as to what's causing it would be appreciated.

In addition to checking your eMac serial number against those in eMac Repair Extension Program for Video and Power Issues, see if the eMac's logs give any clues whether the problem might be with some third-party background process: Refer to What’s a kernel panic? for info on where to find the logs. Since eMacs running 10.5 are fairly rare, if you need help interpreting the logs, you can post excerpts from the logs in the Leopard forums to reach a large knowledgeable audience.

Kernal trap crash with sleep mode

Hi,
After installing the newest OSX my mac crashes randomly when being opened after having been on sleep mode for some time.
Here's the problem report - can someone please explain to me what the problem is and how to fix it, thanks!
I find it strange that it doesn't crash everytime... a kernal trap is a kernal trap, right (whatever a kernal trap might be, anyway)!?
Help is greatly appreciated!
Mon Jan 26 22:30:46 2009
panic(cpu 0 caller 0x001A9C68): Kernel trap at 0x06de3201, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x018dc000, CR4: 0x00000660
EAX: 0x07c37100, EBX: 0x0890af00, ECX: 0x0000070c, EDX: 0x00000000
CR2: 0x00000000, EBP: 0x6a347e38, ESI: 0x00000000, EDI: 0x06ec7000
EFL: 0x00010206, EIP: 0x06de3201, CS: 0x00000008, DS: 0x06eb0010
Error code: 0x00000000
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x6a347c18 : 0x12b4f3 (0x45b13c 0x6a347c4c 0x1335e4 0x0)
0x6a347c68 : 0x1a9c68 (0x464700 0x6de3201 0xe 0x463eb0)
0x6a347d48 : 0x1a038d (0x6a347d60 0x6e91200 0x6a347e38 0x6de3201)
0x6a347d58 : 0x6de3201 (0xe 0x23950048 0x6a340010 0x6eb0010)
0x6a347e38 : 0x6a6d98 (0x6ec82b4 0x6eb7200 0x6a347e68 0x3ece8f)
0x6a347e88 : 0x6a6efa (0x6ec7000 0xe00002eb 0x0 0x10)
0x6a347ea8 : 0x6e4c57 (0x6ec7000 0x50d0111c 0x0 0xffffffff)
0x6a347ed8 : 0x6e64bd (0x6ec2000 0x1 0x53f69c 0x2)
0x6a347f18 : 0x4224ff (0x6ec2000 0x6ee0200 0x2 0x6ebf940)
0x6a347f68 : 0x42165c (0x6ee0200 0x0 0x1 0x0)
0x6a347f98 : 0x42133e (0x6e91200 0x6a347fdc 0x6a347fc8 0x1a8ddc)
0x6a347fc8 : 0x1a017c (0x6e91200 0x0 0x1a018b 0x7441be0)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWOHCI(3.7.2)@0x6df000->0x700fff
dependency: com.apple.iokit.IOFireWireFamily(3.4.6)@0x6a0000
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5ff000
com.apple.iokit.IOFireWireFamily(3.4.6)@0x6a0000->0x6defff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBookPro5,1 (Mac-F42D86C8)

OK, I'll try that. I'll disconnect the soundcard and try putting it to sleep and wakening it again.
It's getting late in Denmark and I have to get up early to go to work. My next post will be around the same time tomorrow.
Thanks for your help!
- Daniel

Panic Kernal: You need to restart your computer, Help please...

Yesterday I installed an update on my MacBook and everything went haywire. I installed the Apple updates
that were recommended for my computer when it did it's weekly update
check. After the install I quit all open applications and did a
restart per the on screen prompt. Finder closed and the computer just
sat for over a half hour and never would finish shutting down. No key
strokes or commands would do anything. As a last ditch effort I held
the power key down until it shut down. I waited a minute then powered
back up. The gray screen with the apple logo comes up then the spinning wheel. Then a
panic kernal saying the computer needs to be restarted. I tried ten
times then I reset the PRAM then I did two hardware checks. First the
short check then the long one. Both tests showed all hardware to be
fine.Then I called Apple. They told me to reset the PRAM, told me to
do a hardware check then told me to boot in safe mode. Then told me to
try an archive reinstall by inserting disc one, power on, then hold
the C key after the startup chime sounds. One of two things happen
when this is done, it either goes to a blank blue screen or the "You
need to restart the computer" message comes up. If I power on with the
disc in and hold the option key the hard drive and the disc shows on
the screen. If I click on the hard drive the "restart message comes up. If I
click on the disc the blank blue screen usually comes up but twice the
"restart" message came up. I have tried all of the start-up key strokes, Once I got into safe mode but I can't get into it anymore, it now gives the you need to restart message. I can get into Verbose and Single user mode but I don't know of anything to try once I'm in either of those modes.I tried to boot system from single user mode by typing in the command sh /etc/rc but a long list of code just comes up and says something about the panic kernal which I believe is telling me that the same problem
I have trying a normal boot is keeping it from booting in single user mode also. I can do a hardware test(I've done this 3 times and everything shows to be OK). The main problem I have now is it won't boot normally and it won't boot from the install disc so I am truly stuck. I am at a loss as to what I should try next
since I can't even reinstall the software. Any help will be greatly
appreciated especially since my free phone help ended 2 days ago and
today was the first time I ever needed it!!
thanks, Jason

Thanks for replying, I have no peripherals attached, I am booting from the MacBook Tiger DVD one that came with the machine. I get the panic kernal with or without the disc installed. All hardware checks out fine in the three hardware checks I've done. I am almost positive the problem is stemming from the Apple updates performed since this is exactly when my problems began(trying to restart after the Apple updates). I just can't get the machine to boot from the disc no matter what I try so I can reinstall the operating system. I even tried using an external DVD-ROM once to see if it would boot from it but it did the exact same thing as when I try booting from the internal drive. Yes my files are backed up to an external hard drive. I've got no problem doing a Nuke and Repave if I must but since it won't boot from the disc I don't know how I can even do this. I know it is under warranty but since the hard ware checks OK it looks like there would be a way to get it running again without sending it in for repairs. However I am starting to think that's what I'm gonna have to do. I'm just glad I still have an old clamshell iBook to work with so I can access the internet to seek help. Thanks for your input, can you think of anything else I could try?

Panic Kernel Trap on MBA

Here's what happened and I hope y'all can give me some solutions -
My computer was running slowly so I reset the PRAM like what's been suggested on the boards here. It really helped to speed up the computer and I got it to boot and got into it (which I hadn't been able to do). I was trying to synch my iPhone and got the message that iTunes needed to be updated. I clicked okay and then I got a message that Mountain Lion needed an update. I clicked okay - this morning I am unable to get the computer to boot (except for in the safe mode boot). I get a panic kernel trap message
After this message displays, the computer then restarts on its own and displays this kernel trap message again. I have not been able to boot the computer today at all. Is there any way to boot the computer and get around this message? I am trying to get the computer to load so I can save my music and photos in the case that I have to erase the drive and re-install software. I don't have any disk to use to reformat my computer since I downloaded Mountain Lion through the iTunes Store. So any advice on how to fix my computer would be greatly appreciated. I just don't know how to proceed in order to get my computer fixed.
Thanks guys!!

I stand corrected: I cannot boot up in safe mode. I get the panic kernel trap that comes up and the computer restarts on its own. It has gone through this loop of saying there was a problem and the computer must restart, then it restarts and displays this message and restarts again.
I am only able to access the disk utilties, nothing else. So I'm pretty sure the only thing I will be able to do is reinstall the OS. I'm not sure how i can do that when I don't have a disk to use though. Hopefully someoone has some idea that will help me.
Thanks again!
Gretchen

PANIC KERNAL!!!

Hello,
I have a Power Mac G4 Mirror Drive Doors. I keep getting Panic Kernals. I have tried everything from reformatting the boot volume ,Disk Warrior reinstalling the OS and I even called the Geek Squad to come out what a mistake that was!
Man that crap is such a gimmick. They just ran some hardware scans on everything and everything checked out except for a video card that might be past its prime. So I have ordered a new video card and will wait until that arrives then I could trouble shoot even more. Has anyone ever had this problem?? also if a LEVEL 5 guy could help me out that would be swell.

Do everything, in order, in Dr.Smokes Resolving Kernel Panics and don't leave out any steps.
Quote from Dr.Smoke "My FAQ is a roadmap: start at the beginning and work through to the end, following the instruction in the order specified, including the "If all else fails..." section if a cause or resolution is not found in an earlier troubleshooting step therein"
Here's more at a brody's KP site.
Cheers!
DALE

Panic kernal attack when upgrading OS

The last 4 times I have attempted to update from Lion to Mountain Lon and 1 try on Mavericks, I have gotten a panic kernal attack on the initial reboot. I then have to rebuild my Mac from Lion. Apple support has been unable to help me and I really don't want to do a complete clean install. The last time there must have been some damage of some type done as my MacBook Pro now runs quite slow even after Disk & Permissions were checked and corrected. Can anyone give me some help on this? I am currently at 10.7.5 on 2.53Ghz Intel Core i5 with 8GB 1067 MHz DDR3 memory.

Boot with the D key and run the hardware test.
You should backup your data before upgrading anything. Once backed up we can isolate your problem further.

Panic Kernal... is all lost?

So I am getting the classic Panic Kernal Screen that tells me I must restart my computer. I have done so many times, however, I cannot get it past the startup gray screen with the white apple. I have looked at all trouble shooting ideas in forums and on the web and they all say to boot from the start-up disc and do an archived re-install. I have tried holding down "C", and holding down "X" and also holding down "OPTN" and still it locks up and tells me to re-start. is there another way to boot from the disc and re-install OS 10.4?
Thanks so much!

HI Eric,
When you hold down the C key are you booting from your install disk?
*"is there another way to boot from the disc and re-install OS 10.4?"*
Mac OS X 10.4, 10.5: About installation options
You can try booting from your Tiger disk and do an erase and install.
Try booting with only the keyboard and mouse connected. Disconnect any other peripherals.
Try booting in Safe Mode
Carolyn

G5 Panic Kernal problem

Christ! The hoops I had to jump through just to post this...anyway I had a panic kernel and want to know what to do about it - here are the details:
Home computer:
Machine Name: Power Mac G5
Machine Model: PowerMac7,3
CPU Type: PowerPC G5 (2.2)
Number Of CPUs: 2
CPU Speed: 2 GHz
Hard drives - 2 internal.
Serial-ATA Bus:
ST3160023AS:
Capacity: 149.05 GB
Model: ST3160023AS
Revision: 3.05
Serial Number: 3JS436TR
Removable Media: No
Detachable Drive: No
BSD Name: disk1
Protocol: ata
Unit Number: 0
Socket Type: Serial-ATA
Bay Name: "A (upper)"
OS9 Drivers: No
S.M.A.R.T. status: Verified
Volumes:
Hard Drive:
Capacity: 148.92 GB
Serial-ATA Bus:
Maxtor 6Y160M0:
Capacity: 152.67 GB
Model: Maxtor 6Y160M0
Revision: YAR511W0
Serial Number: Y486LH9E
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Protocol: ata
Unit Number: 0
Socket Type: Serial-ATA
Bay Name: "B (lower)"
OS9 Drivers: No
S.M.A.R.T. status: Verified
Volumes:
Vicki:
Capacity: 2.88 GB
Available: 1.92 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s3
Mount Point: /Volumes/Vicki
Dave:
Capacity: 149.54 GB
Available: 122.68 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk0s5
Mount Point: /Volumes/Dave
FireWire Bus - 2 external connected drives
Maximum Speed: Up to 800 Mb/sec
LaCie d2 Extreme LUN 0:
Manufacturer: LaCie Group SA
Model: 0x0
GUID: 0xD04B6A0A04B57C
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 800 Mb/sec
Dave's External HD:
Capacity: 297.96 GB
Available: 249.61 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk3s10
Mount Point: /Volumes/Dave's External HD
1394 Storage Front Panel*:
Manufacturer: Maxtor
Model: 0x5000
GUID: 0x10B920001EC9D6
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Deep Thought1:
Capacity: 114.37 GB
Available: 113.56 GB
Writable: Yes
File System: HFS+
BSD Name: disk2s3
Mount Point: /Volumes/Deep Thought1
Memory:
DIMM
256 x 4
512 x 2
all DDr SDRAM
speed:PC3200U-30330
Just before the kernal panic happened:
Machine in 'sleep' mode, woke by using space bar.
Opened up ical, clicked on red button to closed ical window (not quit) and kernal screen appeared.
Log:
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
Tue Jan 8 19:32:19 2008
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000008C PC=0x00000000002C9490
Latest crash info for cpu 0:
Exception state (sv=0x45586000)
PC=0x002C9490; MSR=0x00009030; DAR=0x0000008C; DSISR=0x40000000; LR=0x0003CA1C; R1=0x2CB13DC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002C9438 0x0003CA1C 0x000A9714
Proceeding back via exception chain:
Exception state (sv=0x45586000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x459A3A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x45586000)
PC=0x002C9490; MSR=0x00009030; DAR=0x0000008C; DSISR=0x40000000; LR=0x0003CA1C; R1=0x2CB13DC0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x002C9438 0x0003CA1C 0x000A9714
Exception state (sv=0x459A3A00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
Dave
U.K

Not me, try this;
You are experiencing a Kernel Panic as seen and described in Apple doc.#106227. If not, disregard.
FJ has some good KP tips.
Here's the most used site for Resolving Kernel Panics. Please do all the steps in order, even if you don't think you need to do a certain step.
 Luck! DALE

Unresolved Kernal Trap OSX 10.4.11...HELP!

The Mac Pro I've been using in the studio keeps having a kernal panic and shutting down to the black screen where I must hold down the power button to restart. I saved the error message upon rebooting and was hoping someone on here could shed some light on what's going on. I'm running OSX 10.4.11 on a fully upgraded Mac Pro with 16 GB of ram.
Here is the message as follows:
panic(cpu 1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000134, CR3: 0x01090000, CR4: 0x000006e0
EAX: 0x1484b600, EBX: 0x004ea7bd, ECX: 0x00397a6e, EDX: 0x1484ce00
CR2: 0x00000134, EBP: 0x551a3c98, ESI: 0x1484ced4, EDI: 0x13833db8
EFL: 0x00010246, EIP: 0x00000134, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x551a3a28 : 0x128d1f (0x3c9540 0x551a3a4c 0x131df4 0x0)
0x551a3a68 : 0x1a3135 (0x3cf1f4 0x1 0xe 0x3cea24)
0x551a3b78 : 0x19a8d4 (0x551a3b90 0x5342fc 0x551a3bc8 0x399342)
0x551a3c98 : 0xaea907 (0x1484ce00 0x4ea7bd 0x0 0x1)
0x551a3ce8 : 0xaeb559 (0x139e0f00 0x0 0x4ea7bd 0x0)
0x551a3d18 : 0x3b0844 (0x14734100 0x13833dac 0x140bb594 0x1c)
0x551a3d68 : 0x18a187 (0x14734100 0x4 0x13833dac 0x1c)
0x551a3db8 : 0x12b4da (0x13833d84 0x140bb56c 0x0 0x0)
0x551a3df8 : 0x124b2b (0x13833d00 0x0 0x48 0x551a3edc)
0x551a3f08 : 0x1955a1 (0x551a3f44 0x0 0x0 0x0)
0x551a3fc8 : 0x19ad4e (0x145b4d80 0x0 0x19d0b5 0x14104000) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0283908
Kernel loadable modules in backtrace (with dependencies):
com.motu.driver.USBMidiKext(1.3.4)@0xae9000
dependency: com.apple.iokit.IOUSBFamily(2.6.1)@0x530000
Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386
Model: MacPro1,1, BootROM MP11.005C.B01, 4 processors, Dual-Core Intel Xeon, 3 GHz, 16 GB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: DIMM Riser A/DIMM 1, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 3, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 4, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 3, 2 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 4, 2 GB, DDR2 FB-DIMM, 667 MHz
Network Service: Built-in Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
PCI Card: pci-bridge, sppci_pci2pcibridge, Slot-2
Serial ATA Device: WDC WD2500JS-41SGB0, 232.89 GB
Serial ATA Device: MAXTOR STM3320620AS, 298.09 GB
Serial ATA Device: MAXTOR STM3320620AS, 298.09 GB
Parallel ATA Device: OPTIARC DVD RW AD-7170A
USB Device: My Passport 071A, Western Digital, Up to 480 Mb/sec, 500 mA
USB Device: Vendor-Specific, Up to 12 Mb/sec, 500 mA
USB Device: Microsoft IntelliMouse® Optical, Microsoft, Up to 1.5 Mb/sec, 500 mA
USB Device: MIDI Express XT, Up to 12 Mb/sec, 500 mA
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
FireWire Device: built-in_hub, unknown_value, Unknown
Any help with this would be very much appreciated. I really need to get my work done.

Understanding crash logs isn’t easy and it’s hard (sometimes impossible) to decipher the cause of the problem. Take a look at Apple’s Crash Reporter document at http://developer.apple.com/technotes/tn2004/tn2123.html Also look at Tutorial: An introduction to reading Mac OS X crash reports
http://www.macfixit.com/article.php?story=20060309075929717
Kernel panics are usually caused by a hardware problem – frequently RAM, a USB device or a Firewire device. What external devices do you have connected? When trying to troubleshoot problems, disconnect all external devices except your monitor, keyboard and mouse. Do you experience the same problems?
To eliminate RAM being the problem, Look at this link: Testing RAM @ http://guides.macrumors.com/Testing_RAM Then download & use Memtest & Ramber.
Do you have an Apple Hardware Test disc (the AHT is on the Install/Restore DVD that came with your Mac)? Running the Apple Hardware Test in Loop Mode is an excellent troubleshooting step for finding intermittent hardware problems. It is especially useful when troubleshooting intermittent kernel panics. If Loop Mode is supported by the version of the Apple Hardware Test you are using, you run the Extended Test in Loop Mode by pressing Control-L before starting the test. Looping On should appear in the right window. Then click the Extended Test button.The test will run continuously until a problem is found. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure.In some cases, RAM problems did not show up until nearly 40 loops, so give it a good run.
May be a solution on one of these links.
http://docs.info.apple.com/article.html?artnum=106227 What's a "kernel panic"? (Mac OS X)
http://www.macmaps.com/kernelpanic.html Mac OS X Kernel Panic FAQ
http://www.index-site.com/kernelpanic.html Mac OS X Kernel Panic FAQ
http://www.thexlab.com/faqs/kernelpanics.html Resolving Kernel Panics
http://www.macfixit.com/article.php?story=20060911080447777 Avoiding and eliminating Kernel panics
http://macosg.com/group/viewtopic.php?t=800 12-Step Program to Isolate Freezes and/or Kernel Panics
 Cheers, Tom

Unresolved kernal trap - can anyone decipher?

Following is the info after a forced restart. I don't know how to interpret this but am looking for advice from anyone that can. I suspect bad RAM although it checks out ok. I get numerous cursor hangs and occassional white on black text overlayed on screen (kernal panics?) many times while the machine is basically idle as ws the case in the example below. Thanks for any help that can be provided.
Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x00000000433D2000 PC=0x0000000000032D8C
Latest crash info for cpu 0:
Exception state (sv=0x47DD5000)
PC=0x00032D8C; MSR=0x00083030; DAR=0x433D2000; DSISR=0x42000000; LR=0x0003415C; R1=0x2C8DBDD0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x003D8020 0x0003415C 0x000A9314
Proceeding back via exception chain:
Exception state (sv=0x47DD5000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x00DE1500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x47DD5000)
PC=0x00032D8C; MSR=0x00083030; DAR=0x433D2000; DSISR=0x42000000; LR=0x0003415C; R1=0x2C8DBDD0; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x003D8020 0x0003415C 0x000A9314
Exception state (sv=0x00DE1500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPCModel: PowerBook5,9, BootROM 4.9.6f0, 1 processors, PowerPC G4 (1.5), 1.67 GHz, 2 GB
Graphics: ATI Mobility Radeon 9700, ATY,RV360M11, AGP, 128 MB
Memory Module: SODIMM0/J20STANDARD, 1 GB, DDR2 SDRAM, PC2-3200S-288
Memory Module: SODIMM1/J23REVERSED, 1 GB, DDR2 SDRAM, PC2-3200S-288
AirPort: AirPort Extreme, 405.1 (3.90.34.0.p18)
Modem: Jump, V.92, Version 1.0
Bluetooth: Version 1.7.8f2, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci106b,4318, sppci_othernetwork, SLOT-A
PCI Card: TXN,PCIXXXX-00, cardbus, PC Card
PCI Card: usb, usb, USB20
PCI Card: usb, usb, USB20
PCI Card: usb, ehci, USB20
Parallel ATA Device: Hitachi HTS721010G9AT00, 93.16 GB
Parallel ATA Device: MATSHITADVD-R UJ-846
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
my comments to Apple:
Had a VNC connection going to a local iMac running 10.4.8 (17" G4 USB 2.0)
Had actually stepped away for supper and the PB was not really doing anything other than idling. When I came back to it, found the restart message.
I also have random hangs and occassional white on black screen overwrites with errors requiring restart.
Suspect bad RAM?

One week now with the Samsung RAM - no cursor freezes or kernal panics, and like others have indicated, the unit is running somewhat cooler as noted by temperature monitor.
Extension of another discussion - Re: A way to stop the Freezes in some PowerBooks.

IPQoS panic: BAD TRAP in module "flowacct" due to NULL pointer.

I've recently started using IPQoS and the flowacct module to do some very simple tracking of bandwidth usage (along with one tokenmt action to meter traffic to and from one particular zone) on a host with multiple zones, running Solaris 10 x86, 118844-30. This host has been otherwise stable to date. A couple of hours ago, I got a kernel panic, apparently caused by flowacct:
Dec 21 07:31:46 sol genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=d6e169a4 addr=8 occurred in module "flowacct" due to a NULL pointer dereference
Dec 21 07:31:46 sol unix: [ID 100000 kern.notice]
Dec 21 07:31:46 sol unix: [ID 839527 kern.notice] named:
Dec 21 07:31:46 sol unix: [ID 753105 kern.notice] #pf Page fault
Dec 21 07:31:46 sol unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x8
Dec 21 07:31:46 sol unix: [ID 243837 kern.notice] pid=22655, pc=0xf7cad802, sp=0xd, eflags=0x10283
Dec 21 07:31:46 sol unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6d8<xmme,fxsr,pge,mce,pse,de>
Dec 21 07:31:46 sol unix: [ID 936844 kern.notice] cr2: 8 cr3: ab02000
Dec 21 07:31:46 sol unix: [ID 537610 kern.notice]      gs: 1b0 fs: d6250000 es: d6e10160 ds: fe870160
Dec 21 07:31:46 sol unix: [ID 537610 kern.notice]      edi: d3b25938 esi: d3b26838 ebp: d6e16a18 esp: d6e169d4
Dec 21 07:31:46 sol unix: [ID 537610 kern.notice]      ebx: db0853b4 edx: d3b26828 ecx: 0 eax: 0
Dec 21 07:31:46 sol unix: [ID 537610 kern.notice]      trp: e err: 2 eip: f7cad802 cs: 158
Dec 21 07:31:46 sol unix: [ID 717149 kern.notice]      efl: 10283 usp: d ss: d65fd9c0
Dec 21 07:31:46 sol unix: [ID 100000 kern.notice]
Dec 21 07:31:46 sol genunix: [ID 353471 kern.notice] d6e16904 unix:die+a7 (e, d6e169a4, 8, 0)
Dec 21 07:31:46 sol genunix: [ID 353471 kern.notice] d6e16990 unix:trap+fc8 (d6e169a4, 8, 0)
Dec 21 07:31:46 sol genunix: [ID 353471 kern.notice] d6e169a4 unix:cmntrap+83 ()
Dec 21 07:31:46 sol genunix: [ID 353471 kern.notice] d6e16a18 flowacct:flowacct_update_flows_tbl+337 (d65fd9c0, d3b25000)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16a34 flowacct:flowacct_process+85 (d6e16a4c, d3b25000)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16a50 flowacct:flowacct_invoke_action+32 (d, dfa9cd00)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16a7c genunix:ipp_packet_process+fc (d6e16a94)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16a9c ip:ip_process+85 (2, d6e16ac8, 2)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16ac0 ip:ip_wput_attach_llhdr+92 (dccbf020, d92d61f8,)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16b50 ip:ip_wput_ire+1792 (d7196ee0, dccbf020,)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16ba8 ip:ip_output+70a (d7414e80, dccbf020,)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16bc0 ip:ip_wput+14 (d7196ee0, dccbf020)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16bf4 unix:putnext+1b7 (d7196ee0, dccbf020)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16c40 udp:udp_wput+380 (d5aabc98, dcf78360)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16c74 unix:putnext+1b7 (d5aabc98, dcf78360)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16d54 genunix:strput+16b (d9ad6138, dcf78360,)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16d90 genunix:kstrputmsg+1df (d5c24cc0, dcf12660,)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16e0c sockfs:sosend_dgram+1ca (d5c32d60, dc3504d0,)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16e50 sockfs:sotpi_sendmsg+3f1 (d5c32d60, d6e16ecc,)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16e90 sockfs:sendit+105 (16, d6e16ecc, d6e16)
Dec 21 07:31:47 sol genunix: [ID 353471 kern.notice] d6e16f8c sockfs:sendmsg+131 (16, ce4d5cc4, 8000,)
I had a single "kstat -m flowacct 90" running at the time, but the timing doesn't particularly coincide. My flowacct setting look like this:
action {
module flowacct
name zone1
params {
global_stats TRUE
timer 10000
timeout 10000
max_limit 2048
next_action continue
Pretty much a cut and paste from the Solaris 10 IPQoS documentation. This configuration didn't suffer any similar problems on a test host.
I've searched various places, not had any joy. Obviously, I'm down a while on kernel patching (ironically, I've been holding off to minimise downtime for users, and now this.) But, while 118855-19 does replace some of objects in question, I see no mention of any particular fix for this problem. I'm going to go ahead with patching to 118855-19 (and whatever else smpatch recommends) within the next few days, but I've disabled IPQoS. I'm a little nervous about switching it back on on a production server. Shame.
Anyone had any similar experiences with flowacct?
Cheers,
Chris.

Good news, everyone! A repeat on a test host that's patched up to date as of last week, including kernel 118855-19. I'd tell you what smpatch thinks is missing, but "Failure: Response code was 403".
Dec 23 09:43:14 crippen ^Mpanic[cpu0]/thread=d3275de0:
Dec 23 09:43:14 crippen genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=d3275924 addr=8 occurred in module "flowacct" due to a NULL pointer dereference
Dec 23 09:43:14 crippen unix: [ID 100000 kern.notice]
Dec 23 09:43:14 crippen unix: [ID 839527 kern.notice] sched:
Dec 23 09:43:14 crippen unix: [ID 753105 kern.notice] #pf Page fault
Dec 23 09:43:14 crippen unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x8
Dec 23 09:43:14 crippen unix: [ID 243837 kern.notice] pid=0, pc=0xf9a413ae, sp=0x6, eflags=0x10286
Dec 23 09:43:14 crippen unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 698<xmme,fxsr,pge,pse,de>
Dec 23 09:43:14 crippen unix: [ID 936844 kern.notice] cr2: 8 cr3: 4cdc000
Dec 23 09:43:14 crippen unix: [ID 537610 kern.notice] gs: fe8801b0 fs: fe830000 es: d4890160 ds: d4890160
Dec 23 09:43:14 crippen unix: [ID 537610 kern.notice] edi: d489b6a0 esi: d489b838 ebp: d32759a0 esp: d327595c
Dec 23 09:43:14 crippen unix: [ID 537610 kern.notice] ebx: d66187f4 edx: d489b828 ecx: 0 eax: 0
Dec 23 09:43:14 crippen unix: [ID 537610 kern.notice] trp: e err: 2 eip: f9a413ae cs: 158
Dec 23 09:43:14 crippen unix: [ID 717149 kern.notice] efl: 10286 usp: 6 ss: d6d35d80
Dec 23 09:43:14 crippen unix: [ID 100000 kern.notice]
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275884 unix:die+a7 (e, d3275924, 8, 0)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275910 unix:trap+103f (d3275924, 8, 0)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275924 unix:cmntrap+9a (fe8801b0, fe830000,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d32759a0 flowacct:flowacct_update_flows_tbl+337 (d6d35d80, d489a000)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d32759b8 flowacct:flowacct_process+85 (d32759d0, d489a000)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d32759d4 flowacct:flowacct_invoke_action+32 (6, d5441f80)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275a00 genunix:ipp_packet_process+fc (d3275a18)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275a20 ip:ip_process+85 (2, d3275a4c, 2)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275a44 ip:ip_wput_attach_llhdr+92 (d5e61fc0, d67b1ad0,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275ad0 ip:ip_wput_ire+1aca (d4186c60, d5e61fc0,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275b30 ip:ip_output+1715 (da1b7554, d5e61fc0,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275b48 ip:ip_wput+14 (d4186c60, d5aaff80)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275b74 unix:put+164 (d4186c60, d5aaff80)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275bb0 ip:icmp_inbound+97e (d4186bd8, d5e61fc0,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275c00 ip:ip_proto_input+8ae (d4186bd8, d5e61fc0,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275c58 ip:ip_input+440 (da1b7554, 0, d5e61f)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275c80 ip:ip_rput+f7 (d4186bd8, d5e61fc0)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275cb0 unix:putnext+1b7 (d4186bd8, d5e61fc0)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275d40 gld:gld_recv_tagged+ed (d4188800, d5e61fc0,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275d54 gld:ri_ste_def+2603276e (d4188800, d5e61fc0)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275d88 iprb:iprb_process_recv+1d4 (d4188800)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275da0 iprb:iprb_intr+61 (d4188800, d3275ddc,)
Dec 23 09:43:14 crippen genunix: [ID 353471 kern.notice] d3275dac gld:gld_intr+1e (d4188800, 0)
Dec 23 09:43:14 crippen unix: [ID 100000 kern.notice]
Dec 23 09:43:14 crippen genunix: [ID 672855 kern.notice] syncing file systems...
Dec 23 09:43:14 crippen genunix: [ID 733762 kern.notice] 4
Dec 23 09:43:15 crippen genunix: [ID 733762 kern.notice] 3
Dec 23 09:43:16 crippen genunix: [ID 904073 kern.notice] done
Dec 23 09:43:17 crippen genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c0d0s1, offset 214695936, content: kernel
Dec 23 09:43:20 crippen genunix: [ID 409368 kern.notice] ^M100% done: 22636 pages dumped, compression ratio 2.72,
Dec 23 09:43:20 crippen genunix: [ID 851671 kern.notice] dump succeeded

Unresolved Kernal Trap-Hardware or Software issue?!?!

I could really use some advice here. My PowerBook G4 is driving me crazy. For the past 8 months, it has these "fits" where I either get the Grey Screen of Death or the kernel panic messages all down the left side of the screen.
I've reloaded my OS three times and the issue seems to go away for a while, and then one day it goes off again.
Noticeable situations:
Computer is cold (it's in my office in the basement) after sitting all day... it's been asleep... I open the screen and boom... crash.
Airport is trying to reconnect with my local network after the computer has been sleeping for a while. (Where I've left the screen up but used the "sleep" command.)
Attempts to resolve:
After trying everything under the sun I know of, I thought there might be a RAM issue after reading some posts here in the discussion forum. I ran Apple Hardware Tester to find there was an issue with one of my RAM chips which upon further research suggested that it might not be seated all the way (hence the intermittent crash). So I opened up my PowerBook, switched the RAM chips around and that seemed to solve the issue (for a while). Oh, and the RAM passed all AHT tests afterward.
Question:
Is it possible that the heating/cooling cycle over the years has caused the RAM sockets to become "unstable"? Things seem to work pretty reliably when the computer is warmed up.
Here is the report from my last crash:
Wed Dec 31 17:02:48 1969
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000E80F88 PC=0x00000000000A1A44
Latest crash info for cpu 0:
Exception state (sv=0x4f58ea00)
PC=0x000A1A44; MSR=0x00009030; DAR=0x00E80F88; DSISR=0x08000000; LR=0x000A1A1C; R1=0x3B273C40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0036B828 0x0009EDAC 0x0006445C 0x00066DE0 0x000AFA44 0x000B2AF8
Proceeding back via exception chain:
Exception state (sv=0x4f58ea00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x3b683280)
PC=0x90A42EF4; MSR=0x0800F030; DAR=0x00888000; DSISR=0x08000000; LR=0x90CBFE3C; R1=0xF0102210; XCP=0x00000010 (0x400 - Inst access)
BSD process name corresponding to current thread: WindowServer
Mac OS version:
9F33
Kernel version:
Darwin Kernel Version 9.5.0: Wed Sep 3 11:31:44 PDT 2008; root:xnu-1228.7.58~1/RELEASE_PPC
System model name: PowerBook5,3
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x0009B518 0x0009BEBC 0x00029DD8 0x000AF290 0x000B2AF8
Proceeding back via exception chain:
Exception state (sv=0x4f58ea00)
PC=0x000A1A44; MSR=0x00009030; DAR=0x00E80F88; DSISR=0x08000000; LR=0x000A1A1C; R1=0x3B273C40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0036B828 0x0009EDAC 0x0006445C 0x00066DE0 0x000AFA44 0x000B2AF8
Exception state (sv=0x3b683280)
PC=0x90A42EF4; MSR=0x0800F030; DAR=0x00888000; DSISR=0x08000000; LR=0x90CBFE3C; R1=0xF0102210; XCP=0x00000010 (0x400 - Inst access)
BSD process name corresponding to current thread: WindowServer

Good post.
Things to try;
1) disconnect all third part hardware and try the sleep function
2) reset the power manager
3) use terminal and type in reset-vram
reset-all
4) what I suspect, where did you buy the ram? remove any third party ram and just use what came with the powerbook
5) the hardware test is not going to tell you if the ram is not compatible, it can make mistakes and say its ok when if fact it is not. Although more or less if it does say its a problem then it is a problem but just don't rely on its final word.
Message was edited by: Smokerz

Kernal trap?

Hi, my computer has been crashing every few hours lately and I'd like to know if someone can help me identify the problem. This is for Macbook Pro Software OS X 10.9.2 (13C64) Here is the problem log:
Anonymous UUID:       7DEA5202-5188-24C4-2B19-BA774256D89D
Thu Jul 3 06:58:18 2014
panic(cpu 7 caller 0xffffff80098dbe2e): Kernel trap at 0xffffff7f8a1a937f, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x0000000108a8d000, CR3: 0x000000000bf52000, CR4: 0x00000000001606e0
RAX: 0xffffff8025569000, RBX: 0xffffff80253466f0, RCX: 0xffffff8009f034c0, RDX: 0x6c7070612e6d6f63
RSP: 0xffffff80fd613f20, RBP: 0xffffff80fd613f40, RSI: 0x0000000000000000, RDI: 0xffffff801dc4b280
R8: 0x0000000000000000, R9: 0xffffff8009e01910, R10: 0x00000000000003ff, R11: 0xffffffffffffffff
R12: 0x0000000008000040, R13: 0x000000000e000040, R14: 0xffffff8025346600, R15: 0xffffff8025346a08
RFL: 0x0000000000010286, RIP: 0xffffff7f8a1a937f, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000108a8d000, Error code: 0x0000000000000000, Fault CPU: 0x7
Backtrace (CPU 7), Frame : Return Address
0xffffff80f2fa5df0 : 0xffffff8009822fa9
0xffffff80f2fa5e70 : 0xffffff80098dbe2e
0xffffff80f2fa6040 : 0xffffff80098f3326
0xffffff80f2fa6060 : 0xffffff7f8a1a937f
0xffffff80fd613f40 : 0xffffff7f8a198ea4
0xffffff80fd613fb0 : 0xffffff80098d6ff7
      Kernel Extensions in backtrace:
         com.apple.iokit.IOSerialFamily(10.0.7)[69BF9F85-1A4A-3616-B7D1-E43F3AABCB13]@0x ffffff7f8a194000->0xffffff7f8a1a1fff
         com.ZTE.driver.ZTEUSBCDCACMData(1.3.6)[00000000-0000-0000-0000-000000000000]@0x ffffff7f8a1a5000->0xffffff7f8a1adfff
            dependency: com.apple.iokit.IOUSBFamily(675.4.0)[5C861553-BC5A-3979-A6B4-58C57879DD40]@0xff ffff7f8a122000
            dependency: com.apple.iokit.IOSerialFamily(10.0.7)[69BF9F85-1A4A-3616-B7D1-E43F3AABCB13]@0x ffffff7f8a194000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
13C64
Kernel version:
Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64
Kernel UUID: 9FEA8EDC-B629-3ED2-A1A3-6521A1885953
Kernel slide:     0x0000000009600000
Kernel text base: 0xffffff8009800000
System model name: MacBookPro11,2 (Mac-3CBD00234E554E41)
System uptime in nanoseconds: 3923154809856
last loaded kext at 244791249007: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8b881000, size 65536)
last unloaded kext at 305361859764: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8b881000, size 57344)
loaded kexts:
com.ZTE.driver.ZTEUSBCDCACMData 1.3.6
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.iokit.IOBluetoothSerialManager 4.2.3f10
com.apple.driver.AppleHDA 2.6.0f1
com.apple.driver.AGPM 100.14.15
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.ApplePlatformEnabler 2.0.9d1
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.3f10
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.1.12
com.apple.driver.AppleIntelHD5000Graphics 8.2.4
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.AppleCameraInterface 4.26.0
com.apple.driver.AppleIntelFramebufferAzul 8.2.4
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleUSBCardReader 3.4.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBHub 666.4.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.5.1
com.apple.driver.AppleAHCIPort 3.0.0
com.apple.driver.AirPort.Brcm4360 831.21.63
com.apple.driver.AppleUSBXHCI 670.4.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.nke.ppp 1.9
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.driver.DspFuncLib 2.6.0f1
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.5fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.iokit.IOBluetoothFamily 4.2.3f10
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.3f10
com.apple.driver.AppleSMBusController 1.0.11d1
com.apple.iokit.IOSurface 91
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.AppleGraphicsDeviceControl 3.4.35
com.apple.iokit.IOAcceleratorFamily2 98.14
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.IOPlatformPluginFamily 5.7.0d10
com.apple.driver.AppleHDAController 2.6.0f1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 2.6.0f1
com.apple.driver.AppleUSBMultitouch 240.9
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.6
com.apple.iokit.IOUSBMassStorageClass 3.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.2.7
com.apple.iokit.IO80211Family 630.35
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOUSBFamily 675.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.pthread 1
Model: MacBookPro11,2, BootROM MBP112.0138.B02, 4 processors, Intel Core i7, 2 GHz, 8 GB, SMC 2.18f6
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.63)
Bluetooth: Version 4.2.3f10 13477, 3 services, 15 devices, 1 incoming serial ports
Serial ATA Device: APPLE SSD SM0256F, 251 GB
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: iPhone
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Kernel version:
Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64
Kernel UUID: 9FEA8EDC-B629-3ED2-A1A3-6521A1885953
Kernel slide:     0x0000000009600000
Kernel text base: 0xffffff8009800000
System model name: MacBookPro11,2 (Mac-3CBD00234E554E41)
System uptime in nanoseconds: 3923154809856
last loaded kext at 244791249007: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8b881000, size 65536)
last unloaded kext at 305361859764: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f8b881000, size 57344)
loaded kexts:
com.ZTE.driver.ZTEUSBCDCACMData 1.3.6
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleUpstreamUserClient 3.5.13
Model: MacBookPro11,2, BootROM MBP112.0138.B02, 4 processors, Intel Core i7, 2 GHz, 8 GB, SMC 2.18f6
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343531533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.63)
Bluetooth: Version 4.2.3f10 13477, 3 services, 15 devices, 1 incoming serial ports
Serial ATA Device: APPLE SSD SM0256F, 251 GB
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: iPhone
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1f your
Hi,
If your USB internet stick has a micro SD in it, try the USB internet stick without it and check whether stability improves.   The Panic report indicates a loading of a filesystem extension just before the panic.
Cheers

Panic Kernal - can't load

Hi,
I've just bought a re-furbed mac book pro (2GHz, 512Mb) and I can't start OS X 10.4.9, i get the same error message
'panic(cpu 0 caller 0x0039BC83): unable to find driver for this platform: "ACPI"' and then a series of code.
Worked OK when I first started up, issue started when I selected software update. Followed the instructions on the firmware update and restarted as prompted.
I've only used if for about a day and I've run out out of options, I've tried the following:
Start in safe mode: Doesn't seem to work, still get through to the same error message.
Reset the the PRAM: no difference
Pressed command + S after launch: still get through to same error message
Hold down c at start up and boot from OS X Dvd: no difference, still get through to same error message.
Are there any options to re-install from the install CD (retail version)
Error message comes on after the Grey apple icon appears and then freezes about 2 seconds later.
Thanks

Welcome to Apple Discussions!
What probably happened is that you either installed some PowerPC drivers on there, or are booting off a PowerPC disk. Neither is supported. So if you used the migration assistent to import from PowerPC, backup your data off target disk mode:
http://docs.info.apple.com/article.html?artnum=58583
to another Mac using the principles shown here:
http://discussions.apple.com/click.jspa?searchID=-1&messageID=1872713
And then reimport only that data known to work with your MacBook Pro after erasing and restoring from the system restore disks that came with the MacBook Pro.
If your MacBook Pro didn't come with restore disks, ask the seller to provide them.
If the seller doesn't have them, ask them to contact AppleCare to get them. They are not his to keep, and belong to the machine, and are the only things that can boot them, other than a clone backup, or a disk utility written for Intel Macs such as Techtool Pro 4.5, or Disk Warrior 4.0.

Panic kernal trap

Similar Messages

Maybe you are looking for