10.8.2: Randomly Unable to Save to Hard Drive

[ObeseSquirrel]

I think we can safely conclude that Scannerz can detect bad sectors on an SSD, which is good. Scannerz detects both weak and bad sectors on a drive. A weak sector shows up as an "irregularity" because the drive takes longer to read it than normal, but eventually succeeds. I would wonder if perhaps something similar doesn't happen with SSDs, but their speed is so much faster than a hard drive that it falls beneath Scannerz threshold level. Well, it's theory anyway.

With that said, I find it interesting that the infallible SSD's we've been hearing all the raves about are ending up having the exact same problems hard drives have.

I'm kind of amazed that OSX doesn't have something like Scannerz built into Disk Utility. Hasn't Windows had the ability to detect bad sectors for ages?

Something interesting: I just enabled noatime (by default, OSX records last access time for every file), since it's recommended for SSD's to reduce writes to the disk. So far, it seems like disk writes have been reduced by about 20-30%. That might help speed things up a little, especially for you HDD folks.

 

[TheBSDGuy]

I'm kind of amazed that OSX doesn't have something like Scannerz built into Disk Utility. Hasn't Windows had the ability to detect bad sectors for ages?

Actually, it has to do with the OS, I think. Windows is more or less implicitly tied to hardware, whereas OS X and other Unix variants aren't. That's why any time you add a piece of hardware to a Windows system, you typically have to fool with drivers (or at least used to...it may be different nowadays since it's been over 7 years since I worked on a Windows system).

The trouble with not being implicitly tied to the OS means that timing errors and I/O errors are more or less "generic" when presented to the kernel. It can't tell, per se whether or not the I/O error was specifically from the drive or whether or it was caused by a bad cable. That's why people like me like Scannerz. If the problem is repeatable in cursory mode, it's the media (drive, SSD, whatever) causing the problem. It it isn't repeatable from scan to scan, it's being caused by a cable or something in the circuitry and it can be traced to the major component level.

To go off topic for a moment, after moving back to Lion I wanted to test the actual performance of the GUI stuff to see if the performance difference was real or my imagination.

Below are some comparisons between the two (TSTM means to short to measure). I'd open an app on both Lion and Mountain Lion and time the amount of time it takes for each to open with a digital stop watch. TSTM really means that I can't click the start and stop buttons fast enough to measure it. These obviously aren't scientific, I just wanted to find out if the performance difference was real or my imagination. It wasn't my imagination, Lion's loading stuff a lot faster.

Command: Open Safari
Lion: 1.5 sec.
ML: 7 sec.

Command: Open TextEdit
Lion: TSTM
ML: 5 sec

Command: Open Mail
Lion: 2 sec
ML: 8 sec

I knew it wasn't my imagination. And now I can sync notes to the iPhone again without iCloud.

 

[ObeseSquirrel]

OH MY GOD!!!!!! SERIOUSLY???????

It happened again. One of my programs crashed (MenuTab Pro) which was usually a sign that my disk drive had disconnected. So I opened an MS Word Document, and … I couldn't save it. Neither Disk Utility, not Scannerz would start properly.

Will restart the computer and see if Scannerz finds anything.

I seriously want to destroy my computer right now.

------------------------------------------------

Edit: Ran Scannerz again, and there were no errors.

Mount Command

Running the "mount" command in terminal, I get:

Last login: Sun Mar 24 12:10:16 on ttys000
FirstName-LastName:~ FirstNameLastName$ mount
/dev/disk0s2 on / (hfs, local, journaled, noatime)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
localhost:/RANDOMLETTERSANDNUMBERS on /Volumes/MobileBackups (mtmfs, nosuid, read-only, nobrowse)
/dev/disk2 on /Volumes/Time Machine Backups (hfs, local, nodev, nosuid, journaled)
/dev/disk3 on /Volumes/Parallels Backup (hfs, local, nodev, nosuid, journaled, noowners)
FirstName-LastName:~ FirstNameLastName$

I have no idea if any of that is interesting. ("Parallels Backup" is a partition on my Time Machine drive that keeps a copy of my Parallels VM.)

Glimmerblocker

I did not mention this before. The last time I fully reinstalled OSX, OSX randomly placed some files from Glimmerblocker into the "Incompatible Software" folder without notifying me. (It had previously notified me when I first installed 10.8.3 the day before that the random Parallels 7 files had been placed there.) Yesterday, I reinstalled Glimmerblocker, which is a very tiny program. After doing this, Time Machine made a huge backup file of 19GB, which apparently included all of my Applications, my Library, and my System/Library files. This seemed very strange to me.

If Glimmerblocker is the source of the problem (and I cannot think of a reason why it would be), I'm thinking I should disable it for two weeks and see if the problem stops. But according to Time Machine, I installed Glimmerblocker in early September, while the problem started in early/mid October.

Parallels?

Another thing I have noticed: I have a shortcut to my main Parallels VM in my Doc. By default, it's icon is a red Parallels logo, but after these crashes, or after a SafeBoot, it shows up as the default document icon (blank page with a dog ear) until I click on it again. I'm assuming this simply means that the document icons in the Dock are part of a cache that is cleared upon hard restarts, but I wanted to make sure. Time Machine says that my Dock from October 17, 2012 did not have this shortcut, fyi.

Console/ New Problem?

Since updating to 10.8.3, I have had several problems with my application windows not responding when I clicked on the icon for the active program in the Dock. Closing the program and restarting fixes it. Possibly related, my Console is repeatedly becoming clogged with *LOTS* of:

talagent[205]: CoreAnimation: rendering error 506

with the occasional

talagent[205]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x34

scattered throughout. And as my computer reindexes (Scannerz causes this), I am receiving lots of:

mdworker[1637]: CoreData: error: (264) attempt to write a readonly database

mixed with lots of other mdworker and sandboxd-related errors. If this is all completely unrelated, I might have to start a new topic for it. :sigh:

------------------------

Review

Problem: Computer randomly disconnects from the hard drive so that I am unable to save to disk, though the system otherwise appears functional. There is no consistent interval between these crashes, but it probably averages about once every 2-3 days. Has lasted up to 8 days before. If I can make it 14 days, I will consider the problem solved.

Symptoms: Inconsistent, but I usually know that my drive will fail to save after -ONE- of the following occurs:

1) Certain Applications (usually BetterTouchTool or MenuTab Pro) randomly crash. Word has done it too.
2) Most Applications (excluding Console) are unable to launch, and are left paralyzed in the Dock.
3) Unable to access keychain.
4) Unable to load extensions when starting Safari. (And possibly, extensions failing when Safari opens.)
5) Unable to access wifi: sometimes this is related to keychain problems (#3), but sometimes it happens when wifi simply won't work, possibly correlated with bad wifi for other Macs in the area.

When wifi fails to connect, it is the least likely of the above to be a symptom. When any of the first four occur, it almost certainly means my drive has disconnected.

Cause: Unknown. Seems to happen more when I am moving my computer between locations, but not always. (Today, I did not move my computer before this happened.) It is most likely caused by Either:

1) SSD: At first, I had no reason to believe the SSD was the problem, but later found that Scannerz was reporting some errors, that were not present when I started this thread. I reinstalled my entire system from Time Machine to the SSD, and now Scannerz reports no errors. The i/o problem persists.

*Sidenote* My SSD has a 3-year warranty, so I have plenty of time to trade it out if the SSD is still the most likely suspect.

2) Cable/Logic Board: This is still a possibility. It would explain the inconsistency, as well as the proneness to happening after moving my computer. While I was on vacation, it would happen 2-3 times a day, especially when I had my computer in my lap. It can still happen when I am sitting at a table, but it is much less frequent. But of course, correlation is not causation. (Cable is connected properly.)

3) Bad wifi/ Bad Disk Connections: I would sometimes have this problem in class, right after all the other students with Macs had wifi drop as well. It has also happened at school, shortly after I had ejected my Time Machine disk too quickly.

4) OSX 10.8.2: The problem first showed up on October 10, 2012, only a few days after the last build of 10.8.2 (October 4), which makes sense from a timing standpoint. On the other hand, very few people have reported this problem, and it has just happened again, with 10.8.3 installed. If it is a bug introduced in the October build (which I was initially hoping for) I will be waiting for a *very* long time.

5) TRIM enabled/Sudden Motion Sensor disabled: These settings are recommended for users of SSD's on a Mac. I disabled TRIM at the behest of many users here, but the problem persisted. I left TRIM disabled, however, due to the plausibility that TRIM had somehow caused data corruption on my SSD. With a full reinstall from Time Machine, plus a full reinstall of OSX (thus restoring all system files), I'm thinking it is safe to reenable TRIM (unless someone here disagrees). After trying SMS enabled/disabled, I believe this has nothing to do with it.

6) Software: So far, I have considerred BetterTouchTool, TotalFinder, SideEffects, Time Machine, and Parallels as possible suspects. I not uninstalled all of these long term, but so far, disabling some of SideEffects does not solve the problem, nor does refraining from launching Parallels, nor does reinstalling TotalFinder, BetterTouchTool, or Parallels. Disabling Time Machine does not prevent the problem either. I might be investigating Glimmerblocker soon. (see above)

7) Permissions/Disk Utility/PRAM/SMC/Safe Mode/Resetpassword Utility (for Permissions): none of these have fixed the problem.

 

[TheBSDGuy]

What we know for facts are the following:

1. At one point Scannerz detected bad sectors on your SSD, which in my opinion shouldn't have happened because the SSD is supposed to auto correct and catch them.

2. Mountain Lion is an extremely buggy operating system. Some of the very types of disconnects you described were similar to what I was getting with some applications, and I'm not running anything particularly intensive. Here's a list:

1. TextEdit crashed on me for no apparent reason
2. iPhoto crashes periodically
3. iPhoto recognizes an attached camera via USB "when it wants to" and if it does recognize it, it may not detect that photos need to be downloaded - yet another crap shoot.
4. iWeb ALWAYS crashes
5. NotePad crashes intermittently. I can't use it anyway since I'm not using iCloud or iMap
6. Videos in Firefox are totally screwed up - it might be fixed in a Firefox update, I don't know.
7. Safari Web Content has gone wild at times consuming nearly 100% of the memory
8. Some applications will open "Save" dialogs in the wrong work space.

That's a lot of bugs for doing trivial stuff.

To me, you have three suspects: The SSD, possible cable problems, and the operating system itself.

I don't know if you can do this, but I would get off Mountain Lion as task 1. I've also been reading about others having fairly significant problems with driver (KEXT) compatibility problems and those are serious, crash worthy bugs. I don't know if you can do that because all your backups are likely now from ML. I would try either Lion, or probably even better yet, Snow Leopard. I have none of the problems I've listed above with either of them.

If you can do task 1 and the problems persist then you know it's either the SSD, a cable, or some other problem, but at least you'll know it wasn't the OS. If the problems go away then you know it's the OS. Another thing you could do is contact SCSC's tech support and let them try and help you - you paid for Scannerz so what harm could it do to ask? They know more about this crap than we do!

There are simply too many bugs with Mountain Lion to be ignored.

 

[ObeseSquirrel]

What we know for facts are the following:

1. At one point Scannerz detected bad sectors on your SSD, which in my opinion shouldn't have happened because the SSD is supposed to auto correct and catch them.

2. Mountain Lion is an extremely buggy operating system. Some of the very types of disconnects you described were similar to what I was getting with some applications, and I'm not running anything particularly intensive. Here's a list:

1. TextEdit crashed on me for no apparent reason
2. iPhoto crashes periodically
3. iPhoto recognizes an attached camera via USB "when it wants to" and if it does recognize it, it may not detect that photos need to be downloaded - yet another crap shoot.
4. iWeb ALWAYS crashes
5. NotePad crashes intermittently. I can't use it anyway since I'm not using iCloud or iMap
6. Videos in Firefox are totally screwed up - it might be fixed in a Firefox update, I don't know.
7. Safari Web Content has gone wild at times consuming nearly 100% of the memory
8. Some applications will open "Save" dialogs in the wrong work space.

That's a lot of bugs for doing trivial stuff.

To me, you have three suspects: The SSD, possible cable problems, and the operating system itself.

I don't know if you can do this, but I would get off Mountain Lion as task 1. I've also been reading about others having fairly significant problems with driver (KEXT) compatibility problems and those are serious, crash worthy bugs. I don't know if you can do that because all your backups are likely now from ML. I would try either Lion, or probably even better yet, Snow Leopard. I have none of the problems I've listed above with either of them.

If you can do task 1 and the problems persist then you know it's either the SSD, a cable, or some other problem, but at least you'll know it wasn't the OS. If the problems go away then you know it's the OS. Another thing you could do is contact SCSC's tech support and let them try and help you - you paid for Scannerz so what harm could it do to ask? They know more about this crap than we do!

There are simply too many bugs with Mountain Lion to be ignored.

All that talk about kexts got me thinking… Just downloaded a program I found called "Kext Wizard" and it repairs permissions for all kexts! Just did it, and it found a lot…

… including one called "ioatafamily.kext," which apparently has something to do with hard drives.

I'm going to give it another go, because out of the remaining suspects, running my system from a hard drive for awhile would be the easiest, and I'm not really in the mood for that sort of thing… (DVD drive is still too finicky to run AHT. Well, maybe not now. Hoping…)

EDIT: eh… repeat runs show roughly the same number of errors, meaning it isn't repairing much… Maybe it fixed something. But at least it doesn't seem to make anything worse.

 

[TheBSDGuy]

I don't know if that will do the trick for you, but who knows, it might. If it doesn't I'd SERIOUSLY contact SCSC for tech support. I'm serious. They're located about 7 miles from where I live and they give good tech support, even if the problem ends up not being something Scannerz would have detected anyway. It's almost like getting free consulting. You paid for Scannerz, why not take advantage of all their services.

 

[ObeseSquirrel]

I found the problem!!!!!
It was the SATA cable.

1) I used some compressed air to clean out the disk drive. Afterwards, I was finally able to boot from the AHT disk. (re: Superdrive problems)

2) I then ran AHT on long mode, and then short mode on loop all night. No problems found.

3) I wondered whether dust had gotten caught under the logic board, causing problems similar to those in my Superdrive. Research says that dust almost never caused short circuits, but I wanted to make sure. (I have not been having overheating problems.) I sprayed the compressed air under the logic board and found some dust bunnies, but nothing major.

4) I then wondered whether I had spilled a coke or something under the board, and just didn't remember it. I was about to remove the logic board to look underneath. And when I unsnapped the SATA cable from the board, I found it…

If you look closely at the attached picture, you can see four holes in the cable; one large white one, and three small copper-colored ones. And on the plastic casing to the Superdrive, you can see what appears to be four matching burn marks. My theory is that SSD would disconnect whenever the SATA cable got bumped against the Superdrive, causing a short circuit. That would explain why the problem happened more frequently whenever the computer was moved.

I am confused about the exposed cable hitting the plastic casing, which does not seem like it would be conducive to electricity. However, I am now 99% sure that I have found the problem, and this is a HUGE relief.

Will get this thing repaired shortly.

 

[MacRobert10]

No, you think you have the problem solved. The problems you've been having have been multiple, unrelated to one another in some cases, and erratic.

Bad sectors or blocks on an SSD should have nothing to do with a SATA cable, or at least I don't think so. That's a bonafide media failure. The Wi-Fi problems you've been having are probably due to nothing more than the erratic nature of Wi-Fi. The erratic nature of the problem was likely why the advice given to you to "tap on the bottom of the unit was given" ... it's to try to induce a fault...it just wasn't enough to do it (perhaps if you hit it with hammer???)

I think in this case you're just one of those unlucky people ... you know, the type of guy who gets a flat tire, fixes it, thinks all is well, and then the radiator in the car spring a leak. One unlucky thing after another.

I'm going to shoot SCSC a link to this post because I think they need to add a continuous mode of testing to Scannerz in cursory mode...they seem to listen to customers, so maybe they'll do it. Who knows? If a continuous mode was added, Scannerz might have caught this problem much earlier. Just my opinion. It is, after all, doing essentially the same thing that AHT is doing, it just doesn't lock out the user from the system to get it done.

You need to be patient and see if the problem is really fixed. Based on your photo, I would say the culprit may very well be identified, but only time will tell. Your saga seems to be "everything's working fine" and then a few days later "everything's screwed up."

I will, however, give you kudos for having the b*lls to open your system up and try to isolate the problem. That's a lot more than a lot of other people would consider doing...or do it properly.

Good luck and I hope this works out for you.

 

[ObeseSquirrel]

No, you think you have the problem solved. The problems you've been having have been multiple, unrelated to one another in some cases, and erratic.

Bad sectors or blocks on an SSD should have nothing to do with a SATA cable, or at least I don't think so. That's a bonafide media failure. The Wi-Fi problems you've been having are probably due to nothing more than the erratic nature of Wi-Fi. The erratic nature of the problem was likely why the advice given to you to "tap on the bottom of the unit was given" ... it's to try to induce a fault...it just wasn't enough to do it (perhaps if you hit it with hammer???)

I think in this case you're just one of those unlucky people ... you know, the type of guy who gets a flat tire, fixes it, thinks all is well, and then the radiator in the car spring a leak. One unlucky thing after another.

I'm going to shoot SCSC a link to this post because I think they need to add a continuous mode of testing to Scannerz in cursory mode...they seem to listen to customers, so maybe they'll do it. Who knows? If a continuous mode was added, Scannerz might have caught this problem much earlier. Just my opinion. It is, after all, doing essentially the same thing that AHT is doing, it just doesn't lock out the user from the system to get it done.

You need to be patient and see if the problem is really fixed. Based on your photo, I would say the culprit may very well be identified, but only time will tell. Your saga seems to be "everything's working fine" and then a few days later "everything's screwed up."

I will, however, give you kudos for having the b*lls to open your system up and try to isolate the problem. That's a lot more than a lot of other people would consider doing...or do it properly.

Good luck and I hope this works out for you.

I completely agree about Scannerz having a continuous mode of some sort. It would also be nice if they had the manual available in the help file (so I don't need to search for it online), and an option for the log files to be dumped somewhere other than the Documents folder. (If there was a Preference for this, I don't remember seeing it.

I had to laugh when you said that I'm one of those unlucky people. After jiggering with the SATA cable, I had a really hard time getting my Mac to boot, and even then, it would instantly jump to "do-not-save-anything-or-access-keychain-mode." Tapping the bottom of the computer made the computer more likely to boot up. This was, sadly, the only time I was ever able to make this error repeatable, but I think it more or less confirms that I was correct. (Note: electrical tape does not fix a damaged SATA wire. ) It's kind of funny that I'm about to replace one of the last remaining original parts to my computer.

I may have mentioned earlier that about a year ago, I was having my computer repaired (turned out to be a logic board issue), and that while my computer was gone, I had tried to boot my SSD onto my school's computer using an external Firewire drive. But instead, I heard a click, and my entire drive had been deleted. At the time I had blamed Lion, so I ignored my prior experience and decided to give it another go.

*click

So now my SSD is most likely erased (again), and I am currently working from an HDD on the external Firewire. (Must have been a firmware incompatibility on the SSD. Why does it have to erase things, though?) Luckily, I have a Time Machine backup that I can restore from. But I'm thinking that if you are correct that my SSD is genuinely in trouble, now would be a good time to take advantage of that 3 year warranty...

 

[MacRobert10]

Ya know, that's about the tenth time I've read a post on this or other sites about SSDs suddenly losing all their data.

Rule number 1 for SSDs: Make sure you do daily backups

 

[ObeseSquirrel]

Ya know, that's about the tenth time I've read a post on this or other sites about SSDs suddenly losing all their data.

Rule number 1 for SSDs: Make sure you do daily backups

I honestly think this was an incompatibility issue of some kind, that won't affect my performance once the drive is in my computer. It just means that I should never use this drive externally.

I did send a Return to Manufacturer request to Corsair over the bad sectors issue, and also reported the drive-erase, so that maybe they can update their firmware.

The problem is that by the time they respond, I will probably have my new SATA cable, and I don't want to mess with Time Machine again only to end up replacing the drive anyway, as there's always something that doesn't copy right. (This last time, I had to reinstall all the printers.)

ugh... first world problems

 

[smithrh]

No, you think you have the problem solved. The problems you've been having have been multiple, unrelated to one another in some cases, and erratic.

Been a troubleshooter for a lot of things over the years, professionally as well as personally, and it sounds like you may be surprised at how one problem can be the root of many - or all - problems that you're having.

The fact is that a bad cable to a storage device can - and will - cause all sorts of weird and transient problems.

 

[ObeseSquirrel]

Update:

So, I installed the new SATA cable on Friday, and have not had the disk error since then. Four days is hardly enough time to say the problem is solved, especially given my recent history and the unpredictability of this error, but my thinking is that my problem is solved.

Corsair accepted my Return to Manufacture request, and will hopefully send me a new SSD sometime this week. Until then, I should am operating off of a near-clean HDD, with Mountain Lion installed, along with a few apps for minimum functionality (BetterTouchTool, 1Password).

But this morning I had a weird kernel panic. I don't think it's related to my hardware problems, but I want to mention it here just in case.

I was using Safari, when suddenly, my trackpad refused to scroll or click. My cursor would still move around though. (Briefly, the cursor froze, but then it came back.) I closed the lid on my Mac, but the light stayed lit, and the computer did not go to sleep. I reopened my computer, and my computer restarted. I saw a gray screen, that said my computer had restarted because of a problem, and then my computer was back.

Here is the panic report:

Interval Since Last Panic Report: 333609 sec
Panics Since Last Report: 1
Anonymous UUID: D3F49F46-8CAE-EA2D-34D3-6E48712BE2FE

Tue Apr 9 07:35:20 2013
panic(cpu 0 caller 0xffffff80140b7e95): Kernel trap at 0xffffff7f95804be6, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x000000000000008c, CR3: 0x0000000016d26000, CR4: 0x0000000000000660
RAX: 0x0000000000000000, RBX: 0xffffff8027a62400, RCX: 0x0000000000000003, RDX: 0x0000000000002800
RSP: 0xffffff80fbbd3780, RBP: 0xffffff80fbbd3780, RSI: 0x0000000000000003, RDI: 0xffffff8027a62400
R8: 0xffffff80fbbd33b8, R9: 0xffffff80fbbd33b0, R10: 0x0000000000000001, R11: 0x0000000000000000
R12: 0xffffff8027a68000, R13: 0xffffff80fbbd3818, R14: 0xffffff8027b2e800, R15: 0x0000000000020000
RFL: 0x0000000000010206, RIP: 0xffffff7f95804be6, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000000000000008c, Error code: 0x0000000000000002, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff80fbbd3420 : 0xffffff801401d626
0xffffff80fbbd3490 : 0xffffff80140b7e95
0xffffff80fbbd3660 : 0xffffff80140cd4dd
0xffffff80fbbd3680 : 0xffffff7f95804be6
0xffffff80fbbd3780 : 0xffffff7f957f3e73
0xffffff80fbbd37b0 : 0xffffff7f9581a2cc
0xffffff80fbbd37c0 : 0xffffff7f95816fb5
0xffffff80fbbd3900 : 0xffffff7f95815c10
0xffffff80fbbd3d30 : 0xffffff7f957c220a
0xffffff80fbbd3d60 : 0xffffff7f95817de1
0xffffff80fbbd3da0 : 0xffffff7f957c4c6d
0xffffff80fbbd3de0 : 0xffffff7f957e1b9c
0xffffff80fbbd3e10 : 0xffffff7f957bd773
0xffffff80fbbd3e40 : 0xffffff7f946c03a0
0xffffff80fbbd3e80 : 0xffffff7f946c150a
0xffffff80fbbd3ef0 : 0xffffff80144467a8
0xffffff80fbbd3f30 : 0xffffff80144452aa
0xffffff80fbbd3f80 : 0xffffff80144453d9
0xffffff80fbbd3fb0 : 0xffffff80140b2977
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f946b4000->0xffffff7f946ebfff
dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f94666000
com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7f957ba000->0xffffff7f95886fff
dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f9470b000
dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xffffff7f946f7000
dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffffff7f94666000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0xffffff7f946b4000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
12D78

Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
Kernel slide: 0x0000000013e00000
Kernel text base: 0xffffff8014000000
System model name: MacBookPro7,1 (Mac-F222BEC8)

System uptime in nanoseconds: 193761816834889
last loaded kext at 164935062230569: com.apple.driver.CoreStorageFsck 296.16 (addr 0xffffff7f963f3000, size 98304)
last unloaded kext at 165012383409769: com.apple.driver.AppleUSBCDC 4.1.23 (addr 0xffffff7f963f0000, size 12288)
loaded kexts:
com.apple.filesystems.smbfs 1.8
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.iokit.IOBluetoothSerialManager 4.1.3f3
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AGPM 100.12.87
com.apple.driver.AppleHDA 2.3.7fc4
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.3.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.GeForce 8.1.0
com.apple.driver.AppleBacklight 170.2.5
com.apple.driver.AppleUpstreamUserClient 3.5.10
com.apple.driver.AppleMCCSControl 1.1.11
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleSMCLMU 2.0.3d0
com.apple.driver.AppleMikeyDriver 2.3.7fc4
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.1.3f3
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.SMCMotionSensor 3.0.3d1
com.apple.driver.AppleUSBTCButtons 237.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.driver.AppleIRController 320.15
com.apple.driver.AppleUSBTCKeyboard 237.1
com.apple.driver.AppleUSBCardReader 3.1.7
com.apple.iokit.SCSITaskUserClient 3.5.5
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.3.1
com.apple.iokit.AppleBCM5701Ethernet 3.6.0b1
com.apple.driver.AirPort.Brcm4331 614.20.16
com.apple.driver.AppleFWOHCI 4.9.6
com.apple.driver.AppleUSBHub 5.5.5
com.apple.driver.AppleAHCIPort 2.5.1
com.apple.driver.AppleUSBEHCI 5.5.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleUSBOHCI 5.2.5
com.apple.driver.AppleEFINVRAM 1.7
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.7
com.apple.driver.AppleAPIC 1.6
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.driver.CoreStorage 296.16
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.3.7fc4
com.apple.iokit.IOAudioFamily 1.8.9fc11
com.apple.kext.OSvKernDSPLib 1.6
com.apple.iokit.IOSurface 86.0.4
com.apple.iokit.IOBluetoothFamily 4.1.3f3
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleGraphicsControl 3.3.0
com.apple.nvidia.nv50hal 8.1.0
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.NVDAResman 8.1.0
com.apple.driver.AppleSMBusController 1.0.11d0
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.1.3f3
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleHDAController 2.3.7fc4
com.apple.iokit.IOHDAFamily 2.3.7fc4
com.apple.driver.AppleSMBusPCI 1.0.11d0
com.apple.driver.IOPlatformPluginFamily 5.3.0d51
com.apple.iokit.IONDRVSupport 2.3.7
com.apple.iokit.IOGraphicsFamily 2.3.7
com.apple.driver.AppleSMC 3.1.4d2
com.apple.driver.AppleUSBMultitouch 237.3
com.apple.iokit.IOUSBHIDDriver 5.2.5
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.5
com.apple.iokit.IOUSBMassStorageClass 3.5.1
com.apple.driver.AppleUSBMergeNub 5.5.5
com.apple.driver.AppleUSBComposite 5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.5
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.5
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IO80211Family 522.4
com.apple.iokit.IONetworkingFamily 3.0
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOUSBUserClient 5.5.5
com.apple.iokit.IOAHCIFamily 2.3.1
com.apple.iokit.IOUSBFamily 5.5.5
com.apple.driver.NVSMU 2.2.9
com.apple.driver.AppleEFIRuntime 1.7
com.apple.iokit.IOHIDFamily 1.8.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 220.2
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 345
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore 28.21
com.apple.driver.AppleACPIPlatform 1.7
com.apple.iokit.IOPCIFamily 2.7.3
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
System Profile:
Model: MacBookPro7,1, BootROM MBP71.0039.B0E, 2 processors, Intel Core 2 Duo, 2.4 GHz, 8 GB, SMC 1.62f7
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463531323634485A2D3147314431
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463531323634485A2D3147314431
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MJA2320BH G1, 320.07 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24600000 / 2
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26100000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06610000 / 5
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x06500000 / 3
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x06300000 / 2

Again, I do not think this is related, but when my computer reloaded all my closed apps, my most recent browser tabs were not available in Safari, and this gave me pause. (given the way the i/o errors had occurred).

If anybody understands these logs better than I do, please feel free to interject.

 

[MacRobert10]

I'd write that off as a YAMLB (yet another Mountain Lion bug) problem.

The fault is video related. From the logs the system is a MacBook Pro 7,1 which uses an NVIDIA GeForce 320M, and the very first messages in the log are all related to the card. The reason the tabs weren't saved is because the status gets saved periodically and on closing an app.

Unless this appears again and again, I wouldn't worry about it yet.

 

[ObeseSquirrel]

I'd write that off as a YAMLB (yet another Mountain Lion bug) problem.

The fault is video related. From the logs the system is a MacBook Pro 7,1 which uses an NVIDIA GeForce 320M, and the very first messages in the log are all related to the card. The reason the tabs weren't saved is because the status gets saved periodically and on closing an app.

Unless this appears again and again, I wouldn't worry about it yet.

After 5 days of running my Macbook normally, I had a similar error again! This time, my cursor froze altogether, and the lap top would not go to sleep. I restarted the computer manually, and no kernel bug report showed up. Here's the Console log:

4/14/13 12:32:02.310 PM mDNSResponder[47]: 110: Could not write data to clientPID[-1]() because of error - aborting connection
4/14/13 12:32:02.314 PM mDNSResponder[47]: 110: DNSServiceGetAddrInfo v4v6 3999.voxcdn.com. PID[-1]()
4/14/13 12:32:02.314 PM mDNSResponder[47]: 111: Could not write data to clientPID[-1]() because of error - aborting connection
4/14/13 12:32:02.320 PM mDNSResponder[47]: 111: DNSServiceGetAddrInfo v4v6 3999.voxcdn.com. PID[-1]()
4/14/13 12:32:02.320 PM mDNSResponder[47]: 112: Could not write data to clientPID[-1]() because of error - aborting connection
4/14/13 12:32:02.324 PM mDNSResponder[47]: 112: DNSServiceGetAddrInfo v4v6 3999.voxcdn.com. PID[-1]()
4/14/13 12:33:04.050 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:39:53.896 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:40:49.045 PM 1Password Helper[214]: Failed to return databaseID, encryption key is not loaded
4/14/13 12:44:22.120 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:44:25.486 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:45:09.077 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 12:53:15.440 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:02:06.223 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:11:51.729 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:23:18.583 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:35:28.652 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:38:54.246 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:41:00.151 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:41:05.078 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:41:38.575 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:03.506 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:06.719 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:49.519 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:48:50.743 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:50:45.898 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:51:45.168 PM netbiosd[70]: name servers down?
4/14/13 1:51:53.801 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:52:46.214 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:40.193 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:41.480 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:42.007 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:43.421 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:47.473 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:48.644 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 1:59:51.221 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:00:00.083 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:09:24.109 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:12:12.311 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:16:53.185 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:19:16.222 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:21:58.010 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:25:12.634 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:25:50.191 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:30:17.864 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:39:26.157 PM WindowServer[69]: CoreAnimation: context hosting changed while locked!
4/14/13 2:39:52.501 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:40:22.247 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:40:27.571 PM WindowServer[69]: CoreAnimation: context hosting changed while locked!
4/14/13 2:40:41.147 PM WindowServer[69]: CoreAnimation: context hosting changed while locked!
4/14/13 2:41:43.197 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:43:37.586 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:44:27.896 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 2:44:30.097 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:00:17.624 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:00:57.553 PM com.apple.usbmuxd[35]: _heartbeat_failed heartbeat detected detach for device 0x35c-192.168.1.65:0!
4/14/13 3:04:46.470 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:08:03.146 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:08:18.158 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:11:02.340 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:11:24.989 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:13:56.158 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:15:09.912 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:15:53.014 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:21:23.417 PM com.apple.usbmuxd[35]: _heartbeat_failed heartbeat detected detach for device 0x364-192.168.1.65:0!
4/14/13 3:22:58.408 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:24:57.606 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:26:12.056 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:26:16.752 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:28:16.100 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:28:29.408 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:29:06.271 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:06.275 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.289 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.306 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.323 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.339 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.356 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.372 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.389 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.405 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.422 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.439 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.457 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.471 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.489 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.504 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.521 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.568 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.605 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.639 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:06.687 PM talagent[154]: CoreAnimation: rendering error 506
[I deleted 25 lines of this same dialogue for the word count.]
4/14/13 3:29:07.684 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.719 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.767 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.802 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.850 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.886 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.933 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:07.968 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.016 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.051 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.099 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.133 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.182 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.217 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.265 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.301 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.349 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.383 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.431 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.466 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.514 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.553 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.597 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.665 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.686 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.729 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.759 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:08.771 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.780 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.802 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.813 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.830 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.846 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.867 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.884 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.906 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.922 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.934 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.950 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.970 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:08.983 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:09.000 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.580 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:10.581 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.611 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.627 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.644 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.660 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.677 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.693 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.710 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.727 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.743 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.761 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.777 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.794 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.810 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.826 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.862 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.910 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.945 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:10.993 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.028 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.075 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.111 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.159 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.194 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.241 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.277 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.324 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.360 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.408 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.454 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.490 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.525 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.573 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.609 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.656 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.693 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.740 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.775 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.823 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.873 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.908 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.956 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:11.991 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.039 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.073 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.122 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.157 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.205 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.240 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.288 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.323 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.371 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.406 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.470 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.487 PM talagent[154]: CGSSetWindowShadowAndRimParametersWithStretch: Invalid window 0x20
4/14/13 3:29:12.488 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.505 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.520 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.537 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.554 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.569 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.586 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.603 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.620 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.637 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.653 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.670 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.686 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.705 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.720 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:12.736 PM talagent[154]: CoreAnimation: rendering error 506
4/14/13 3:29:33.434 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:29:58.125 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:40:01.037 PM WindowServer[69]: Created shield window 0x1ec6 for display 0x042730c0
4/14/13 3:40:01.037 PM WindowServer[69]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
4/14/13 3:40:01.069 PM WindowServer[69]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
4/14/13 3:41:57.287 PM WindowServer[69]: handle_will_sleep_auth_and_shield_windows: no lock state data
4/14/13 3:41:57.290 PM WindowServer[69]: Created shield window 0x1ec7 for display 0x003f003d
4/14/13 3:41:57.290 PM WindowServer[69]: handle_will_sleep_auth_and_shield_windows: no lock state data
4/14/13 3:42:07.646 PM Safari[2183]: CGContextClipToRect: invalid context 0x0
4/14/13 3:44:16.000 PM kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0x1a = Fifo: FBISTATE Timeout Error
4/14/13 3:44:16.000 PM kernel[0]: IOVendorGLContext::ReportGPURestart
4/14/13 3:44:36.000 PM kernel[0]: NVDA(OpenGL): Channel timeout!
4/14/13 3:45:10.000 PM kernel[0]: PM notification timeout (pid 54, hidd)
4/14/13 3:45:10.000 PM kernel[0]: PM notification timeout (pid 9613, BetterTouchTool)

This seems to be related to the GPU somehow, but I cannot tell whether it is hardware or software-related. (PLEASE be the software!!!)

Importantly, this error seems distinct from my earlier i/o problems. I have had graphics freezes in Mountain Lion before (usually related to Dashboard), but never this frequently. I first noticed these endless pages of "CoreAnimation" entries shortly after returning from my vacation/installing 10.8.3.

If anybody understands these console logs, please help me with this!

 

[swingerofbirch]

Similar Thread

I created a very similar thread in the early morning hours today. I discovered this afterward or I would have added my post here. Here is my original post and also a link to it:

https://forums.macrumors.com/threads/1570454/

I have a 2012 13" MBP with a Samsung 830 256 GB SSD.

Just tonight, I tried taking a screenshot and got a message that I did not have permission to. I then tried saving open files and was told there was an error.

Creating a new folder in the Finder caused a -50 error.

I tried rebooting and got to the Apple logo with spinning wheel but it never went anywhere. No error messages.

So, I restarted to Recovery Mode (Command-R). I opened Disk Utility from there, and it told me that there were errors with both the HD (listed as Samsung) and with Macintosh HD. The Macintosh HD error had something to do with the Journal. It could not be repaired.

So, I booted to a cloned drive I had made with SuperDuper. It booted very slowly and beachballed and my internal HD did not show up.

On a whim I decided to run Disk Utility from the cloned drive on the internal drive, and it again found errors but fixed them! I was so relieved (I do have a back-up clone but it's not terribly recent).

I could see the internal Macintosh HD and all the files appear to be there. I tried restarting to the internal drive, but it just stays on the spinning wheel.

I restarted back to the clone, and it still shows the internal drive. I verified it again, and it says the drive is OK.

So, it seems like I should be able to back-up my data tomorrow (I want to wait till I get a new drive because I don't want to write over the data on my cloned drive in case it corrupts what I already have saved).

But I'm wondering if once I back up, erase, and re-install my internal drive, assuming it works, should I trust it?

I have a few theories:

I do record a lot of video and use the drive pretty heavily. Could I have depleted the write cycles in 8 months of heavy use?

Could it be another hardware error on the computer that caused the drive to corrupt? The reason I ask is that this computer previously had the SATA cable between the hard drive and logic board fail, and I had similar problems where the computer wouldn't boot. On the MacBook Pro I had before this one, that same part failed 3 times! It seems to be a pattern for me that I have SATA cables fail.

Could it have been a software bug? The computer had some weird quirks since I got it back from my last repair. The repair depot installed Lion on it, even though it came with Mountain Lion. I upgraded it to Mountain Lion instead of doing a clean install. Something was odd with permissions in that I couldn't update iLife apps through the Mac App Store because it said that I had updates for a different user. I could never figure out what to do about that, but I always assumed it was a permissions issue, possibly caused by the depot installing Lion on a computer designed for Mountain Lion and possibly also installing iLife apps that had been registered to the depot instead of me. I don't know . . .

I guess I'll figure out the answers to my own questions once I back-up, erase, and reinstall OS X on the internal drive and see if it boots. I'm just worried that even if it does work, that it may still be failing and corrupt again due to either the SSD failing or due to something else like the SATA cable.

Any thoughts?

Thank you. Sorry I wrote so much. This got me so anxious, I didn't realize how much I wrote--I literally penned this out in a couple of minutes and the words got away from me!

----------

EDIT:

When I tried selecting the Macintosh HD as the start-up disk from Startup Disk under System Preferences I got this message:

You can’t change the startup disk to the selected disk.

The bless tool was unable to set the current boot disk.

That seems like an odd message for a disk that shows up OK under disk utility.

Is this a clue as to what's wrong?

 

[ObeseSquirrel]

I created a very similar thread in the early morning hours today. I discovered this afterward or I would have added my post here. Here is my original post and also a link to it:

https://forums.macrumors.com/threads/1570454/

I have a 2012 13" MBP with a Samsung 830 256 GB SSD.

Just tonight, I tried taking a screenshot and got a message that I did not have permission to. I then tried saving open files and was told there was an error.

Creating a new folder in the Finder caused a -50 error.

I tried rebooting and got to the Apple logo with spinning wheel but it never went anywhere. No error messages.

So, I restarted to Recovery Mode (Command-R). I opened Disk Utility from there, and it told me that there were errors with both the HD (listed as Samsung) and with Macintosh HD. The Macintosh HD error had something to do with the Journal. It could not be repaired.

So, I booted to a cloned drive I had made with SuperDuper. It booted very slowly and beachballed and my internal HD did not show up.

On a whim I decided to run Disk Utility from the cloned drive on the internal drive, and it again found errors but fixed them! I was so relieved (I do have a back-up clone but it's not terribly recent).

I could see the internal Macintosh HD and all the files appear to be there. I tried restarting to the internal drive, but it just stays on the spinning wheel.

I restarted back to the clone, and it still shows the internal drive. I verified it again, and it says the drive is OK.

So, it seems like I should be able to back-up my data tomorrow (I want to wait till I get a new drive because I don't want to write over the data on my cloned drive in case it corrupts what I already have saved).

But I'm wondering if once I back up, erase, and re-install my internal drive, assuming it works, should I trust it?

I have a few theories:

I do record a lot of video and use the drive pretty heavily. Could I have depleted the write cycles in 8 months of heavy use?

Could it be another hardware error on the computer that caused the drive to corrupt? The reason I ask is that this computer previously had the SATA cable between the hard drive and logic board fail, and I had similar problems where the computer wouldn't boot. On the MacBook Pro I had before this one, that same part failed 3 times! It seems to be a pattern for me that I have SATA cables fail.

Could it have been a software bug? The computer had some weird quirks since I got it back from my last repair. The repair depot installed Lion on it, even though it came with Mountain Lion. I upgraded it to Mountain Lion instead of doing a clean install. Something was odd with permissions in that I couldn't update iLife apps through the Mac App Store because it said that I had updates for a different user. I could never figure out what to do about that, but I always assumed it was a permissions issue, possibly caused by the depot installing Lion on a computer designed for Mountain Lion and possibly also installing iLife apps that had been registered to the depot instead of me. I don't know . . .

I guess I'll figure out the answers to my own questions once I back-up, erase, and reinstall OS X on the internal drive and see if it boots. I'm just worried that even if it does work, that it may still be failing and corrupt again due to either the SSD failing or due to something else like the SATA cable.

Any thoughts?

Thank you. Sorry I wrote so much. This got me so anxious, I didn't realize how much I wrote--I literally penned this out in a couple of minutes and the words got away from me!

----------

EDIT:

When I tried selecting the Macintosh HD as the start-up disk from Startup Disk under System Preferences I got this message:

You can’t change the startup disk to the selected disk.

The bless tool was unable to set the current boot disk.

That seems like an odd message for a disk that shows up OK under disk utility.

Is this a clue as to what's wrong?

This seems much more serious than my problem ever was, as you are showing actual drive corruption. I suppose one of the first things I would do is check your drive's warranty and see if they will replace it.

Also, maybe take a good look at your SATA cable like I did, though my error was distinctly different than yours appears to be. (Mine would work fine for several days, then would "disconnect" randomly, correlated with movement of the laptop.)

You might want to try running Scannerz, as this helped me some.
Consistent errors in the same places=problem with the drive.
Inconsistent errors = hardware problem
(though my hardware issue was rare enough that even Scannerz didn't pick it up, but it did find some errors in the drive.)

In any case, I think you will be best served resolving this issue in your own thread, as this one has already gotten pretty bogged down in my own issues, which may very well be completely different.

Best of luck to you.