View Single Post
  #5  
Old June 16th 18, 06:06 AM posted to alt.comp.os.windows-10
Zaghadka
external usenet poster
 
Posts: 315
Default Windows 10 64bit suddenly will not sleep.

On Fri, 15 Jun 2018 11:45:51 +0100, in alt.comp.os.windows-10, Mike Swift
wrote:

In article , Mike Swift
writes
Otherwise, you shut down running applications one-by-one from the task
manager and check powercfg after each application you shut down, and
eventually, hopefully, you should find the offending application.

Good luck.


Thanks, I'll give that a try.

Cheers, from past experience I'll need it :-)

Mike


Update.

I found the culprit Audiosrv PID 16376 Windows Audio
LocalServiceNetworkRestricted

stopping this gave a clear powercfg -requests

As I understand it permanently stopping this wil disable all sound
functions so I' no nearer solving the not sleeping problem.


No, it wouldn't really fix it. The reason that releases the audio stream
system request is because you just shut down the entire Windows audio
service, which is what manages the audio streams in the first place,
AFAIK. If it *is* a running process, it's gotta be something else.

What version of Windows are you on? The upgrade to 1803 went rough on one
of my systems. Every other system update it kept my old, working audio
drivers. 1803 *insisted* on installing the latest VIA driver, which
happens to be broken. This was a known issue since the very first release
of Windows 10 that it was broken, in my case, and 1803 insisted that I
have it anyway. I found a workaround online, using the generic Microsoft
HD Audio driver, but maybe your driver got updated to something that's
now broke?

Fiddling about with drivers is not something I can easily discuss on
Usenet, though. It needs pictures to really show you what to do. But it
could be a problem with the audio driver itself, if it isn't an
application. You can Google how to rollback a driver, or install an old
driver, or alternate driver, and see if you have any luck with that.

On my broken system, rollback was not an option, and I didn't have the
older working driver archived, so I was SOL. Luckily, there was that
generic Microsoft driver that worked in place of the latest, broken VIA
driver. Windows threw up a big incompatibility warning when I tried to
install it though.

So, important point: Messing around with drivers is tricky business, so
if you try anything more than a rollback, be careful to have a system
restore point ready, or a system backup. You put the wrong drivers in,
and you can wind up with a bunch of blue screens (stopping you from
reverting the change) or outright boot failure.

Sorry I couldn't really help. That's about all I can think of.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten
Ads