Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Rhuantavan

macrumors newbie
Original poster
Jun 24, 2003
22
0
Rence, Slovenia
Hi,

Can anyone figure out what is wrong with my machine from the crash log below? Today the mac crashed and yesterday it did too, but I believe the crash log was totally different (don't remember what it was).

Thanks a lot!


Code:
Interval Since Last Panic Report:  90176 sec
Panics Since Last Report:          1
Anonymous UUID:                    7021781D-39C9-4E96-85BB-A24045FF99A4

Thu Mar 10 10:15:21 2011
Machine-check capabilities (cpu 0) 0x0000000000000806:
 family: 6 model: 23 stepping: 6 microcode: 1547
 Intel(R) Xeon(R) CPU           E5462  @ 2.80GHz
 6 error-reporting banks
 threshold-based error status present
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): 0xb200001084200e0f valid
  MCA error code:            0x0e0f
  Model specific error code: 0x8420
  Other information:         0x00000010
  Threshold-based status:    No tracking
  Status bits:
   Processor context corrupt
   Error enabled
   Uncorrected error
panic(cpu 0 caller 0x2a9d27): Machine Check at 0x002a356f, thread:0x124c5000, trapno:0x12, err:0x0,registers:
CR0: 0x8001003b, CR2: 0x4fe0b090, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x00000005, EBX: 0x56097000, ECX: 0x124c5000, EDX: 0x00000084
ESP: 0x0010bcd8, EBP: 0x0010bcd8, ESI: 0x077d1b7c, EDI: 0x00000000
EFL: 0x00000087, EIP: 0x002a356f

Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x819e18 : 0x21b50c (0x5d4438 0x819e4c 0x223974 0x0) 
0x819e68 : 0x2a9d27 (0x595f04 0x595ff1 0x2a356f 0x124c5000) 
0x819f58 : 0x2a1912 (0x1 0x0 0x0 0x0) 
0x10bcd8 : 0x225dae (0x56097000 0x299e72b6 0x1690 0x0) 
0x10bd28 : 0x225ea0 (0x77d1b7c 0x0 0x0 0x4f10bf14) 
0x10bd48 : 0x232436 (0x77d1b7c 0x0 0x1 0x828) 
0x10bd78 : 0x2267cc (0x4f10bf10 0x73b30dc 0x0 0x54b170) 
0x10bda8 : 0x54b1d6 (0x73b30dc 0x1 0x0 0x55ef374d) 
0x10bdc8 : 0x55ee6862 (0x73b30c0 0x0 0x73977
Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 4 GB, SMC 1.25f4
Graphics: NVIDIA GeForce 8800 GT, NVIDIA GeForce 8800 GT, PCIe, 512 MB
Memory Module: global_name
Bluetooth: Version 2.3.8f7, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
Network Service: Ethernet 2, Ethernet, en1
PCI Card: NVIDIA GeForce 8800 GT, Display, Slot-1
Serial ATA Device: WDC WD2502ABYS-02B7A0, 233,82 GB
Serial ATA Device: WDC WD5000AAKS-00YGA0, 465,76 GB
Serial ATA Device: WDC WD5000AAKS-00YGA0, 465,76 GB
Serial ATA Device: WDC WD5000AAKS-00YGA0, 465,76 GB
Parallel ATA Device: OPTIARC DVD RW AD-7170A
USB Device: Hub, 0x05ac  (Apple Inc.), 0x911c, 0xfd500000
USB Device: Keyboard Hub, 0x05ac  (Apple Inc.), 0x1006, 0xfd530000
USB Device: Apple Keyboard, 0x05ac  (Apple Inc.), 0x0221, 0xfd532000
USB Device: Apple Cinema HD Display, 0x05ac  (Apple Inc.), 0x921c, 0xfd520000
USB Device: Logitech USB Headset, 0x046d  (Logitech Inc.), 0x0a0b, 0x3d100000
USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8206, 0x5d200000
FireWire Device: built-in_hub, Up to 800 Mb/sec
FireWire Device: unknown_device, Unknown
 
Have you tried repairing permissions?

Yeah repairing permissions is one of those things that almost never fixes an issue, especially kernel panics. Kernel panics almost always indicate a hardware fault. People need to stop recommending it, it's a bit silly. Repair permissions is meant to fix broken installers, not at all meant to fix crashes.

In this case, the panic log is most definitely pointing to defective hardware. It's most likely a dying CPU, but either way, get it to an Apple Store and they'll tell you what's up. The various flags really point to a dying CPU (seriously, read the logs before you start recommending "Fix Permissions.")

(The GeForce 8800 GT's are also very unreliable so there is a chance it could be that. Apple Store will tell you.)

For reference on why repairing permissions is useless:
http://www.unsanity.org/archives/000410.php
 
You really need a debug kernel to turn those Hex addresses in the stack backtrace into real kernel routines. If you aren't an ADC Select (or higher) member, though, you might not be able to get a hold of such a kernel.

That said, if I am reading that correctly, you might be having Machine Check Exception induced panics, in which case I would suspect either your memory (first) or CPU (second) going bad. :eek:

I think there's a memory tester on the installation DVD; you should run that.
 
You really need a debug kernel to turn those Hex addresses in the stack backtrace into real kernel routines. If you aren't an ADC Select (or higher) member, though, you might not be able to get a hold of such a kernel.

That said, if I am reading that correctly, you might be having Machine Check Exception induced panics, in which case I would suspect either your memory (first) or CPU (second) going bad. :eek:

I think there's a memory tester on the installation DVD; you should run that.

That's true, it could be memory, but "Processor context corrupt" does not bode well in since that is normally not in memory.
 
A peripheral (USB or Firewire) with failing firmware can also cause panics, although it's not too common. Still, it's worth eliminating as a factor by removing any unnecessary peripherals and using a backup kb/mouse if possible.

And yeah, test that RAM.
 
Wirelessly posted (iPhone: Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8F190 Safari/6533.18.5)

yadmonkey said:
A peripheral (USB or Firewire) with failing firmware can also cause panics, although it's not too common. Still, it's worth eliminating as a factor by removing any unnecessary peripherals and using a backup kb/mouse if possible.

And yeah, test that RAM.

Not too common ? The only kernel panics I have had in the last few years were caused by defective external FireWire drives.
 
Not too common ? The only kernel panics I have had in the last few years were caused by defective external FireWire drives.

I've never had Firewire devices cause a panic, but I have had a bad Firewire bus cause panics.

I will note again that the OP's crash log specifically points to a fault on the CPU.
 
Kernel Panic

Hello,

Have you made use of the Apple Hardware Test program to further diagnose the problem? I suggest doing that as it will tell you more information if your CPU is dying..


Another route is getting for your machine, which is Mac Pro 3,1, the Apple Service Diagnostic which luckily, I have and can provide for you.. If you are interested I can forward this useful tool to you. The Apple Hardware Test gives cryptic, hex based error codes and can be kind of difficult to diagnose problems with.

Apple Service Diagnostic is much better as it will tell you in PLAIN ENGLISH what the problem could be.. Let me know..

Josh
 
Hello,

Have you made use of the Apple Hardware Test program to further diagnose the problem? I suggest doing that as it will tell you more information if your CPU is dying..


Another route is getting for your machine, which is Mac Pro 3,1, the Apple Service Diagnostic which luckily, I have and can provide for you.. If you are interested I can forward this useful tool to you. The Apple Hardware Test gives cryptic, hex based error codes and can be kind of difficult to diagnose problems with.

Apple Service Diagnostic is much better as it will tell you in PLAIN ENGLISH what the problem could be.. Let me know..

Josh

What is the difference between the Apple Hardware test and the Apple Service Diagnostic? Is Service Diagnostic available any ware to the end user?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.