Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

7 kernal panics on Quicken website!

7 and counting, I assume. I'm a regular contributor on the Intuit Quicken user forum. In the last week I've had 7 KPs right in the middle of posting a comment. It doesn't happen every time I post, but the KPs all happen in the middle of typing a response. Frustrating to say the least. Yes, I've submitted reports.


I'm on Yosemite, latest Safari, etc

MacBook Pro (15-inch Mid 2010), OS X Mavericks (10.9.2)

Posted on Jan 2, 2015 5:19 PM

Reply
11 replies

Jan 2, 2015 5:38 PM in response to Levoy Hurley

When you upgraded from Mavericks 10.9.x to Yosemite, did you upgrade the RAM

and double-check the available unused capacity of the computer's hard disk drive?


Are the kernel panic messages also in accord with Activity Monitor presentation of

concurrent symptomatic evidence of any other configuration causes of the event?


A kernel panic can be due to conflicts in software, as well as poor quality RAM.

Could you specify the system resources available? 😐

Jan 2, 2015 6:25 PM in response to Levoy Hurley

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View ▹ Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

Jan 2, 2015 6:47 PM in response to K Shaffer

I maxed out the RAM (from OWC) right after I got the MBP; that was 4 years ago.


I have 200GB free on my 750GB drive. However - a couple of weeks ago things were really slow. TechTool Pro (ver 7) tried to optimize HD but all the free space was fragmented into little chunks. Tried several things but eventually gave up and did a "clean" install. Booted from ext drive, wiped the internal HD, reinstalled Yosemite (from ext HD), and restored docs, apps, and settings from Time Machine. Ran TTP optimizers and this time everything was able to finish.


I'm fairly certain my KPs started after all this was done. (other than this, the MBP does run a lot better) Coincidence?


(I've also run all the TTP tests, and also Apple Hardware Test. )

Jan 2, 2015 7:07 PM in response to Levoy Hurley

UPDATE: After I posted the above it occurred to me that I left something out. I vaguely remembered seeing something about "TechTool Protection" during all those gyrations. I check my system and sure enough I had let TTP install this little utility and it was running in the background. I disabled it and restarted. I do know how to get the logs, but let's give it a day or so to see if I get another KP. If the problem is still there, it won't take long to surface.

Jan 3, 2015 1:10 PM in response to Linc Davis

Well, just as I was starting to feel lucky I got another KP - same circumstances. I was going to attach a text copy of the log file but see now I can't. So here it is....

**********************************************************

Sat Jan 3 13:41:58 2015


*** Panic Report ***

panic(cpu 2 caller 0xffffff7f8a7acf63): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff81234b8000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.7.21/src/Apple MuxControl/kext/GPUPanic.cpp:127

Backtrace (CPU 2), Frame : Return Address

0xffffff81111130f0 : 0xffffff8007b3a811

0xffffff8111113170 : 0xffffff7f8a7acf63

0xffffff8111113250 : 0xffffff7f887c3b9f

0xffffff8111113310 : 0xffffff7f8888d18e

0xffffff8111113350 : 0xffffff7f8888d1fe

0xffffff81111133c0 : 0xffffff7f88b0c056

0xffffff81111134f0 : 0xffffff7f888b082d

0xffffff8111113510 : 0xffffff7f887ca5f1

0xffffff81111135c0 : 0xffffff7f887c80fc

0xffffff81111137c0 : 0xffffff7f887c907a

0xffffff81111138a0 : 0xffffff7f89daa446

0xffffff81111138e0 : 0xffffff7f89db9dff

0xffffff8111113900 : 0xffffff7f89de8493

0xffffff8111113930 : 0xffffff7f89de84ed

0xffffff8111113970 : 0xffffff7f89dbfa1f

0xffffff81111139c0 : 0xffffff7f89d8a027

0xffffff8111113a60 : 0xffffff7f89d85da1

0xffffff8111113a90 : 0xffffff7f89d83873

0xffffff8111113ad0 : 0xffffff800810064c

0xffffff8111113b60 : 0xffffff8008102773

0xffffff8111113bc0 : 0xffffff8008100003

0xffffff8111113d00 : 0xffffff8007bea517

0xffffff8111113e10 : 0xffffff8007b3e91c

0xffffff8111113e40 : 0xffffff8007b235a3

0xffffff8111113e90 : 0xffffff8007b33e8d

0xffffff8111113f10 : 0xffffff8007c0a142

0xffffff8111113fb0 : 0xffffff8007c3ac66

Kernel Extensions in backtrace:

com.apple.driver.AppleMuxControl(3.7.21)[32B7E2DE-1F9D-3555-B687-7A76A62B81D2]@ 0xffffff7f8a79e000->0xffffff7f8a7b1fff

dependency: com.apple.driver.AppleGraphicsControl(3.7.21)[62689710-EEA7-307A-AC83-B8F25DA88 A6A]@0xffffff7f8a796000

dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xfffff f7f885a9000

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f88324000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f8871c000

dependency: com.apple.driver.AppleBacklightExpert(1.1.0)[0183904C-6A16-32C4-9405-EEFD7F820B 02]@0xffffff7f8a799000

com.apple.nvidia.classic.NVDAResmanTesla(10.0)[796AE430-39FB-3255-8161-D52AFA28 EE2B]@0xffffff7f88773000->0xffffff7f889dcfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f88324000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f88763000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f8871c000

com.apple.nvidia.classic.NVDANV50HalTesla(10.0)[7FE40648-F15F-3E18-91E2-FDDDF4C DA355]@0xffffff7f889e7000->0xffffff7f88c90fff

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA 28EE2B]@0xffffff7f88773000

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f88324000

com.apple.GeForceTesla(10.0)[67CD214F-0F26-3BEF-BAD0-CF0F83C2616D]@0xffffff7f89 d67000->0xffffff7f89e34fff

dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f88324000

dependency: com.apple.iokit.IONDRVSupport(2.4.1)[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f88763000

dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f8871c000

dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.0)[796AE430-39FB-3255-8161-D52AFA 28EE2B]@0xffffff7f88773000


BSD process name corresponding to current thread: WindowServer


Mac OS version:

14B25


Kernel version:

Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64

Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61

Kernel slide: 0x0000000007800000

Kernel text base: 0xffffff8007a00000

__HIB text base: 0xffffff8007900000

System model name: MacBookPro6,2 (Mac-F22586C8)


System uptime in nanoseconds: 27620406862585

last loaded kext at 3104420936797: com.apple.filesystems.smbfs 3.0.0 (addr 0xffffff7f8a909000, size 389120)

last unloaded kext at 3081175371191: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7f8a8a0000, size 16384)

loaded kexts:

com.parallels.kext.vnic 10.0.2 27712

com.parallels.kext.netbridge 10.0.2 27712

com.parallels.kext.hypervisor 10.0.2 27712

com.parallels.kext.usbconnect 10.0.2 27712

com.apple.filesystems.smbfs 3.0.0

com.apple.driver.AudioAUUC 1.70

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AGPM 100.14.37

com.apple.filesystems.autofs 3.0

com.apple.iokit.IOBluetoothSerialManager 4.3.1f2

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.AppleMikeyHIDDriver 124

com.apple.driver.AppleMikeyDriver 267.0

com.apple.driver.AppleHDA 267.0

com.apple.driver.AppleIntelHDGraphics 10.0.0

com.apple.driver.AppleUpstreamUserClient 3.6.1

com.apple.GeForceTesla 10.0.0

com.apple.driver.AppleIntelHDGraphicsFB 10.0.0

com.apple.driver.AppleSMCPDRC 1.0.0

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleLPC 1.7.3

com.apple.driver.AppleSMCLMU 2.0.4d1

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.1f2

com.apple.driver.AppleMuxControl 3.7.21

com.apple.driver.AppleMCCSControl 1.2.10

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleHWAccess 1

com.apple.driver.AppleHV 1

com.apple.driver.SMCMotionSensor 3.0.4d1

com.apple.driver.AppleUSBTCButtons 240.2

com.apple.driver.AppleUSBCardReader 3.5.0

com.apple.driver.AppleUSBTCKeyboard 240.2

com.apple.driver.AppleIRController 327.5

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 35

com.apple.iokit.SCSITaskUserClient 3.7.0

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.6.5

com.apple.driver.AppleUSBHub 705.4.1

com.apple.driver.AppleFWOHCI 5.5.2

com.apple.driver.AirPort.Brcm4331 800.20.24

com.apple.iokit.AppleBCM5701Ethernet 10.1.2b3

com.apple.driver.AppleAHCIPort 3.0.7

com.apple.driver.AppleUSBEHCI 705.4.14

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleACPIButtons 3.1

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 2.1

com.apple.driver.AppleACPIEC 3.1

com.apple.driver.AppleAPIC 1.7

com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0

com.apple.nke.applicationfirewall 161

com.apple.security.quarantine 3

com.apple.security.TMSafetyNet 8

com.apple.driver.AppleIntelCPUPowerManagement 218.0.0

com.apple.driver.IOBluetoothHIDDriver 4.3.1f2

com.apple.AppleGraphicsDeviceControl 3.7.21

com.apple.kext.triggers 1.0

com.apple.iokit.IOSerialFamily 11

com.apple.driver.DspFuncLib 267.0

com.apple.kext.OSvKernDSPLib 1.15

com.apple.iokit.IOAudioFamily 200.6

com.apple.vecLib.kext 1.2.0

com.apple.nvidia.classic.NVDANV50HalTesla 10.0.0

com.apple.nvidia.classic.NVDAResmanTesla 10.0.0

com.apple.iokit.IOFireWireIP 2.2.6

com.apple.driver.AppleSMBusPCI 1.0.12d1

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.IOPlatformPluginFamily 5.8.0d49

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.1f2

com.apple.driver.AppleHDAController 267.0

com.apple.iokit.IOHDAFamily 267.0

com.apple.iokit.IOUSBUserClient 705.4.0

com.apple.driver.AppleGraphicsControl 3.7.21

com.apple.driver.AppleBacklightExpert 1.1.0

com.apple.driver.AppleSMBusController 1.0.13d1

com.apple.iokit.IOSurface 97

com.apple.iokit.IOBluetoothFamily 4.3.1f2

com.apple.iokit.IONDRVSupport 2.4.1

com.apple.iokit.IOGraphicsFamily 2.4.1

com.apple.driver.AppleSMC 3.1.9

com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.0

com.apple.iokit.IOUSBMassStorageClass 3.7.0

com.apple.driver.AppleUSBMultitouch 245.2

com.apple.iokit.IOUSBHIDDriver 705.4.0

com.apple.driver.CoreStorage 471

com.apple.driver.AppleUSBMergeNub 705.4.0

com.apple.driver.AppleUSBComposite 705.4.9

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.0

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.iokit.IOAHCISerialATAPI 2.6.1

com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.0

com.apple.iokit.IOFireWireFamily 4.5.6

com.apple.iokit.IO80211Family 700.52

com.apple.iokit.IOEthernetAVBController 1.0.3b3

com.apple.driver.mDNSOffloadUserClient 1.0.1b8

com.apple.iokit.IONetworkingFamily 3.2

com.apple.iokit.IOAHCIFamily 2.7.0

com.apple.iokit.IOUSBFamily 705.4.14

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 300.0

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.AppleKeyStore 2

com.apple.driver.AppleMobileFileIntegrity 1.0.5

com.apple.driver.AppleCredentialManager 1.0

com.apple.driver.DiskImages 389.1

com.apple.iokit.IOStorageFamily 2.0

com.apple.iokit.IOReportFamily 31

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleACPIPlatform 3.1

com.apple.iokit.IOPCIFamily 2.9

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.Libm 1

com.apple.kec.pthread 1

com.apple.kec.corecrypto 1.0

Jan 3, 2015 1:30 PM in response to Levoy Hurley

You have the MacBookPro6,2—the Edsel of Macs. It may have the logic-board defect that was covered by this recall.

Make a "Genius" appointment at an Apple Store, or go to another authorized service provider, to have the machine tested. The routine hardware diagnostics used by service providers do not detect the fault. There is a specific test for this issue that Apple calls "VST" (for "Video Switching Test.") Ask for it. A "Failed" result means that the fault is present. However, according to reports, some units may pass the test, and yet still be deemed eligible for repair under the program. Your experience may vary.

Print the first page of the panic report, if any, and the support page linked above, and bring them with you.

Note that the recall only applies within three years of purchase. After that, Apple may refuse the service. In that case, you may be quoted a price of about $300 (in the U.S.) for a "depot repair," which involves shipping the unit to a central repair facility and takes about two weeks. For that flat fee, anything found wrong with it should be fixed, not just the logic board.

The model was discontinued on February 24, 2011, so the recall has nominally ended. Some units may have been sold after that date by Apple as refurbished, or by resellers as new, and they might still be covered.

Residents of the EU may be entitled to warranty service for up to six years after purchase.

Some owners report that their unit was repaired under the program after the deadline had passed. Others report that the repair was covered by the extended warranty from a credit-card issuer. Again, your experience may vary.

Sometimes the replacement part is also defective, so be prepared for that possibility. If you decide to pay for a new logic board, test thoroughly during the 90-day warranty period on the repair. Some owners have reported that they went through as many as three replacement boards before getting one that worked.

If it's too late for your unit to be repaired free of charge, and you don't want to pay for the service, you may (or may not) be able to stop the panics by disabling automatic graphics switching. To use the discrete graphics processor, you'll need a third-party utility to switch to it manually.

Often the problems start after an OS upgrade. If the upgrade was recent, and you have backups, then you can revert to a previous OS X version.

If you're dissatisfied with Apple's response, please keep in mind that no one here represents the company or can help with customer-service issues.

Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

*An SSD doesn't need to be zeroed.

Jan 3, 2015 1:46 PM in response to Levoy Hurley

The recall link that Linc posted is of little value as it merely states that the recall has ended without any details of the problem.

If you have you have an Apple Store, you might try arguing that you were never notified of the recall and you never experienced any symptoms that would highlight the problem for you to act within the constraints of the recall. As most people didn't seem to see the problem until upgrading the OS, I would think they would try to avoid a lawsuit and just fix it for you, but I don't work for Apple.

Jan 3, 2015 2:27 PM in response to Barney-15E

You've got to be kidding me. This is deja vu all over again. 😢 This MBP is a replacement for my June 07 MBP - another Edsel. That was the one with the bad video chip (nVidia?). That wasn't really a recall but a warranty extension with no expiration. The first failure was Christmas day 2009. New logic board free. That board lasted about 4 months, the next one about 6. Apple gave up and sent me a new MBP for Christmas 2010 - this one. So I've already had one freebie; doubt they'll be eager for another one (assuming they keep that sort of record handy).


I hate dealing with the local Apple Store, but fortunately we have a very good independent shop here in Tucson that can do in two days what it would take the Apple Store a week to do. Unfortunately I may have to eventually deal with them since this recall is a little different.


I have no intention to pay to fix this MBP. I've already been planning for a new one in 2015. I've been hoping to hold out for the next update which should have the Broadwell chip. I saw that Intel is finally in production (big announcement coming at CES) . With only a minor bump last July, it looks to me like the current MBP is a little long in the tooth.

Jan 8, 2015 3:47 PM in response to Levoy Hurley

Just to close this out - the repair cost is $360, which I believe includes shipping if you take it to an Apple service provider. 5-7 day turnaround.


I'm still going to try to hold out for the release of the next (Broadwell) chipset, hopefully about mid year. Shouldn't be too difficult as long as the issue doesn't become more pervasive; at least I know how to deal with it.


Thanks for the help, all.

7 kernal panics on Quicken website!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.