HELP!!! Comp. unexpectedly shuts down

[lezer23]

Recently, (after 10.4.3) I will be doing simple tasks on my fairly new PB, and a gray screen will comp saying "you must restart your computer now" in five lanuages. It really pisses me off because Apple was supposed to be the machine that doesnt break, and I take good care of my computer. Does someone know what this could be caused by, and possible how to fix it?
Thank you guys so much!
:confused:

[Laser47]

Its called a kernel panic, equivelent to the Windows Blue screen of death. Everything should be fine after you restart your computer.

[Jaffa Cake]

What you're describing is a kernel panic. They can and do happen every once in a while, but repeated occurrences would point to an underlying problem. One of the chief culprits is bad RAM – have you installed any extra in your machine? If so, you could try removing it and see if that stops the problem – and if it does, get your RAM replaced.

[lezer23]

I wish that was the quick fix but it still happens after I restart, and I cant believe my mac is doing this because i bought a mac because my windows laptop was doing the bluescreen. I cant believe this! It is less than 3 months old!:mad:

[Mitthrawnuruodo]

Like Laser said, if this is a one time thing then just reboot and all should be fine, but if it occurs often then there's something severly wrong either with some software you're using or, even worse, your hardware.

Now is a good time to back up your data!

One thing: Are you, by any chance, running a torrent application as one of those "simple tasks"? Torrent apps are a known source for Kernel Panics.

[lezer23]

What you're describing is a kernel panic. They can and do happen every once in a while, but repeated occurrences would point to an underlying problem. One of the chief culprits is bad RAM – have you installed any extra in your machine? If so, you could try removing it and see if that stops the problem – and if it does, get your RAM replaced.

I bought my mac in the apple store, and they upgraded it 1GB, but I dont think that the apple store would install bad RAM?!?

[lezer23]

Like Laser said, if this is a one time thing then just reboot and all should be fine, but if it occurs often then there's something severly wrong either with some software you're using or, even worse, your hardware.

Now is a good time to back up your data!

One thing: Are you, by any chance, running a torrent application as one of those "simple tasks"? Torrent apps are a known source for Kernel Panics.

I do not run Torrent apps

[lezer23]

One thing that is odd, though, is that it had never happened to me at school while often at home. Could it be something with my network?

[Jaffa Cake]

I bought my mac in the apple store, and they upgraded it 1GB, but I dont think that the apple store would install bad RAM?!?In that case it might be worthwhile taking it back to the Apple Store and get them to take a look at it, and get them to replace your RAM.

Occasionally bad sticks can make it through quality control, and I think too that good sticks can go iffy from time to time...

[lezer23]

In that case it might be worthwhile taking it back to the Apple Store and get them to take a look at it, and get them to replace your RAM.

Occasionally bad sticks can make it through quality control, and I think too that good sticks can go iffy from time to time...

I just talked with apple, they reset my PRAM and NVRAM

would that help?

[Jaffa Cake]

Hmm... I've just done a quick search on kernel panics and this (http://forums.macrumors.com/showthread.php?t=159811&highlight=kernal+panic) thread mentions that the 10.4.3 update seems to be showing up problems in slightly suspect RAM. You mention in your opening post that you've recently updated your OS – did you experience any problems prior to the update?

[lezer23]

Hmm... I've just done a quick search on kernel panics and this (http://forums.macrumors.com/showthread.php?t=159811&highlight=kernal+panic) thread mentions that the 10.4.3 update seems to be showing up problems in slightly suspect RAM. You mention in your opening post that you've recently updated your OS – did you experience any problems prior to the update?

No I did not, and should I post some of the panic info in panic.log?
Thanks so much jaffa

[Laser47]

Try running the apple hardware test. Its on the first install dvd just hold option when you turn you PB on and choose hardware test on the screen. Run the extended test. If it doesnt pass take it to an apple store or call them. If your machine passes it might be software.

[Sun Baked]

One thing that is odd, though, is that it had never happened to me at school while often at home. Could it be something with my network?Could be something with the a/c power outlet you are using.

If it is a noisy, over-/under-volt, etc. it will cause you hardware problems -- like kernal panics.

These are usually the problems that are location related when you are running on a/c power.

However, if it also happens while running on battery power connected to the network -- could be the network itself, or something coming over the network.

[lezer23]

Could be something with the a/c power outlet you are using.

If it is a noisy, over-/under-volt, etc. it will cause you hardware problems -- like kernal panics.

These are usually the problems that are location related when you are running on a/c power.

However, if it also happens while running on battery power connected to the network -- could be the network itself, or something coming over the network.

come to think of it... it has never happened on battery....

[HiRez]

Since Jaffa said he wasn't experiencing problems before the 10.4.3 update, I'd suspect that, assuming his RAM is ok and first I would try disconnecting all external cables and devices to see if the problem still happens.

After that, I would do a backup to an external disk and then try an Archive and Install from your OS X DVD (which should allow you to retain all your documents and settings). After that is possible you'd need to do a clean install but I'd try the Archive method first and run the updates (make sure you repair permissions after upgrading).

[IJ Reilly]

If a 0.5% chance that it will help is good enough, then go ahead and reinstall OSX. Otherwise, chase down the other 99.5% probability that it's a hardware problem of some kind, most likely RAM. Yes, it is entirely possible to have good RAM go "bad" after an OS update (whether it is actually bad or not, I don't know, but the hardware treats it as such). This happened to me after upgrading from 10.2 to 10.3, with RAM installed by Apple at the factory, so I know from personal experience that it can happen. So make no assumptions based on the origin of the RAM and have it thoroughly tested before taking any desperate measures (of which reinstalling the OSX is a leading example) that aren't likely to solve your problem.

[lezer23]

If a 0.5% chance that it will help is good enough, then go ahead and reinstall OSX. Otherwise, chase down the other 99.5% probability that it's a hardware problem of some kind, most likely RAM. Yes, it is entirely possible to have good RAM go "bad" after an OS update (whether it is actually bad or not, I don't know, but the hardware treats it as such). This happened to me after upgrading from 10.2 to 10.3, with RAM installed by Apple at the factory, so I know from personal experience that it can happen. So make no assumptions based on the origin of the RAM and have it thoroughly tested before taking any desperate measures (of which reinstalling the OSX is a leading example) that aren't likely to solve your problem.

I just ran Apple Hardware extended test, and all devices passed. This is really puzzling... I have already taken out every cable (I thought the USB was the problem) except for power and ethernet. Im running out of options here, and I need this comp everyday for school.

BTW, resetting the PRAM and NVRAM didnt help at all.

Thanks for your answers, I really appreiciate it

[IJ Reilly]

I just ran Apple Hardware extended test, and all devices passed. This is really puzzling... I have already taken out every cable (I thought the USB was the problem) except for power and ethernet. Im running out of options here, and I need this comp everyday for school.

BTW, resetting the PRAM and NVRAM didnt help at all.

Thanks for your answers, I really appreiciate it

The Hardware Test CD doesn't seem to detect all problems. Apple dealers have a more complete testing suite that will pick up problems not detected by Hardware Test. If the Mac is still covered under warranty, I'd take advantage of it. If not, you can try downloading an application called memtest. It's a bit of a pain to use (should be run in single user mode). Another suggestion is to download AppleJack (can be found on versiontracker) and run the full set of tests and repairs. It's fixed quite a few of my mystery issues.

[HiRez]

If a 0.5% chance that it will help is good enough, then go ahead and reinstall OSX.Oh it's 0.5%? That's great, I was not aware of that statistic, thank you. In my experience it's probably more like 10%-20%, and with him having his KPs right after upgrading, I'd say higher, but whatever. Yes it certainly could be a hardware issue, but reinstalling OS X with Archive option is a lot easier and faster than tracking down hardware problems, for a first step.

[janey]

One thing: Are you, by any chance, running a torrent application as one of those "simple tasks"? Torrent apps are a known source for Kernel Panics.
Actually, to be nitpicky, it's only one particular BitTorrent client that does that. Azureus has had that KP bug, but I do believe it got fixed a few versions back.


btw, I had a situation with my iBook where it wouldn't work after upgrading to 10.4.3 - kept kernel panicing before it got a chance to run loginwindow...reinstall usually fixes things - sometimes it's caused by really corrupt installs and such.

[ElectricSheep]

No I did not, and should I post some of the panic info in panic.log?

I couldn't hurt.

[IJ Reilly]

Oh it's 0.5%? That's great, I was not aware of that statistic, thank you. In my experience it's probably more like 10%-20%, and with him having his KPs right after upgrading, I'd say higher, but whatever. Yes it certainly could be a hardware issue, but reinstalling OS X with Archive option is a lot easier and faster than tracking down hardware problems, for a first step.

I thought I was being generous. In fact I've yet to encounter a single problem that required the reinstallation of OSX, but I was trying to allow that it was possible that it might in some instances actually be necessary, however remotely.

You need only read through similar issues reported here on MR to conclude that the vast, vast majority of kernel panics are hardware issues, and a clear majority of those are RAM-related. Most of the balance are defective motherboards, requiring service from Apple. In any event, a reinstallation of OSX will not fix a hardware problem, so while it might be easier, it also won't help.

[Mitthrawnuruodo]

Actually, to be nitpicky, it's only one particular BitTorrent client that does that. Azureus has had that KP bug, but I do believe it got fixed a few versions back.No, not only Azureus. The only KP I've had with my iBook was caused by the official torrent client itself: BitTorrent, back when I was running Panther (also caused numerous complete system freezes). But, it's true, that Azureus is the only one (I've heard) to do this with Tiger... ;)

[opusthe2nd]

Its happening to me a bit as well now. I cant point anything to it. I am betting it is the 2nd stick I put it in. I couldnt even get it to boot or boot from the DVD. Finally pulled a stick and it booted. Put the stick back in a days ago and it pooped out just once so far.

Never happened before the 10.4.3.update.

[IJ Reilly]

Are we seeing many/any other reports of RAM failures after the 10.4.3 update? It's hard to imagine why an OS upgrade would cause RAM to become unstable, but in fact this does seem to occur.

[lezer23]

ok guys... just poped out the extra ram, but it was to no avail.... Still KPed with the 512MB stick. Im going to resinstall OSX now, and I will let you know what happned. Here is some of the log file:

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000BFDFFBFD PC=0x00000000000675F0
Latest crash info for cpu 0:
Exception state (sv=0x32559780)
PC=0x000675F0; MSR=0x00009030; DAR=0xBFDFFBFD; DSISR=0x42000000; LR=0x00067598; R1=0x17883C10; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00067588 0x0006E6BC 0x00086488 0x00057B5C 0x000291C0 0x000233AC
0x000ABFAC 0x696C6472
Proceeding back via exception chain:
Exception state (sv=0x32559780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2D9A7C80)
PC=0x9000B208; MSR=0x0200F030; DAR=0xE40BF000; DSISR=0x40000000; LR=0x9000B15C; R1=0xBFFFF630; XCP=0x00000030 (0xC00 - System call)


Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x2100DC80)
PC=0x000227A8; MSR=0x00009030; DAR=0x00000004; DSISR=0x40000000; LR=0x000A9814; R1=0x0D0BBE30; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00032D64 0x000A9814
Exception state (sv=0x2DDE5780)
PC=0x9000B208; MSR=0x0000F030; DAR=0xA0741298; DSISR=0x40000000; LR=0x9000B15C; R1=0xBFFFF6D0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC

*********

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8304 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x2D881280)
PC=0x0006628C; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00066218; R1=0x17893C90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x000702E8 0x00062444 0x000A87F0 0x000ABC80
Exception state (sv=0x2DB8DC80)
PC=0x92981F20; MSR=0x4000F030; DAR=0x00000016; DSISR=0x40000000; LR=0x9075B02C; R1=0xF0509730; XCP=0x00000010 (0x400 - Inst access)

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC

*********


Sat Nov 19 08:50:49 2005
panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 00000000000A33C4, msr = 0000000002143000, dsisr = 42000000, dar = 000000000285E000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 00000000c07c0000

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x000A8D00 0x000A7F90 0x000ABC80
Proceeding back via exception chain:
Exception state (sv=0x3B12C000)
PC=0x000A33C4; MSR=0x02143000; DAR=0x0285E000; DSISR=0x42000000; LR=0x0009FDC4; R1=0xFC14FC21; XCP=0x00000008 (0x200 - Machine check)
Backtrace:

backtrace terminated - unaligned frame address: 0xFC14FC21


Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPC


Thats it for now.. tell me if u guys want more

[ElectricSheep]

panic(cpu 0 caller 0x000A8D00): Uncorrectable machine check: pc = 00000000000A33C4,

That's definitely not good. Machine Check exceptions are typically caused by a signal sent to an interface on the processor; this hints faulty hardware somewhere in your system. Couple that with the seemingly random DSI exceptions you were getting (panicking in different parts of the kernel) is further evidence you are experiencing failing hardware rather than a software issue.

[Sun Baked]

Try a different using the machine circuit breaker in the house.

If there are motors (air cond, refrigerators, fans, etc.) or fluorescent lights on the same line, they will cause just as many problems as an overloaded breaker.

[yenko]

ok guys... just poped out the extra ram, but it was to no avail.... Still KPed with the 512MB stick. Im going to resinstall OSX now, and I will let you know what happned. Here is some of the log file:

.........................
Thats it for now.. tell me if u guys want more

More than likely....you have a corrupt/broken/damaged directory file.
Causes vary from forced shutdowns, corrupt installs, corrupt app, and more.
The fix is to run fsck -f, or use Disk Warrior to repair the directory.
Also make sure your file system is Journaled. ;)

[lezer23]

That's definitely not good. Machine Check exceptions are typically caused by a signal sent to an interface on the processor; this hints faulty hardware somewhere in your system. Couple that with the seemingly random DSI exceptions you were getting (panicking in different parts of the kernel) is further evidence you are experiencing failing hardware rather than a software issue.

This sucks!!! what should I do? I have not reinstalled OSX yet due to the overwhelming comments that it probably will not do anything... What you are describing-- is it RAM, my logic board, etc? Is it something that I can fix, and what did I do to make it happen so I dont do it in the future. Thanks!

Oh and on the comments about power supply, it happens when I'm on battery too, I wish the fix were that easy.... Let me know your thoughts please! :confused:

[Sun Baked]

Oh and on the comments about power supply, it happens when I'm on battery too, I wish the fix were that easy.... Let me know your thoughts please! :confused:Earlier posts said it didn't happen on the battery and only at home, oh well.

[IJ Reilly]

If the problem is hardware-related, which seems quite likely, you are out of options except to bring it in for service.

You've already had several software trouble-shooting suggestions (short of reinstalling OSX). You could try some of them; they are relatively painless.

[MUCKYFINGERS]

buddy, i had this same problem and i took mine to the local applestore. they diagnosed the problem as a bad logic board, and my ibook got sent in for repair . . . it's been fixed and they're sending it back now, all within a week. if it's only 3 months old, you still have applecare, so go take advantage of it now.

[lezer23]

buddy, i had this same problem and i took mine to the local applestore. they diagnosed the problem as a bad logic board, and my ibook got sent in for repair . . . it's been fixed and they're sending it back now, all within a week. if it's only 3 months old, you still have applecare, so go take advantage of it now.

I think im gonna do the same. Watch out though, this same thing happened to my windows machine, and they replaced the logic board but it didnt help. But hey its windows. I guess were just unlucky, but it was happened to two of my computers of different platforms. WEIRD!

Thanks for all your help!

Although, now computer has some variety in its KPs or they may not be KPs. Now, sometimes white text over black backround spralws over the screen, and sometime the comp just freezes. I think I like the sprawled text, although the normal 5 language KP is very nice as well. Any thought on which way you like to be informed that your comp needs to shut down immediatly? :D
Have a nice thanksgiving all

[lezer23]

I just reinstalled OSX, and was really excited because for about 5 minutes after inital startup, my latop was fine. But then, out of the shadows, came the treacherous sign of complete defeat. The 5-language wonder also known as the Kernel Panic. Of course, if something has been learned from this, I have reinforced some of your comments on it now being a software issue. I think the most possible explanation is RAM, HDD, or more likely Logic Board. The reason I am thinking Logic Board instead of RAM is because, I have already (as previously posted) removed one of those sticks, and it still had a KP. Now unless it was the factory installed stick (which it is probably not) (and which I cannot remove by hand) that has ruled out the RAM. Additionally, my toshiba had a kp problem and it was the motherboard. It is probably not the HDD because it passes all tests and it is SMART verified. Also, my Ram passed its test even though many say that the apple test is not comprehensive enough. Any links on where I could get a mobo test or full computer test, so I could rule out even more. I plan on taking the machine to my local Apple Store on Wednesday, and hopefull they will fix it without sending it out (Pretty unlikely). Thanks! ;)

[opusthe2nd]

I am going have them send me a box for mine tomorrow I think. They want me to loop the hardware test tonight first though.