everything just STOPS

[roarg]

Unibody Macbook Pro June 2009 edition
13.3'' OSX snow leopard 10.6.2
2.26Ghx intel core 2 duo 4GB DDR3


Basically, every couple hours or so, my whole computer just stops responding.
First symptoms are: my internet stops working(still responding) then, as i try to force quit, program dose not respond, nor does it close. All programs not responding. I even try to reboot finder, no luck. I try to restart or shut down computer, dosent work. This is all accompanied by the SBBOD.
only way to fix this is to manually restart, holding the power button...

ive had this problem for about a month now, and have run Virus barrier X5 several times, no viruses.

help?

 

[angelwatt]

Some things to try, to track down the issue. First, see if there are any crash logs related to it.

~/Library/Logs/CrashReporter/

You'll likely have a number of logs, not all are bad, sometimes things just crash. I suggest going to list view and then sorting by Date Modified. Then look for logs that occurred about the same time as when you force reboot.

Also, just make note of the time when you do the reboot. Open Console (/Applications/Utilities/) and choose the Console Messages on the list at left. There's tons of logs coming in, but scroll up to the time you noted and see if you can see anything obvious. It'll be hard to spot stuff admittedly, but worth a shot. If you suspect a specific application maybe being the culprit you can see if it has a specific log file in the list at left too.

 

[roarg]

This happens everyday, and the logs seems to show JavaApplicationStub_2009-09-15-012237_*****-macbook-pro.crash

as the most frequently occuring..

but it dosent seem to have a log for ever crash that has happened, but ill be sure to post the next one when it does

 

[roarg]

Ok it just happened. No crash log, but console says:

09-12-23 3:20:16 PM com.apple.launchd[1] *** launchd[1] has started up. ***
09-12-23 3:20:40 PM com.intego.commonservices.daemon[47] Using preferences format 3

09-12-23 3:20:47 PM com.apple.launchd.peruser.501[92] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self

09-12-23 3:20:49 PM com.apple.launchd.peruser.501[92] (com.apple.Kerberos.renew.plist[116]) Exited with exit code: 1

09-12-23 3:20:52 PM com.apple.launchd.peruser.501[92] (com.apple.CSConfigDotMacCert-@me.com-SharedServices[122]) Exited with exit code: 1

09-12-23 3:20:53 PM com.apple.WindowServer[72] Wed Dec 23 15:20:53 ****-macbook-pro.local WindowServer[72] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

09-12-23 3:20:56 PM Adium[139] *** WARNING: Method drawsGrid in class AIAnimatingListOutlineView is deprecated. It will be removed in a future release and should no longer be used.

09-12-23 3:20:58 PM [0x0-0x11011].com.adiumX.adiumX[139] SocketRead: read(5) error 0

09-12-23 3:20:58 PM [0x0-0x11011].com.adiumX.adiumX[139] SocketRead err = -9802


09-12-23 3:21:03 PM SystemUIServer[97] /SourceCache/SpotlightUI/Spotlight-507.4/menu/Application/../Models/MDQueryWorker.m __+[MDQueryWorker startQuery:withOptions:]_block_invoke_1 Can't execute query '(* = "sm*"cdw || kMDItemTextContent = "sm*"cdw)'


09-12-23 3:21:22 PM [0x0-0x11011].com.adiumX.adiumX[139] SocketRead: read(5) error 0

09-12-23 3:21:22 PM [0x0-0x11011].com.adiumX.adiumX[139] SocketRead err = -9802

09-12-23 3:21:25 PM [0x0-0x12012].org.mozilla.firefox[144] Debugger() was called!

____________________________


then i rebooted.. is it adium?

 

[angelwatt]

Here's something to look at, found by searching on some of the log info.
http://discussions.apple.com/thread.jspa?threadID=2271244&tstart=0

 

[roarg]

ok i installed the update package, check and fixed disk and permisssions. it seems my disk was corrupt.. =/?

what causes this and how do i prevent it?

 

[angelwatt]

ok i installed the update package, check and fixed disk and permisssions. it seems my disk was corrupt.. =/?

what causes this and how do i prevent it?

That list is long for what causes it, but prevention is kind of hard. A lot of people run the permissions check before and after each system update or whenever they start having computer problems. The problems can be caused by programs that don't handle certain errors well, or when applications crash, the system is turned off improperly, etc. At least you found the problem and got a solution.

 

[roarg]

ahh, they are still here! a bit more frequent actaully.. should i do disk repair again?