The_PJN
Level 1 (0 points)

Q: Mac Pro 1,1 (2006) - Screen of Death

Worked fine for months without issue. Then a few weeks ago second hard drive died (May or may not be related. Hard drive doesn't seem to work in any other machine either now.)

 

Now today out of nowhere the cascading multi-language screen of death. Thought maybe it was a heat issue but after cranking the A/C and leaving Mac Pro off for 4-5 hours the same issue. Boots, runs for a few minutes and then... screen of death.

 

What's up with that?

 

Mac Pro specs:

http://www.everymac.com/systems/apple/mac_pro/specs/mac-pro-quad-2.66-specs.html

(Bumped up to 32GB of RAM but otherwise the same as far as I remember. Running 10.6.8)

 

Also this insanity popped up upon one restart. Never seen this before. Very encouraging... *sigh*

 

IMG_1677.jpg

I doubt if this'll be resolved via message board but a nudge in the right direction might materialize.

Hug your working computers tight folks. Don't take them for granted.

Mac Pro, Mac OS X (10.6.8), Death screen

Posted on Jul 26, 2015 8:29 PM

by The hatter,Solvedanswer
The hatter The hatter
Level 9 (60,935 points)
A:

FBDIMMs fail esp. older DIMMs

 

The three likely GPUs too - X1900 (dust and heat), 8800GT (solder - can be baked), 7300GT OEM

 

When you have a good system, clone it - a couple times.

 

If you can get it running Etrecheck will at least also show hardware profile and software items of interest

Posted on Jul 27, 2015 8:14 AM

Close
The_PJN

Q: Mac Pro 1,1 (2006) - Screen of Death

  • All replies
  • Helpful answers

  • by lllaass,Helpful

    lllaass lllaass Jul 27, 2015 1:35 AM in response to The_PJN
    Level 10 (190,813 points)
    Apple Watch
    Jul 27, 2015 1:35 AM in response to The_PJN

    Run Apple hardware test

    Using Apple Hardware Test - Apple Support

    The Machine Check language usually indicates a hardware problem.

    Are you running 10.6.8.

    Can you boot from install DVD or Lion USB install medial and do a fresh install on a new disk?

  • by The hatter,Solvedanswer

    The hatter The hatter Jul 27, 2015 8:14 AM in response to The_PJN
    Level 9 (60,935 points)
    Jul 27, 2015 8:14 AM in response to The_PJN

    FBDIMMs fail esp. older DIMMs

     

    The three likely GPUs too - X1900 (dust and heat), 8800GT (solder - can be baked), 7300GT OEM

     

    When you have a good system, clone it - a couple times.

     

    If you can get it running Etrecheck will at least also show hardware profile and software items of interest

  • by Grant Bennet-Alder,Helpful

    Grant Bennet-Alder Grant Bennet-Alder Jul 27, 2015 6:10 PM in response to The_PJN
    Level 9 (61,390 points)
    Desktops
    Jul 27, 2015 6:10 PM in response to The_PJN

    That kernel panic information is saved in a battery-backed store, and copied to a Log on next startup. the report is available in its entirety in the log described in this article:

     

    Mac OS X: How to log a kernel panic - Apple Support

     

    You are welcome to post the entire panic log here for Readers to analyze.

     

    as others have already pointed out, kernel panic, machine check, such as this one are most often caused by uncorrectable RAM Memory errors. That means some of your RAM DIMMs will need to be replaced.

  • by The_PJN,

    The_PJN The_PJN Jul 27, 2015 8:36 PM in response to lllaass
    Level 1 (0 points)
    Jul 27, 2015 8:36 PM in response to lllaass

    I cannot run the Apple Hardware Test apparently. Dang.

     

    Yes running 10.6.8.

     

    I do have a Snow Leopard install disk that I could boot from. That's an option.

     

    No Lion USB install or secondary drive available at the moment (That died a couple weeks ago too. Hopefully unrelated. Hopefully not a cursed machine.) but obtainable and try-able.

     

    Good tips, good tips. Thanks.

  • by The_PJN,

    The_PJN The_PJN Jul 27, 2015 8:56 PM in response to The hatter
    Level 1 (0 points)
    Jul 27, 2015 8:56 PM in response to The hatter

    Failure happens this is true. But... Things like this only happen to other people... Right?

     

    Backups = Yes. (Most of the time)

    Cloning my system = From this point on.

     

    Etrecheck. Got it. I've compressed air cleaned the heck outta the thing after giving it some space and reseated/swapped around the RAM. Been on without issue for almost an hour now. Not doing anything extensive, mind you. Just running Rember right now. See if that tells me anything.

     

    Thanks.

  • by The_PJN,

    The_PJN The_PJN Jul 27, 2015 8:55 PM in response to Grant Bennet-Alder
    Level 1 (0 points)
    Jul 27, 2015 8:55 PM in response to Grant Bennet-Alder

    "...available in its entirety", eh? So they are. Sweet.

     

    In that case if anyone wants to analyze said log here is what seems to be the first one that started the whole mess:

     

    Sun Jul 26 16:10:15 2015

    Machine-check capabilities (cpu 1) 0x0000000000000006:

    family: 6 model: 15 stepping: 6 microcode: 198

    Intel(R) Xeon(R) CPU            5150  @ 2.66GHz

    6 error-reporting banks

    Machine-check status 0x0000000000000005:

    restart IP valid

    machine-check in progress

    MCA error-reporting registers:

    IA32_MC0_STATUS(0x401): 0x1000000020000000 invalid

    IA32_MC1_STATUS(0x405): 0x0000000000000000 invalid

    IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid

    IA32_MC3_STATUS(0x40d): 0x0020000000000000 invalid

    IA32_MC4_STATUS(0x411): 0x0000000000000011 invalid

    IA32_MC5_STATUS(0x415): 0xb200001080200e0f valid

      MCA error code:            0x0e0f

      Model specific error code: 0x8020

      Other information:         0x00000010

      Status bits:

       Processor context corrupt

       Error enabled

       Uncorrected error

    panic(cpu 1 caller 0x2aaf41): Machine Check at 0x009c4bc4, thread:0x2a46b3d4, trapno:0x12, err:0x0,registers:

    CR0: 0x8001003b, CR2: 0x44329c80, CR3: 0x00100000, CR4: 0x00000660

    EAX: 0x2a8c5204, EBX: 0x00000009, ECX: 0x2a9e7004, EDX: 0x2a8c5204

    ESP: 0x9fcd3ba0, EBP: 0x9fcd3be8, ESI: 0x2a99a004, EDI: 0x00000009

    EFL: 0x00000202, EIP: 0x009c4bc4

     

     

    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)

    0x9887afb8 : 0x21b837 (0x5dd7fc 0x9887afec 0x223ce1 0x0)

    0x9887b008 : 0x2aaf41 (0x59dfe4 0x59e0d1 0x9c4bc4 0x2a46b3d4)

    0x9887b0f8 : 0x2a29f2 (0x1 0x458b0424 0x24048908 0x32896ff)

    0x9fcd3be8 : 0x9c4e00 (0x897db004 0x9 0x1 0x0)

    0x9fcd3c08 : 0xb9805a (0x2a99a004 0x9 0x0 0x0)

    0x9fcd3c38 : 0xab4aa4 (0x2a99a004 0x9fcd3c78 0x0 0x0)

    0x9fcd3c98 : 0xbb5877 (0x2a9e7004 0x2a938004 0x26 0x0)

    0x9fcd3d28 : 0x128a5ac (0x2a9e7004 0x2b0cd004 0xffffffff 0x26)

    0x9fcd3d58 : 0x12e7238 (0x2a9e7004 0x2b0cd004 0x0 0x0)

    0x9fcd3df8 : 0xb0e258 (0x2a9e7004 0x2a9f3004 0x0 0x0)

    0x9fcd3e38 : 0x9dde2b (0x2a9e7004 0x2a9f3004 0x0 0x0)

    0x9fcd3ed8 : 0x553ec7 (0x0 0x2b18ab00 0x1 0x2a46b3d4)

    0x9fcd3f28 : 0x552ea6 (0x2b18ab00 0x7 0x9fcd3fc8 0x2ab75b)

    0x9fcd3f88 : 0x552eea (0x2a2af300 0x2b0653d4 0x8b60153b 0xffffffff)

    0x9fcd3fc8 : 0x2a179c (0x2a2af300 0x0 0x10 0x2a85c9e4)

          Kernel Extensions in backtrace (with dependencies):

             com.apple.nvidia.nv40hal(6.4.2)@0x1247000->0x13e4fff

                dependency: com.apple.NVDAResman(6.4.2)@0x96e000

             com.apple.NVDAResman(6.4.2)@0x96e000->0xc5bfff

                dependency: com.apple.iokit.IOPCIFamily(2.6.8)@0x928000

                dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000

                dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000

     

     

    BSD process name corresponding to current thread: kernel_task

     

     

    Mac OS version:

    10K549

     

     

    Kernel version:

    Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386

    System model name: MacPro1,1 (Mac-F4208DC8)

     

     

    System uptime in nanoseconds: 2443467034103

    unloaded kexts:

    com.apple.driver.AppleFileSystemDriver 2.0 (addr 0xe66000, size 0x12288) - last unloaded 84257062013

    loaded kexts:

    com.apple.driver.AppleHWSensor 1.9.3d0

    com.apple.filesystems.autofs 2.1.0

    com.apple.driver.AppleUpstreamUserClient 3.5.7

    com.apple.driver.AppleMCCSControl 1.0.26

    com.apple.driver.AppleHDA 2.0.8f3

    com.apple.driver.AudioAUUC 1.57

    com.apple.GeForce 6.4.2

    com.apple.driver.AppleMCEDriver 1.1.9

    com.apple.Dont_Steal_Mac_OS_X 7.0.0

    com.apple.driver.AudioIPCDriver 1.1.6

    com.apple.driver.AppleIntelMeromProfile 19

    com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1

    com.apple.driver.AppleLPC 1.5.1

    com.apple.iokit.IOAHCIBlockStorage 1.6.6

    com.apple.iokit.SCSITaskUserClient 2.6.9

    com.apple.BootCache 31.1

    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

    com.apple.driver.AppleFWOHCI 4.7.7

    com.apple.driver.AppleUSBHub 4.2.5

    com.apple.driver.AppleIntel8254XEthernet 2.1.3b1

    com.apple.driver.AppleAHCIPort 2.2.0

    com.apple.driver.AppleIntelPIIXATA 2.5.1

    com.apple.driver.AppleEFINVRAM 1.4.0

    com.apple.driver.AppleUSBEHCI 4.2.6

    com.apple.driver.AppleUSBUHCI 4.2.5

    com.apple.driver.AppleACPIButtons 1.3.6

    com.apple.driver.AppleRTC 1.3.1

    com.apple.driver.AppleHPET 1.5

    com.apple.driver.AppleSMBIOS 1.7

    com.apple.driver.AppleACPIEC 1.3.6

    com.apple.driver.AppleAPIC 1.4

    com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0

    com.apple.security.sandbox 1

    com.apple.security.quarantine 0

    com.apple.nke.applicationfirewall 2.1.14

    com.apple.driver.AppleIntelCPUPowerManagement 142.6.0

    com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.9 - last loaded 615065264226

    com.apple.iokit.IOUSBMassStorageClass 2.6.7

    com.apple.driver.AppleProfileReadCounterAction 17

    com.apple.driver.DspFuncLib 2.0.8f3

    com.apple.driver.AppleProfileTimestampAction 10

    com.apple.driver.AppleProfileThreadInfoAction 14

    com.apple.driver.AppleProfileRegisterStateAction 10

    com.apple.driver.AppleProfileKEventAction 10

    com.apple.driver.AppleProfileCallstackAction 20

    com.apple.nvidia.nv40hal 6.4.2

    com.apple.NVDAResman 6.4.2

    com.apple.iokit.IOFireWireIP 2.0.4

    com.apple.driver.AppleHDAController 2.0.8f3

    com.apple.iokit.IOHDAFamily 2.0.8f3

    com.apple.iokit.IOSurface 74.2

    com.apple.iokit.IOBluetoothSerialManager 2.4.5f3

    com.apple.iokit.IOSerialFamily 10.0.3

    com.apple.iokit.IOAudioFamily 1.8.3fc2

    com.apple.kext.OSvKernDSPLib 1.3

    com.apple.driver.ApplePolicyControl 3.0.17

    com.apple.driver.AppleGraphicsControl 3.0.17

    com.apple.iokit.IONDRVSupport 2.2.1

    com.apple.iokit.IOGraphicsFamily 2.2.1

    com.apple.iokit.AppleProfileFamily 41

    com.apple.driver.AppleSMC 3.1.0d5

    com.apple.driver.IOPlatformPluginFamily 4.7.0a1

    com.apple.iokit.IOUSBHIDDriver 4.2.5

    com.apple.driver.XsanFilter 402.1

    com.apple.driver.AppleUSBMergeNub 4.2.5

    com.apple.driver.AppleUSBComposite 3.9.0

    com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.9

    com.apple.iokit.IOBDStorageFamily 1.6

    com.apple.iokit.IODVDStorageFamily 1.6

    com.apple.iokit.IOCDStorageFamily 1.6.1

    com.apple.iokit.IOATAPIProtocolTransport 2.5.1

    com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.9

    com.apple.iokit.IOFireWireFamily 4.2.7

    com.apple.iokit.IOUSBUserClient 4.2.4

    com.apple.iokit.IONetworkingFamily 1.10

    com.apple.iokit.IOAHCIFamily 2.0.7

    com.apple.iokit.IOATAFamily 2.5.1

    com.apple.iokit.IOUSBFamily 4.2.6

    com.apple.driver.AppleEFIRuntime 1.4.0

    com.apple.iokit.IOHIDFamily 1.6.6

    com.apple.iokit.IOSMBusFamily 1.1

    com.apple.kext.AppleMatch 1.0.0d1

    com.apple.security.TMSafetyNet 6

    com.apple.driver.DiskImages 289.1

    com.apple.iokit.IOStorageFamily 1.6.3

    com.apple.driver.AppleACPIPlatform 1.3.6

    com.apple.iokit.IOPCIFamily 2.6.8

    com.apple.iokit.IOACPIFamily 1.3.0

     

    Now there are 5 more logs and I'm not sure it is the same problem each time but starting here seems like more than enough right now.

     

    "...uncorrectable RAM Memory errors." Okay. So IF that is the case that the RAM is the problem; then odds are I should be able to replace said problem RAM and the sunshine and rainbows will return. Oh I really hope that that's the worst I'm lookin' at here.

     

    Thanks.

     

    Oh and some more possibly helpful but probably not screenshots:

    Screen shot 2015-07-27 at 10.20.17 PM.pngScreen shot 2015-07-27 at 10.21.04 PM.pngScreen shot 2015-07-27 at 10.21.25 PM.jpg

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder Jul 27, 2015 10:35 PM in response to The_PJN
    Level 9 (61,390 points)
    Desktops
    Jul 27, 2015 10:35 PM in response to The_PJN

    Go about you business, but every half hour or so, re-invoke that last report you posted (its data is STATIC). Sooner or later you will get one that looks more like this one:

     

    eccerrors2.jpg

     

    graphic from anandtech.com

  • by The_PJN,

    The_PJN The_PJN Jul 28, 2015 8:03 PM in response to The_PJN
    Level 1 (0 points)
    Jul 28, 2015 8:03 PM in response to The_PJN

    Haven't gone too overboard as yet. Scared to push it too hard too soon. But everything's been backed up now at least.

     

    Been refreshing the memory report every now and then. So far so good though.

     

    See if I can finagle up some new RAM in the meantime.

     

    Thanks for the help everyone!