Sleep/Wake issue and Yahoo

[fccgrant]

Hello, All-

I have just recently and reluctantly upgraded my PC from Windows 7 to Windows 10 Home Version 1607. My computer does not use the EPG and all Network devices are disabled. All recordings are scheduled manually.

I have been running test recordings and things seem to be recording OK. However, I have run into a problem that has been discussed on and off and that is the condition where the system will sleep and then wake up a minute later after all recordings have finished for the evening.

I have turned off Wake On options on my Network Card even though the card is disabled. But here is the strange thing...If I run Windows Resource Monitor and observe the Network section both NRecord.exe and NTray.exe are trying to reach beap.adss.yahoo.com. If I turn off the NPVR service the network activity ceases. This is verified by stopping and then restarting the Windows Resource Monitor. In this case I suspect that all requests are being sent to the loopback address but does make me curious on why.

This further makes me wonder if this Network activity could be related to why some computers wake up after a minute after going to sleep when recordings are completed.

Looking forward to the responses and thanks...Jerry

[mvallevand]

If you don't have network devices enabled how is it able to use DNS? What IP are you seeing?

Martin

[fccgrant]

Currently it is hitting the local loopback address of 127.0.0.1.

Jerry

If you don't have network devices enabled how is it able to use DNS? What IP are you seeing?

Martin

[mvallevand]

Make sure your network is free of malware that might be the cause of the network traffic. Also make sure you have sleep enabled when media sharing is set.

Martin

[fccgrant]

OK...that was interesting. So at one point (around 2014) I put the beap.adss.yahoo.com in the host file. So that part is cleared up and now shows up as my computer name. Still find it strange that it is (I'm assuming) pinging the 127.0.0.1.

I went and set 'sleep enabled when Media Sharing' setting. We'll see how it goes.

Thanks...Jerry

Make sure your network is free of malware that might be the cause of the network traffic. Also make sure you have sleep enabled when media sharing is set.

Martin

[fccgrant]

The PC woke up at around 2:05 AM according to the logs and Windows. There was no scheduled programs for this time and the EPG option is disabled.

The system then generated an error message when at the point where it would be expected to go to sleep. This usually annoys Windows and will typically crash the system.

Please see the attached log files.

Thanks...Jerry

OK...that was interesting. So at one point (around 2014) I put the beap.adss.yahoo.com in the host file. So that part is cleared up and now shows up as my computer name. Still find it strange that it is (I'm assuming) pinging the 127.0.0.1.

I went and set 'sleep enabled when Media Sharing' setting. We'll see how it goes.

Thanks...Jerry

[Graham]

The PC woke up at around 2:05 AM according to the logs and Windows. There was no scheduled programs for this time and the EPG option is disabled.

The nrecord.log.3 has ...

...
2019-09-02 00:18:06.531 [DEBUG][9] Recording service noted the system was resuming...
2019-09-02 00:18:06.531 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2019-09-02 00:39:27.828 [DEBUG][14] Resuming...
2019-09-02 00:39:29.312 [DEBUG][6] cycling MVP servers
2019-09-02 00:39:36.020 [DEBUG][9] Recording service noted the system was resuming...
2019-09-02 00:39:36.020 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2019-09-02 01:00:56.805 [DEBUG][22] Resuming...
2019-09-02 01:00:58.429 [DEBUG][6] cycling MVP servers
2019-09-02 01:01:05.430 [DEBUG][9] Recording service noted the system was resuming...
2019-09-02 01:01:05.430 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2019-09-02 01:22:26.820 [DEBUG][25] Resuming...
2019-09-02 01:22:33.595 [DEBUG][6] cycling MVP servers
2019-09-02 01:22:35.515 [DEBUG][9] Recording service noted the system was resuming...
2019-09-02 01:22:35.515 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2019-09-02 01:43:56.800 [DEBUG][23] Resuming...
2019-09-02 01:43:57.055 [DEBUG][6] cycling MVP servers
2019-09-02 01:44:05.588 [DEBUG][9] Recording service noted the system was resuming...
2019-09-02 01:44:05.588 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2019-09-02 02:05:26.820 [DEBUG][18] Resuming...
2019-09-02 02:05:28.326 [DEBUG][6] cycling MVP servers
2019-09-02 02:05:35.299 [DEBUG][9] Recording service noted the system was resuming...
2019-09-02 02:05:35.299 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat

It appears that something that is not NextPVR is repeatedly waking the system. What does cmd prompt command ... powercfg /requests ... tell you immediately after one of these random wakes? Thanks.

[fccgrant]

Hi, Graham-

I think there is a file in the Log zip file that was called 'crash.txt' or something like that which came from the Event Viewer. Winodws crashed before I could do the cmd prompt step. In any case, it was NRecord.exe that was the source of the wake up according to Event Viewer. There should also be a systemInformation text file that will describe the system NPVR is using. I still suspect the network activity described in an earlier message may have something to do with this.

Thank...Jerry

The nrecord.log.3 has ...


It appears that something that is not NextPVR is repeatedly waking the system. What does cmd prompt command ... powercfg /requests ... tell you immediately after one of these random wakes? Thanks.

[Graham]

I think there is a file in the Log zip file that was called 'crash.txt' or something like that which came from the Event Viewer.

nrecord.log.1 has ...

2019-09-02 02:27:40.347 [DEBUG][9] Requesting wake up for 'RecordingOID1604-backup' at 9/9/2019 8:54 PM
2019-09-02 02:27:40.347 [DEBUG][9] Requesting wake up for 'RecordingOID1604' at 9/9/2019 8:53 PM
2019-09-02 02:27:43.472 [DEBUG][11] Client Listener starting on port 7969
2019-09-02 18:53:30.849 [DEBUG][19] Resuming...
2019-09-02 18:53:31.458 [DEBUG][6] cycling MVP servers
2019-09-02 18:53:31.567 [DEBUG][10] EPG Updates Disabled
2019-09-02 18:53:39.422 [DEBUG][9] Recording service noted the system was resuming...
2019-09-02 18:53:39.422 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat

crash.txt has ...

The system has returned from a low power state.

Sleep Time: ?2019?-?09?-?02T07:04:25.440019500Z
Wake Time: ?2019?-?09?-?02T07:05:26.836244500Z

Wake Source: Timer - NRecord.exe

I can't reconcile the times in crash.txt with the times in nrecord.log.1

We have seen numerous issues with wake and sleep over the years ... we have never found a problem with NextPVR that was responsible (even when Windows blames nrecord.exe).