Sage server stops

[motobarsteward]

Anyone seen this?

My server service just stops. I Can't get a client to connect to it. When I try and use the SageTV service manager to stop and re-start the service, it just hangs. If I use the windows service manager, it complains that the service doesn't respond in a timely manor. If I use the task manager to kill the SageTV service process tree, nothing happens and the process sits there all un-dead! This machine only ever runs the service, with nielm's web server and Orb to get to those places that Placeshifter can't reach. (I don't use or configure the live tv part of orb. I just use the file sharing and media streaming)

It's done this twice in the last two days. I installed 6.3.1 on 26th Feb. Up until this, my server had been up since I did a complete clean build and install on 19th Jan 2007 with Sage 6.0.19

I've never had any problem with the server service in all the time I've been running SAGE. Now it dies twice in two days. Both times it appears to be when I cahnge the channel from the client. The log on the server shoes nothing, I guess because the sage sevice had died before it new anything was wrong with it. (I hope that, one day, that's the way I go!)

The only way to recover is to re-boot the server, which is a real pain as it's in the garage.

The only thing I have in the event system is a very curious message: -
"The description for Event ID ( 54 ) in Source ( Cap7134 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\00000066. "

which follows the message: -
"A device driver is leaking locked I/O pages causing system degradation. The system has automatically enabled tracking code in order to try and catch the culprit."

If nobody has any ideas, I'll log a bug with sage tomorrow.

PS if it screws up recording Shaun tomorrow, I'll ask for my money back!

[motobarsteward]

The Cap7134 message may be to do with the AVerMedia A169 capture card I have in my server while a get a replacement for my Hauppauge MCE500 that went dicky in over Chrismas (Diagonal interference lines, know problem).

The Hardware manager reports that this card has a service called "Cap7134" associated with it.

Not sure about the IO page leak though

I wonder if my lockup is also related. Anybody got any experience of these Avermedia cards?