Model A1181: 1.83, 2, 2.1, 2.13, 2.16, 2.2, or 2.4 GHz Core 2 Duo processor

1434 Questions View all

Black Screen, must restart

I got this black screen, which i assume is the equivalent of BSOD. When I rebooted I got this:

Interval Since Last Panic Report: 102842 sec

Panics Since Last Report: 4

Anonymous UUID: 361C5093-4B3A-4AB0-9031-3840BFEFEDCA

Sun Dec 13 14:24:49 2009

panic(cpu 1 caller 0x41c4b3): "hfs_swap_HFSPlusBTInternalNode: catalog key #37 offset too big (0x04A4)\n"@/SourceCache/xnu/xnu-1486.2.11/bsd/hfs/hfs_endian.c:500

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

0x34edb948 : 0x21b2bd (0x5cf868 0x34edb97c 0x223719 0x0)

0x34edb998 : 0x41c4b3 (0x5b99ec 0x25 0x4a4 0x2)

0x34edba38 : 0x4114fe (0x34edba58 0x454ae10 0x1 0x1)

0x34edba78 : 0x2fb83c (0x305d0a10 0x4277004 0x0 0x0)

0x34edbb38 : 0x2fc2b7 (0x0 0x0 0x200 0x0)

0x34edbb88 : 0x435029 (0x4550f00 0x42773c0 0x66e9190 0x4277004)

0x34edbbb8 : 0x43b912 (0x4277004 0x1 0x4b59f48 0x4af1fd0)

0x34edbcc8 : 0x41a89c (0x4b249d4 0x0 0x4b59ef0 0x34edbd08)

0x34edbda8 : 0x2f8cd8 (0x34edbdc0 0x246 0x34edbde8 0x2f9481)

0x34edbde8 : 0x2da81e (0x4b249d4 0x53b3b24 0x34edbe18 0x0)

0x34edbe08 : 0x2da88e (0x4b249d4 0x0 0x0 0x0)

0x34edbe28 : 0x2ef42c (0x4b249d4 0x1 0x34edbed8 0x583d3f)

0x34edbe88 : 0x46ace9 (0x5f4b410 0x34edbed8 0x3c 0x0)

0x34edbef8 : 0x46ca9a (0x49c9280 0x5f4b410 0x4998000 0x0)

0x34edbf38 : 0x46cb6b (0x0 0x5 0x34edbf5c 0x1)

0x34edbf78 : 0x4ee5dc (0x4998000 0x53b3a20 0x53b3a64 0x0)

0x34edbfc8 : 0x29deb8 (0x51762e0 0x0 0x10 0x51762e0)

BSD process name corresponding to current thread: crash_inspector

Mac OS version:


Kernel version:

Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386

System model name: MacBook2,1 (Mac-F4208CAA)

System uptime in nanoseconds: 283252105105

unloaded kexts: 2.0 (addr 0x2ebb4000, size 0x12288) - last unloaded 98126169710

loaded kexts: 7.0.0 6.0.6 1.1.2 1.7.9a4 3.1.0 6.0.6 3.0.0d4 3.1.14b1 412.19.4 19 4.0.1d0 1.4.9 170.0.14 2.1.0 251.1.4 1.8.0b4 1.8.0b4 1.8.0b4 2.6.0 1.6.0 31 1.0.0d1 2.0.1 2.5.0 1.3.0 3.8.4 4.4.0 3.7.5 3.7.5 1.3 1.4 160.0.0 1.3 1.4 1.3 1.4 96.0.0 0 0 2.1.11 96.0.0 17 - last loaded 34725604060 10 14 10 10 20 73.0 2.2.4f3 10.0.3 1.7.9a4 1.7.2fc1 1.3 2.0.3 310.6 1.9 41 1.7.9a4 1.7.9a4 3.0.1d2 4.0.1d0 2.0 2.0 2.2.4f3 2.2.4f3 2.2.4f3 3.8.5 3.8.4 3.7.5 2.6.0 1.6 1.6 1.6 402.1 2.5.0 2.6.0 2.0.2 2.5.0 3.8.5 4.1.7 3.8.5 1.3.0 1.6.1 1.1 6 1.0.0d1 281 1.6 1.3 2.6 1.3.0

Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2.16 GHz, 2 GB, SMC 1.17f0

Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram

Memory Module: global_name

AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), Atheros 5416:

Bluetooth: Version 2.2.4f3, 2 service, 1 devices, 1 incoming serial ports

Network Service: AirPort, AirPort, en1

Serial ATA Device: WDC WD2500BEVT-11ZCT0, 232.89 GB

Parallel ATA Device: HL-DT-ST DVDRW GSA-S10N

USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8501, 0xfd400000

USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8240, 0x5d200000

USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8205, 0x7d100000

USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0229, 0x1d200000

Im not sure what I should do, or if it was a 1 time thing.

Answer this question I have this problem too

Is this a good question?

Score 2
Add a comment

2 Answers

Most Helpful Answer

this line indicates you may have corrupted system files (or worse, a failing hard drive):

panic(cpu 1 caller 0x41c4b3): "hfs_swap_HFSPlusBTInternalNode: catalog key #37 offset too big (0x04A4)\n"@/SourceCache/xnu/xnu-1486.2.11/bsd/hfs/hfs_endian.c:500

Try booting from the grey restore disc which came with your computer, and run Disk Utility -> Repair Disk. It will hopefully repair the issue(s), and if not, provide additional diagnostic info.

If you do not have access to your restore discs, you can try a Safe Boot, by powering the machine on while holding down the SHIFT key - part of this process forces a unix fdsk disk repair utility to run.

Hopefully these suggestions will resolve your issues, and as always, if you can start up your system make sure you backup important files as soon as possible, just in case!

Was this answer helpful?

Score 1
Add a comment

It sounds like a directory problem (the reference to a catalog key, which is software), which may or may not be caused by a hardware problem. David's advice was good.

If you can get it going, go to and download SMART Utility. This can be run in demo mode to see if any of your hard drive's SMART attributes have failed (Disk Utility will only tell you *after* the whole drive has failed; SU gives you more advance warning.) SMART is the self-monitoring hardware most modern hard drives have built into them.

Was this answer helpful?

Score 0
Add a comment

Add your answer

ccowin will be eternally grateful.
View Statistics:

Past 24 Hours: 0

Past 7 Days: 1

Past 30 Days: 2

All Time: 2,416