greg1
asked on
can't logon after resuming from hibernate
To start my PC or to resume from hibernation, I usually tap the spacebar on my keyboard.
No apparent starting/running issues starting from a cold boot or if NOT using the hibernate feature.
However, if resuming from hibernate, I am often unable to enter the password at the logon screen (The keyboard doesn't respond to attempts to type the password, but the mouse works).
After hitting the reset button on the box, the PC occasionaly has some issue, then seems to run fine after scandisk or another reboot process.
In the interm, I have disabled hibernation, but would like to use it for power savings and convenience.
My system:
512mb pc133
winxp pro sp1
p3 500
40gb maxtor hdd (primary master, o/s located here)
10gb maxtor hdd (primary slave,pagefile located here)
BIOS Version: Award Software, Inc. ASUS P3B-F ACPI BIOS Revision 1006
BTW: I'm triple booting winxp/2k/me, all on separate partitions, but i use winxp 99.9% of the time.
Any ideas?
No apparent starting/running issues starting from a cold boot or if NOT using the hibernate feature.
However, if resuming from hibernate, I am often unable to enter the password at the logon screen (The keyboard doesn't respond to attempts to type the password, but the mouse works).
After hitting the reset button on the box, the PC occasionaly has some issue, then seems to run fine after scandisk or another reboot process.
In the interm, I have disabled hibernation, but would like to use it for power savings and convenience.
My system:
512mb pc133
winxp pro sp1
p3 500
40gb maxtor hdd (primary master, o/s located here)
10gb maxtor hdd (primary slave,pagefile located here)
BIOS Version: Award Software, Inc. ASUS P3B-F ACPI BIOS Revision 1006
BTW: I'm triple booting winxp/2k/me, all on separate partitions, but i use winxp 99.9% of the time.
Any ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You could fiddle with the power management settings You might be set to ACPI mode. They say this isn't always the best for desktops. Maybe your motherboard is not fully compatible with this. I know my asus was not. You could try switching to APM from ACPI in the bios. I guess this would only be an answer if you had the same problem before sp1.
Hibernation is really for laptops, cant think of any reason to use it on a desktop.
Mike
Hibernation is really for laptops, cant think of any reason to use it on a desktop.
Mike
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Does standby work?
Mike
Mike
ASKER
Thx for all the comments...
I'm having a problem only when running winxp pro sp1, not win2k.
I'm not using a usb keyboard.
The machine is a desktop.
Standby works, (and hibernate usually does too).
I like the convenience and power savings provided by the hibernate feature, even on a desktop.
I'm having a problem only when running winxp pro sp1, not win2k.
I'm not using a usb keyboard.
The machine is a desktop.
Standby works, (and hibernate usually does too).
I like the convenience and power savings provided by the hibernate feature, even on a desktop.
ASKER
Thx for all the comments...
I'm having a problem only when running winxp pro sp1, not win2k.
I'm not using a usb keyboard.
The machine is a desktop.
Standby works, (and hibernate usually does too).
I like the convenience and power savings provided by the hibernate feature, even on a desktop.
I'm having a problem only when running winxp pro sp1, not win2k.
I'm not using a usb keyboard.
The machine is a desktop.
Standby works, (and hibernate usually does too).
I like the convenience and power savings provided by the hibernate feature, even on a desktop.
ASKER
Thx for all the comments...
I'm having a problem only when running winxp pro sp1, not win2k.
I'm not using a usb keyboard.
The machine is a desktop.
Standby works, (and hibernate usually does too).
I like the convenience and power savings provided by the hibernate feature, even on a desktop.
I'm having a problem only when running winxp pro sp1, not win2k.
I'm not using a usb keyboard.
The machine is a desktop.
Standby works, (and hibernate usually does too).
I like the convenience and power savings provided by the hibernate feature, even on a desktop.
greg1 are pressing refresh? click the "reload this screen" in the upper lefthand corner.
I had the same problem. It would not work in xp but it worked fine in 98.
Maybe there are some updated drivers for xp on your mothboard or computer manufacturer's site.
Mike
I had the same problem. It would not work in xp but it worked fine in 98.
Maybe there are some updated drivers for xp on your mothboard or computer manufacturer's site.
Mike
if the logon screen is necesary then you should probably look for an updated as is said above, however it is possible to tell the computer to resume windows on the desktop instead of the logon screen. This is done in the hibernate properties.
hope this helps a little
hope this helps a little
But it seems like a keyboard problem, and not a logon problem. All I know is that my asus motherboard and windows xp did not mix when it came to power management. I never found a way to fix it.
ASKER
puff 019, If you mean disabling the logon screen after resume by:
Start > Settings > Control Panel > Power Options > Advanced, then uncheck the "Prompt for password when computer resumes from standby" box.
This will of course resume to the desktop. However, this is not an acceptable solution, as I need the logon for security reasons.
--------------------------
Regarding the ACPI comments made by Gallant uk & reduakm...
This is what MS has to say:
"ACPI overview
Advanced Configuration and Power Interface (ACPI) is an open industry specification that defines a flexible and extensible hardware interface for the system board. Software designers use this specification to integrate power management features throughout a computer system, including hardware, the operating system, and application software. This integration enables Windows to determine which applications are active and handle all of the power management resources for computer subsystems and peripherals.
ACPI enables the operating system to direct power management on a wide range of mobile, desktop and server computers, and peripherals.
ACPI is the foundation for the OnNow industry initiative that allows system manufacturers to deliver computers that start at the touch of a key on a keyboard.
ACPI design is essential to take full advantage of power management and Plug and Play in Windows. If you are not sure whether your computer is ACPI-compliant, check your manufacturer's documentation. To change power settings that take advantage of ACPI, use Power Options in Control Panel.
During Windows Setup, ACPI is installed only if all components present during Setup support power management. Some components, especially legacy components, do not support power management and can cause erratic behavior with Advanced Power Management (APM), or may prevent ACPI from being installed. Examples of such components are Industry Standard Architecture (ISA) components and an out-of-date BIOS."
Since this is an intermitant issue for me (it usually resumes with the keyboard functioning), I wonder if the above info applies to this situation...and what is meant by "erratic behavior"...come to think of it I believe this machine has a second printer port in an isa slot.
I think I'll pull that card out of the isa slot, and see if the problem reoccurs.
Start > Settings > Control Panel > Power Options > Advanced, then uncheck the "Prompt for password when computer resumes from standby" box.
This will of course resume to the desktop. However, this is not an acceptable solution, as I need the logon for security reasons.
--------------------------
Regarding the ACPI comments made by Gallant uk & reduakm...
This is what MS has to say:
"ACPI overview
Advanced Configuration and Power Interface (ACPI) is an open industry specification that defines a flexible and extensible hardware interface for the system board. Software designers use this specification to integrate power management features throughout a computer system, including hardware, the operating system, and application software. This integration enables Windows to determine which applications are active and handle all of the power management resources for computer subsystems and peripherals.
ACPI enables the operating system to direct power management on a wide range of mobile, desktop and server computers, and peripherals.
ACPI is the foundation for the OnNow industry initiative that allows system manufacturers to deliver computers that start at the touch of a key on a keyboard.
ACPI design is essential to take full advantage of power management and Plug and Play in Windows. If you are not sure whether your computer is ACPI-compliant, check your manufacturer's documentation. To change power settings that take advantage of ACPI, use Power Options in Control Panel.
During Windows Setup, ACPI is installed only if all components present during Setup support power management. Some components, especially legacy components, do not support power management and can cause erratic behavior with Advanced Power Management (APM), or may prevent ACPI from being installed. Examples of such components are Industry Standard Architecture (ISA) components and an out-of-date BIOS."
Since this is an intermitant issue for me (it usually resumes with the keyboard functioning), I wonder if the above info applies to this situation...and what is meant by "erratic behavior"...come to think of it I believe this machine has a second printer port in an isa slot.
I think I'll pull that card out of the isa slot, and see if the problem reoccurs.
I think it's wise to reiterate one of the points I made earlier. Hibernate does not require either APM or ACPI to work.
A search on the internet also reveals that the key mentioned in the error log is related to the defragmentation utility and so probably not related to this problem.
I have also discovered this patch. It may help; the fault it cures is similar to yours.
http://www.microsoft.com/downloads/release.asp?ReleaseID=37942&area=search&ordinal=22
Also if you haven't already I'd like to suggest you go to microsoft Windows Update, and download the latest critical fixes.
A search on the internet also reveals that the key mentioned in the error log is related to the defragmentation utility and so probably not related to this problem.
I have also discovered this patch. It may help; the fault it cures is similar to yours.
http://www.microsoft.com/downloads/release.asp?ReleaseID=37942&area=search&ordinal=22
Also if you haven't already I'd like to suggest you go to microsoft Windows Update, and download the latest critical fixes.
ASKER
Gallant uk, thanks for your response...
I'm not clear on what you are alluding to regarding hibernate not requiring APM or ACPI. Please elaborate further, but read the following first.
The issue seems to be: The machine resumes from hibernate successfully, but occasionally after resuming, the keyboard does not respond to user input. So possibly the issue is related to APM or ACPI (maybe the legacy/isa problem is happening)
Thanks for the info about the error log entry.
According to MS the patch that you refer to addresses the following issue:
"The Computer Cannot Enter Standby or Hibernate If a Direct3D-Based Screen Saver Is Running"
Also according to MS, the patch is included in sp1 for winxp, which I have previously applied. The link below lists fixes included in sp1 for winxp.
http://support.microsoft.com/default.aspx?scid=/support/ServicePacks/Windows/XP/SP1FixList.asp
I'm not clear on what you are alluding to regarding hibernate not requiring APM or ACPI. Please elaborate further, but read the following first.
The issue seems to be: The machine resumes from hibernate successfully, but occasionally after resuming, the keyboard does not respond to user input. So possibly the issue is related to APM or ACPI (maybe the legacy/isa problem is happening)
Thanks for the info about the error log entry.
According to MS the patch that you refer to addresses the following issue:
"The Computer Cannot Enter Standby or Hibernate If a Direct3D-Based Screen Saver Is Running"
Also according to MS, the patch is included in sp1 for winxp, which I have previously applied. The link below lists fixes included in sp1 for winxp.
http://support.microsoft.com/default.aspx?scid=/support/ServicePacks/Windows/XP/SP1FixList.asp
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
greg1:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thx for all the comments
ASKER
the solution...new mb & cpu
ASKER
from the event log
ERROR:
The server {80EE4901-33A8-11D1-A213-0
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
WARNING:
The server {80EE4901-33A8-11D1-A213-0
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
--------------------------
i first noticed the problem a couple of months ago, before sp1.