6 Replies Latest reply: Aug 6, 2013 7:01 PM by kenackr
kenackr Level 1 (0 points)

It seems like I'm getting the blue screen of frozen death about 40% of the time on startup and getting tired of it.


Everytime it happens I repair permissions and it looks like there is a cat fight going on. I have 3 bootable drives in my Mac Pro 4,1 2.26ghz, 32 gram, 4 x 1 TB wd black's, boot drive +1 other = enterprise drives.


Yesterday, after the blue screen of frozen death, I repaired permissions on the 3 boot amigos and all of of them had changed permissions on the same areas:

  • System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/dt.jar........ and more concerning Java stuff
  • Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/management-agent.jar"
  • System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib
  • System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Support/LockScreen.app/Contents/Resources/ko.lproj/MainMenu.nib"
  • System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Remot e Desktop Message.app/Contents/Resources/Dutch.lproj/UIAgent.nib"
  • "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Remo te Desktop Message.app/Contents/Resources/zh_CN.lproj/UIAgent.nib"
  • "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Remo te Desktop Message.app/Contents/Resources/Dutch.lproj/UIAgent.nib
  • System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPluginCocoa.bundle/Contents/Resources/



I copied the entire list of permission repairs and copied it to word and it is attached for your viewing pleasure.


My concern is that "java virtual machines", "Remote Management", and "java VM framework" keeps getting mentioned. Because I'm not knowledgeable  about these things AND that it keeps happening  unbeknownst  to me on a daily basis  it makes me very nervous.


I still don't understand how "permissions" for drives get changed or why anyhow.


Lastly, I've read that resetting permissions should cure the blue frozen screen of startup, but it's not happening here.


Help if you can, please.


if you want to see the whole banana you'll have to tell me how to attach it.




Mac Pro (Early 2009), Mac OS X (10.6.8), 8 core, 32 GRam, 4 TB HD
  • Baby Boomer (USofA) Level 9 (57,290 points)

    You are not being hacked.  See KB Article http://support.apple.com/kb/TS1448





    Disconnect all devices from the computer then do the following:


    Boot up from your Snow Leopard Install DVD while holding down the "c" key.

    Select the language you wish to use, and then choose "Disk Utility" from the menu bar.

    Your HD should appear in a panel on the left hand side of the window which opens. Select it and then click on the "repair disk" button in the right hand section of the window.

    Once this process has been completed restart your computer and repair permissions directly from Disk Utility.


    If Disk Utility is unable to complete the repair, you will need to use a stronger 3rd party utility like DiskWarrior, Techtool PRO (not Deluxe) or Drive Genius.










  • WZZZ Level 6 (12,845 points)

    I don't know why the Permissions repairs appear to keep changing, but all those related to Java are normal. I get tons of the Java ones. And they will keep reappearing whenever I repair Permissions, which is hardly ever.


    See if this fixes the blue screen issue. Open Terminal in Utilities and copy/paste in the following.


    sudo update_dyld_shared_cache -force


    You will be asked for your admin password, which won't appear in any form when you type it in and you will be given a warning about using the sudo prefix. Keep going and hit return. When you get a new $ sign prompt, you will be finished. Just close the window.


    You should also try a Safe Boot: Shift at the startup chime and give it much longer to boot than usual. This is normal. Leave it in Safe Boot a minute or two without opening anything and then restart as usual. After restarting, also wait a few minutes  without opening anything. Probably try this first.


    You aren't being hacked.

  • andyBall_uk Level 7 (20,490 points)

    Hi WZZZ


    the man page for update_dyld_shared_cache says

    'Note that the new cache does not take effect until the OS is rebooted'


    'If a safe-boot is done (booting with shift key held down) the cache is deleted.'


    Your suggestion to try Safe mode is a good one.

  • WZZZ Level 6 (12,845 points)

    Reboot necessary noted. Thanks for pointing that out.

  • kenackr Level 1 (0 points)

    Baby Boomer,


    Thanks for the reply!


    I have done it direct from the install disk as you suggest and while on the boot drive. Seems to make no difference.


    Thanks for the kb tip article, I wasn't aware of it.

  • kenackr Level 1 (0 points)



    I tried your suggestion on the terminal and got this exchange:




    Also did the safe boot and a reboot after that.


    Proof will be in the pudding.


    I'll keep you informed.


    This seems to one of those things that could have easily been corrected by Apple. WHy with this grade of technology did they allow this persist?