![]() |
|
|||||||
| Tech Support Trouble running the game? Found a bug? Post here. |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Okay, I didn't know if I was supposed to put this in tech support but W.E
So, my problem is that EVERYTHING (including alty) unexpectedly quits like all the time. sometimes there is enough time to do something, but I can't even play alty anymore most of the time. I've tried repairing my disk in disk utility, but it said that it was OK, I've tried deleting corrupted fonts (people said that that might be the problem) But nothing works. Do any of you know what the problem is or have had this problem or how to fix the problem? Please help, I would be very grateful
|
|
#2
|
|||
|
|||
|
Run "memtest" (http://www.memtestosx.org/joomla/index.php) and see what it throws up. Sounds like broken RAM.
|
|
#3
|
|||
|
|||
|
Is there a free application similar to that?
|
|
#4
|
|||
|
|||
|
You repaired the disk. Have you also repaired permissions? You could try turning off all (or most, but I'd go with all) startup items in Login Items and restarting the computer to see if that fixes it.
|
|
#5
|
|||
|
|||
|
Sorry I didn't realize it was a paid app for OS X. Here are some alternative http://guides.macrumors.com/Testing_RAM, I strongly suggest "memtester" (built from source).
Or... If you have boot-camp installed with Windows running, try seeing if Windows also behaves cranky, if so it's almost definitely a RAM/hardware issue. But if you don't, try memtester. Does the computer restart randomly too? |
|
#6
|
|||
|
|||
|
Quote:
Tg, could you get on ichat. I don't have intel so I do not have boot camp, The Computer doesn't restart randomly but I have had 3 kernel panics since this little party started. |
|
#7
|
|||
|
|||
|
Well kernel panics can give you a clue as to what is failing. If the BSD name of the corresponding crashing thread in all kernel panics is changing, then it's a good chance it's faulty RAM. Otherwise it could be one driver in which case you could try removing the driver/app responsible for bringing down the system.
|
|
#8
|
|||
|
|||
|
Nikon says that it was a memory issue with one of the chips and looks to be resolved now.
|
![]() |
|
|