Author Topic: Blockland caused a kernel panic on my Mac  (Read 3354 times)

It has to be. My computer is fine and nothing else was running.
Maybe hard disk corruption has begun on/spead to the part were Blockland is located on the disk?

Oh. Well prove me wrong but I don't have any viruses.

Anyway, the idea of anything not having a viruses for it is stupid because new ones are developed every hour, etc. etc. etc.

Probably hardware failure.

My hardware is not failing. I am watching my computer work properly right now. Would console.log help?

My hardware is not failing. I am watching my computer work properly right now. Would console.log help?

All hardware fails one time or another. Post a console.log if you like yes.

All hardware fails one time or another. Post a console.log if you like yes.
I am sure my hardware is not failing. Hold on.

It has to be. My computer is fine and nothing else was running.
Things run in the background without you launching.
Hell, you've admitted other stuff was running - antimalware. (As a side note, antimalware does /not/ prevent viruses).

I'd suggest the general things - go through updating drivers, try clean install of blockland.

It does sound like a hardware issue, as the kernal panic is the mac equivalent of BSOD; there can be a wide variety of things causing that but common things include out of date drivers, corrupt memory units, hard disk issues etc. Just because your computer is running fine now, doesn't mean there isn't an underlying hardware issue.

Console log may help, may also be useful to see if you can replicate the issue and say what you were doing when it happened.


Ninja - Belongs in help

Things run in the background without you launching.
Hell, you've admitted other stuff was running - antimalware. (As a side note, antimalware does /not/ prevent viruses).

I'd suggest the general things - go through updating drivers, try clean install of blockland.

It does sound like a hardware issue, as the kernal panic is the mac equivalent of BSOD; there can be a wide variety of things causing that but common things include out of date drivers, corrupt memory units, hard disk issues etc. Just because your computer is running fine now, doesn't mean there isn't an underlying hardware issue.

Console log may help, may also be useful to see if you can replicate the issue and say what you were doing when it happened.


Ninja - Belongs in help


What? Read the topic more carefully next time. I do not have antimalware. I said that in Lion you get antimalware.

I am not going to update drivers. My computer is too old.

I am sure it's not hardware failure because my computer functions fine befor and after


What?! Read the topic next time. I do not have antimalware. I said that in Lion you get antimalware.
Still, you will have other processes running, to think otherwise is naive.

I am not going to update drivers. My computer is too old.
This is no excuse to not update your drivers, drivers are specific to the hardware your computer contains

I am sure it's not hardware failure because my computer functions fine befor and after
As I said, "Just because your computer is running fine now, doesn't mean there isn't an underlying hardware issue."



It was running fine before. And what do processors have to do with antimalware?

Log:

Diagnostic:
RAM and or Processor were overworked with the amount of applications running in the background, and your Mac saved itself by shutting down.

It was running fine before. And what do processors have to do with antimalware?
Processes, not processors.

I still believe you should try updating drivers.
For your intel card - http://www.intel.com/p/en_US/support/detect

Looking at your ram/processor (2gb and dual core 1.85), i'd think you should be able to run blockland, however they are very low specs for recent computers. I'm not quite sure the system resources that are used by OSX. Did it crash when you were doing something quite arduous? Like setting off lots of physics or explosions at once? or having a lot of bricks ghosted?

You allotted too much RAM to the system, and to protect from asploding, your computer stopped itself. This is caused by running a server and other people making lots of different things, usually. So what Jeep said.

Eww...Macs..

Good thing i don't have a dell or HP ether.

 http://store.razerzone.com/store/razerusa/en_US/pd/productID.243119900

Best thing I've ever played on.