Currently Being ModeratedMar 6, 2013 6:40 AM (in response to Jacob Sager Weinstein)
throw out the 3GB FBDIMMsHow To Install and Remove Memory Mac Pro2x2GB FBDIMM DDR2 667MHz @ $31
Metro Vacuum ED500 DataVac 500-Watt 0.75-HP Electric Duster 120-Volt
I assume this is one of Apple ATI 5770s. And that is the only graphic card. That also means you can't run anything less than 10.6.5
Currently Being ModeratedMar 6, 2013 7:02 AM (in response to Jacob Sager Weinstein)
A kernel panic is not ONE problem, it is any one of hundreds of problems. When it happens, Mac OS X writes a suicide note and stuffs it in a special area of battery-backed RAM. At Startup, that note is copied into a log and can be read out later.
Do not guess about what might be wrong. Go and get one or more of those panic logs and look at them. If they are baffling, cut and paste the text of one here on the forum and readers will help you figure out what happened.Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
Currently Being ModeratedMar 6, 2013 7:01 AM (in response to Grant Bennet-Alder)
These use to be handy "FAQ" tips for troubleshooting:
Resolving Kernal Panics
Currently Being ModeratedMar 6, 2013 1:42 PM (in response to The hatter)
Thanks, The Hatter. I'm working through all the links you've provided and see if I can narrow down the problem.
And, Grant, thanks as well-- I really appreciate the specific information. You've enabled me to track down the panic log -- but they are indeed baffling. I'm pasting one below, in case somebody wiser than I can interpret it for me.
Wed Mar 6 11:25:26 2013
panic(cpu 2 caller 0x2ceabf): Kernel trap at 0x00baf978, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x8da19000, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x7db19000, EBX: 0x07eb6004, ECX: 0x0ff00000, EDX: 0x0ff00000
CR2: 0x8da19000, EBP: 0x4469bc38, ESI: 0x0ff00000, EDI: 0x08feab04
EFL: 0x00010206, EIP: 0x00baf978, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000
Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)
0x4469ba98 : 0x2203de (0x6b08cc 0x4469bab8 0x229fb0 0x0)
0x4469bac8 : 0x2ceabf (0x6bd9e0 0xbaf978 0xe 0x6bd989)
0x4469bb78 : 0x2e5564 (0x4469bba0 0x4469bb88 0x4469bb98 0x22cbbb)
0x4469bb98 : 0xbaf978 (0xe 0x44690048 0xff1b0010 0x10)
0x4469bc38 : 0x1547167 (0x8ad2c04 0x7eb6004 0xff00000 0x7eb6004)
0x4469bc58 : 0x153e35c (0x7eb6004 0x8feab04 0x0 0xff00000)
0x4469bc88 : 0xcb6c56 (0x7eb6004 0x9465004 0x4469bca0 0x0)
0x4469bd38 : 0xd27c8a (0x7eb6004 0x9465004 0x8971c14 0xff)
0x4469bdc8 : 0xd2933e (0x7eb6004 0x8a97c04 0x0 0x0)
0x4469be28 : 0xd2b46a (0x7eb6004 0x8a97c04 0x8 0x2)
0x4469be58 : 0x1562269 (0x7eb6004 0x8a97c04 0x0 0x0)
0x4469be88 : 0xd2b589 (0x7eb6004 0x8a97c04 0x0 0x0)
0x4469bed8 : 0xb9eb05 (0x7eb6004 0x0 0x0 0x0)
0x4469bf68 : 0xb5362c (0x7eb6004 0x1 0x7c637f0 0x7c63be8)
0x4469bf98 : 0x23e4ae (0x8af4400 0x7eb6004 0xfa6d03 0x7eb4028)
0x4469bfc8 : 0x2c7d0c (0x84ad60 0x0 0x10 0x92f8410)
Kernel Extensions in backtrace:
dependency: com.apple.iokit.IONDRVSupport(2.3.4)[393829BA-614C-4ED7-B4AD-CE577A41C683]@0xb3 b000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[EE3F8FBE-3457-4F0E-A3A3-B9B1A44DCF6B]@0 xb07000
dependency: com.apple.NVDAResman.G7xxx(7.0.4)[6581C9F3-3221-4530-BEB4-627CB8D602AE]@0xb4c00 0
BSD process name corresponding to current thread: kernel_task
Mac OS version:
Darwin Kernel Version 11.4.2: Thu Aug 23 16:26:45 PDT 2012; root:xnu-1699.32.7~1/RELEASE_I386
Kernel UUID: 859B45FB-14BB-35ED-B823-08393C63E13B
System model name: MacPro1,1 (Mac-F4208DC8)
System uptime in nanoseconds: 37415286581
last loaded kext at 10244857365: com.apple.driver.AppleHWSensor 1.9.5d0 (addr 0x3125000, size 28672)
Currently Being ModeratedMar 8, 2013 3:14 AM (in response to Jacob Sager Weinstein)
I spent yesterday morning swapping various combinations of FBDIMMS in and out, and I ended up with the same kernel panic no matter which ones I had in. So either they're all damaged, or the problem is elsewhere.
Then I ran the Hardware Test overnight on loop mode, in accordance with the suggestion in one of The Hatter's links. After 61 passes and nearly 13 hours, it didn't find any hardward problems...
Currently Being ModeratedMar 8, 2013 9:32 AM (in response to Jacob Sager Weinstein)
The Mac Pro has error-correcting memory and memory problems give you very distinctive signatures, which your panic log does NOT show.
What it does suggest is that you may have problems with your NVIDIA Graphics card.Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
Currently Being ModeratedMar 9, 2013 6:41 AM (in response to Jacob Sager Weinstein)
After working my way through various diagnostics, I reached the conclusion that your very kind online help had taken me as far as I could go without actually getting in-person help. So I bit the bullet and lugged my Mac Pro to the closest Apple store.
Their diagnosis agreed with Grant's: it was a graphics card issue. Fingers crossed they have now fixed the problem.
Thanks again for all the help-- I really appreciate your being so generous with your time and expertise.
Currently Being ModeratedMar 9, 2013 6:58 AM (in response to Jacob Sager Weinstein)
You aso have mere 3GB which is starving anyway, and means you are using OEM FBDIMMs that are old, these type fail and older DIMMs run hotter.
The only way to test RAM sometimes is with a known good set, and your swapping around 2x512 and 2x1GB is not reassuring. ECC works, but not when memory is not functioning properly. Some errors are found, but even AHT and Memtest are not full-proof. I had some new OWC memory, started having parity errors, and within 2 days had enough errors - real files written to disk - that eventually I had to reinstall and restore - and buy some memory elsewhere thank you OWC.
$29 for 2x2GB seems like a no-brainer. Except I'd "splurge" and get 8GB quad symmetrical memory, which is ideal for this system.
Currently Being ModeratedMar 9, 2013 8:41 AM (in response to Jacob Sager Weinstein)
Rather than replace the old one with the same model, many older Mac Pro users have substituted the Apple-firmware 5770 card (about US$250). It works in all models of Mac Pro, and drivers first appear in 10.6.5 and later. It is a much better card than any of the "stock" options.
Apple only recommends the 5770 for the 2010 model, because it was issued AFTER the earlier models were discontinued. (I find it amusing Apple does not recommend the 5770 for the very similar 2012 model either, because they have not tested it there either.)
If the Apple Store has ordered you a different card, your order will be subject to their standard 14-day no questions asked return policy.Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers