Desktop version waking up my PC from sleep?
iok_1
Member Posts: 2
✭
Hi, my Windows 10 PC wakes up too often from sleep and I don't know how to prevent it.
My Fing app is on the 2.8 version which I believe is the latest. Even after turning off wake timers via power options, I still get these results. Please help, I really like the app and don't want to be forced to uninstall. Thanks.
As for the results I mentioned-
After some troubleshooting, I did the following command on cmd and found this:
My Fing app is on the 2.8 version which I believe is the latest. Even after turning off wake timers via power options, I still get these results. Please help, I really like the app and don't want to be forced to uninstall. Thanks.
As for the results I mentioned-
After some troubleshooting, I did the following command on cmd and found this:
C:\Windows\system32>powercfg /waketimers
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:54:34 PM on 2/20/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:45:34 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:23:34 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:23:25 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:23:28 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:23:02 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:22:59 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:23:00 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:22:58 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:23:00 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:22:59 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:22:58 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:22:57 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:22:57 PM on 2/19/2022.
Reason: generic
Timer set by [SERVICE] \Device\HarddiskVolume3\Program Files\Fing\resources\extraResources\fingagent.exe (Fing.Agent) expires at 7:22:57 PM on 2/19/2022.
Reason: generic
I also created a DMP file of the Fing Service from within the Task Manager. Here it is, maybe someone can better interpret.
I also created a DMP file of the Fing Service from within the Task Manager. Here it is, maybe someone can better interpret.
Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Admin\AppData\Local\Temp\fingagent.DMP]
User Mini Dump File with Full Memory: Only application data is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19044 MP (12 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Sat Feb 19 13:25:07.000 2022 (UTC - 5:00)
System Uptime: 0 days 0:04:26.288
Process Uptime: 0 days 0:04:18.000
................................................................
..................
For analysis of this file, run !analyze -v
wow64cpu!CpupSyscallStub+0xc:
00000000`77c81cfc c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1530
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 7746
Key : Analysis.Init.CPU.mSec
Value: 234
Key : Analysis.Init.Elapsed.mSec
Value: 15893
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Timeline.OS.Boot.DeltaSec
Value: 266
Key : Timeline.Process.Start.DeltaSec
Value: 258
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 2.8.0.0
FILE_IN_CAB: fingagent.DMP
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00001740
PROCESS_NAME: fingagent.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000000`00a3ec38 00000000`77c81b5d : 00000023`77d0390c 00007ffe`dda70023 00000000`00d8ddf8 00000000`00b3f958 : wow64cpu!CpupSyscallStub+0xc
00000000`00a3ec40 00000000`77c811b9 : 00000000`00b3f68c 00007ffe`dda739b4 00000000`00a3ed10 00007ffe`dda73aaf : wow64cpu!Thunk0ArgReloadState+0x5
00000000`00a3ecf0 00007ffe`dda738c9 : 00000000`00880000 00000000`00170100 00000000`00000000 00000000`00a3f560 : wow64cpu!BTCpuSimulate+0x9
00000000`00a3ed30 00007ffe`dda732bd : 00000000`00000000 00000000`00b823c8 00000000`00000000 00000000`00000000 : wow64!RunCpuSimulation+0xd
00000000`00a3ed60 00007ffe`deee3592 : 00000000`00000010 00000000`00000010 00007ffe`def41a90 00000000`0087f000 : wow64!Wow64LdrpInitialize+0x12d
00000000`00a3f010 00007ffe`dee84cdb : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : ntdll!LdrpInitializeProcess+0x1932
00000000`00a3f440 00007ffe`dee84b63 : 00000000`00000000 00007ffe`dee10000 00000000`00000000 00000000`00881000 : ntdll!LdrpInitialize+0x15f
00000000`00a3f4e0 00007ffe`dee84b0e : 00000000`00a3f560 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrpInitialize+0x3b
00000000`00a3f510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: wow64cpu!CpupSyscallStub+c
MODULE_NAME: wow64cpu
IMAGE_NAME: wow64cpu.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_wow64cpu.dll!CpupSyscallStub
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 10.0.19041.662
FAILURE_ID_HASH: {289a12fb-10fd-bb5b-3edc-4567046643a5}
Followup: MachineOwner
---------
0:000> .exr -1
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
Tagged:
0
Answers
-
Hey @iok_1
Are you using the latest version of Fing Desktop?
May we ask you to install fing desktop on another device and confirm if that device is experiencing the same issue, waking up when in sleep mode?0 -
Hi, yes, I have 2.8 which appears to be the latest. I can try installing Fing on my other PC. In the meantime, since my first post, I switched the Fing.Agent Windows service to manual. Not ideal, but it only starts when I ask it to now.Karl_From_Fing said:Hey @iok_1
Are you using the latest version of Fing Desktop?
May we ask you to install fing desktop on another device and confirm if that device is experiencing the same issue, waking up when in sleep mode?
That seemed to fix the issue at first. But a day or two later, my PC woke up from sleep anyway. It turns out the main culprit was my keyboard USB driver. I turned off its ability to wake up my PC from sleep and so far, with both options off, my PC has behaved.
Still, just now I put the Fing.Agent service back to automatic and we'll if see my PC wakes up from sleep again. I'm still confused about why it has wake timers active once more (I just checked) after switching to automatic.
1
Categories
- 5.6K All Categories
- 2.8K Ask about Connected Technology
- How To...
- 1K Devices & Security
- 1.5K Network Troubleshooting & Connectivity
- 109 General Discussion, Weird & Wonderful
- 42 Network Infrastructure
- 5.2K Ask about Fing
- 530 Fing Account Change Request
- 1.1K Fing Desktop
- 1.3K Fing App
- 1.6K Fingbox
- 485 Announcements, Beta Testing & Release Notes
- 153 Community Updates
- 28 Getting started
- 13 Community User Guides