Home Forums Hardware Mac Desktops & Notebooks Could this be a logic board problem?

About a month ago, I started having system panics on my Mac Pro. It is configured as follows:

Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 2 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.25f4
Serial Number (system): G88222M1XYK
Hardware UUID: 15475C4D-77C3-57F0-8789-F3D091D66342

ATI Radeon HD 2600 XT:

Chipset Model: ATI Radeon HD 2600
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x9588
Revision ID: 0x0000
ROM Revision: 113-B1480A-252
EFI Driver Version: 01.00.252
Displays:
Cinema HD Display:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected

I took it to the Apple Store and we first decided to do a clean install and import my settings and documents from Time Machine that resides on a 500GB Time Capsule. That helped, but I soon had additional problems. The panic logs pointed to the graphics card and possibly the logic board. The graphics card was replaced and it appeared that the problem was solved. A few days ago, I started having trouble running Disk Warrior. It would stall at the beginning of Step 5 whether it was running from a bootable SuperDuper! clone or from the Disk Warrior DVD. I have also noticed a general slowdown in performance that I have blamed on the 10.5.8 system update or the Security Update 2009-004, but, looking back, I believe the performance immediately after installing these updates was unchanged and that the slowdown occurred thereafter. Also, the slowdown seems intermittent.

Just now, I tried to run Disk Warrior again and the "black curtain of death" descended upon my display. A panic log was generated. It is set forth below. My question is whether or not this panic log is consistent with trouble on the logic board. If so, I'll haul my heavy Mac Pro back to the Apple Store and have a serious talk about logic board replacement. I won't quote anyone by name to Apple, but I will tell them that I have discussed the log with persons who know how to read them and they think I should be talking to Apple about a new logic board. If you believe the log points to something else, I'll listen. Thanks in advance for any help you can give.


Sat Aug 15 23:31:29 2009
panic(cpu 1 caller 0x001AB0FE): Kernel trap at 0x0014351c, type 14=page
fault, registers:
CR0: 0x80010033, CR2: 0x9b09d800, CR3: 0x011b1000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x0597b9a0, ECX: 0x9b09d800, EDX: 0x024389c0
CR2: 0x9b09d800, EBP: 0x37ccfc88, ESI: 0x04ab2e80, EDI: 0x0000001e
EFL: 0x00010202, EIP: 0x0014351c, CS: 0x00000008, DS: 0x00080010
Error code: 0x00000000
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x37ccfa18 : 0x12b4c6 (0x45f91c 0x37ccfa4c 0x13355c 0x0)
0x37ccfa68 : 0x1ab0fe (0x469a98 0x14351c 0xe 0x469248)
0x37ccfb48 : 0x1a1713 (0x37ccfb60 0x24d76 0x37ccfc88 0x14351c)
0x37ccfb58 : 0x14351c (0xe 0x48 0x10 0x10)
0x37ccfc88 : 0x143d52 (0x24389c0 0x1 0x3 0x3ef2a7)
0x37ccfca8 : 0x122a26 (0x24389c0 0x1 0x37ccfcd8 0x3efdc7)
0x37ccfcc8 : 0x188533 (0x476dfa0 0x597b9a0 0x37ccfcf8 0x43eba6)
0x37ccfcf8 : 0x44455d (0x47d7b80 0x1e 0x7665444f 0x54656369)
0x37ccfd28 : 0x4445c4 (0x47d7b80 0x1e 0x200000 0x503f488)
0x37ccfd48 : 0x188921 (0x47d7b80 0x1e 0x0 0x0)
0x37ccfd78 : 0x18a36c (0x47d7b80 0x503f4b0 0x37ccfdac 0x11dd27)
0x37ccfdb8 : 0x12d4d6 (0x503f488 0x4bdef9c 0x0 0x0)
0x37ccfdf8 : 0x1264fa (0x503f400 0x0 0x3c 0x37ccfee4)
0x37ccff08 : 0x198fa3 (0x37ccff44 0x0 0x0 0x0)
0x37ccffc8 : 0x1a1cfa (0x4a7ee60 0x0 0x10 0x0)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffedc8
BSD process name corresponding to current thread: coreservicesd
Mac OS version:
9L30
Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009;
root:xnu-1228.15.4~1/RELEASE_I386
System model name: MacPro3,1 (Mac-F42C88C8)
System uptime in nanoseconds: 22754696301
unloaded kexts:
(none)
loaded kexts:
com.vmware.kext.vmnet 2.0.5 - last loaded 12630581158
com.vmware.kext.vmioplug 2.0.5
com.vmware.kext.vmci 2.0.5
com.vmware.kext.vmx86 2.0.5
com.kensington.mouseworks.driver.VirtualMouse 3.0
com.kensington.mouseworks.driver.KMWUSBHIDMouse 3.0
com.kensington.mouseworks.iokit.KensingtonMouseDriver 3.0
com.kensington.driver.kbd_driver 1.8
com.kensington.keyboard.base.driver 1.8
com.kensington.keyboard.old.base.driver 1.8
com.apple.driver.InternalModemSupport 2.4.0
com.apple.filesystems.autofs 2.0.2
com.apple.driver.AppleHDAPlatformDriver 1.7.1a2
com.apple.driver.AppleHDAHardwareConfigDriver 1.7.1a2
com.apple.driver.AppleUpstreamUserClient 2.7.5
com.apple.driver.AppleHDA 1.7.1a2
com.apple.kext.ATY_Lamna 5.4.8
com.apple.driver.AppleHWSensor 1.9d0
com.apple.iokit.IOBluetoothSerialManager 2.1.8f2
com.apple.Dont_Steal_Mac_OS_X 6.0.3
com.apple.driver.AppleTyMCEDriver 1.0.0d28
com.apple.driver.AppleHDAController 1.7.1a2
com.apple.iokit.IOFireWireIP 1.7.7
com.apple.driver.AppleUSBDisplays 2.0.2
com.apple.driver.AudioIPCDriver 1.0.6
com.apple.ATIRadeonX2000 5.4.8
com.apple.driver.ACPI_SMC_PlatformPlugin 3.4.0a17
com.apple.driver.AppleMCEDriver 1.1.7
com.apple.driver.AppleLPC 1.3.1
com.apple.driver.CSRUSBBluetoothHCIController 2.1.8f2
com.apple.driver.CSRHIDTransitionDriver 2.1.8f2
com.apple.driver.AppleUSBMergeNub 3.4.6
com.apple.driver.PioneerSuperDrive 2.0.9
com.apple.iokit.SCSITaskUserClient 2.1.1
com.apple.driver.XsanFilter 2.7.91
com.apple.iokit.IOATAPIProtocolTransport 1.5.3
com.apple.iokit.IOAHCIBlockStorage 1.2.2
com.apple.driver.AppleFileSystemDriver 1.1.0
com.apple.driver.AppleUSBHub 3.4.9
com.apple.driver.AppleAHCIPort 1.7.0
com.apple.driver.AppleIntelPIIXATA 2.0.1
com.apple.driver.AirPortBrcm43xx 365.91.19
com.apple.iokit.IOUSBUserClient 3.4.9
com.apple.driver.AppleIntel8254XEthernet 2.1.2b1
com.apple.driver.AppleFWOHCI 3.9.7
com.apple.driver.AppleUSBEHCI 3.4.6
com.apple.driver.AppleUSBUHCI 3.3.5
com.apple.driver.AppleEFINVRAM 1.2.0
com.apple.driver.AppleACPIButtons 1.2.5
com.apple.driver.AppleRTC 1.2.3
com.apple.driver.AppleHPET 1.4
com.apple.driver.AppleACPIPCI 1.2.5
com.apple.driver.AppleSMBIOS 1.4
com.apple.driver.AppleACPIEC 1.2.5
com.apple.driver.AppleAPIC 1.4
com.apple.security.seatbelt 107.12
com.apple.nke.applicationfirewall 1.6.77
com.apple.security.TMSafetyNet 3
com.apple.driver.AppleIntelCPUPowerManagement 76.2.0
com.apple.driver.DiskImages 199
com.apple.BootCache 30.4
com.apple.driver.DspFuncLib 1.7.1a2
com.apple.iokit.IOSerialFamily 9.4
com.apple.iokit.IOHDAFamily 1.7.1a2
com.apple.iokit.IOAudioFamily 1.6.9fc5
com.apple.kext.OSvKernDSPLib 1.1
com.apple.iokit.IONDRVSupport 1.7.3
com.apple.iokit.IOGraphicsFamily 1.7.3
com.apple.driver.IOPlatformPluginFamily 3.4.0a17
com.apple.driver.AppleSMC 2.3.1d1
com.apple.driver.AppleUSBBluetoothHCIController 2.1.8f2
com.apple.iokit.IOBluetoothFamily 2.1.8f2
com.apple.iokit.IOUSBHIDDriver 3.4.6
com.apple.driver.AppleUSBComposite 3.2.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1
com.apple.iokit.IOSCSIBlockCommandsDevice 2.1.1
com.apple.iokit.IOBDStorageFamily 1.5
com.apple.iokit.IODVDStorageFamily 1.5
com.apple.iokit.IOCDStorageFamily 1.5
com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1
com.apple.iokit.IOAHCIFamily 1.5.0
com.apple.iokit.IOATAFamily 2.0.1
com.apple.iokit.IO80211Family 216.1
com.apple.iokit.IONetworkingFamily 1.6.1
com.apple.iokit.IOFireWireFamily 3.4.9
com.apple.iokit.IOUSBFamily 3.4.9
com.apple.driver.AppleEFIRuntime 1.2.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOStorageFamily 1.5.6
com.apple.iokit.IOHIDFamily 1.5.5
com.apple.driver.AppleACPIPlatform 1.2.5
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.2.0

Tough question, JoBoy...

The general, but *not* 100%, reaction to crash/panic logs around here has been that they are pretty much unintelligible, and I, personally, don't see anything in yours that rings a bell, but when the more knowledgeable responders see it you may get a more responsive answer.

For the moment, though, I suggest that you dig out your Apple Hardware Test disc and run its "Extended Test" in loop-mode (control-L) for *at least* 5 loops.

(My gut feeling is that if your issue has survived an erase and install, and the original diagnosis of graphics card was incorrect, and your logic board has been implicated, then a new logic board is in your future.)

Running the Apple Hardware Tests as Artie suggested would be a good first step. I would also recommend a surface scan of the hard drive using Drive Genius, TechTool Pro, or TechTool Deluxe that comes with AppleCare. S.M.A.R.T. tests in my experience are not all that reliable an indicator of drive failure.

I did nine (9) loops and "No problems found" was the result.
Then, I decided to take a kamikaze approach. I again put Disk Warrior to work and walked away. Two hours later, I returned and it was just finishing up its work. It actually worked, albeit dreadfully slow. It has never done that to me before. Now, I'm wondering if things have been slowed down by the latest security update. I'll talk with Alsoft tomorrow.

> I did nine (9) loops and "No problems found" was the result.

I hope that's authoritative and you do *not* have a hardware problem.

> I again put Disk Warrior to work and walked away. Two hours later, I returned and it was just finishing up its work. It actually worked, albeit dreadfully slow. It has never done that to me before.

DW has been known to take 24 hours and longer to do its thing when it has encountered severe directory damage. (I once agonized over its "no progress" bar for several excruciating hours before it completed its run.)

But you haven't told us how your Mac has been running since you ran DW?

And, under any circumstances, you ought to take joemike's suggestion to heart.

(For what it's worth, I wouldn't waste my time contacting Alsoft unless I had something definitive to tell them.)

I used TechTool DeLuxe that comes with AppleCare to do all hard drive analyses. No problems at all. Thanks for thinking of it. I'll be interested to hear why DiskWarrior has suddenly become so sluggish. Two hours is way too long. I really thought I had a hardware problem.

> I'll be interested to hear why DiskWarrior has suddenly become so sluggish.

Have you read my post with which yours crossed?

Out of curiosity, how long a list of corrections did DW generate after its two hour run?

Today, I read your post that crossed with mine last night. I shut down my machine after sending last night's post. I'd never heard of really long directory rebuilding. DiskWarrior has always been quite quick on my machines. I've used DW's various incarnations on several previous Macs. This was a new experience. The thing that made me think something was wrong was when the horizontal barber pole (progress indicator) appeared to slow, then stop, and then run backward!

I did not save the report, but I should have. My recollection is that it was quite lengthy, but not outrageously so.

> The thing that made me think something was wrong was when the horizontal barber pole (progress indicator) appeared to slow, then stop, and then run backward!

Was it really running backwards, or was it an optical illusion?

> I did not save the report, but I should have. My recollection is that it was quite lengthy, but not outrageously so.

The time DW ran for 2-3 hours on my iBook G3 the report was 7 pages long!

> DiskWarrior has always been quite quick on my machines.

It never took more than a few minutes to do its thing before that one instance (and hasn't since)...really threw me!

But back to the chase... How is your Mac running now?

diskwarrior runs slow if:

- the hard drive has IO errors
- the computer is short on memory
- the directory (used disk space is a good gauge) is large. (100+gb used)

Hard drives attached through SATA-to-USB adapters can also be highly intolerant of io errors, taking several minutes to "give up" on even one bad block, so having a drive with a mess of IO errors can take hours, or even days, to scan. Internal SATA buses seem to give up on bad blocks in more reasonable timeframes.

It's sometimes faster to run DW while booted to the computer that has the problem, so starting off an external attached drive. This means DW has local access to the hard drive, and is using the internal sata bus, both of which can help matters. But if the computer is shallow on memory, (1gb etc) then target moding it is usually a better idea.

It was not an optical illusion, but I don't know how those elapsed time tapes operate, so I don't know the significance of the observation.

After repeatedly running DiskWarrior on all three internal drives, things seem to be running well.

Thank you for the suggestions. Through much testing using Apple Hardware test (expanded version run 9 cycles) and TechTool Deluxe, it appears that the internal hard drives are in good shape. I have 2Gb RAM. 99Gb disk space used. No SATA to USB adapters.

For now, the troubles seem to have cleared up.

> After repeatedly running DiskWarrior on all three internal drives, things seem to be running well.

That hair-raising DW run may have been your lucky charm; I've got my fingers crossed for you.

Your observation is something I've been wondering about as well. Could it be that my directories were in such disarray that it took two hours to iron it out? I went for several months without updating DiskWarrior while I was updating many other applications and battling a dying graphics card. Apparently, my priorities were not the best. Having used DW for many years, I had begun to wonder if I was just pandering to my compulsive tendencies using it regularly. The experience that I've shared in this thread has convinced me that DW actually may be a fundamental necessity for keeping things in good working order.

Any comments about this view would be welcome.

I'm paranoid, schizophrenic and a compulsive user of Disk Warrior. That said, I run DW once a week to keep the directory clean. It rarely finds errors but when it does, I allow it to fix them immediately. I believe in nipping problems in the bud before they become so numerous that a not-so-bad situation becomes a terrible one.

I know that there are people who disagree (dkmarsh being one) but that's my 2¢. Perhaps dk will chime in with his thoughts on the matter. Regardless of who's right, I am not having any problems with Leopard and the same was true for Tiger, Panther and Jaguar.

I like being obsessive-compulsive!

> The experience that I've shared in this thread has convinced me that DW actually may be a fundamental necessity for keeping things in good working order.

Any comments about this view would be welcome.

The question of preventive maintenance - DiskWarrior, permission repair, oil-change, etc. - has been addressed more than once by the participants in these forums with no consensus having been reached.

Jon runs DW weekly, I test my monthly backup for bootability, and, since I'm there, give it a monthly run, and dkmarsh doesn't even own it.

The logical answer, then, is for each to react to hir own instincts.

Both you and I have agonized while that barber pole spun for hours, so our point of view is different from that of many, if not most, Mac users, but, on the other hand, both of us have also run DW many times to no apparent end.

So the bottom line may well come down to how much of a gambler you are *and* how much trouble reinstallation will be for you should you lose your bet.

So the bottom line may well come down to how much of a gambler you are *and* how much trouble reinstallation will be for you should you lose your bet.

that's probably the most insightful statement I've seen on this issue. I don't run dw except maybe twice a year on the servers but then I'm able to deal with any minor issues that more frequent runs may prevent, so my advice doesn't apply to a lot of people.

In my case, I did not use Disk Warrior for six months. I was accumulating assorted troubles, including a graphics card failure unrelated to DW. When I upgraded DW, the results required me to start this thread. My tolerance for gambling has evaporated. I just don't need more down time or hassles. I'm a bruised user of Apple computers since the Apple II and Lisa. I'm an experienced professional in my field, but it's not information technology. For me, regular use of DW is a small price to pay to prevent problems I'm not qualified to handle. Thanks, Artie505, for your terse and very articulate summary.

> My tolerance for gambling has evaporated. I just don't need more down time or hassles.

> For me, regular use of DW is a small price to pay to prevent problems I'm not qualified to handle.

Well put...perhaps the only good reason I've ever run across for running DW regularly.

> Thanks, Artie505, for your terse and very articulate summary.

You're very welcome. (Learning to write writing footnotes to financial statements has its benefits [and disadvantages ].)