freeze on screensaver — memory issue?
Last night I left the computer alone for several hours, and when I came home the screensaver (photo slideshow) was still running, then before bed I looked over and noticed the screensaver was frozen on a single picture and the system wouldn't respond to mouse or keyboard input to kill the screensaver. I had to force it to power down with the power button.
Here's what I found in Console covering the last few hours of activity (so, looks like 10:06pm was the last thing logged before/when it froze, then 7:31am is the
| 11/3/12 7:41:11 PM | GoogleSoftwareUpdateDaemon[2446] | -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown. |
| 11/3/12 7:49:13 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2485[ksadmin] clearing CS_VALID |
| 11/3/12 7:49:13 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2486[ksadmin] clearing CS_VALID |
| 11/3/12 8:39:23 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2610[GoogleSoftwareUp] clearing CS_VALID |
| 11/3/12 8:49:14 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2646[ksadmin] clearing CS_VALID |
| 11/3/12 8:49:14 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2647[ksadmin] clearing CS_VALID |
| 11/3/12 9:38:06 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2768[GoogleSoftwareUp] clearing CS_VALID |
| 11/3/12 9:49:13 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2808[ksadmin] clearing CS_VALID |
| 11/3/12 9:49:13 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2809[ksadmin] clearing CS_VALID |
| 11/3/12 10:06:20 PM | mDNSResponder[18] | PenaltyTimeForServer: PenaltyTime negative -5991, (server penaltyTime -2078304887, timenow -2078298896) resetting the penalty |
| 11/4/12 7:31:54 AM | kernel | npvhash=4095 |
| 11/3/12 10:36:49 PM | kernel | CODE SIGNING: cs_invalid_page(0x1000): p=2925[GoogleSoftwareUp] clearing CS_VALID |
| 11/4/12 7:31:54 AM | kernel | PAE enabled |
| 11/4/12 7:31:54 AM | kernel | Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 |
Are these messages suggestive of memory going bad, or something else identifiable? I've also had some issues withoccasional spontaneous restarts over the last couple of years, but that's never really been diagnosed either.
Mac mini, Mac OS X (10.6.8), 2007 1.83 GHz Core Duo, 2GB RAM
