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.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
HELP!!! Comp. unexpectedly shuts down
- Thread starter lezer23
- Start date
- Sort by reaction score
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
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
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.
lezer23 said:
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.
ElectricSheep said:
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!
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.
You've already had several software trouble-shooting suggestions (short of reinstalling OSX). You could try some of them; they are relatively painless.
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.
MUCKYFINGERS said:
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?
Have a nice thanksgiving all
Well...
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!
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!
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.