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

eyeluvmyimac

macrumors regular
Original poster
Oct 27, 2002
229
1
I was just coding (or attempting to code) in BB Edit then suddenly, this error message comes up. I have never seen or heard of anything like this before. I could not do anything, (ex: take screenshot, use mouse, keyboard, etc). So I grabbed my good 'ole Canon DV camera and took a still to show you all. After I restarted, it took much longer to restart than normal. If anyone knows how this could have happened, what it meant/what happened, and if anything needs to be done, please reply. Thank you.

PS- See the power logo in the center? I didn't notice that when I got the error message, so I have no idea how it got there.

error.jpg
 
awhile ago mine always did that...it was when i unplugged this one usb connector...i don't know maybe something wrong with the connector cause since i stopped using it it hasn't happened
 
Don't worry, it was probably a random thing. Before Jaguar, that kind of crash was much messier:

(Oh no! Macrumors crashed my computer! :))
 

Attachments

  • img_1358.jpg
    img_1358.jpg
    99.1 KB · Views: 454
..

Damn that used to happen to me a lot, but not so often with10.2 even though i have seen it a few times. (I like the way it rolls up on the screen - very Xish)
 
I had the same thing eyeluvmyimac had pop up a few times when I first had my iMac. I think that it had something to do with the external USB floppy disk drive.
 
Originally posted by FelixDerKater
They should admit that an error occurred, at least. Just saying that you computer needs to be restarted is a bit too vague.

it doesnt really matter. no matter what, you still have to reboot. doesnt really matter whether or not it tells you an error occurred. it tells you what the proper course of action is.
 
Originally posted by guitargeek
Well, it would be nice if it were more descriptive so that you can avoid it in the future.

not really. if you are knowledgeable enough to understand what the errors are, then you are smart enough to know where to look.

a kernel panic is a rare occurrence, and happens not because of the user, but errant software and/or bad hardware/drivers.
 
Do a hardware test

This is the exact same message I got a week ago with my 800mhz iBook. Eventually that is all my iBook would display. I ran a hardware diagnostic and the results whoed my soldered ram had gone bad - good thing it is still under warranty. If I were you I'd run that hardware diagnostic.
 
I've had that pop up several times on my TiPowerBook running OS 10.2.3 while going through a Keynote run.

Since I'm running the first TiPowerBook, there's probably not enough v-ram to keep such a graphics-dependent little jewel like Keynote totally happy. I jammed the display down from millions to thousands, and upped the OS to 10.2.4.

No problems since.
 
Originally posted by voicegy
I've had that pop up several times on my TiPowerBook running OS 10.2.3 while going through a Keynote run.

Since I'm running the first TiPowerBook, there's probably not enough v-ram to keep such a graphics-dependent little jewel like Keynote totally happy. I jammed the display down from millions to thousands, and upped the OS to 10.2.4.

No problems since.

it should work just fine in millions of colors now. the ati chipset on the original ti's were the victim of a flaw in the apple provided drivers that seemed to only be brought out by keynote. 10.2.4 should have fixed the problem.
 
well , i had a problem with 10.2.3 when installing it and my computer started doing that a lot, after 10.2.4 , never has it done it again.

when i asked for my comp specs it didn't show anything at all before, now everything is fine, after reinstalling or better said, upgrading to 10.2.4
 
Why I Love MacRumors

Originally posted by sparkleytone
it should work just fine in millions of colors now. the ati chipset on the original ti's were the victim of a flaw in the apple provided drivers that seemed to only be brought out by keynote. 10.2.4 should have fixed the problem.

After reading the above I visited my Dock and upped the colors to millions and ran the Keynote presentation...flawless.:D
 
Never

I've used tons of hacks, haxies, and other programs that im not supposed to use, and the only time in the year that ive been running os x that i've had a kernal panic is when i opened my powermac G4 400 while it was running. (Something that i advise you all not to dojavascript:smilie(':rolleyes:'))
 
Never

I've used tons of hacks, haxies, and other programs that im not supposed to use, and the only time in the year that ive been running os x that i've had a kernal panic is when i opened my powermac G4 400 while it was running. (Something that i advise you all not to :rolleyes:)
 
Never

I've used tons of hacks, haxies, and other programs that im not supposed to use, and the only time in the year that ive been running os x that i've had a kernal panic is when i opened my powermac G4 400 while it was running. (Something that i advise you all not to do:))
 
Yup, that's exactly the message I got that I posted in another thread a few days ago, while trying to connect to a Windows computer over SMB. I thought I was the first guy to discover this and thought that they had changed the notice since the 10.2.4 update, but alas, no. Not that I'm complaining! I haven't had a kernel panic happen to me since 10.1.4 I believe and that was b/c of bad RAM and a bad Apple power adapter that fried my RAM.
 
Originally posted by voicegy
I've had that pop up several times on my TiPowerBook running OS 10.2.3 while going through a Keynote run.

Since I'm running the first TiPowerBook, there's probably not enough v-ram to keep such a graphics-dependent little jewel like Keynote totally happy. I jammed the display down from millions to thousands, and upped the OS to 10.2.4.

No problems since.

On my iBook 500Mhz (8MB Ati) it crashed once. I find that you reallllllly should run your mac at 800x600 if you have 16MB/8MB and 640x480 if you have 8MB and need higher performance.

Sometimes the video card can die, and thus take down OSX with it. I attribute 98% of my keranl panics to running games and comming out of sleep. OSX only let me down maybe 2 times doing somethign else (running from public beta to 10.2.4 on 2 macs)
 
I do have continuing problems in 10.2.4 with SMB networking, but things are improving.

For example, you can get an eternal beachball this way:
(a) connect to a windows PC with SMB, so that the drive shows up on your desktop
(b) shut down the windows PC
(c) drag the network drive to the eject (trash)

I've gotten eternal beachballs with Appletalk too when using Airport while my hub was dying. Mac OS X is very sensitive to network hiccups.

I have never seen a kernel panic from these though (yet :eek: ).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.