Windows 7 will not "fall" asleep

For a long time now, my 64-bit W7 will not fall asleep unless I tell it to. I have made all the recommended adjustments to Power Options, to no avail. To find out if something was preventing sleep mode, I ran the instruction "powercfg -requests" on a command prompt first thing after restarting and got this:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\LBB>powercfg -requests
DISPLAY:
None.

SYSTEM:
[DRIVER] Realtek High Definition Audio (HDAUDIO\FUNC_01&VEN_10EC&DEV_0887&SUBSYS
_1458A002&REV_1003\4&26fe9049&0&0201)
An audio stream is currently in use.
[DRIVER] \FileSystem\srvnet
An active remote client has recently sent requests to this machine.

AWAYMODE:
None.

C:\Users\LBB>

I had run WU just before I restarted so maybe the "remote client" entry was related to that, though I thought that restarting would remove references to that. Earlier I ran Malwarebytes, ccleaner and an Avast full virus scan. My Startup list is pared down pretty well. Not sure what to do next. The DRIVER Realtek statement above is for my onboard audio. Updated a month or so ago. Not sure why an audio stream would currently be in use with nothing having been opened except the startup items like Avast, ccleaner and MBAM.
edit: I should note that the Realtek driver is one of the Startup items.

Thanks for any assistance.

 

Looks like you have to Update or install your Graphics driver.

 

Thanks for the input.
I just ran WU and updated my card 2 months ago as part of an effort to determine the source of a BSOD problem.

Is the Realtek audio an issue in keeping it from going to sleep on a time out, vs. forced asleep by choosing Sleep in the shutdown menu?? I just question whether this mainboard hardware should be on my startup list at all.

 

I made my suggestion based on the above.
Regrettably I no longer have W7 in use so I cannot check the Power Option settings between W10 and W7.
In my W10 Startup, Realtek is enabled and causes no problem with comp Sleep operation.

 

Is Realtek listed for you on an elevated Command Prompt: powercfg -requests?

I ran powercfg energy which traces such things for 60 secs. Results:

Power Efficiency Diagnostics Report
Computer Name ZPC-C5Z87-GF65
Scan Time 2019-03-10T03:16:15Z
Scan Duration 60 seconds
System Manufacturer Gigabyte Technology Co., Ltd.
System Product Name Z87-DS3H
BIOS Date 09/24/2013
BIOS Version F1
OS Build 7601
Platform Role PlatformRoleDesktop
Plugged In true
Process Count 113
Thread Count 1823
Report GUID {df27137a-a0a3-4628-987e-483ad014e421}
Analysis Results
Errors
Power Policyisk idle is disabled (Plugged In)
The disk is not configured to turn off after a period of disk inactivity.
Power PolicyCI Express ASPM is disabled (Plugged In)
The current power policy for PCI Express Active State Power Management (ASPM) is configured to Off.
System Availability Requests:System Required Request
The device or driver has made a request to prevent the system from automatically entering sleep.
Requesting Driver Instance HDAUDIO\FUNC_01&VEN_10EC&DEV_0887&SUBSYS_1458A002&REV_1003\4&26fe9049&0&0201
Requesting Driver Device Realtek High Definition Audio
System Availability Requests:System Required Request
The device or driver has made a request to prevent the system from automatically entering sleep.
Driver Name \FileSystem\srvnet
CPU Utilizationrocessor utilization is high
The average processor utilization during the trace was high. The system will consume less power when the average processor utilization is very low. Review processor utilization for individual processes to determine which applications and services contribute the most to total processor utilization.
Average Utilization (%) 16.58
Platform Power Management CapabilitiesCI Express Active-State Power Management (ASPM) Disabled
PCI Express Active-State Power Management (ASPM) has been disabled due to a known incompatibility with the hardware in this computer.
-----------------------------------------------------------------

Once again it points to Realtek. I checked on Device Mgr and the Realtek Audio Controller has no "sleep" option check box.

 

If I open Device Manager > Network Adapters > RIGHT click RealTek Family Controller > click on Properties > Power Management > What is Ticked??

 

Thanks!

"The Allow This computer To Turn Off This Device...." is checked. I already went through every item on Device Manager looking for something not checked for that. Found nothing. Maybe you saw the same forum thread I did!!

 

No, I just had a look in Device Manager.

Just a silly question, did you make the adjustments - then Shut down the comp to allow Windows OS to make the adjustments?

 

Yes I did.
I uninstalled Avast just to see since it was a relatively recent install... no.
I also unchecked Realtek in the Start Up list (and restarted)... no.

 

You have already followed MS suggestions on this Topic:
https://support.microsoft.com/en-nz/help/976877/windows-7-does-not-go-to-sleep
I'm running out of ideas and if all else fails have you done sfc /scannow to make sure all Files are in place?
Have you disconnected any/all peripherals and run comp in 'bare bones' to see if Sleep will work?
If all else fails the last resort would be to Refresh W7.

 

I ran sfc, nada. I put it in Safe Mode to see if it would sleep and it would not turn off the display or go to sleep. Odd from what I have read. My peripherals consist of a Trackball, std keyboard, a 12 year old HP printer and an old set of HK speakers. I cannot imagine these causing an issue. powercfg -requests still lists the onboard Realtek audio with an active audio stream. Cannot figure that one out. I turned off the Realtek audio manager software to no benefit with the audio stream or the sleep issue. I also found a new driver for the video card but no joy there. The other driver updates seem "out there". Gigabyte suggested to not flash the Bios unless truly necessary. Realtek is up to date, I turned off the on board video since I have a Geforce PCI card (long overdue on that one).

Last thing I can think of is to do a selective startup process to see if any of the startup apps is the problem. I hate doing that.