|
#1
| |||
| |||
| scary crash... Something weird just happened to my iBook...: - strange stripes suddendly appeared on the screen, and then It went blank (black), It would not wake up so I kept the start button pressed for a while to make it restart....I heard then a fan noise, but It restarted properly.... What could it be? (for info: the HD on this computer crashed and died 4 months ago and it was replaced with a new one). |
|
#2
| ||||
| ||||
| It could have been a kernel panic or video crashing for some reason. Has it done that before? |
|
#3
| |||
| |||
| no, never... what's a panic kernel? |
|
#4
| |||
| |||
| thanks....found the panic.log, here you go: Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000010 PC=0x00000000246A9C9C Latest crash info for cpu 0: Exception state (sv=0x28025500) PC=0x246A9C9C; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x246A9C98; R1=0x0F6A37C0; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x246A9C98 0x246A9C34 0x002D1C84 0x246AA298 0x246AA104 0x004419E8 0x0086C2DC 0x0086DE3C 0x0086E138 0x0086E248 0x004418A0 0x0086C2DC 0x0086C9A8 0x0086CA40 0x0086783C 0x002D15CC 0x002D0494 0x000A9514 Kernel loadable modules in backtrace (with dependencies): com.apple.iokit.IOUSBMassStorageClass(1.4.5)@0x246a7000 dependency: com.apple.iokit.IOUSBFamily(2.5.9)@0x43f000 dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4.9)@0x58e000 dependency: com.apple.iokit.IOStorageFamily(1.5)@0x4a7000 com.apple.driver.AppleUSBEHCI(2.5.9)@0x863000 dependency: com.apple.iokit.IOUSBFamily(2.5.9)@0x43f000 dependency: com.apple.iokit.IOPCIFamily(1.7)@0x460000 com.apple.iokit.IOUSBFamily(2.5.9)@0x43f000 Proceeding back via exception chain: Exception state (sv=0x28025500) previously dumped as "Latest" state. skipping... Exception state (sv=0x23912C80) PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown) Kernel version: Darwin Kernel Version 8.9.0: Thu Feb 22 20:54:07 PST 2007; root:xnu-792.17.14~1/RELEASE_PPC panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access Latest stack backtrace for cpu 0: Backtrace: 0x000952D8 0x000957F0 0x00026898 0x000A8004 0x000AB980 Proceeding back via exception chain: Exception state (sv=0x28025500) PC=0x246A9C9C; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x246A9C98; R1=0x0F6A37C0; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x246A9C98 0x246A9C34 0x002D1C84 0x246AA298 0x246AA104 0x004419E8 0x0086C2DC 0x0086DE3C 0x0086E138 0x0086E248 0x004418A0 0x0086C2DC 0x0086C9A8 0x0086CA40 0x0086783C 0x002D15CC 0x002D0494 0x000A9514 Kernel loadable modules in backtrace (with dependencies): com.apple.iokit.IOUSBMassStorageClass(1.4.5)@0x246a7000 dependency: com.apple.iokit.IOUSBFamily(2.5.9)@0p ********* |
|
#5
| ||||
| ||||
| Wow you learn fast ![]() You have had one kernel panic on your computer for some USB driver issue but that was on 22 February. So probably this time the video froze, or the windowserver had something odd happening there, or there might have been some pressure on the video cable. Bottom line that if this has happened only once and will not repeat, I wouldn't worry too much. |
|
#6
| ||||
| ||||
![]() That's a OS X Kernel Panic. It's like the Blue Screen of death on Windows. Has anything bad happened though like data loss? The Doctor
__________________ Microsoft is the only company that would have its users turn their computers off by pushing a button marked ‘Start'. Can't remember the souce to the Quote |
|
#7
| ||||
| ||||
| Depending on what model iBook it is, it's possible that you have a bad motherboard. I had to return my old iBook to Apple to get the issue fixed (bad video processor, or something...), but they did it for free and apologized kindly. http://www.apple.com/support/ibook/faq/
__________________ • 2.66GHz Mac Pro Quad Xeon • 2.2GHz Santa Rosa MacBook Pro • 2.0GHz iMac Core Duo • 8GB iPhone |
|
#8
| |||
| |||
| 1. No, I did not get this image on the screen, It just went dark...after the stripes, I think I was using Acrobat when this happened. 2. No, I did not have any data loss |