Is instant on, or resume from sleep expected to be slower?

I have a MBA 1.6 GHz Core 2 Duo with 4 GB RAM and after upgrading to Lion it takes an unusual amount of time (around 10 seconds) to wake up from the sleeping state (closing the lid).  This time varies depending on how long the system has been in sleep.  Less than 5 minutes the resume is immediate or what it was like with Snow Leopard, more than 15 minutes it takes around 10 seconds...  I have a video of this issue occuring but can't figure out how to attach.

This is right before the login screen...
And finally the login screen...  Note the delta between the time in the start frame and this picture...

Similar Messages

  • 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.

  • Resume from Sleep / Hibernate issues

    Hi all,
    First time poster. I have a Helix and am running into a heap of resume from sleep (and hibernate) issues.
    The sleep issues tend to happen overnight - I do not have this issue if I sleep the machine and then wake it up 5-10 minutes later (e.g. moving between meetings at work). However, when I attempt to wake the machine up in the morning, it fails to resume from sleep, and instead boots from scratch.
    Typically, when the unit is in this state, the status led on the lid is rapidly blinking (which I believe means that it's trying to enter sleep) Since there is nothing in the Windows event log during the overnight period, I'm wondering whether it's trying to enter a deeper sleep mode and failing.
    This happens every second day or so. Which is really frustrating as a tend to lose some work.
    I tried enabling hibernate as a trial, to see if that would avoid the issue, but resuming from hibernate fails as well. At least I get a Windows event log entry for this (source: kernel-power. The unit fails to resume from hibernate with status 0xC000000D)
    I have the September 10 BIOS update, and am running Windows 8.1 Enterprise (though I had the issue with Windows 8 as well).
    Any ideas on how I can troubleshoot this?
    Regards
    AC

    Windows 8: In Windows 8, the default shutdown behavior puts the system into hybrid shutdown (S4) and all devices are put into D3. Remote wake from hybrid shutdown (S4) or classic shutdown (S5) is completely unsupported. In Windows 8, NICs are explicitly not armed for wake in both the classic shutdown (S5) and hybrid shutdown (S4) cases because users expect zero power consumption and battery drain in the shutdown state. This behavior removes the possibility of spurious wakes when explicit shutdown was requested. As a result, Wake-On-LAN is only ever supported from sleep (S3) or hibernate (S4) in Windows 8.
    Note that in Windows 8, hybrid shutdown (S4) stops user sessions but the contents of kernel sessions are written to hard disk. This enables faster boot.
    http://msdn.microsoft.com/en-us/library/windows/desktop/aa373229(v=vs.85).aspx
    From the Helix User Guide:
    •Slow blinking: The tablet is in sleep mode.
    •Fast blinking: The tablet is entering hibernation mode or sleep mode.
    That was my reason for clarifying if hybrid-sleep was enabled; since it's the default setting and you noted that the LED was blinking fast. Does the LED ever stop blinking fast?
    There can/may be multiple log entries during a normal sleep operation,  because "the system uses the lowest-powered sleep state supported by all enabled wake-up devices." If one of those devices wakes the system (this does not mean power on) then the logs will report the devices and will likely return to a another level of sleep, but this does not mean full power loss or empty logs.
    If the system has successfully entered sleep state, then you should see the following message in System Event logs. 
    Event 42, Kernel - Power
    This system is entering sleep.
    Sleep Reason: Button or lid
    When the system is successfully woke you will see a System Event Log similar to this:
    Event 1, Power - Troubleshooter
    The system has returned from a low power state.
    Sleep time: 2013-10-08T01:42:25.XXXXXXXX
    Wake time: 2013-10-08T05:53:21.XXXXXXXX
    However, there will be other events in the logs after sleep and prior to this wake period, such as hardware device issues(My helix has Bluetooth device warnings, nfc driver warnings and some other nondescript hardware errors), kernel messages (about boot manager, boot options, etc.).
    Have you changed the behavior of the power button?
    You also can program the power buttons so that by pressing the power button you can shutdown the tablet or put it into sleep or hibernation mode. To achieve this, you need to change your power plan settings. To access power plan settings, do the following:
    From the desktop, tap the battery status icon in the Windows notification area.
    Tap More power options.
    In the navigation panel, tap Choose what the power buttons do
    Follow the onscreen instructions to configure settings.
    Lastly, when you updated to Windows 8.1, did you format the whole C:\ (mSATA) drive?
    Helix: 3697 CTO.
    Thinkpad user since IBM. I do not work for Lenovo or any entity working for Lenovo.

  • X220 resume from sleep and boot issues

    This is driving me crazy! I have an X220 with Windows 8 and UEFI boot installed.
    It all started when I first installed Windows 8 a few months ago which required me to update my BIOS to the latest version. The installation process often got stuck when booting from the Installation CD (the round circle stopped spinning, the display was at full brightness). Eventually I managed to boot into the Installer (when the boot logo doesn't get stuck, the display is then dimmed to minimum).
    I was quite happy to have a superfast lightweight OS which booted in an instant.. When suddenly it started to get stuck when booting (same issue with the boot logo not spinning anymore). This happens quite randomly, but I often manage to boot (maybe 2-3 times a week, I don't boot often though..). Now, the booting hangs are less of an issue for me but more often that that it fails to resume from sleep. The LEDs flash and then it instantly drops to sleep mode again (well at least the sleep/moon LED is active). This happens quite often as I sleep/resume up to 5-10 times a day (changing lecture rooms, meeting rooms, save battery when the lectures are boring, ...)
    Now after researching and spending hours in debugging this issue, it seems that I'm not the only one having this (or a similar) issue, but often without any definitive solution being specified.
    This is what I have already tried:
    * Upgrade BIOS and SSD firmware to latest
    * Install/update latest drivers
    * Mess around with BIOS options
    ** UEFI/Legacy First options
    ** Intel Virtualization/vt-d
    ** Others..
    I know based on other threads that I'm not the only one experiencing exactly these issues. Has anyone managed to fix this?
    Thank's in advance
    Fabio Scala

    I had a similar issue, as soon as a described even a little bit of it to warrenty support they sent someone to swap the board
    It seems thats the only fix, its been fine since 

  • Update to 10.6.8 - system hang (mouse issue) after resume from sleep

    I am on older
    MacBook Pro3.1
    Intel Core 2 Duo
    2.6GHz
    Run on 10.6.8 almost flawelessly. Shortly after upgrade to 10.6.8 system started to hang periodically after resuming from sleep. Symptoms are that it stops responding to mouse (be it touch pad or USB mouse). Keyboard seems to be ok but system doesn't seem to be fully functional. I am able to ssh from the other computer and 'shutdown -r now' after reboot system seem to be ok until next resume from sleep. What interesting though is that this problem newer manifests then I am using external monitor.

    Found problem. It was due to magic mouse that I left on. I carry this mouse in the laptop bag but rarely use it. Last time I used it (around the same time I install the update) I left it on in the bag. It was apparently disconnecting/connecting on its own and by some reason sometimes was breaking touch pad and other usb mouse connected to laptop, as soon as I switched magic mouse off broblem was fixed

  • X120E Touchpad inoperable after resuming from sleep

    hello friends I'm a happy X120E user and a tech [pc's, mac's, lans, etc] - I do all sorts of tasks with my x120e and its been great.  I recently "upgraded" my SSD so a fresh new install of Windows 7 was in order.  After updating everything I have a problem I did not experience previously at all - not once in 3 years of use.
    Upon resuming from sleep [and as far as I can remember this only occurs when resuming on battery], the touchpad/cursor is inoperable, frozen in the centered position, and I have found no way to 'wake' it.  I finally have to shutdown/restart to get things functioning again.  Keyboard works fine, but not touchpad or trackpoint [either/both].
    maddeningly, its not consistent in this. sometimes it works, sometimes it does not.
    I have seen the same issue with, and without, the supplied Lenovo Ultranav driver installed. 
    Question: in the X120E implementation, is the touchpad a PCI bus device or a USB device?  I see no power plan options [i.e. "Advanced" >"Allow this device to wake the computer"] available via Device properties. There are no pointer/mouse/touchpad options whatsoever under Power Plan Settings.
    Will Fn+F8 enable/disable the touchpad on this notebook?  or,... should it?

    No. Powering off and on again didn't work. My drive is a Seagate 750GB internal SATA drive in a Vantec NexStar-3 external enclosure. I don't think it is a driver issue. After the device removal error it won't mount on my PC or my Mac via FireWire or USB.
    What I need to know is if there is some way to connect to the drive and make it mount with other software, using some kind of keystroke during startup, or maybe through terminal or something. I can't even try to repair the drive because it won't show up in disk utility.

  • Windows explorer + other windows applications crashing regularly at resume from sleep and hibernate

    Good evening,
    I have a Thinkpad W510 (4319-29G) running Windows 7 Pro 64bit. The system is loaded with the latest software and drives from Lenovo including BIOS 6NET74WW (1.34), upgrade was done Dec 7th (windows update performed Dec 15th).
    The machine has
    - 8Gb RAM
    - nVidia Quadro FX880M, driver version is 8.17.12.5896, 7-9-2010 and video card BIOS is 70.16.5f.0.b
    - dual harddrives,
       - one Seagate Momentus XT 500Gb (ST95005620AS) FW rev SD23 in the main location with C: and some other partitions
       - one Hitatchi 320 Gb (HTS723232L9SA60) FW rev FC4ZC50B in the bay.
    - Intel Centrino Advanced-N 6200 AGN, driver version 13.3.0.24, 7-14-2010
    - Intel 82577LM Gigabit Network Connection, driver version 11.5.10.1030, 7-22-2010
    Recently I have experienced crashes of multiple windows components at resume from sleep and hibernate.
    It seems to happen when swithing location (from work to home) and thus switching from docking station with wired network connection to no dock and wireless network connection (dont know if this has any bearing but anyway).
    In the event viewer I typically have some 6-12 application errors logged. Sample output from event viewer is:
    Log Name: Application
    Source:Application Error
    EventID:1000
    Level:Error
    Logged:2010-12-15 20:30:02
    Task category100)
    Keywords: Classic
    Computer: xxxxxxx (my computername)
    Then for each application the following detailed data is written in event viewer in the general tab:
    #1
    Faulting application name: rundll32.exe_nview64.dll, version: 6.1.7600.16385, time stamp: 0x4a5bc9e0
    Faulting module name: nview64.dll, version: 6.14.10.13527, time stamp: 0x4c35752f
    Exception code: 0xc0000005
    Fault offset: 0x00000000000f0786
    Faulting process id: 0x115c
    Faulting application start time: 0x01cb9bd59882f1f6
    Faulting application path: C:\Windows\system32\rundll32.exe
    Faulting module path: C:\Program Files\NVIDIA Corporation\nView\nview64.dll
    Report Id: b606b17d-0881-11e0-be39-00a0c6000000
    #2
    Faulting application name: taskhost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
    Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
    Exception code: 0xc000041d
    Fault offset: 0x00000001800bb350
    Faulting process id: 0x10c0
    Faulting application start time: 0x01cb9bd5694caebe
    Faulting application path: C:\Windows\system32\taskhost.exe
    Faulting module path: nview64.dll
    Report Id: b6ae8cb2-0881-11e0-be39-00a0c6000000
    #3
    Faulting application name: sidebar.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc9e1
    Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
    Exception code: 0xc000041d
    Fault offset: 0x00000001800bb350
    Faulting process id: 0x6f0
    Faulting application start time: 0x01cb9bd5986a397a
    Faulting application path: C:\Program Files\Windows Sidebar\sidebar.exe
    Faulting module path: nview64.dll
    Report Id: b6bd0bd9-0881-11e0-be39-00a0c6000000
    #4
    Faulting application name: Explorer.EXE, version: 6.1.7600.16450, time stamp: 0x4aebab8d
    Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
    Exception code: 0xc000041d
    Fault offset: 0x0000000008c3b350
    Faulting process id: 0x1210
    Faulting application start time: 0x01cb9bd569d9ae8e
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: nview64.dll
    Report Id: b6d21ac7-0881-11e0-be39-00a0c6000000
    #5
    Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
    Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
    Exception code: 0xc000041d
    Fault offset: 0x00000001800ba570
    Faulting process id: 0x11c4
    Faulting application start time: 0x01cb9bd569aa125c
    Faulting application path: C:\Windows\system32\Dwm.exe
    Faulting module path: nview64.dll
    Report Id: b72bfbe8-0881-11e0-be39-00a0c6000000
    #6
    Faulting application name: rundll32.exe_PWMTR64V.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bc9e0
    Faulting module name: nview64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c35752f
    Exception code: 0xc000041d
    Fault offset: 0x00000001800bb350
    Faulting process id: 0x1450
    Faulting application start time: 0x01cb9bd59995023a
    Faulting application path: C:\Windows\system32\rundll32.exe
    Faulting module path: nview64.dll
    Report Id: b7e4521b-0881-11e0-be39-00a0c6000000
    It seems that a module "nview64.dll" is always the first application to crash. I suspect this has something with graphics to do.
    I dont know if this event triggers the following crashes or if it is so that the display is initialized before the other programs.
    After all crash diagnostic messages have been shown windows explorer restarts and also other applications restart but a lot of system tools in the system tray are gone so a cold start is needed to restore all tools again.
    I really would appreciate any help and suggestions how to fix this really annoying issue.
    Thanks, Anton

    I had a similar issue, as soon as a described even a little bit of it to warrenty support they sent someone to swap the board
    It seems thats the only fix, its been fine since 

  • Airport no longer works after resuming from sleep

    I got a new MacIntel a month or so ago, and it has always done this, under 10.4.4 and now 10.5.5
    When resuming from sleep, airport shows full strength for second, then the signal disappears. NOTHING in settings, reconnecting etc will get it to work again. (this is 'deep' sleep, not just the display turning off)
    If you restart (restart not shut down), then when it comes back, airport is just gone - even the menu bar indicator. The computer now thinks it has no airport installed at all. No matter how many times you restart, there is no longer any airport.
    If you shut down, wait a minute and restart, it works as normal.
    Since airport is the only way I connect to the network, and I don't want to waste electricity, this is unacceptable and clearly a flaw.
    I called tech support and they had me move airport to the top of the list, delete plists and other stuff, none of which made any difference. I'm thinking this is a low level system software fault, and I hope I don't have to take it back for a motherboard replacement.

    I also have this problem, although, not very often.
    I'm still running 10.4.4. This never happened with
    prior versions. Rebooting is the only way to
    correct the problem. Simply turning off Airport and
    turning it back on does not help.
    Thats interesting actually because I Never had any trouble on my G5 iMac of otherwise identical specification, on on intel. Hmm. I was thinking this was an intel issue.
    Wonder if its a hardware problem (though I suspect not).

  • I7 iMac with Bootcamp 3.1 and Windows7 64-bit won't resume from sleep

    When I try to resume from sleep, by clicking the magic mouse button, the screen comes up and I can move the mouse around but the bluetooth keyboard does not work and I can't launch any programs. Have to use the rear button to force a power off and restart.
    Is anyone able to resume from sleep okay and carry on using Windows 7? If so, any tips? Thanks in advance, very frustrating.

    I don't have an iMac, and it seems those have some design "issues" to say the least. I'd say yes, motherboard and/or firmware (UEFI or SMC, or both) could be buggy and at fault.
    Other than resetting SMC and running Apple Hardware Test, not sure what else or next to try.
    I've seen a number of BIOS updates out in the last months for my PC motherboards that have definitely improved sleep, S3, hibernation - EVGA, Gigabytes, and Intel - all X58 vs P55 (Lynnfield Core i5/7 LGA 1156) the iMac uses.
    http://anandtech.com/cpuchipsets/showdoc.aspx?i=3634
    http://en.wikipedia.org/wiki/IntelCorei5
    First I switched to Windows Vista/7, then I switched to build-my-own and custom parts. Love the looks of iMac, came close at one point, but I prefer the specs, options, and configure for my own needs in hard drives, graphics over cool factors.
    The iMac even in 2008 when it came with Penryn 64-bit processors never got 64-bit Vista/Boot Camp drivers, and that was why I didn't buy iMac back then, just lack of support I guess, and not seeing the market and need (for a good solid Windows desktop machine by Apple).

  • T440S OSD Brightness control failure after resume from Sleep

    Hi,
    I have owned a T440S since late 2013.
    Relevant Details:
    T440S
    Model : 20AQCTO1WW
    OS : Windows 7 professional (original installation by Lenovo)
    Latest Drivers installed as of June 2014 - including HotKey and Power Management
    HotKey ver : 8.30
    Power Managment : 6.65.1
    Since receiving this laptop, OSD birightness control has always failed to work, i.e. does not appear on the screen
    when using the Fn+F5/F6 key combination nor does it control actual screen brightness AFTER FIRST resuming from sleep
    mode.
    Sequence of steps that demonstrates the above symptom:
    1. OSD brightness works fine after reboot
    2. Putting the machine to sleep (I do not use hibernate) for a duration longer than a few minutes
    3. Open lid  the first time, hit Fn to resume machine
    4. Pressing Fn+F5/F6 key combo does not display the brightness slider nor does it control brightness
    5. Closing the lid and opening it again, causes OSD brightness slider to flash brifely and is now fully functional
        using Fn+F5/F6 keys
    Your tech department should easily be able to re-create this issue on any stock T440S/Win7pro machine, as
    I have seen others comment about this very issue across other T440/OS variants.
    This very same behavior has been there since the beginning.
    When is Lenovo going to FINALLY FIX IT ONCE AND FOR ALL?
    Thx,
    --Alon
    Solved!
    Go to Solution.

    Try this hotfix:
    https://support.microsoft.com/kb/2752407
    W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
    X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
    Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

  • Crashes when resuming from sleep.

    I just bought my macbook 6 days ago. Occasionally, upon opening the macbook it will not be resuming from sleep but the OS will actually be rebooting itself. This happens very infrequently. In the 6 days I've been using it (and I've been using it a lot) I've only noticed this happening twice. Though this is my first Mac, I am by no means a computer novice and I'm sure I'm not shutting down the OS, especially since I didn't have to press the power button to turn it back on. Is this something I should be concerned about? Or is it just one of those rare quirks I have to live with? Any input is appreciated. Thanks!
    MacBook   Mac OS X (10.4.8)   Custom-Built PC (WinXP)
    MacBook   Mac OS X (10.4.8)   2.0Ghz Core 2 duo, OSX 10.4.8, 80GB HD

    It really shouldn't reeboot from scratch when just waking from sleep!
    The only time it would, is if the battery power drained completely before re-charge (even while sleeping), or if it was actually shut down purposely/accidently.
    Quick question: assume you are just closing your macbook to put to sleep? Not pressing pressing power button or selcting sleep in the finder? Although you can use both the latter, they do offer opportunity to shut down 'accidently'.
    Only other though; Check the following: "System Preferences"/Energy Saver/Sleep-Schedule (=button bottom right) , here you can set scheduled start up and wake options... by default they would not be activated.
    If all above is as suggested then I suspect a problem.

  • Resume From Sleep Login UI Problem

    I'll keep this short and sharp.
    Previously, when I would resume my mac from sleep, it would make the screen look similar to the normal login screen. With things spread out and nicly formatted. With the menu bar showing the essentials like network, time, and battery in the upper left.
    Now, when I resume from sleep a small window appears telling me I need to enter my password to "unlock the screen".
    What would cause this? Any applications that I might have installed without being aware?
    I have restarted 2/3 times, and I will continue to do so for a short while more, in the hope that it can help me.
    Oh. This is after resuming from sleep only. When I get to the normal login screen after turning it on, it's fine, and just as normal.
    Thanks in advance!
    ~Before (yesterday)
    ~After (today) after multiple restarts

    Hi buddy,
    Its really hard to say something about this I can only say that I cant notice this problem on my Windows installation.
    By the way: Do you use the Windows version from Toshiba or your own Windows installation?
    Theoretically it could be a problem of your Windows installation or HDD itself Are you able to test another HDD or Windows installation that you can make sure its not a software problem?

  • Resume from sleep causes total Interent connectivity loss

    This just started happening about a week ago. I used to be able to close the lid on my iBook, open it later and resume working online normally. Now when I open the lid or resume from sleep mode, the airport shows that it is connected, but I have no Internet access (server not found messages). I've tried turning the Airport off and on, but this doesn't seem to fix the issue. I have to totally restart the iBook to regain any Internet connectivity. Any ideas if this is due to a recent update? Anyone else having this problem? The most recent update I remember install was one for MS Office 2004, but it's not just affecting Entourage, no Interent apps will connect after sleeping.

    Hi Kib,
    I've had the same exact problem intermittently for the entire time i've owned my ibook (1 year). The problem was intermittent enough that I never took it too seriously. But, just this morning it would appear my internet connection is permanently gone. No amount of restarting or renewing the DHCP will work. And, as in your case, airport indicates that it is "connected". Seems like a degenerative condition. I'm going to call apple and get some help. I just got apple care and I'm going to take full advantage of it, especially after all the trouble i had with my ibook display.

  • T61p: Vista - BSOD when resume from sleep / hibernate, casued by classpnp.sys

    I've got a T61p (Type: 6457) with preinstalled Vista, later upgraded with SP1. Everything worked like a charm, untill a week or so, when the BSOD appeared when either resuming from sleep or hibernation.
    I've checked the minidump, and it seems as the classpnp.sys is causing the trouble, however, I've yet not found a good solution to fix the problem (I'm close to doing a restore to factory install, but would like to avoid if possible
    Anyone?
    edit: typos
    Message Edited by birwi on 04-12-2009 06:38 PM

    There's an issue with your GPU, video driver or both...try running this for a while:
    http://freestone-group.com/video-card-stability-te​st.htm
    If there's an underlying problem, this test will reveal it. And when I say "a while" I mean for an hour or more...
    Please be advised that if your GPU is on its way out (I've had them fail on T60p due to VRAM corruption) this test might just finish it and push it over the edge. Proceed at your own risk.
    Good luck.
    Cheers,
    George
    In daily use: R60F, R500F, T61, T410
    Collecting dust: T60
    Enjoying retirement: A31p, T42p,
    Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
    Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

  • T60 Type 2623 Blue Screen on Resume from Sleep Mode problem solved - XP Pro

    I hope that this post ends some frustrations for some people.
    I hope that IBM deals with this issue by getting ATI to fix the video driver issue.
    After three months of tracking down blue screens when resuming from Sleep Mode and some lockups while working, I have identified the problem on my T60 Type 2623 running Windows XP-Pro and all service packs and updates.  The Sleep Mode resume issues were intermittant and it would be fine for a day or two and then reboot on Resume or reboot every time I used Resume for a while.  For months the Blue Screen would reboot and attempt to send the message to Microsoft using the logs, but the logs were always corrupted.  I disabled every driver that I could and the problem continued for months.
    The problem solution came about when I decided to try my Rhapsody Music account after many months of not using it.  I kept getting a message about DRM (Digital Right Management) being disabled and Rhapsody software could not self-fix this.  So I finally called Rhapsody and they spent over an hour with me trying to get Rhapsody to work.  The support person asked me about my computer and I noted that it was an IBM T60.  He then asked about my Video Card and I responded that it was an ATI Mobility Radeon X1300.  After a few minutes on hold he asked about my driver version which was 8.442.3-080103a1-057754C the set from January 31, 2008.  He noted that there is a known problem wit the 8.4 driver and it interferes with DRM.  He had me go to control panel Settings and Hardware and then roll-back the driver to the prior version.
    After a reboot, the DRM issue was solved and I soon discovered that my resume from Sleep mode no longer crashed.  In fact it has been fine and crash free for over a month now.  I have noted that the older driver can sometimes resize my screen to something like 600 X 800 if I close the lid under certain circumstances, but that is just a function key reset to get my normal desktop resolution back.  At least it is not a blue screen reboot with a corrupted log file.
    Message Edited by retro74 on 07-05-2008 08:50 AM
    Solved!
    Go to Solution.

    Unfortunately I could not fix the problem so I wiped my system and loaded all new drivers before I found this posting.
    Is there a way to get the old ATI driver that works? The only one available on the ATI and Lenovo website is the latest one with the problem. I agree with you David, Lenovo should have fixed this problem already with ATI.
    John

Maybe you are looking for