I've been getting several kernel panics on my base model MBP Retina. Each time, I was using Chrome. The panic log seems to be related to the Graphics. Every single time the HD4000 kext is on the stack trace. A snippet of panic log: Code: Kernel Extensions in backtrace: com.apple.driver.AppleIntelHD4000Graphics(7.2.8)[6B02D782-A79F-399C-81FD-353EBFF2AB81]@0xffffff7f82404000->0xffffff7f8246afff dependency: com.apple.iokit.IOPCIFamily(2.7)[C0404427-3360-36B4-B483-3C9F0C54A3CA]@0xffffff7f80869000 dependency: com.apple.iokit.IONDRVSupport(2.3.4)[474FE7E9-5C79-3AA4-830F-262DF4B6B544]@0xffffff7f808cd000 dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[EF26EBCF-7CF9-3FC7-B9AD-6C0C27B89B2B]@0xffffff7f80894000 BSD process name corresponding to current thread: Google Chrome He Mac OS version: 11E2620 Kernel version: Darwin Kernel Version 11.4.2: Wed May 30 20:13:51 PDT 2012; root:xnu-1699.31.2~1/RELEASE_X86_64 Kernel UUID: 25EC645A-8793-3201-8D0A-23EA280EC755 System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F) Here's a thread on Apple Support Forums on this: https://discussions.apple.com/thread/4028778?start=0&tstart=0 It seems like Chrome maybe the one causing it. Even so, this is Apple's fault, since a non-privileged user space program should not be able to cause a kernel panic. The kernel QA and security audit team needs to step up their game.