Put the mini into target disk mode, connect the thunderbolt from the mini to the MBP, boot the MBP off of the mini disc, see if it happens then. Is it hardware of software.

You'll have to use the MBP for the screen. If the FW port on the mini was working you could connect the two with FW while the mini is in TDM, then the monitor to the thunderbolt on the MBP.

If your MBP has two thunderbolt ports you can use the monitor. I forget which one you have, I don't think it does though.

I might try that (only one T-Bolt port). But with so much chatter about this on the Apple support forums (and others), I'm more inclined to think this a software bug — especially since the problem never existed before the update.

I'm also considering just plugging in the MBP for this week to confirm that there's no problem on that system, and then, as much of a PIA as it is, wipe the Mini with a multi-pass and do a clean reinstall of everything. Or possibly postpone the latter for a few weeks if it looks like a new Mini might be in Chanuclause's bag.

But to put this in the context of my typical day, I very very rarely log out, and only restart when it's necessary. And generally, I only launch System Prefs once in a great while to change my desktop pic set or tweak a setting. So these problems are not necessarily killing my workflow, but are a concern because, metaphorically speaking, even if you can't hear it, you don't want any trees falling in the forest.

Definitely not a hardware issue. I shut down the Mini and replaced it with the MBP, and then proceeded to continue the work that I had started earlier, using ID, Pshop, and AI. After a couple of hours, I encountered the same problems.

But wait — there's more! (as they say on TV) While working on the Mini, I found that I could access only one of the two partitions on my external drive. And when I created a new folder on the desktop, I was unable to rename it. I got a "couldn't complete the task" error. While working on the MBP, I was able to open both partition windows, but the contents simply would not appear! I had also read that some people were experiencing data loss on their external drives since installing Mavericks — so maybe this was what they were referring to. My stuff is still there, but until a reboot, I can't see it.

So at least I know this isn't a hardware thing. Nor is it an isolated situation. And, at least for me, it appears to be instigated by moderately processor-intensive activity (like working in three CC apps at the same time), which is why at first, I thought the MBP had dodged the bullet. F'n bummer!

And the saga continues. ID locks up during some simple tasks, like relinking an image. And when I force-quit, it will not relaunch, which means another forced shutdown. So now it is compromising my workflow.

Sh¡t, Apple... who built this OS, the same clowns that developed healthcare.gov?

Something to look forward to.

Can't come quickly enough.

Weird. My Snow Leopard just works....

I am sorry for your frustration !

I give you some empathy.

.

Stick around MrPooh

empathy is just what Mavericks needs oodles of lately;)


.

?
You are responding to the wrong person.
Please re-register to make your next 1st smart ass comment.
TYVM!

Yawn...