Computer doesn't wake up for recording

[K.S.]

It seems that GBPVR recording service doesn't like when my computer goes off hibernation or stand by. Now external application (wosb) wakes up the machine, but as soon as it goes on, Rec. Service collapse with usual message:

ok, as your box is able to wake up on schedule, give HtV's advices a try. my advice: try reinstalling .NET while you still have NOD32 uninstalled. you have to get it to work just with the basics before adding up NOD32 & the like. keep it as simple as possible

[zvm]

HtV, thank you very much for your effort. At first, it seemed this advice on useb power management helped, at least for standby. But, as I run more tests, situation was more like before: it didn't work most of the time.
I think I'm gonna satisfy with either leaving computer running all necessary time, or waking up computer with external application.
And it seems to me that waking up is much more stable and reliable from standby than from hibernation - with GBPVR or external application.

[zvm]

ok, as your box is able to wake up on schedule, give HtV's advices a try. my advice: try reinstalling .NET while you still have NOD32 uninstalled. you have to get it to work just with the basics before adding up NOD32 & the like. keep it as simple as possible

Thanks for the advice. I'll try that as well.
Currently I am running without NOD32. But, at some point, I have to have some antivirus.
Either way, it doesn't seem that my tuner/computer wakes up easily.

Bottom line, I'm not recording that much, and it wouldn't be pain in the ass to do some stuff manually... I've probably spent more time testing so far than I will save with automation (if it succeed!) in next year or so.
I'll let you know if I manage anything more than I have now.
Thanks again!

[HtV]

It is very well possible that your system for one reason or another is just not capable to do hibernating/waking ok. When you go searching for info on this you'll see that there are numerous people out there which can't get it fixed. So if you can do without it might be wise to just leave it here.

[zvm]

Hello again!
Now, I am having trouble with normal recordings - without standby or hibernation wake-ups.
GBPVR RecService almost regularly crushes when I shutdown GBPVR - especially after I set some recordings and exit the program.
I get the usual message:

28.1.2007 12:42:26.609 ERROR [21] FATAL UNHANDLED EXCEPTION:: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Net.UnsafeNclNativeMethods.OSSOCK.WSAGetOverlappedResult(SafeCloseSocket socketHandle, IntPtr overlapped, UInt32& bytesTransferred, Boolean wait, IntPtr ignored)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

NOD32 is uninstalled, GBPVR reinstalled...
I understand this is related to .NET 2.0 Framework. I didn't reinstalled it nor got a hotfix (Microsoft recommends this only if absolutely necessary, which is not my case) Reinstallation might help, but only might... Any suggestions?

PS: It seems to me that NOD32 was not main problem here, but only additional.

[HtV]

I think I would go for re-installing .Net2, and perhaps re-install gbpvr too, You can leave gbpvr.db3 and config.xml so you won't loose anything.
Only other thing I can think of, is a firewall that's in the way. You could also try the hotfix, it won't hurt. If you want it, I think I still have it somewhere.

[sub]

Hello again!
Now, I am having trouble with normal recordings - without standby or hibernation wake-ups.
GBPVR RecService almost regularly crushes when I shutdown GBPVR - especially after I set some recordings and exit the program.
I get the usual message:

28.1.2007 12:42:26.609 ERROR [21] FATAL UNHANDLED EXCEPTION:: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Net.UnsafeNclNativeMethods.OSSOCK.WSAGetOverlappedResult(SafeCloseSocket socketHandle, IntPtr overlapped, UInt32& bytesTransferred, Boolean wait, IntPtr ignored)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

NOD32 is uninstalled, GBPVR reinstalled...
I understand this is related to .NET 2.0 Framework. I didn't reinstalled it nor got a hotfix (Microsoft recommends this only if absolutely necessary, which is not my case) Reinstallation might help, but only might... Any suggestions?

PS: It seems to me that NOD32 was not main problem here, but only additional.

That is the classic error message described in survival guide. It is caused by some process trying to hook into the GB-PVR process to monitor its networking calls, but doing it incorrectly and causing a crash.

Your options are to remove whatever firewall or other network monitoring software is causing the issue, or install that Microsoft patch.

[zvm]

Yes, it is. And some process DW20.EXE looks suspicious to me. It appears from time to time, and occupies whole CPU power at times GBPVR RecService crushes. And it seems to me that it is more likely RECording Service won't crush if I do scheduling through Web Scheduling.
Whole this may not be true, cause it is based purely on few watches from my side - and I am not Windows process/service expert.
I can't tell what software is causing the issue, so... patch seems as an option. Or leave it as it is, and be careful.

I think I would go for re-installing .Net2, and perhaps re-install gbpvr too, You can leave gbpvr.db3 and config.xml so you won't loose anything.
Only other thing I can think of, is a firewall that's in the way. You could also try the hotfix, it won't hurt. If you want it, I think I still have it somewhere.

If it won't hurt, as you say, I would give a try, why not!? Thank you for your offer!
Let's make an arrangement how can you send it to me. How big is that hotfix? Is it suitable for mail?

Last option would be .net 2 reinstall. I remember I spent quite a lot time getting it properly install and running. I would like to avoid going through that again. Maybe another time would be with less problems, but who knows!?

[sub]

I dont think reinstalling .net will help.

Yes, it is. And some process DW20.EXE looks suspicious to me. It appears from time to time, and occupies whole CPU power at times GBPVR RecService crushes.

Thats DrWatson, the Windows component that is run to collect error information when a process dies unexpectedly. This is is normal, and not the cause of your problem.

I can't tell what software is causing the issue

What does the crash entry in the Windows Event Viewer say? It often identifies the offending module (.DLL). Viewing the properties of that DLL will often say the manufacturer which will give a clue as to what software product is causing the problem.

[zvm]

I dont think reinstalling .net will help.

Thats DrWatson, the Windows component that is run to collect error information when a process dies unexpectedly. This is is normal, and not the cause of your problem.

What does the crash entry in the Windows Event Viewer say? It often identifies the offending module (.DLL). Viewing the properties of that DLL will often say the manufacturer which will give a clue as to what software product is causing the problem.

Sub, why didn't you mentioned that before!? You, most probably (and hopefully), solved the problem with this hint!!
File is nl_lsp.dll, and it is from NetLimiter! But, how come it is active if I am not using NetLimiter anymore!? I didn't uninstall NetLimiter, but I stopped it! Or I just think I did!?
I browsed through all the errors in the Event Viewer log. Random checking always resulted with the same "culprit" - nl_lsp.dll from NetLimiter. That probably means NOD32 was OK.

Should I uninstall NetLimiter, or there is another way ? I would like to keep NetLimiter on my computer. It can be deactivated most of the time. I would use it only occassionaly.