Windows 10 Resume from Sleep Very Slow

Completed the upgrade to Windows 10. Machine is now very slow to wake from sleep. Full resume takes about 2 minutes. When resume starts, touchpad lights up but screen stays black. It seems that the machine is going through some type of process that takes long. I noticed that the graphics drivers for AMD were updated. I tried to reinstall the old AMD drivers but the install failed. Could the graphics drivers be causing the problem? What other drivers that might have been updated could cause the problem?

Later news! The problem driver was the AMD Radeon 6700M series ver 15.200.1062.1003. The slow resume from sleep and similar delay in startup was resolved by disabling ULPS. See this URL in the AMD community forum https://community.amd.com/thread/184727

Similar Messages

Slow resume from sleep X121e

Hi! When I haven't used my x121e for a couple of hours it resumes from sleep very slowly. Is it anything I can do to make it resume faster from sleep? Maybe a bios setting?
After a few hours the thinkpad logo appears on the screen and after that it says "resuming winows". Is there any way to disable this and make the computer always wake fast?

This is really an annoying issue and waste the lot of time.
Kindly update the BIOS and then check the issue should get resolve.
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/8quj08us.exe
Best Regards,
Tanuj
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!

X220 very slow reconnecting to WiFi when resuming from sleep

So my X220 with the Intel 6205 card is having issues reconnecting to WiFi when resuming from sleep or hibernation. It takes about a minute for it to do so, though occasionally it will reconnect right away. Maybe 1 out of 20. When doing a cold boot or restart, it connects immediately upon the desktop showing up.
This was not always the case, in fact when I first got my X220 in June, I have not had this issue.... In fact, I don't know when it started happening, but it was maybe a couple months ago. I just thought it was my old router going bad. Well I got a new router, and it still happens. I have the latest Intel WiFi drivers from Lenovo, and I even tried downgrading to the previous driver from Intel's site. Still the same problem. I tried setting a default profile in access connections, and that does not help. In fact, it behaves the same way if I totally uninstall access connections as well. In fact I tried this on three different brand routers, and I can reproduce it on all of them (Asus, Netgear & TP-Link) so I think this is not a router issue. Other devices in the house reconnect right away with no issues (iPhone 4, PS3, Mac desktop, Dell laptop).
I currently have BIOS 1.24, but this was happening with 1.21 and 1.23 as well. My X220 originally came with 1.16, and I haven't updated it until 1.21. Unfortunately I don't remember that far back, if the problem started occuring then.
There was a brief discussion about this in another thread, but it went nowhere so perhaps this will get more attention. At least one other user reported the same issue.
Here's a clip of exactly what happens. When i press the button or open the lid from sleep, the windows wifi icon will start spinning for a few seconds, then turn into an X. then only about a minute later, does it quickly connect to the wifi and I have full signal. Manually clicking on the icon and selecting the access point does not speed up the process. It will only connect when it wants to, about a minute after resuming from sleep/hibernation.
http://youtu.be/dmboeA7HBgg
| X220 i7-2620M | 12.5" IPS | Intel 520 Series 180GB Main SSD | Mushkin 120GB mSATA SSD | 8GB RAM | Intel 6205 WiFi | BT | Win7 Pro 64 SP1 |
Solved!
Go to Solution.

Normally when a laptop running windows tries to connect to a network, it may also seek to identify certain components on the network, for example, asking the router "Who are you?". In your case, maybe the config are corrupted because the network address entries are messed up. Queries send out to the network come back with no replies, and the computer waited for the default time till timeout and it gives up.
Try this one at a time, reboot, or try all at once and reboot
TCP/IP stack repair options for use with Vista or 7.
Start, Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log
Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log
Reboot the machine.

Wakes from sleep very slowly, starting to flicker sometimes, very slow to load websites

wakes from sleep very slowly, screen starting to flicker sometimes, very slow to load. i use microsoft email and just did an update. did this affect my system? My msn mail is awkward..... today, beeping sounds starting at random. ???

i did a restore off the Toshiba discs i had made, and again, it ran fine in the beginning, then all of sudden a month or two, and it started being slow again.
I expect something you installed or updated caused the trouble. Best strategy is to identify the culprit.
I would restore from the Toshiba discs again. Then carefully add things one-at-a-time, rebooting, and checking things out after each.
Be sure you create a restore point prior to adding hardware or installing software. Microsoft programs like Windows Update will automatically make one before installing anything.
-Jerry

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

Slow LAN Networking Speeds after Resuming from Sleep

I use my mac mini as a HTPC running Plex. I have it connected to my Windows media server with 802.11n. Works fine but sometimes after resuming from sleep the network speed drops off to an unacceptable level (from 72 Mb/sec to 5 Mb/sec). Disconnecting and reconnecting doesn't help. Switching to G doesn't help. Only restarting the mini restores the connection to full speed.
None of my Windows clients on the same network have any troubles.
Thoughts?

Looks like Plex might be causing the problem. I always have plex running and it appears as though if Plex makes a request for a file on the share before OS X is done re-mounting it after sleep, it kills the whole process.
Shouldn't the OS be robust enough to handle a situation like this?

T540p problem with resume from sleep Windows 10 technical preview

On Windows 10 technical preview the resume from sleep problem shows up again. With 8.1 I solved it with drivers.
I'm running lattest BIOS and Intel and nVidia drivers.
Also on Windows 10 the fingerprint software causes endless loop as logon screen cannot be displayed because of fingerprint software crash.
I know this is technical preview but I'd like to let you know of problems so you fix them by release time.

so please help me how to roll back to windows 8.1
http://windows.microsoft.com/en-us/windows/preview-backup-restore

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

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.

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!

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.

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

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?

Windows 10 Resume from Sleep Very Slow

Similar Messages

Maybe you are looking for