New
#1
wake behavior is erratic
could I please piggyback here; this is an issue I thought had gone away many Windows7 updates ago but apparently not. I have a HP/Compaq "p" minitower windows 7 PRO x64, up to date, using a "genuine" Microsoft optical mouse and pedestrian keyboard - both wire-attached to usb ports [and I have moved them from one port to another trying to debug].
It being a 'desktop' I have it set to non-hybrid, no-hibernate Power plan settings. The mouse is set, as you have indicated to "allow" or "enable" wakeup the computer.
the wake behavior is erratic. pressing the mouse left-button or the enter key of the keyboard seems to start the wake process ok, but the mouse is unreliable no matter which port it is in [front/hub or rear]. Sometimes it will resume operation ok. other times the tracking function never returns. System must be restarted. Since there is only one entry for 'mouse' as regards power settings, I'm clueless as to how to remedy but let me ask....
In BIOS settings are options for S5 [by itself] or S3/S4 power management, or neither [both disabled]. Should I go with both disabled or is this a non-issue?
is there any chance that the wrong chipset driver for the root hub device is loaded? In my experience the answer is no... an incorrect model [chipset] driver package from Intel would bail if it does not identify the intended bridge components, right?
I do not know if this is telling or not, but the SATA-connected DVD ODD seems to get into an unreliable state after wakeup also. I have no such thing in my years of experience but the device works fine: then the PC sleeps, when awakened, insert disc and it either fails after many seeks/retries or it takes an unacceptably long time to read or respond to anything [and prevents the system from shutting down or doing much of anything else!]. on a restart, its just dandy. Drives are cheap: I can replace the drive.... just wondering if it is indicating anything other than a ill-behaved device
Last edited by Brink; 04 Jan 2014 at 14:05. Reason: moved to new thread to get better support