Screen is not working after resuming from sleep mode

Hello,
i got a problem with my ideapad u330 touch, after i got out of the sleep mode my screen will not come on, so I need to switch it off and back on again then it works fine.
I recently upgraded to win 8.1, i don't know if it has something to do with this, but before it works fine.
Thank you very much

hi McGuinness,
Are you able to recreate the issue if you boot in Safe Mode?
Things that you can try:
1. Press the Windows logo key‌ +R and type devmgmt.msc. On the Device Manager, navigate to the Display Adapter (right click > choose Properties) and on the Driver Tab, check if the Rollback Driver is clickable to restore the previous display driver.
2. Navigate to the Control Panel > Programs and uninstall the Intel display driver and reboot. Navigate to the D:\Drivers folder and locate the Intel Display driver installer (D:\Drivers\VGA\Intel) or download and run the file below to re-install the display driver.
Intel Video Driver for 64-bit Windows
Version 9.18.10.3165
After installing. Try to put the computer to sleep and observe (if the power button is blinking, this indicates that the unit is in sleep mode).
Regards
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!

Similar Messages

Fingerprint reader not working after resuming from sleep

I kind of mentioned this problem in a previous post and was directed here http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67245 which is a patch that could possibly fix it.This patch didn't work. What is happening is when my laptop comes back from sleep either the fingerprint reader is unresponsive, it says "waiting..." at the top of the screen instead of the normal scan message and is unresponsive, or in some cases when I click other credentials it shows a third account (first is my account, second is the reader account,and the third is a stop sign thing that says the fingerprint reader isn't attached). When I sign in with my normal password and try to go to the fingerprint software it pops up a little window that is labeled Lenovo Fingerprint 2.0 and the message is "Pleae wait...".
Other then returning from sleep the fingerprint reader has been working fine. Any suggestions are greatly appreciated, thanks.
Edited to add patch link.
Message Edited by Skurvy_Pirate on 09-22-2008 07:40 PM
Solved!
Go to Solution.

Well I got it working again but I'm not exactly sure how. I will go over what I went through so you guys can get an idea and possibly fix it. To start off I talked to MS support and I worked with them for a really long time. They tried intstalling different drivers (other then AuthenTec) and anytime we did that it would say "Fingerprint reader not available" at the login. They tried changing the power settings and which devices could wake up my computer and that had no effect either. I called Lenovo and they basically just told me to download the software that was already on the computer and change the option to have it wake up the computer, which doesn't exist. They were very unhelpful.
What eventualy got it working (and it's been working so far), is uninstalling the driver and software. Then reinstalling it all and installing the patch linked above. The first time I installed it I just double clicked it and went through the installation process. But you need to go into the folder it installs it into (C:\DRIVERS\VISTA\FPIRPON\) and double click FPIRPOn.reg which will add the fix to the registry. On top of this I also went into Device Manager and unchecked the box that allows the computer to turn of the fingerprint reader under Properties->Power Management for the device. The last thing I did was do a registry edit to force the USB to reset when waking from sleep. I found the registry edit here http://support.microsoft.com/kb/928631/en-us.
So I am pretty sure it was the patch that fixed it when I correctly installed it because I had tried both the power management thing to keep it from getting turned off AND the registry edit and it didn't work. I also thing that Vista SP1 fixes what the registry edit does, but I tried it anyways because I was desperate haha. I'm going to undo the registry edit and power management thing one at a time and see if it still works. If it doesn't keep working I'm guessing it's a hardware problem and going to call Lenovo to get it fixed.
Anyone who is having this problem I would suggest they try the patch in the link that I first posted (http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67245)and follow the installation instructions carefully. Good luck!

Wireless not working after resume from sleep, T440s

Some times when I resume laptop from SLEEP, wireless are not working...
Solved!
Go to Solution.

Try new drivers. Helped me a lot.
http://ns3369637.ovh.net/index.php/outils/Drivers/Intel/Wlan/PROSet-Wireless-WiFi-Software/Intel-PRO...

My zero Key isn't working after waking from sleep mode. This is a real problem for me because my password contains a zero

My zero Key isn't working after waking from sleep mode. This is a real problem for me because my password contains a zero. I don't recall spilling anything or jamming it just that it worked before I closed the computer and wasn't after I woke it up.
I would like to fix the key but if that's not possible right away , Is there a way to reset my password without being able to type with a key thats in it?

Start by swapping the keyboard. You don't need to spend a fortune, and handy to have spare. USB cables can be bad even new.
When I had some problems Apple wanted to blame the mouse, keyboard, cable, but in the end I found
A. run Disk Warrior
B. Corrupt pref or conflict with version of Hardware Monitor and other background tasks

T61 - WWAN does not connect when resuming from sleep mode

Hi.
I have a T61 with integrated WWAN, which works perfectly - except I use sleep mode a lot, and when i resume from sleep mode, WWAN doesn't connect, I always get the same error - IP configuration failed. If I restart my OS, WWAN works normally again.
So far i have tried on Windows XP, Vista 32, Vista 64 and Windows 7 32 bit - always the same!
I connect via Access Connections, maybe there is a known issue?
Thank you, B

This bugs me as well. With the new Verizon software I just installed, it says "Adapter Disabled" when I resume from sleep.
I suspect a driver bug that needs to be adressed.
I use Vista Business 32bit, but had the same problem with XP.
Don Mannino

High CPU load after resuming from sleep mode

When my laptop resumes from sleep mode, LabVIEW 2012 starts to generate a very high and always constant CPU load (25%) without any VI running. I need to close all front panels to get back to the usual <1% CPU load level.
This behaviour spoils my carbon footprint and frequently eats up my battery. Any ideas what is causing this ?
Thank you,
Dirk

I'm guessing your issue may be related to this:
http://forums.ni.com/t5/LabVIEW/Why-is-using-100-of-a-CPU-1-out-of-8-when-it-does-nothing/m-p/242745...
Dirk@LV wrote:
This behaviour spoils my carbon footprint and frequently eats up my battery.
Thank you,
Dirk
Sorry about your carbon footprint, NI has a lot to answer!
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

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

Touchpad permanently not working after resuming from suspend

I lost touchpad and trackpoint functionality after resuming from suspend on my ThinkPad E530 (3259CTO).
Even after a complete power off (with the battery removed), the touchpad is detected but doesn't send any event, and the trackpoint is not detected.
In Windows, in the UltraNav control panel, the touchpad is marked as enabled and cannot be disabled, the trackpoint is grayed.
In Linux, I can see the difference is kernel traces when the driver is loaded.
Before : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00
Now : psmouse serio1: synaptics: Touchpad model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x0/0x0
After looking at https://gerrit.chromium.org/gerrit/#/c/31105/ and Synaptics public documentation, I was able to get more information : the device status register (F01_RMI_Data0) is 0x45, which means the touchpad is in flash programming mode since there is a firmware CRC failure.
It looks like http://code.google.com/p/chromium-os/issues/detail?id=24298, so it's probably not a Lenovo specific problem, but a bug in Synaptics firmware.
Can Lenovo provide the firmware to flash like http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/X220-Touchpad-jumpy-response-when-used-with-90... which would hopefully make my touchpad working again ?
The original firmware should work, but an updated one would be better, if it avoids losing the touchpad again later.

I don't know why, but this made me think of the episode of the simpsons when home tries to get over 300 pounds so he can work from home. When he tries to dial the phone he hist all the buttons and gets a recording that says "We're sorry, you're fingers are too fat. To obtain a special dialing wand, please mash the keypad now."
BTW, sorry I can't help... but at least I am entertained easily.

Keyboard & Mouse Not Working on Resume From Sleep

About 1/10 of the time when I resume from sleep my keyboard and mouse do not work. They wake the computer (a 27" iMac) but do not work any longer past that, requiring me to hard reboot my computer (holding the power button to turn off then rebooting).
I have no issues using my keyboard and mouse, both bluetooth, at all. When this happens, even hooking up an external keyboard does me no good as it also does not work. Sleeping and reawakening does no good either.
Anyone have any ideas? So far nothing seems amiss when it comes to my configuration or hardware. Thanks in advance!

I have experienced the same problem which affects a 3rd party USB mouse and my wireless trackpad. Both may be unresponsive when the computer (late 2009 21.5" iMac) wakes. When it happens both devices are affected, never just one of them.
I don't need to reboot to fix the problem. The mouse responds by disconecting and re-connecting. The trackpad reconnects by holding its power button for a few seconds.
The problem does not affect my wireless keyboard.
No clues on the Console. Sorry I can't be more help.

Can't get yosemite to working after waking from sleep mode

I just installed Yosemite to my Mac Mini. When the computer goers to sleep for more then 30 seconds I can wake the computer but then after i see the desktop I can't do anything on the computer every click i make does not respond and I have to force the computer to shut down and I have to reboot every time my computer goes to sleep.

I have the exact same issue for the first time after installing Yosemite. On resume from sleep, I can see the desktop, and can move the cursor with the mouse, but clicking on icons, etc. does nothing, and the keyboard does nothing. A cold boot works fine. This is a Mac Mini bought in the Summer of 2014. I run no unusual software. I have eliminated all log in items in Preferences/Accounts, reset the NPRAM, have no peripherals (other than standard Apple mini mouse and wireless keyboard), and have shutdown and unplugged to reset. It makes no difference whether a password is required or not - once it goes to sleep, this is the result, and only a forced shut-down by holding the power button and a cold boot give me control back. This problem does not appear if it merely goes into screensaver mode - which I invoke with a hot corner.

Why doesn't my built in display re-initialize after resuming from sleep mode?

Hi,
I have a MacBook Pro (2.53 GHz Intel Core 2 Duo, 4 GB RAM) which I purchased a few years ago. I always have a secondary display monitor plugged in.
When I bought this system, it came with Snow Leopard and I recently upgraded to Lion. That's when this issue began:
If I physically fold the screen down and put the MacBook to sleep mode that way, often times when I resume my secondary display will return but my primary built in display will not - it just remains black. In some cases this creates a serious problem because my menu bar / dock are still on the main display and so I have no dock.
I notice the problem has not occurred if I put the unit to sleep using the Sleep command... but sometimes I forget.
I am wondering if anyone else is having this type of issue, and if there is a way to solve the issue? Is it possible this is a bug?
Thanks,
Steve

etresoft wrote:
It is definitely not a Leopard bug because it has been happening on every portable Mac I've ever had.
I don't agree. I had no problems at all with my MacBook Pro running Tiger. I initially did an upgrade from Tiger to Leopard and when the problems started I assumed it was a problem with the upgrade. I then completely erased and did a clean install of Leopard. The problem has actually gotten worse since I did the clean re-install.
etresoft wrote:
Just close the screen, wait for it to go back to sleep, then open it again. It will probably be fine.
As I mentioned in my opening post, I've gone through that song and dance more times than I can count. I've closed it, waited for as much as an hour, opened it back up...same problem. I've hard powered it down, closed it, disconnected the AC adapter, removed the battery, opened it, held down the power button for 15 seconds, re-installed the battery, reconnected the AC adapter, pushed the power button, and the display will still be dark. It's sometimes taken as many as 5 or 6 iterations of that process before it will finally reset whatever problem it was having and boot normally with a functioning display.

Apple TV needs Restart for Airplay especially after resuming from Sleep Mode

1. I always have to restart my Apple TV for Airplay when I resume it from Sleep Mode. Neither my MAC not my PC nor my iPhone/iPad can connect to Airplay if it's not retsarted. I did a complete Factory Reset of Apple TV thinking it would be the best way of troubleshooting but in vein. Any help/suggestion/tips from anybody please?
2. Also - Does Apple TV needs internet always for Airplay? I guess that should work on the LAN even if there is no internet connectivity, Correct?
Regards,

Hey loftysub,
I'd check out the following article, it should be able to help you out:
Troubleshooting AirPlay and AirPlay Mirroring
http://support.apple.com/kb/TS4215
Cheers,
David

External UCube speakers don't work after awakening from sleep mode since 10.7.5 upgrade

Ever since I upgraded to 10.7.5 when I wake my computer from sleep mode...my external UCube speakers don't work unless I unplug them and plug them back in. I've already tried resetting the SMC. It recognizes and shows the speakers in the sound preferences...but no sound unless I reconnect the usb cable. Worked fine in 10.7.4
Any ideas? Its ridiculous all the audio problems being reported.

I have a mac mini (A1283) with OS 10.7.4. Upon upgrading to 10.7.5 it did not start up again. Instead, the light was on and the hard drive did not start up. The light on the connected USB mouse was not lit.
My solution:
Cold start with Command-v pressed.
This should start Verbose mode (see http://support.apple.com/kb/HT1492 ).
What happened on my mac mini was that the grey startup screen with the Apple logo appeared for a long while before the login screen came.
Maybe Cmd-v set open firmware params and fixed some corruption.
Anyway: my mac mini works again.

[SOLVED] Sound (snd_hda_intel) not working after resume from suspend

Using the latest kernel 2.6.30.4, On HP2133, whenever I get back from resume, sound is not working.
Running the following brings back the sound, but that is obviously a hack:
fuser -k /dev/snd/*
rmmod snd_hda_intel
modprobe snd_hda_intel
/etc/rc.d/alsa start
I have on my /etc/modprobe/50-sound.conf:
options snd-hda-intel model=laptop
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
Here's the exact hardware specification:
# lspci -nnv|grep Audio
80:01.0 Audio device [0403]: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) [1106:3288] (rev 10)
Any idea where to look for this?
Last edited by yhager (2009-08-21 16:54:00)

[SOLVED]
I downgraded to kernel 2.6.29 and the problem is gone.
Note: I also had X VT problems with 2.6.30.4 (xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call). Those were solved too by downgrading to 2.6.29.

USB devices not working after wake from sleep on WinXP!!! HELP PLEASE!

I would like to put my windows xp to sleep whenever I leave the macbook pro for fear of overheating too much when I'm not using it.
The only problem is that I can't use any more USB devices if I plug them in once I wake it from sleep.
Like my mouse for example, I'm using a laser mouse with a usb plugin but it doesn't respond once I try to use it after WinXP on wake....
Experiencing a ton of wake problems lately...
Sleep is important for a MBP....I hope...

Welcome to Windows. Some devices do not like to be put to sleep in Windows.
There could be driver updates or hot fixes from MS to fix these.
A very proven method (though not for battery life) is to instruct the devices not to go to sleep when the system goes to sleep. You can do this via the device manager in the control panel.
Its not a gracious solution but it will do what you want it to do.

Screen is not working after resuming from sleep mode

Similar Messages

Maybe you are looking for