10.6.4 complete system freeze when resuming from screensaver-VMWare Fusion

I have a Macbook Pro, 3,1. I just upgraded to 10.6.4 and noticed the following symptoms:
Shortly after launching VMWare Fusion 3.1 running a Windows XP VM (from a Bootcamp partition), a series of pop up messages were complaining about a bad OpenGL driver. The message popped up repeatedly and wouldn't let me out, even though I kept pressing "Ok". I had to force quit Fusion, which caused a chkdsk on relaunch of the XP VM.
After a complete reboot, I started VMWare again. The Fusion complaints haven't shown up again, but when resuming from the screensaver, the system either completely freezes up, or the screen login window starts to flash rapidly and seize up. I'm running Spaces with 6 virtual screens. Whether I'm in the Fusion Spaces screen or any other Spaces screen, the system freaks out when resuming from a screensaver.
I use this system at work, so I have to be able to lock my screen when I leave my cube. The only way I've been able to ensure the system doesn't freeze up and cause a hard reset of the XP VM is to completely disable the screensaver and power saver features, such as Start Screen Saver = Never, Computer Sleep = Never, Display Sleep = Never and launch the login window by clicking on my user name in the upper right corner of the screen on the menu bar. Even that causes a sluggish screen and I'm not confident it will keep working. I also made sure (from day one) that the Windows XP screensaver functions were all completely disabled. I prefer to use the OS X screensaver for everything, if for no other reason than having a single screen locking/unlocking point for when I step away.
This was all working properly in 10.6.3. The only nit-nat I noticed about Fusion in 10.6.3 was that it had to be launched in the "Primary Window", which seems to be the upper leftmost Spaces desktop. If I ever moved it to, or started in any other Spaces desktop, it would also exhibit the same random lockups. Keeping it in the "primary" space seems to have stopped the lockups.
I noticed that there seemed to be significant updates to the OpenGL drivers in 10.6.4. I am experiencing an unfortunate side effect of these updates and hope I'm not alone and that a fix is coming soon. Looking at the other posts, there seem to be a lot of similar problems. I wanted to describe my configuration in case the Apple dev team reads these posts. Thanks.

I ended up doing an erase and fresh install of Snow Leopard (10.6.0), upgraded to 10.6.4 with the combo update, then a fresh install of all my apps, including VMware 3.1. Everything has been solid for 2 days now. I'm guessing that my system had a magic combination of issues that weren't visible in 10.6.3 but became obvious only after upgrading to 10.6.4. I had been upgrading my OS since 10.5.0 over the last 2 years and needed to do a clean re-install for some time now.
I'm guessing that others who are noticing problems with the 10.6.4 update have a similar situation with their installations. Think back on all the times a software installation failed, or the system required a hard boot. Plus, I had a lot of 3rd party apps on my box that never posted updates for later Snow Leopard releases, so who knows? Anyway, it's good to have a clean and snappy system again. A lot of my apps launch a lot faster now and survive the screen saver and power saver modes just fine.
Message was edited by: mausoleum

Similar Messages

  • When resuming from screensaver

    When resuming from screensaver screen is pixelated in large blocks about a quarter inch square. I can put in my password after i roll the cursor around enough to see where to click to put in my password. Is there a fix for that yet?

    Just wanted to say that i got an adwise in the thread that i posted earlier that has worked for me.
    Adwise form Softwater:
    Try deleting this file:
    ~/Library/Preferences/com.apple.screensaver.plist
    and then re-starting your mac.
    Don’t worry, deleting the file is harmless. It will just recreate itself to default settings when the computer reboots. It may be that the current file is corrupt.
    Note: to get to this file in Lion, you have to chose ‘Go’ menu from the Finder menubar at the top of the screen, while keeping the ‘option’ key held down. When you do this, you will see ‘Library’ in the Go menu bar. Click on it and navigate to Preferences and look for the filecom.apple.screensaver.plist and trash it.

  • System freeze after resume from suspend

    I am running arch for about 5 month now and I always had freezes after resuming from suspend (to ram - systemctl suspend) every once in a while (like once a week or less). The freezes increased massively over the last month or so and for about 2 weeks now it happens 95% of the times I resume from suspend.
    The monitor turns on and shows things exactly how I left them, but is completely unresponsible EXCEPT for I can switch to another TTY (Ctrl+Shift+F*), however I cannot type or do anything in it...
    It doesnt have anything to do with the X server as it also happens after I suspend from TTY (without any X running).
    I also checked journalctl -b -1 (shows previous boot, since I always have to hard-reset the system) but it doesnt show anything after:
    Mar 13 17:16:54 Ununhaswellium systemd-sleep[3624]: Suspending system...
    (the suspend event before resuming)
    Are there any log files that could give a hint on what exactly goes on after the resume?
    Im running the latest official 3.13.6-1 kernel and updated my BIOS to the latest beta version yesterday - didnt help either...
    Ive read pretty much every thread on the internet by now about freezes after resume from suspend but none really helped
    Last edited by CharlieBra7o (2014-03-15 09:58:51)

    Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
    And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
    Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

  • System freeze after resume from suspend to RAM

    Hi,
    since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
    kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
    kernel: sas: trying to find task 0xfff880008b5b680
    kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
    kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
    kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
    kernel: sas: trying to find task 0xffff8804606ccb40
    kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
    kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
    kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
    kernel: sas: ata7: end_device-0:0: cmd error handler
    kernel: sas: ata8: end_device-0:1: cmd error handler
    kernel: sas: ata7: end_device-0:0: dev error handler
    kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
    kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
    res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
    kernel: ata7.00: status { DRDY }
    kernel: ata7: hard resetting link
    kernel: sas: ata8: end_device-0:1: dev error handler
    kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
    kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
    kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
    res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    kernel: ata8.00: status { DRDY }
    kernel: ata8: hard resetting link
    This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
    Here's my setup:
    $ lsblk -St
    NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
    sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
    sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
    sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
    sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
    sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
    $ lsblk -f
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs Recovery 567437B974379B27
    ├─sda2 vfat DC2D-099E /boot
    ├─sda3
    ├─sda4 ntfs FEBED982BED933BD
    ├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
    └─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
    sdb
    └─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
    sdc
    └─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
    └─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
    sdd
    └─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
    └─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
    I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
    Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
    Any ideas on how I could narrow down this issue? Thanks a lot!
    EDIT
    I just checked and confirmed that this issue is originating from the OCZ Revodrive:
    $ dmesg | grep ata7.00 | head
    [ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
    [ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
    [ 7.146442] ata7.00: configured for UDMA/133
    $ dmesg | grep ata8.00 | head
    [ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
    [ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
    [ 7.320022] ata8.00: configured for UDMA/133
    Last edited by tuttiarch (2015-01-31 15:54:29)

    Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
    And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
    Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...

  • Z68A-GD55 B3 Freezes when resuming from S3 sleep

    When resuming (waking up) from S3 sleep, the computer freezes after about 1 second. 
    I've tried
    * Removing all USB devices
    * Disabling all USB controllers via BIOS
    * Removing external video card and only using integrated graphics
    * Resetting CMOS and using all BIOS defaults
    * Updating to the latest official BIOS (M5)
    The only clue I have is an event logged in the Event Viewer each time this happens: Driver PCI returned invalid ID for a child device (FFFFFFFFFFFFFFFF00).

    This is a link to the topic I have going https://forum-en.msi.com/index.php?topic=154271.0  where I have had similar issues with the same board.  The same message you receivedQuote from: bomax on 19-November-11, 11:31:36
    Driver PCI returned invalid ID for a child device
    is the one I got on the Blue screen freeze after flashing the BIOS.  I am not freezing or BSODing now during gaming but when I come out of sleep or when I have went to shut the PC down.  I am about to check the voltages but I will try you fix too.  I have wondered about the BIOS for the (G3) compared to the (B3).  I have the latest (B3) beta BIOS for this board, I just curious.

  • Helix freezes when resuming from sleep mode

    Every time I close the lid, the Helix enters sleep mode. Then, when I reopen it and enter my password, the computer freezes, most often taking me to the Photos app.  In order to resume work, I have to use the Power button to shut down and restart.  Very frustrating -- can't even walk across the room with the lid closed without having to restart, often losing whatever I was working on.  Any ideas?

    Hi Yvonnerose,
    Thank you for the reply!
    1) Update your bios and update the Intel Management Engine firmware to the latest. Below is the link to enter the downloads page and download latest application accordingly, please click on "Select Product" then in "QUICK PATH" enter the MTM no. select the exact model.
    http://support.lenovo.com/en_US/downloads/default.page#
    2) if issues still persist, please check the installed RAMS or he secondary RAM installed as in some cases it has been found cause the interruptions. If the system is shipped with dual memory try running with only one RAM first to check if problem still persist.
    3) If both of the above fails please contact nearby Authorized Lenovo service support teams, they will able to advise according on the next course of action.
    Hope this helps. 
    Best regards,
    Hemanth Kumar
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • [SOLVED (in kernel 3.8.8)] Random complete system freezes

    I have installed Arch Linux on my desktop, however I am getting random complete system freezes when I use either GNOME Shell or KDE 4 when using OpenGL compositing. I have resorted to using Xfce (which uses Xrender for compositing).
    Sometimes the system freezes immediately upon login.
    Sometimes GNOME Shell says "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." and forces me out.
    Sometimes the system works fine for an hour or so before it freezes.
    Sometimes the driver appears to have crashed but then recovers (screen goes blank for a second and windows/decorations are redrawn, then works fine until it completely freezes again).
    I am using the xf86-video-ati driver with a ATI Radeon HD 3850. I suspect the problem is with the video driver and/or kernel.
    I have tried:
    - Using Alt+SysRq+? keystrokes after adding kernel.syseq=1 to /etc/sysctl.conf (system doesn't respond at all once frozen)
    - Keeping an SSH connection open (SSH client says "host down" once the computer is frozen)
    - Doing a memtest (ran for 11 hours with no problems)
    - Redownloading and reinstalling all packages from a different mirror (no improvement)
    - Disabling KMS (GNOME Shell runs very slow, at wrong resolution, and the resolution settings doesn't give me the option of the correct resolution)
    - Adding radeon.agpmode=-1 to my kernel parmaters (no improvement)
    - Edit: Also I tried installing linux-lts (GDM and GNOME Shell graphics ends up all broken)
    I was previously using Fedora 17 with the open source driver without any problems.
    dmesg: http://pastie.org/private/z3c793diqvujvtzjecxr4q
    pacman -Q: http://pastie.org/private/jy8a5fpsxidkkg2dheyq
    /var/log/Xorg.0.log: http://pastebin.com/NaXiA6q9
    /var/log/Xorg.0.log.old: http://pastebin.com/MPKGrLSV
    uname -a: http://pastie.org/private/lqp73mj3bztdzptcisxt4g
    lspci: http://pastie.org/private/ziiazawut1gfpwxjviova
    What should I try next to help troubleshoot this problem?
    Thanks
    Last edited by jesseschalken (2013-04-23 04:56:46)

    https://wiki.archlinux.org/index.php/Do … g_Packages

  • Mavericks 10.9.4 complete system freeze on any webpage with Flash

    Been running 10.9.4 without problems on this rMBP 15" 2.3GHz, 16GB RAM.  Today it started freezing when I tried to load a flash video from comedy central.  Complete system freeze, cursor stuck, no feedback, hard restart required.  I thought it might be Silverlight at first so I disallowed it in Safari and it seemed to be ok, but after loading another video the system froze again.
    It now occurs for all browsers I try, Safari, Firefox, Chrome.  I have now *uninstalled Adobe Flash* via Adobe's uninstaller, and disabled extensions in Safari.  When I go to youtube.com the system freezes completely again.
    I have run Disk Utility and at first it reported that repairs were needed.  I tried a Command-R restart but the computer would boot up eventually into a black screen and then I'd hear "To continue in English, press return" but then nothing would happen.  I restarted and tried to go into Safe Mode but it didn't work, read that I needed to disable FileVault for that approach.  I could still boot normally (and still can), so I disabled FileVault and have tried booting into Safe Mode.  It still doesn't work though--sometimes when I restart it just doesn't go into Safe Mode, and sometimes it goes to a black screen.  However, now when I run Disk Utility's Repair Disk, it reports no problems.
    I don't know what to do from here except back up to Time Machine and restore from backup.

    Thanks for your suggestion Eric.  I tried that and it gave me the recovery volume option.  But when I selected it, after a few seconds the screen went black and stayed there until a voice said "To continue in English, press return".  I'm guessing that it is in recovery mode correctly but there is a problem with the graphics card which leads to the screen shutting down.  I don't know what else I could try except taking this in to an apple bar, but holla if you have any ideas!

  • K7N2 Delta2 Platinium - System freezes when copying or writing to HDD

    I am experiencing a strange problem. I don't know what I have changet to my system but since 3 days ago I am geting this system lock up when I move or copy files from one HDD to another. Windows doesn't show any error message. When copying files, either in the midle of the proces or at the end the system LOCKS UP  and there is nothing i can do except a hot restart. I never had this problems and it was months that my computer was very stable. I have no ide how to test to get some info about this issue. Any opinions ?
    Thanx

    The tems are cool. CPU varies from 44°(idle) to 58° celcius (full load). Motherboard also 35° celcius. Now i dont know whats the start but let me tell the whole story. First of all i have this system since long time ago. Normally i install the computer once, than I optimize the system as i want it to be and than i back it up. Now Since i have all my programs installed in the way i want i dont like to reinstall the computer often, because it will take me two week to complete all the tweaks and changes that i do normally. So this system that is now runing has passed to three different motherboards (computer changes). Maybe the process of installing and reinstalling drivers in the system has degraded it. I am very carefull to clean drivers, registry and all. Although the system shows now errors, about 7 months ago i used to suffer system freezes when burning DVD. I couldn't resolve the issue since the problem was Nero being victim of SERVICE PACK 2. Anyway i have read that Windows XP SP has some Buffer and Cache problems and it makes conection with the burning problems. Since then i don't know how, after some times the burning problem disappeared ... i could burn DVD with the same version of NERO and everything was fine untill 3 days ago  . So i got the new NERO 7 with its new EXTRA BUFFER feature whitch works fine. Soon after installing NERO 7 one of my HDD crashed (i dont thing it has any conection with nero), it lost the partition table and it was recognised as UNALLOCATED. I recovered all the datas using a software calle R-Studio (very good by the way it can recover FDISK, Format, Delete, everything). After i had reformated the drive that crashed, I copyed back all the rescued files. Its there that the Copy Hang Ups started. WINDOWS doesn't show any ERROR at all, that means that there is no controller or HDD problem. I checked the drive and its fine. What reasured me that the drive was not the cause, was that even when i started copying between the other drives of my system i got the same problem.  So maybe my system is in a very very bad shape, or i dont have a clue of this thing        What is strange its that WINDOWS DOESN'T SHOW ANY ERROR MESSAGE, and PRIME STRESS TEST GOES ON FOR HOURS WITHOUT THE SMALLEST PROBLEM.
    Thanx Dr. Stu I also tried copying at stock speed and i got the same problem.

  • System freezes when link to Google Hangouts

    Hello, 
    Can anyone help with an answer why my System freezes when I try to link to Google Hangouts
    I am using a Samsung Notebook N150 , windows 7 starter , service pack 1 .
    I have tried a system restore but get a "shadow error " , have also tried in Safe mode
    I am not sure how to post the event viewer here ?
    Thank you  

    Hi,
    For event log, you can upload it to a public folder like OneDrive, then paste the download link here for further analyzing.
    When does this issue happen? I mean something you have changed might causes this issue, or this plug-in doesn't work since you installed to Windows 7 Starter. Hangouts doesn't support certain mics and webcams.
    Since this plug-in is related with audio\video, I suggest you update the drivers for your audio\video device.
    Some thirty audio\video packages can also cause a crash.
    Try to uninstall and reinstall the plug-in.
    For Product Google Hangouts, It's better to contact this support, they're more familiar with this product
    https://support.google.com/hangouts/?hl=en#
    NOTE
    This response contains a reference to a third party World Wide Web site. Microsoft is providing this information
    as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites.
    Yolanda Zhu
    TechNet Community Support

  • Minor lag from GUI when resume from sleep

    Hey people!
    I've been on archlinux for a couple of months now and I have fixed bugs here and there but something I have just noticed yesterday (it would happen before but I couldn't say when it would occur) is that after my system resume from sleep (it's not slow, it takes 1 or 2 secs) gnome GUI is a bit slow and it doesn't stop till I reboot my pc (it doesn't occur until my pc resumes from sleep).
    It's not that bad but quite annoying. I don't really know how to approach that kind of problem. I think it would be related to something like "gnome is not completly reloaded when resume from sleep and there are some infinite loop going on"...
    I hope someone has a clue in here!

    hey, sorry to revive an old thread, but this was the only other person I could find with this issue.
    I had originally reinstalled power manager and the the pm driver because it wouldn't save any custom power settings. When I finally got it working, it wouldnt wake up from sleep just like the above user's issue.
    Machine is relatively new win7x64 install with all updates (lenovo updates too) installed.
    Would like to avoid a total reinstall if at all possible.

  • Airport Card turned off when resuming from sleep - New since 10.6.6

    I use safe sleep regularly, as I use my laptop at both work and home. Ever since the update to 10.6.6 though, I have had to manually turn my Airport connection back on after resuming from sleep.
    Previously, although it was unreliable about connecting to a preferred network (an unrelated, but equally frustrating issue*) at least it would remain on. Now I've had to add the icon to my Menu bar just so I don't have to dig into System Preferences every single time I reawaken my laptop.
    Does anyone know why this is happening, and if there is anything I can do to prevent it? I apologize if this has been asked before, but when I searched I was unable to find anything.
    *This issue is unrelated and not the focus of my post, but if you happen to know about it I would absolutely appreciate your input.
    When resuming from sleep, despite being between 5-20 feet from my preferred router I will often receive a dialog asking me to select from a list of SSIDs and enter a password even though that information is already saved. Then, once I complete this information Airport doesn't actually connect and the only way to resolve the issue is to turn Airport off and then back on. After this, it will automatically connect with no problems and remain connected until I put the computer into Sleep mode again.

    Maybe check in your keychain and verify the password saved is correct for your wireless router?
    Do you broadcast the network name?
    Could you describe "unreliable about connecting to a preferred network"?
    Is "use secure virtual memory" checked in the Security preference pane? If so try unchecking that maybe? If it's a hibernation issue sometimes that could cause weirdness.

  • A problem with a macbook retina when resuming from sleep.

    After many questions and a complete reinstall at an apple store I stil have the problem. When resuming from sleep, and sometimes seemingly at random, the machine swaps to a different application. I run several desktops full screen and it will swap to a different desktop virtually every time I resume. Not a huge deal but annoying. It seemed to start happening when I installed Office for Mac, but that might just be coincidence. I'm not running anything weird in the background, just a utility to show when the graphics card is active. Any help would he greatly appreciated.

    Running games at full resolution may produce occasionally-choppy video, but nothing that would prevent you from playing. I mayself have played Portal and Left 4 Dead 2 on mine, and I haven't noticed any problems.

  • Access Violation in aapltp.sys when resuming from sleep.

    Hello,
    *I have diagnosed an issue in the aapltp.sys (touch pad) driver included with the MacOS 10.6.2 DVD. This issue causes a illegal access to be performed by this driver when the computer resumes from sleep (I have never reproduced it when resuming from hibernate or during normal operation). This issue occurs about once in every 10 resume operations, with both Windows 7 and Windows Vista. I have not experimented other versions of the OS.*
    *The version of this driver included with 10.5.x DVD does not have this issue - this is a new regression.*
    *In summary, KeyMagic (another apple driver) running on a system thread calls the OS for a dispatch (FxDevice::Dispatch). This ends up being routed to aapltp. While executing, aapltp dereferences a memory position offseted from a register that contains NULL. This causes an Access Violation which escalates into a BugCheck.*
    *AFAIK Apple does not distribute driver symbols so I was unable to dig into the cause for the fault in this driver. I am appending some additional crashdump information that might be useful. If you require additional information, let me know. I can either provide you with the full crashdump of perform further analysis if you make the symbols available.*
    * Bugcheck Analysis *
    SYSTEMTHREAD_EXCEPTION_NOTHANDLED (7e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004a7ea74, The address that the exception occurred at
    Arg3: fffff88005134718, Exception Record Address
    Arg4: fffff88005133f70, Context Record Address
    Debugging Details:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    aapltp+ca74
    fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
    EXCEPTION_RECORD: fffff88005134718 -- (.exr 0xfffff88005134718)
    ExceptionAddress: fffff88004a7ea74 (aapltp+0x000000000000ca74)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 000000000000005b
    Attempt to read from address 000000000000005b
    CONTEXT: fffff88005133f70 -- (.cxr 0xfffff88005133f70)
    rax=0000000000000000 rbx=0000000000000004 rcx=fffffa80057899e0
    rdx=0000057ffa876618 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004a7ea74 rsp=fffff88005134950 rbp=fffffa8005789d50
    r8=fffff88004a7b140 r9=0000000000000000 r10=fffffa80056809e0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000057ffa99e188 r15=0000057ffa99e188
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    aapltp+0xca74:
    fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1 ds:002b:00000000`0000005b=??
    Resetting default scope
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 000000000000005b
    READ_ADDRESS: 000000000000005b
    FOLLOWUP_IP:
    aapltp+ca74
    fffff880`04a7ea74 807e5b01 cmp byte ptr [rsi+5Bh],1
    BUGCHECK_STR: 0x7E
    DEFAULTBUCKETID: NULLCLASS_PTRDEREFERENCE
    LASTCONTROLTRANSFER: from fffff88000e52f90 to fffff88004a7ea74
    STACK_TEXT:
    fffff880`05134950 fffff880`00e52f90 : fffffa80`05661e70 0000057f`fa9443a8 fffffa80`056809e0 fffffa80`056bbc50 : aapltp+0xca74
    fffff880`051349b0 fffff880`00e5299f : 00000000`00000000 fffffa80`05661e70 fffffa80`056bbc50 fffffa80`056bbc50 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x4b8
    fffff880`05134a30 fffff880`00e51f98 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05661fc2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
    fffff880`05134aa0 fffff880`00e57558 : fffffa80`04e2fb00 fffffa80`05661e70 fffffa80`04e2fb00 fffffa80`05661e70 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
    fffff880`05134b10 fffff880`00e41245 : fffffa80`05661e70 fffffa80`04160c30 fffffa80`04e8ea58 00000000`000f2008 : Wdf01000!FxPkgIo::Dispatch+0x37c
    fffff880`05134b90 fffff880`04a672f6 : fffffa80`04160c30 fffffa80`056bcc90 00000000`00000000 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
    fffff880`05134bc0 fffff880`04a6660b : fffffa80`056bcc90 fffffa80`04e8c010 fffffa80`08897640 fffffa80`04e8ec20 : KeyMagic+0x32f6
    fffff880`05134c30 fffff800`03334166 : fffffa80`04e00040 00000000`00000080 fffffa80`03cd1740 fffffa80`04e00040 : KeyMagic+0x260b
    fffff880`05134d40 fffff800`0306f486 : fffff800`03209e80 fffffa80`04e00040 fffffa80`03ce6680 fffff880`0122ca90 : nt!PspSystemThreadStartup+0x5a
    fffff880`05134d80 00000000`00000000 : fffff880`05135000 fffff880`0512f000 fffff880`05134770 00000000`00000000 : nt!KxStartSystemThread+0x16
    SYMBOL_NAME: aapltp+ca74
    MODULE_NAME: aapltp
    IMAGE_NAME: aapltp.sys
    DEBUGFLR_IMAGETIMESTAMP: 49c7fb1c

    Thanks for posting this information in this forum. You just saved me a couple thousand dollars!
    Based on my experience if you want to get this problem fixed as soon as possible you need to do the following:
    1. www.apple.com/feedback
    2. Post a video of the problem on www.youtube.com
    3. Send www.apple.com/feedback a link to the video on youtube.
    4. Encourage others to visit your youtube video and to post their own.
    Good luck!

  • When resuming from standby mouse-click/keyboard doesn't work.

    When resuming from standby about 80% of the time the mouse on my Macbook Pro (Early 2011) stops working. I think it is a software issue. It appears that the mouse will do a click or click and drag but will not let go when removing my fingers. The issue only happens within 5seconds of waking up. The issue is only fixed with a hard reboot. I can bring up the shutdown menu, but am unable to slect shut down as the mouse/keyboard won't give input. This issue was present in Lion and was gone for the first few months of Mavericks but appeared again this week.
    I can freely move around the mouse cursor and enter expose with three fingers but cannot select anything.
    Any help would be appreciated.
    Thanks.

    You can use viewToModel() method to get caret position for x, y location. No need to click.
    Regards,
    Stas

Maybe you are looking for