Satellite L675 D Hard Freezing Under Low System Loads

L675 D
AMD Turion 2 P540 Dual Core 2.4GHz
4Gb Ram (3.75 Usable)
64 Bit
Windows 7 Home Premium
The computer hard freezes with no HD light activity, mouse response, keyboard response, etc. The screen freezes and all inputs fail regardless of how long it is left alone. On a handful of occasions a repeating (very annoying) tone has accompanies the freeze and does not stop until the power button is held down. The problem started intermittently a few months ago and has increased in frequency. Numerous virus scans by various anti-virus software programs have revealed no viruses. It seems the busier I keep the computer the less likely it is to freeze. Examples include playing games or streaming hulu. However, if I leave the computer running with either no programs running or a low demand program (MS Word in class) it freezes usually within a couple of minutes. I am in college and the only way I keep the computer from freezing while taking notes is if I have hulu streaming in the background. I frequently clear unused programs and items that I don't use. Idle Physical memory usage is at 37% and Idle CPU Usage is around 3%. I have a cooling pad for the laptop and the air from the fan never seems hot or even warm. Any advice is greatly appreciated as this is starting to get a bit old.

Try using System Restore to restore a previous restore point from before this became an issue.
- Peter

Similar Messages

Late 2008 MacBook Pro unibody - Hard Freezes under Vista 32bit

Hi folks,
I am a relatively new Mac fan (started a few years ago when I purchased a Mac Mini for home because I didn't want to suffer Windows at home as well as at work!)
Anyhoo, late last year I purchased a MacBook Pro Unibody jobbie so that I could have the best of both worlds for my work. I can run Visual Studio under Vista for C++ development under boot-camp and run the Mac and OSX for just about everything else.
However: I have a problem that is testing my patience to brand new levels. In summary:
About once every couple of hours or so (and it's not reliable: could be after 30 seconds, could last several hours) Vista freezes. And I mean freeze: it takes a "hold the power button down" routine to get out of it. This, of course, has made Vista and lots of my work pretty upset. There's nothing quite like writing to a file when this happens for maximum tears. I'm running through tissues like you'd never believe
I have done some research on this over the months and have tried many possible solutions including, but not limited to, ensuring that I'm fully patched up and that there is no suspicious software, updating all the drivers (paying particular attention to NVIDIA's ones - as a DirectX/OpenGL programmer for the past 10 years I'm acutely aware of how touchy they are). None of these have worked.
The closest I've come to something that looks like a solution is this thingie called Riva Tuner; but it does not recognise the April 2009 NVIDIA drivers.
I understand that it could be linked with something NVIDIA's drivers do to speed up/slow down the cards depending on load/heat/whatever.
I'm so far down my tether at this point I really do not know where to turn. I love my MacBook, but I need Bootcamp and Vista to do my job. It was my choice to get a Mac rather than a PC, so I guess it's my own fault. I have seen many other users on the Internet who have the same problem but none of them appears to have a fool-proof resolution to this issue.
Thus, I thought I'd come here, get my best begging trousers on and grovel to Apple and to the learned users here to see if there is something that I can do to get everything working again so that I can continue to bask in the MacBook Pro glory knowing that my Vista installation is reliable.
Grovelling over,
Mr Cuttle.
Message was edited by: Mr Cuttle

Do you have anything against running Windows in a VM (virtual machine) under OSX to do your work? On the unibody, this is much more stable than boot camp in my experience.
here are the steps I took
1) install smcfancontrol in OSX
http://www.eidac.de/
2) install virtualbox free virtualization software from Sun Microsystems
http://download.virtualbox.org/virtualbox/2.2.2/VirtualBox-2.2.2-46594-OSX.dmg
3) install Windows using virtualbox like normal; use smcfancontrol to bump fan speeds if it runs hot (normally not needed unless you watch video or game).
4) turn on seamless mode and run your windows apps side by side with OSX apps for free.
if you have issues setting it up, read here:
http://www.virtualbox.org/manual/UserManual.html
this video shows how it works, albeit with a weird Japanese game app instead of Visual C++
http://www.youtube.com/watch?v=Z47MKa9Jdwk
and this screenshot that I took shows just how much you can do with this:
http://img505.imageshack.us/img505/5916/picture1zdk.png

10.4.10 and hard freezes

As we are just about to get 10.5.0, I need to get to the bottom of an issue I have with my Mac Pro (4-core, 5gb, 2 x 500gb, 1 x 250, Bluetooth & Wireless).
When I update to 10.4.10, it suffers from random hard freezes. The system will just stop, no kernel panics, etc, just stopped. Only a power cycle will fix.
Anyone any idea of how to diagnose, or other options?
I dont want to get to leopard and not be able to use it as it may have the same issues as 10.4.10.

If you have a free drive (buy one if you don't) erase it, write zeros to it and then install a clean copy of Mac OS X and the software you're frezzing with. If the problems go away then you know the issue isn't hardware.

Satellite L675 is locked in a loop of "configuring system"

I have a Satellite L675 pre-loaded with Windows7 64-bit, because it was very slow so I decided to recovere it to the factory default out-of-box.
But it has now been locked in a loop of "configuring system" with several reboots for more than an hour - does that make any sense?
Regards,

Hello
The recovery process takes a very long time and your notebook will restart several times during this process. A lot of drivers and tools will be installed so its not unusual.
In my opinion you should wait a little bit longer until recovery installation finished successfully. Just relax during this time with newspaper and coffee ;)

Satellite A210-1UP - Every few minutes the system freezes

Hi,
I just installed windows 7 32 bit on a satellite A210-1UP
Every few minutes the system freezes and then continues as if nothing happened.
No errors or blue screens are displayed
I would like to know if windows 7 can run without problems on this system ?
Which is the recommended bios version to run windows 7 ?
Thanks in advance !
Kind Regards
Stijn

Hi buddy,
Yes, Windows 7 works on Satellite A210 properly, the hardware is powerful enough.
I dont think the freezes are problem of Windows 7 or your notebook itself, I think its a software malfunction Have you installed all drivers and are yellow exclamation marks in device manager?
Such freezes could be also caused by security software or if you run a lot of background processes. Good security software is AntiVir in my opinion so I can recommend this program to you.
Also check the startup folder and msconfig (start > run > msconfig). There are all programs listed they startup with Windows and you can disable the programs that you dont need at startup like Adobe Reader, Java Updater, Nero tools, etc. but thats depending on installed software. ;)

My Satellite L675-S7016 freezes when I don't work with it 5-10 minutes

My Satellite L675-S7016 freezes when I don't work with it 5-10 minutes and only if plugged with power cable, on battery power no problem with freezing.
I switch off sleep options in power manager on all power profiles, but problem still here.
Who ever met the same problem? How to solve?

od, what computer do you have? Does it ever "unfreeze" or do you have to power it down? When does it freeze?
- Peter

Mid-2009 MBP Has Been Hard Freezing, I think it may be the SSD or software?

Please read this fully so you don't end up suggesting something I've already tried.
I have the Mid-2009 version of the 13" MBP that I received in December 2009. Almost two years ago, I upgraded it to8 GB of RAM and a 256 GB SSD. Everything has been running smoothly until about 2 or so weeks ago. My computer has been having hard freezes, meaning, it's not simply an application freezing up; force quit doesn't work, the clock stops ticking, the whole system freezes. It was very predictable too. Whether i was watching youtube videos with flash, reading online articles without it (I have ad block) or doing something completely non-flash or web related, my computer would hard freeze after about an hour or two or so of use, requiring a hard reset (holding the power button until it turned off and then restarting).
I did some research on this and from what I initially found I thought it was problems with the motherboard. However, I found that to be odd because my motherboard was replaced by Apple in September 2012. I read somewhere to try a system hardware diagnostic test (press D upon start up). On the short hardware test, the one that only takes a few minutes, it passed without any problems. Then I tried the longer hardware test, the one that says takes more than an hour. I put that one on and left it alone. I came back every so often and checked on it and it was fine at first. The mouse responded and the test was showing some measurable progress. However I came back, and at 2 hours 11 minutes and 59 seconds into the hardware test, it froze without completing it.
Then I tried doing something everyone says to do when anything happens: I repaired disk permissions. I did that, and according to Disk utility everything went rather swimmingly. However, that didn't fix anything,in fact, it made things slightly worse. Ever since I reset disk permissions, everytime I open Safari, it freezes immediately, and that has only happened since I repaired disk permissions. My home page is about:blank, if anyone was wondering. I've only discovered this happening with Safari as of now. I switched Chrome as my primary web browser for now.
Being the resourceful person I am, I tried to isolate the problem. My sister, luckily, has an identical MBP. First, using target disk on my computer, I booted my SSD onto her computer - this is to see if the problem was HDD/SSD related or motherboard related. When I booted my SSD onto her computer the same problems occurred: Safari froze upon start up, and then computer would hard freeze after about two hours. However, when I booted her HDD onto my computer via target disk, there were no problems. Safari opened just fine and I used her computer for several hours without issue.
At this point, I was pretty sure it was the SSD, but I thought it was possibly a bad Sata cable or something. But nope. Last night, I switched harddrives completely. No target Disk. I put my SSD in her computer and put her HDD in my computer. I got the same results as target disk. It can't be the motherboard or memory, because both computers worked fine with my sisters harddrive. Only the computer booted off of the SSD would have these problems.
At this point I think it could be two possibilities
A) Either the SSD itself is starting to become defective
B) Some software component of my SSD is buggy
I think it could be something software related because why would Safari and safari only freeze after launch, but no other apps? Also something of note, these problems were happening, I tried to see if doing anything with software update would help, updated everything that needed to be updated, and these problems still occurred.
What do you guys think? anyone have an idea of what it could be? Any suggestions of how I handle this? Applecare is expired. I'm considering doing a clean install but I'm not fully backed up yet and I don't want to waste my time and have it not work. But I also don't want to buy a new hard drive or SSD and have it do the same things. And I'm not getting a new computer if the only problem with it is contained within the storage unit, whether that problem is within the software or hardware related.
Responses and suggestions would be highly appreciated, thanks.
EDIT: this information may be of interest: currently have 19.51 GB of available space (out of 256 GB). At one point, about a month and a half or so ago, my storage was as low as 9 or so GB free.
I am running OSX 10.6.8

I have tried making a new user account like you suggested. It fixed the Safari problem; Safari opened and played video just fine. However, the computer still hard freezed after about 2 hours. I am about to back up my computer via time machine after this (hopefully it'll finish before it hard freezes again, I haven't backd up in more than a year). If that doesn't work, I guess I'll have to move folders individually onto an external. I will proceed after backup with a clean install as that is my only other option for now.
However, after a clean install, should I restore directly from time machine? I would think wiping the hard drive and replacing it with what's on time machine wouldn't solve the problem because the inherent corruption is being restored. However, what about just restoring my User folder? What would the process be for getting everything back to normal as quickly as possible? Do you know of any good ways to get my apps and other preferences back to normal ASAP without corrupting anything? Will I have to re-register anything? For example, I have Adobe CS4 that I received from my highschool IT department. I have since graduated, so I don't have the disc or any of the password codes. Would it be risky to restore the application support folder (because that's where the bug may lie)? Or if I just drag just drag apps, would that still work or is the application support necessary too?

Random hard freezing issues, Windows 8 64-bit on Macbook Pro (Late 2008)

Hi,
I recently upgraded to OS X 10.8.3 and got a hold on copy of Windows 8 64-bit. As I'm running on my old trustworthy 15 inch Macbook Pro (Late 2008), my hardware is officially unsupported. Over the years I've had XP, Vista, Win7 32-bit and 64-bit running running on the same machine, and thought I'd give Win8 a chance.
To be able to install Win8 on my unsupported hardware, I tricked the Bootcamp assistant that I was going to install Win7, and after the reboot and start of the Win7 installation, I exited the installer, rebooted, switched DVD to Win8 and did the installation from there. So far so good. For installing the Bootcamp drivers, I followed the instructions in https://discussions.apple.com/thread/4894920?tstart=90.
Now, the machine runs just fine with Windows 8, and I've installed some basic third party applications (Firefox, Spotify, Steam). However, I get completely random hard freezes on the machine (sound looping, no other activity whatsoever) during normal use. These can occur 20 minutes after start, or 3-4 hours in. The freezing behavior is very much similar to how my model can behave under overheating conditions (which mostly have occured in past Windows versions while gaming), however overheating doesn't seem to be the issue here (based on simple palpation ).
Have anyone experienced a similar problem, or know something about it? My current idea is that some weird things are going on with the Bootcamp drivers, so unless anyone comes up with a suggestion I might try doing a rollback to the point before I installed the drivers to see what I can make of it.
Thanks!

Had a few similar short system freezes, after installing Windows 8 x64 on 13” MacBook Pro Mid-2010 with BootCamp 5.0.5033.
There is a suggestion that DisableDynamicTick may fix the problem: https://discussions.apple.com/message/21565295#21565295. There were similar topics at Microsoft forums: 1, 2, 3. It was said “that this will likely reduce system battery life, so it should be undone when you update your Windows build or if it doesn't resolve your issue”, and that “this problem is resolved in the release versions of Windows 8”.
Another possibility is that there is indeed a buggy driver, within BootCamp 5.0.5033, or a 3rd party, like a wireless network driver in the following case http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/system-fr eeze-randomly-after-installing-windows-8/49488183-26cf-4389-af21-a85dc366c99a?pa ge=2#LastReply.
The problem has been noticeable on my MacBook, but not annoying enough yet to spend time troubleshooting. If you find a robust solution, using the links above or other method, it would be interesting to know.
HTH

[Solved by moving to Ubuntu] VirtualBox freezes the entire system

Hello everyone,
I have some major issues with VirtualBox, I have recently installed it for the first time, but it just randomly freezes my entire system. There shouldn't be any load on the processor for this to happen. I don't really know what the cause is. I tried both Windows XP and Windows 7 as guest systems with the same sad outcome. The host and guest freeze and I have to do a hard restart. There always is some noise that comes from the sound card and, in the case of VMWare, from the case speaker.
I tried disabling AMD-V - using a Phenom II x4 955 - but it didn't work. I also tried adding nohz=off to the grub line but it also didn't work. I have recompiled the kernel modules after the last kernel update - 2.6.32. I can't really say whether it's only related to the last kernel update or not as I only started using it after the update.
It seems that I have similar issues with VMWare player.
Here's my system information:
Arch64
Kernel 2.6.32
Phenom II x4 955
4 GB of ram
Virtualbox 3.1.2-2 from the AUR
This only issue occurs with VirtualBox and VMWare, I did test the memory and it's okay. I also have plenty of fans - 2x120mm + 2x80mm - and my system temperature (using k10temp) never goes above 48 c under load. So, it isn't an issue with overheating.
Does anyone have any similar issues? Do you have any suggestions for this?
Thanks!
Last edited by DavidR (2010-01-21 23:54:22)

Should I ask to have this thread moved to the 'Pacman & Package Upgrade Issues'? Will anyone be able to help there? I am seriously starting to consider downgrading the kernel once again and seeing whether it will work.
Does anyone have a machine with another 64-bit distro with this kernel version? If so, can the problem be replicated there? I don't know whether this is really related to Arch or the kernel. Should I file a bug report somewhere? and if so, where can I do it?
http://www.archlinux.org/news/477/
May it be related to the xen support that has been added to Arch64?
Last edited by DavidR (2010-01-14 08:18:30)

Rendering and Low System Memory issues in PE9.

Hello again.
N.B: I am an ex-PE3 user.
I am having a few issues with PE9.
1. My main issue is that I am regularly getting the 'low system memory; please proceed with caution' message. I have googled it and read people's suggestions, but am not sure where to go from here. I have tried saving my file under another name, but am already up to '....E' (fifth) version of the file I've been working on this afternoon. The total time of the project is only approx 45 min's, although I will say that this 'low system memory' issue seems to be worst today, as I'm adding more still photos.
2. One of the suggestions made by Steve G on one of the forums was to make sure projects are regularly rendered. When I hit 'Enter' to render, the little render window pops up for a split second and then disappears. And I would assume from the red line above my timeline that my file is not rendered.
3. When I switch to 'Sceneline' view, my horizontal scroll-bar across the bottom will only drag SO far (to a certain point in my project; but definitely not to the end of my project. It is really frustrating. I sometimes can fix it by flicking between Sceneline and Timeline, but I have to do this multiple times... and it seems a ridiculous way to do it.
It would be fantastic if someone could help me with these issues, please!
System details:
AMD processor 3.2 Ghz
4 gig RAM (3.12 gig usable)
Windows 7 Ultimate

Hi everyone:
Thankyou for all your suggestions.
Sorry, Bill, but both those links give me an error message. I was all set to read them, but they won’t work, unfortunately.
What is meant by ‘page file managed’, sorry? And do you mean ‘hard disk drives’ by HDD, or does it stand for something else in this context? I’m not sure what you mean by how do I have them allocated. Again, apologies for my ignorance. I do have only one HDD, but it is partitioned.
The image sizes all seem to have a depth of 24, but vary in dimensions – I can see that some are quite large (around 3 mg in size, with dimensions of 4288x2848, for example). Is the actual mg-size relevant, or only the physical length and width?
I have tried to look at the frame size of my project, but it seems to be greyed out. In pale digits, there is 720x576 written.
Just before I sent this, I thought of one other thing to try first.
I tried starting a ‘New Project’. I then inserted just 6 still photos, for experimentation purposes. I then hit ‘Enter’ and the Rendering window came up and appears to have rendered correctly. So I then tried looking at one of my other projects (that hadn’t previously been rendered) and tried to render it. In this case, as in for the project I am currently working hard on, the Rendering window flashes up for about ¼ of a second and then disappears.
What is going on???
From: Bill Hunt [email protected]
Sent: Friday, 11 March 2011 2:00 AM
To: rachel jewiss
Subject: Rendering and Low System Memory issues in PE9.
although I will say that this 'low system memory' issue seems to be worst today, as I'm adding more still photos.
What are the pixel x pixel dimensions of those still images?
What is the Frame Size of your Project?
How is your Page File Managed, and what is the size? This http://forums.adobe.com/thread/632449?tstart=30 will give you some background and tips.
Also, tell us about your HDD's, and how you have them allocated.
For more discussion on Rendering, please see this http://forums.adobe.com/thread/794719?tstart=0.
Good luck,
Hunt

Satellite L675-11H - Can't access and/or read files on USB flash drive

Hi all,
I recently bought a Toshiba Satellite L675-11H and was trying to transfer files from a USB flash drive on my Toshiba hard disk. The files have been previously transferred from my old laptop (HP - XP) to my USB flash drive.
My new laptop can't access the USB flash drive at none of the USB ports I connect the flash drive to. What might be the problem here? Thank you for your help or any helpful advice!

Hi Rush,
Can you post more detailes about this behavior? What happens if you connect the HDD to your notebook, do you see that Windows installs drivers for new USB device or do you get an error message? If you have connected the USB drive check the disk management of Windows if its recognized there (Control panel > system and security > Administrative tools).
Have you already tested other USB devices such as USB mouse? If they dont work too the problem could be related to USB ports. In this case you should remove all USB ports from device manager and restart your notebook. Also update the chipset driver could help.

Mid 2014 Macbook Pro Hard Freezing due to GPU Hang...

Hello,
I have a Mid-2014 Macbook Pro (10.10.2) that I have been using for a few weeks now. I keep on getting random hard freezes on Google Chrome. Before, this used to happen about once a week, but now it seems to be happening much more often (like once to twice per day) - I haven't updated my software recently so this could possibly be an issue. When I had this exact same GPU hanging issue on my first Macbook Pro (bought 2 months ago), I had it exchanged for this one, but now I am encountering the same problem! I tried looking at Console.app and got a System report telling me that I had a "GPU reset"and also showed an "Intel GPU Hang Summary" with a "hang analysis". I know this is most probably relating to the GPU to some extent, but I'm not sure what exactly is the cause of this hanging. Any ideas? Also, any way to get around the hanging problem (I can just decide not to use Chrome anymore, but that would be a band-aid solution at best).
Thanks!

Could this really be a hardware issue at this point?
The best way to determine that is to have it tested.

Macbook Pro Mid 2014 Hard Freezes and Crashes

So I bought my Macbook about a month ago, and ever since then Ive been having this same issue over and over again. I have tried every solution apple has thrown at me and nothing has seemed to fix it. I have sent it out for a repair, reinstalled the OSX, Cleared the pRam, and various other things. I have not narrowed down the situation myself and cant seem to figure out what is causing these hard freezes and crashes. It always happens randomly at something GPU related it seems. Almost like the video card gets to stressed out at crashes. From scrolling up the page of a website to switching to a different video on youtube, all these little and sometimes big things have caused it to crash. Apple has sent it out for repair and they claimed that they fixed the logic board, but that didn't work because the issue still persists. I have reinstalled the OSX from guidance of a apple care associate over the phone. Ive eliminated almost every possible situation they have given me and nothing seems to fix it. Im not sure if there is a defect in these particular models or I just got a lemon but either way its frustrating. I will post the specs below and provide any other info that is asked.
SPECS:
GPU: Intel Iris Pro
Processor : 2.2 GHz Intel Core i7
Software: OS X 10.9.4
RAM: 16 GB 1600 MHz DDR3

Here is the Diagnostic report from earlier tonight:
Mon Oct 13 22:19:43 2014
panic(cpu 2 caller 0xffffff8002854c66): "a freed zone element has been modified: expected 0 but found 0, bits changed 0, at offset 24 of 32 in zone: kalloc.32"@/SourceCache/xnu/xnu-2422.110.17/osfmk/kern/zalloc.c:461
Backtrace (CPU 2), Frame : Return Address
0xffffff81ef62b970 : 0xffffff8002822f79
0xffffff81ef62b9f0 : 0xffffff8002854c66
0xffffff81ef62ba30 : 0xffffff800285273d
0xffffff81ef62ba90 : 0xffffff8002851dc9
0xffffff81ef62bb90 : 0xffffff800282aa3f
0xffffff81ef62bbc0 : 0xffffff8002c4e7dd
0xffffff81ef62bbf0 : 0xffffff8002c65767
0xffffff81ef62bc20 : 0xffffff8002c63cf3
0xffffff81ef62bc70 : 0xffffff8002c621b5
0xffffff81ef62bcd0 : 0xffffff8002c5268c
0xffffff81ef62bd10 : 0xffffff7f83e2140e
0xffffff81ef62bd40 : 0xffffff7f83e2124e
0xffffff81ef62bd60 : 0xffffff8002c64408
0xffffff81ef62bd70 : 0xffffff8002c5268c
0xffffff81ef62bdb0 : 0xffffff8002c8b903
0xffffff81ef62bdd0 : 0xffffff8002c96241
0xffffff81ef62bde0 : 0xffffff8002cccef8
0xffffff81ef62be20 : 0xffffff80028b24bb
0xffffff81ef62be50 : 0xffffff8002826bc1
0xffffff81ef62be80 : 0xffffff80028139c5
0xffffff81ef62bef0 : 0xffffff800281e013
0xffffff81ef62bf70 : 0xffffff80028c9b8d
0xffffff81ef62bfb0 : 0xffffff80028f3f66
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAcceleratorFamily2(98.22)[0EC64777-94B9-32E3-AC03-A2367895744 B]@0xffffff7f83e05000->0xffffff7f83e68fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[4662B11D-2ECA-315D-875C-618C97CDAB2A]@0xffffff 7f82ebe000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0 xffffff7f83d74000
BSD process name corresponding to current thread: plugin-container
Mac OS version:
13E28
Kernel version:
Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
Kernel slide:     0x0000000002600000
Kernel text base: 0xffffff8002800000
System model name: MacBookPro11,2 (Mac-3CBD00234E554E41)
System uptime in nanoseconds: 563483606094
last loaded kext at 246884990321: com.apple.filesystems.msdosfs    1.9 (addr 0xffffff7f83eeb000, size 65536)
last unloaded kext at 381093543497: com.apple.driver.AppleIntelMCEReporter    104 (addr 0xffffff7f83dc7000, size 32768)
loaded kexts:
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleUpstreamUserClient    3.5.13
com.apple.driver.AppleGraphicsDevicePolicy    3.6.22
com.apple.driver.AudioAUUC    1.60
com.apple.iokit.IOBluetoothSerialManager    4.2.6f1
com.apple.iokit.IOUserEthernet    1.0.0d1
com.apple.driver.ApplePlatformEnabler    2.0.9d6
com.apple.driver.AGPM    100.14.28
com.apple.driver.X86PlatformShim    1.0.0
com.apple.driver.AppleIntelHD5000Graphics    8.2.8
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleHDA    2.6.3f4
com.apple.driver.AppleHWAccess    1
com.apple.driver.AppleThunderboltIP    1.1.2
com.apple.driver.AppleBacklight    170.3.5
com.apple.driver.AirPort.Brcm4360    842.21.65
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport    4.2.6f1
com.apple.driver.AppleSMCLMU    2.0.4d1
com.apple.driver.AppleLPC    1.7.0
com.apple.driver.AppleCameraInterface    4.26.0
com.apple.driver.AppleIntelFramebufferAzul    8.2.8
com.apple.driver.AppleMCCSControl    1.2.5
com.apple.driver.AppleUSBTCButtons    240.2
com.apple.driver.AppleUSBCardReader    3.4.1
com.apple.driver.AppleUSBTCKeyboard    240.2
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
com.apple.BootCache    35
com.apple.driver.AppleUSBHub    683.4.0
com.apple.driver.XsanFilter    404
com.apple.iokit.IOAHCIBlockStorage    2.6.0
com.apple.driver.AppleAHCIPort    3.0.5
com.apple.driver.AppleUSBXHCI    683.4.0
com.apple.driver.AppleSmartBatteryManager    161.0.0
com.apple.driver.AppleACPIButtons    2.0
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleACPIEC    2.0
com.apple.driver.AppleAPIC    1.7
com.apple.nke.applicationfirewall    153
com.apple.security.quarantine    3
com.apple.kext.triggers    1.0
com.apple.iokit.IOSerialFamily    10.0.7
com.apple.iokit.IOSurface    91.1
com.apple.iokit.IOBluetoothFamily    4.2.6f1
com.apple.driver.DspFuncLib    2.6.3f4
com.apple.vecLib.kext    1.0.0
com.apple.iokit.IOAudioFamily    1.9.7fc2
com.apple.kext.OSvKernDSPLib    1.14
com.apple.iokit.IO80211Family    640.36
com.apple.driver.mDNSOffloadUserClient    1.0.1b5
com.apple.iokit.IONetworkingFamily    3.2
com.apple.iokit.IOBluetoothHostControllerUSBTransport    4.2.6f1
com.apple.driver.AppleHDAController    2.6.3f4
com.apple.iokit.IOHDAFamily    2.6.3f4
com.apple.driver.AppleBacklightExpert    1.0.4
com.apple.iokit.IONDRVSupport    2.4.1
com.apple.driver.AppleGraphicsControl    3.6.22
com.apple.AppleGraphicsDeviceControl    3.6.22
com.apple.iokit.IOAcceleratorFamily2    98.22
com.apple.driver.X86PlatformPlugin    1.0.0
com.apple.driver.AppleSMC    3.1.8
com.apple.driver.IOPlatformPluginFamily    5.7.1d6
com.apple.driver.AppleSMBusController    1.0.12d1
com.apple.iokit.IOGraphicsFamily    2.4.1
com.apple.iokit.IOSCSIBlockCommandsDevice    3.6.6
com.apple.iokit.IOUSBMassStorageClass    3.6.0
com.apple.iokit.IOSCSIArchitectureModelFamily    3.6.6
com.apple.driver.AppleUSBMultitouch    240.9
com.apple.driver.AppleUSBMergeNub    650.4.0
com.apple.driver.AppleThunderboltDPInAdapter    3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily    3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter    1.4.5
com.apple.iokit.IOUSBHIDDriver    660.4.0
com.apple.driver.AppleUSBComposite    656.4.1
com.apple.iokit.IOUSBUserClient    660.4.2
com.apple.iokit.IOAHCIFamily    2.6.5
com.apple.driver.AppleThunderboltNHI    2.0.1
com.apple.iokit.IOThunderboltFamily    3.3.1
com.apple.iokit.IOUSBFamily    683.4.0
com.apple.driver.AppleEFINVRAM    2.0
com.apple.driver.AppleEFIRuntime    2.0
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.iokit.IOSMBusFamily    1.1
com.apple.security.sandbox    278.11.1
com.apple.kext.AppleMatch    1.0.0d1
com.apple.security.TMSafetyNet    7
com.apple.driver.AppleKeyStore    2
com.apple.driver.DiskImages    371.1
com.apple.iokit.IOStorageFamily    1.9
com.apple.iokit.IOReportFamily    23
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleACPIPlatform    2.0
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.corecrypto    1.0
com.apple.kec.pthread    1

Mac Mini Experiencing Hard Freeze 3-4 Times Per day...

About 10 days ago, my mid-2011 Mac Mini started experiencing a hard freeze wherein I would get the spinning beachball and slowly each open app would be come unresponsive and my only resort was to hold down the power button to restart. Upon reboot, the system would work fine for about an hour then the freeze would start again. I've rolled back my configuration to a state prior to the freezing, and in desperation, have done a completely clean re-install of the OS.
System specs:
Mid-2011 Mac Mini 2.7 GHz Core i7
16 GB RAM
256GB SSD
750GB HDD
Attached to a 27" LED Cinema Display, and an Airport Extreme Basestation/TimeCapsule (TimeMachine temporarily disabled)
I've been reading the logs, but don't really know how to interpret them so I've included a a number of postings right up until I force the reboot.
Thanks in advance!
Log below: The system performs fine until 12:15 or so
Sep 6 12:03:56 Kriss-Mac-mini.local WindowServer[94]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
Sep 6 12:04:05 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:04:05 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:04:27 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04eb0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04f40
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04fd0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba05090
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfbc0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfc50
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009dfce0
Sep 6 12:06:31 Kriss-Mac-mini.local WindowServer[94]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10ba04e20
Sep 6 12:06:44 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:06:44 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:06:55 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:07:38 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:07:38 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:07:49 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:08:36 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:08:36 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:08:47 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:09:33 Kriss-Mac-mini.local com.apple.qtkitserver[759]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:09:33 Kriss-Mac-mini.local com.apple.qtkitserver[759]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:09:33 Kriss-Mac-mini kernel[0]: Sandbox: sandboxd(769) deny mach-lookup com.apple.coresymbolicationd
Sep 6 12:09:35 Kriss-Mac-mini.local sandboxd[769] ([759]): com.apple.qtkits(759) deny mach-lookup com.apple.printtool.agent
Sep 6 12:10:15 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGAffineTransformInvert: singular matrix.
Sep 6 12:10:15 --- last message repeated 3 times ---
Sep 6 12:10:15 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:10:25 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:10:25 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:11:00 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[776]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:11:01 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:11:09 Kriss-Mac-mini.local WindowServer[94]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
Sep 6 12:11:15 --- last message repeated 1 time ---
Sep 6 12:11:15 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[782]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:11:24 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGAffineTransformInvert: singular matrix.
Sep 6 12:11:24 --- last message repeated 1 time ---
Sep 6 12:11:24 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:11:47 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[786]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:12:35 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:12:58 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[790]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:13:06 Kriss-Mac-mini.local com.apple.qtkitserver[777]: CGSGetWindowBounds: Invalid connection
Sep 6 12:13:10 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[794]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:15:12 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[806]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:15:22 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[809]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:15:51 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[816]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:16:07 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[818]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:17:10 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[823]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:17:24 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[825]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:18:22 Kriss-Mac-mini.local Locum[829]: Connection with distnoted server was invalidated
Sep 6 12:19:05 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:19:05 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[766]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:19:05 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:20:01 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[844]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[845]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:23:55 Kriss-Mac-mini.local Google Chrome Helper[844]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
Sep 6 12:23:56 Kriss-Mac-mini.local Google Chrome Helper[845]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
Sep 6 12:23:58 Kriss-Mac-mini.local Google Chrome Helper[847]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:23:59 Kriss-Mac-mini com.apple.launchd[1] (com.apple.coremedia.videodecoder[835]): Exit timeout elapsed (20 seconds). Killing
Sep 6 12:24:01 Kriss-Mac-mini.local Google Chrome Helper[847]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
Sep 6 12:24:01 Kriss-Mac-mini.local Google Chrome Helper EH[848]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
Sep 6 12:27:54 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendAttachNotification (thread 0x7fff7d227180): sending attach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.
Sep 6 12:27:54 Kriss-Mac-mini.local usbmuxd[44]: _AMDeviceConnectByAddressAndPort (thread 0x100781000): IPv4
Sep 6 12:28:45 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _handle_timer heartbeat detected detach for device 0xc-10.0.1.117:0!
Sep 6 12:28:52 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff7d227180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: moduleFromLegacyDefaults: <ScreenSaverDefaults: 0x7fc57321f5a0>
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: Attempted search for modules of unknown type (4)
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:46:04 Kriss-Mac-mini.local ScreenSaverEngine[887]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 6 12:49:01 Kriss-Mac-mini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=891[GoogleSoftwareUp] clearing CS_VALID

I looked these up and none of the network profiles list these MAC addresses. Strange.
I went to dinner and when I returned the computer was frozen again. These strange entries appeared in the log:
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d657190
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d62bb70
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6570c0
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x100e6f130
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d680450
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d63b650
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6804e0
Sep 6 15:33:07 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10d6805a0
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5edd40
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c517540
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x1009b1150
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5d2120
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c5de420
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10c51e650
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10cd8b020
Sep 6 15:33:14 Kriss-Mac-mini.local WindowServer[80]: CGXSetTrackingAreaEnabled : Invalid tracking area 0x10cdfb8f0
Sep 6 15:57:58 Kriss-Mac-mini.local Dock[128]: CGSSetWindowTransformAtPlacement: Singular matrix [inf 0.000 0.000 inf]
Sep 6 15:58:00 Kriss-Mac-mini.local Dock[128]: Unable to open IOHIDSystem (e00002bd)
Sep 6 15:58:00 Kriss-Mac-mini kernel[0]: virtual bool IOHIDEventSystemUserClient::initWithTask(task_t, void *, UInt32): Client task not privileged to open IOHIDSystem for mapping memory (e00002c1)
Sep 6 16:02:35 Kriss-Mac-mini.local com.apple.usbmuxd[44]: _SendDetachNotification (thread 0x7fff75469180): sending detach for device 60:c5:47:57:e8:27@fe80::62c5:47ff:fe57:e827._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.
Sep 6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: Created shield window 0xdf for display 0x0424faa4
Sep 6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
Sep 6 16:02:40 Kriss-Mac-mini.local WindowServer[80]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
Sep 6 16:03:50 Kriss-Mac-mini kernel[0]: PM notification cancel (pid 322, Transmit)
Sep 6 16:03:50 Kriss-Mac-mini kernel[0]: IOPMrootDomain: idle cancel
Sep 6 16:06:17 Kriss-Mac-mini kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=352[GoogleSoftwareUp] clearing CS_VALID
Then I rebooted. Curious about the screenshot entry. I'm stumped.

Mac Pro 2008 with 8800 GT, hard freezes with screen savers/OpenGL. You too?

I have been experiencing random intermittent hard crashes of my "early 2008" model 8-core Mac Pro. Now I have finally found an easy reproducible test case (see below), and hope others will try it and post the results. This is a video-driver related crash that I have now duplicated with two different video cards.
The symptom is that my screen randomly freezes. The mouse moves, but there's no way to use the Mac[1]. Holding the Power button to force the Mac to shutdown is the only way out.
Usually, this occurs when I get to my office in the morning, or after the gym. That's because the screen saver is running. I found that the screensaver, other OpenGL/3D type applications, are what triggers this bug.
The bug seems to be with the graphics driver. Immediately before the freeze, messages like this are printed in the system log:
Mar 26 18:34:14 Mac-Pro kernel[0]: NVChannel(GL): Graphics channel exception!
status = 0xffff info32 = 0xd = GR: SW Notify Error
Mar 26 18:34:14 Mac-Pro kernel[0]: 0000000c
Mar 26 18:34:14 Mac-Pro kernel[0]: 00200000 0000502d 00000470 00000000
Mar 26 18:34:14 Mac-Pro kernel[0]: 00000482 000002ac 00000003 00000003
Mar 26 18:34:14 Mac-Pro kernel[0]: 00000000 00000000 01be0003
Mar 26 18:34:14 Mac-Pro kernel[0]: NVChannel(GL): Graphics channel exception!
status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Mar 26 18:34:14 Mac-Pro kernel[0]: 0000000b
Mar 26 18:34:14 Mac-Pro kernel[0]: NVChannel(GL): Graphics channel exception!
status = 0xffff info32 = 0x3 = Fifo: Unknown Method Error
Other errors like these also appear (the actual log output volume is too large for this forum):
Mar 26 21:15:15 Mac-Pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0x6 = Fifo: Parse Error
Mar 26 18:34:14 Mac-Pro kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
Anyway, finally I found on another thread about a similar issue[2], a recommendation to run Folding@Home program to trigger the freeze. They were talking about another Mac model, but sure enough, it triggers my problem every time. I downloaded the client[3], installed it, and then launched the app which gets put in the Applications folder. It doesn't even finish bouncing once in the dock before the Mac Pro freezes.
This is not a bug specific to Folding@Home; juding from the log messages and the effect, this is exactly the same crash that is intermittently triggered by the default Mac OS X screensavers (I use Arabesque, but I think any OpenGL screen saver does it). It's just that running Folding@Home is an easier way to trigger the bug than leaving your screensaver running for hours.
So, that is pretty unfortunate, right? I mean, not only can my new Mac Pro not sleep without losing all unsaved data (yes, I have the reboot-instead-of-wake problem[4], too, but that is another issue...) but it also crashes at random whenever the screen saver runs for a while, or somebody uses OpenGL programs. I have set my machine to never use the screen saver, but still.
So, first and foremost, my question for other 2008 Mac Pro owners with the 8800 video card is: does your Mac puke all over itself when you launch Folding@Home?
I just found it a little bit hard to believe that every Mac owner of the most expensive new Mac and the higher end video card will have these crashes. It could be, but it seemed far-fetched. So I tried some troubleshooting:
a
1.) I considered that I had a bad video card, so I got another GeForce 8800 GT and installed that. Still crashed.
2.) I disconnected my second monitor, and tried it with only one monitor. Still crashed.
3.) I booted from the pristine boot disk my Mac shipped with (10.5.1). Still crashed.
4.) I reduced the resolution on my 30" Cinema display to 800x600. Still crashed.
5.) Just to stave off the usual chorus of "try zapping your PRAM" posts, I zapped the PRAM. Of course, this did nothing (I don't think this has really fixed a problem since the 1990s...). Anyway, it still crashed.
6.) In doing all these tests, I disconnected all USB/FireWire peripherals.
7.) My Mac is totally up-to-date with Software Update as of Thu, Mar 27, 2008. Mac OS X 10.5.2.
I don't want to return this Mac to Apple; it is wicked fast and that really helps me with my work. But, the frequent crashing really is a productivity-killer.
So: does every 2008 Mac Pro owner with an 8800 GT have this problem?
(Note: there are lots of similar problems with other Macs and the new Mac OS X 10.5... I hope to specifically address this particular model and crash in this thread.)
If not, I will go to the next extreme step: pulling out some of my RAM. I have 12GB of RAM, and it all seems to work fine, no parity errors or anything. But I know sometimes problems don't happen unless there's "too much" RAM, "too high" resolution, and so on. But I would like to hear from others before I go banging on my precious DIMMs and riser cards.
Thanks for any information!
The next step will be to determine if this is just another unfortunate defect that affects ALL 2088 Mac Pros (in which case I would want to keep my fast Mac and wait for fixed drivers), or if perhaps just a subset of them have defective video cards that cause the driver to crash in this way (in which case I would want a replacement).
---------- NOTES: ----------
[1]: I can connect via SSH on the command line to the Mac. However, the GUI environment seems borked; opening apps or trying to gracefully quit them via AppleScript either does not work or really hard freezes everything, such that SSH no longer works either.
[2]: A similar (but perhaps different) issue affecting notebooks is discussed here, and there are some people with Mac Pros, too: http://discussions.apple.com/thread.jspa?messageID=6786960
[3]: The Folding @ Home client, which can be used to trigger this bug, can be gotten here: http://folding.stanford.edu/English/Download
[4]: The severe defect affecting many (most?) 2008 Mac Pro machines' ability to sleep without losing data is discussed in this other thread: http://discussions.apple.com/thread.jspa?threadID=1353551

Hello guys, thank you for the replies.
I do have more data at this point.
ujeezy: Those posts on MacNN and others like them did give some clues.
Jon BWFC: I think you are (partly) right that it's (partly) an issue with the driver. But I have confirmed with a fair degree of certainty in my case that it is a hardware issue too, likely with the video card and not the Mac Pro itself.
cmcom: I think it sounds like you problem is different than the one we're talking about (although who knows, the driver could be causing that too). The freeze we are seeing locks up the whole Mac, and no application crash report is produced.
I had another GeForce 8800 card, so I went through some exhaustive troubleshooting. I tested each card, installed in each of the 16x slots, booting from either my normal 10.5.2 boot disk or a clone of the pristine virgin system disk that shipped with the Mac, and tried to see if the Mac would crash.
Unfortunately this was harder than it seems, because:
a.) both my GeForce 8800 cards appear to be defective, but in different ways (see [1] and [2] below)
b.) In my testing, I thought I was seeing the crash sometimes, but later I discovered that there are different ways to make the Mac crash like this. That is, there are bugs in Mac OS X 10.5.x (probably in the NVIDIA driver) that cause similar crashes, and these bugs occur on all Mac Pro units and even other Mac models, without any hardware defects. Unfortunately, the Folding@home exercises one such bug.[3]
So the upshot is, all those times I was using Folding@home to test this issue were bogus, because Folding@home crashes any Mac Pro with the NVIDIA card, and crashes MacBook Pro machines with NVIDIA chips as well.
Argh! So I had to retest. It took a couple of days but I found another reliable way to crash my Mac Pro, more quickly than just leaving the screensaver on for a day or two: run this OpenGL virtual fish tank simulator[4] for 2-3 minutes. Unlike the Folding@home test, this did not crash any of my other Macs, and after exhaustive testing I found that it ONLY crashed the Mac Pro with one of the GeForce 880 cards installed, and not the other one. This was regardless of what slot it was installed in or what boot disk was used.
Whew! So, I concluded that indeed, there is a hardware defect in one of my GeForce 8800 cards which causes the machine to lock up. [2]
What made this problem much harder to deal with was the fact that Mac OS X (specifically the graphics driver parts of the OS, perhaps NVIDIA-specific) crashes with these same symptoms in other cases too. Like when you run Folding@home, or in some of these cases people are talking about with their MacBook Pro machines.
So, when there is a bona-fide hardware defect, it is really hard to isolate. (It took me like four days.)
The thing is, the defective NVIDIA card that crashes the Mac[2] was a REPLACEMENT card for the 8800 card that shipped with my Mac. I called Apple about the video artifacts I was seeing and they replaced the card.
I am now running the original card (and suffering the ugly video artifacts, but no crashes). At my own expense, I ordered an ATI card (the RADEON HD 2600 XT) and I will install that.
I hope someday to have my Mac work without graphics glitches or crashes. For now, operating (mostly) without crashes will have to do.
The original problem with this Mac continues, though: the video doesn't work correctly; it starts displaying visual artifacts after 1-72 hours of use[1]. That could either be because:
a.) a hardware defect in that video card
b.) a software problem with the driver/OS
c.) a hardware defect in the Mac itself
I strongly suspect A, but hopefully my buying a different card and testing with that will help further isolate what is wrong.
I am marking this thread "solved" because the specific issue I originally posted about has been resolved: the GeForce 8800 card causing the crashes is defective, and using another card fixes that issue.
[1]: The original GeForce 8800 card that shipped with my Mac Pro exhibited annoying-but-not-deadly video artifacts, which can be seen here: http://masonmark.com/wp-content/uploads/2008/04/bogusvideoartifacts.jpg
[2]: Apple replaced the video card, and that is when my deadly video-corruption-plus-frozen-Mac crash problem began. A screenshot example of that problem can be seen here: http://masonmark.com/wp-content/uploads/2008/04/crashedmac_pro_akashitball.jpg
[3]: The red herring in this case was the Mac OS X bug (seemingly specific to NVIDIA-equipped Macs including Mac Pro and MacBook Pro) that causes a very similar full system crash. This bug can easily be triggered by running the Folding@home version "6.10beta2" demo application. That is a serious bug, and since my employer is a Mac software company I reported this bug to Apple via the official channel. It is Apple bug number 5830772.
[4]: The OpenGL fish tank simulator I found, which would trigger the system crash caused by my defective 8800 video card (but would not crash any other Mac, or crash my Mac Pro with the other 8800 video card installed) can be found at: http://uri.cat/software/Fish/

Satellite L675 D Hard Freezing Under Low System Loads

Similar Messages

Maybe you are looking for