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

OS X keeps crashing on me!(?)

A pretty safe bet at that point. Unfortunately, most kernel panics are hardware related. If the issues continue, and it's not the RAM, then it's likely to be something more... expensive.
 
sk3pt1c said:
i think sleep on a mac and hibernate on a pc work differently :rolleyes:
Click to expand...

dinno how it works on the mac, but on a pc, the whole RAM is being copied to the HDD, the startup system is being reminded next time it just has to copy that to the RAM again, and then all the hardware is being shut down...
hwy would it be sifferent on the mac? doing it like thgis makes perfect sence IMO...
 
You ...

... said you had Apple Care Protection, bought in the UK? Apple Care is applicable anywhere and not bound to the country where it was filed - don´t let yourself get fooled by some store clerks at your place.

If it´s Apple local playing funky, write to Apple Europe and/or US and describe your problems getting proper Apple Care treatment; you payed for it firsthand, they will listen.

By calling Apple itself, you can get a customer case number, with which you would be able to contact any Apple certified ServiceProvider in your region. He then must do all necessary repairs, if it fits the specs of Apple Care, of course.
 
i didn't get apple care because it does not apply here, i read the contract carefully and did not consult with any store clerk.

anyway, the fact of the matter is that my RAM has passed all the tests so far so i'd like some advice on what it could be that's causing this panic attack :)

are there any diagnostic tools out there that i can use to check all my hardware thoroughly?

can i actually contact Apple directly by email to tell them my problem?
 
Checking memory in System Profiler

On the Menu Bar open the ? > About this Mac panel. Open the button More Info… Your System Profiler will start up. Find Hardware and click to reveal the Memory panel. Check the status of your memory now.

Sleep mode is buggy on all the Macs I've ever had. Simply shut down and wait the two or three minutes for her to start up again is all.
 
I think it's funny that people in mac forums always tell people to repair permissions, flash pram and then when those things don't work, it means you have bad RAM...

it seems like this is the advice given—no matter what the problem actually is—when OS X crashes. The implication being that OS X itself couldn't possibly have a problem or anything, so it simply must be a hardware failure, and since usually the only non-Apple-branded hardware is added RAM, that's the favorite whipping-boy.

in PC land, when the OS crashes, people start looking for driver and software conflicts, and start asking to see crash logs, etc. They don't tell people to rip their machine open and start "reseating" the RAM.

Please.

If the RAM isn't properly set, the machine probably won't boot up to begin with. He's having a problem with Sleep mode. Lots of people have trouble with Sleep mode. Often it's got something to do with an external hard drive or a USB connection to a cable modem or something like that, but it's an OS X problem, not a hardware problem. Driver incompatibility, or a buggy bit of code. something like that.

You guys were surprised when you found out he only had original RAM in there, like Apple uses magic RAM that's somehow better than the sticks fabbed and tested in the same factory that didn't get an apple stamp on them. if anything, apple goes cheap on their RAM to cut costs.

skeptic, can you post a crash log for us to look at? maybe we can get some useful information? or do you guys want him to keep pulling the RAM out and blowing on it like a Nintendo cartridge, hoping it will eventually work?
 
Ha, ha, ha. Now I'm laughing too. :rolleyes:

Speaking for myself, I never suggested that Apple RAM could not be the culprit, and I would not, as I've had bad RAM right out of the box. Also, I did not suggest resetting the PRAM or repairing permissions. Though this rarely helps, it can't hurt to try. But the fact remains that the vast majority of kernel panics are hardware related, and the vast majority of those are caused by bad RAM. Once RAM is eliminated as the problem, then experience dictates that other hardware issues should be investigated.

Sleep-related issues have to be considered on a model-by-model basis. Many Mac models, if not the vast majority, have absolutely no problems with sleep. Other do. I could not say which, though perhaps someone else can.
 
I'm suprised nobody has actually asked for the crash log.

Can you Spotlight for Console, open up the Logs sidebar, go to /Library/Logs, open the "panic.log" and post the most recent?
 
hahahaha, you rock man
i must say that i agree with you up to an extent

EDIT:looking for the log now

i'm not messing with the RAM anymore, since it did pass all those tests
so it's either something else, or it's fixed now (hopefully)
i've set it to go into safe sleep everytime i close the lid, i don't know
if that's gonna help at all...
i do have an external hard drive but it hasn't caused any problems for almost a year now...
 
right, here's the latest log

Code: 
Sun May 13 08:14:18 2007


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000037C3BCF9 PC=0x00000000002FEBD8
Latest crash info for cpu 0:
   Exception state (sv=0x43B60000)
      PC=0x002FEBD8; MSR=0x00009030; DAR=0x37C3BCF9; DSISR=0x40000000; LR=0x002FEC64; R1=0x2C8A3C20; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x002FEC64 0x003003EC 0x002B6EA4 0x002EAD54 0x0008B50C 0x0002921C 
         0x000233F8 0x000ABCAC 0x00000000 
Proceeding back via exception chain:
   Exception state (sv=0x43B60000)
      previously dumped as "Latest" state. skipping...
   Exception state (sv=0x4EF0BC80)
      PC=0x9000B6E8; MSR=0x0200F030; DAR=0xE02AF000; DSISR=0x42000000; LR=0x9000B63C; R1=0xBFFFBB30; XCP=0x00000030 (0xC00 - System call)

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=0x43B60000)
      PC=0x002FEBD8; MSR=0x00009030; DAR=0x37C3BCF9; DSISR=0x40000000; LR=0x002FEC64; R1=0x2C8A3C20; XCP=0x0000000C (0x300 - Data access)
      Backtrace:
0x002FEC64 0x003003EC 0x002B6EA4 0x002EAD54 0x0008B50C 0x0002921C 
         0x000233F8 0x000ABCAC 0x00000000 
   Exception state (sv=0x4EF0BC80)
      PC=0x9000B6E8; MSR=0x0200F030; DAR=0xE02AF000; DSISR=0x42000000; LR=0x9000B63C; R1=0xBFFFBB30; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.9.0: Thu Feb 22 20:54:07 PST 2007; root:xnu-792.17.14~1/RELEASE_PPC

and i have a last revision Powerbook 17" , if that makes a difference :)
 
The panic log doesn't reveal anything to me. The only time I get anything out of them is when they mention a specific component, which doesn't seem to happen very often.

You mention an external hard drive. I'd try running the Mac without it or any other peripherals attached for a while. The less you've got in the mix, the better, in terms of diagnosing the issues.
 
i'm finishing the re-install of the combo now.
will leave it for a bit and if it crashes again i'll try leaving the external HD
unplugged...
i
 
and yes, it's happened again! :(
i'll try having the external HD disconnected for a few days, see if that does anything...

help!
 
I know you don't want to keep messing with the RAM, but did you actually try it with only one stick in for a while? Did it also crash after sleep in that configuration?
 
i'm sorry but i don't remember
i had it running on one stick for a while and then starting testing them using memtest and rember
i'm trying to sleep after disconnecting the external hd, see what happens...
 
crashed again (with the external HD unplugged)
so i'm guessing no sleep mode for me until i get a new mac...
or pay ****loads to get it fixed :)
 
OSX crashing

I went through this post and noticed you use airport.

"...nah, i connect via airport"

I was having the same problems...

I know you have a PB G4 but there is a known issue with the MB and MBP, the airport, and Kernel Panics:

http://docs.info.apple.com/article.html?artnum=303712

Their fix is a little dated here, but I delved in futher and found a tip on re-uploading the firmware for my base station. So far so good.

...you might want to investigate this path.

I would first do this: Turn your airport off. Then do a test of putting your computer to sleep. And go from there.
 
Very doubtful. As you say, this is a MacBook/Pro issue. Also, I would expect to see Airport turn up in the log if this was the case, which apparently it does not.
 
i have reset PMU and PRAM and it didn't really help :(
doesn't seem to be the external hard drive either...
so i really have no idea what it could be! :confused:
 
sk3pt1c said:
i have reset PMU and PRAM and it didn't really help :(
doesn't seem to be the external hard drive either...
so i really have no idea what it could be! :confused:
Click to expand...

Start up in safe mode by holding the shift key as the computer starts up.
This will avoid loading third-party drivers. See if it still crashes...

Also, are you using filevault or encrypted virtual memory? A combo of those two? Try disabling encrypted virtual memory if thats the case...

Try making a new user, that is not admin, and log in as only that user. See if the crashing still happens.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back