Sage HTPC goes black, CPU 100%

[DaveWC]

I was trying to hook up a HD100 extender using the HDMI cable rather then composite. It wasn't working, no video, no sound, nothing. It worked fine on the composite connection. So I thought it might be the HDMI cable so I took the TV down to my HTPC and hooked the HDMI cable into my video card. That worked fine. No idea why it doesn't work from the extender but that's the least of my problems. After reconnecting my other TV to the HTPC it was black & nothing would cause it to work. I rebooted & it came up fine but once it went into Sage it went black. When I get into Task Manager it shows the SageTV software is using the CPU 100%. It's also hung, can't exit other then through the Task Manager. No idea what caused this problem or what to do about it.

[DaveWC]

Further to this, it only goes black and hangs if I enable SageTVService mode. If I don't it works fine.

[DaveWC]

So am I lost here? Is there some debug mode I can run that will tell me what's causing SAGETV.EXE to hang when SAGETVSERVICE.EXE is running? Conversely, if SAGETV.EXE is running 1st then SAGETVSERVICE.EXE won't start.

[rwc]

Hi dave,

I'm seeing the same thing--but it happens directly on my server. I've found that if I disable the service and then re-enable it, things start to work again.

I know it doesn't solve your problem...but trust me, you aren't alone on this one

[DaveWC]

It's on my server that this happens too. It's not the end of the world. It just causes you to lose a bit of confidence in the software that this can happen for no reason.

btw, I got the HD100 working with the HDMI cable. That's progress.

[Opus4]

Contact tech support for more help, since there aren't many suggestions here. But, I don't see any info about what type of system you are using - OS, tuners, etc. Maybe there is some setting in sagelicent.properties that messes up the UI, so you could try getting rid of that file & its autobackup to reconfigure the UI when service mode is used.

The instructions for debug logging are here, but as the post says: don't send the log to support unless it is requested.

- Andy

[DaveWC]

Ok, I'll contact tech support. Here's what I'm using...

E6850 Duo 2 Core CPU
Sapphire Radeon HD 3650 video
4Gb Corsair PC6400 RAM
Windows XP Home Edition 32bit
2 Hauppauge PVR-500 dual tuners
2 WD Caviar 1Tb HDD
ASUS P5K-E/WIFI mobo
LG GGC-H20L Blu-Ray HD DVD player
Corsair 620HX psu
USB-UIRT

The system was running pretty well until today. It froze, I rebooted and now the problem exists. The only change I made at that time was trying to get my HD100 working over an HDMI cable. That is working now. Thanks for your time.

[carlgar]

Originally Posted by DaveWC

The system was running pretty well until today. It froze, I rebooted and now the problem exists. The only change I made at that time was trying to get my HD100 working over an HDMI cable. That is working now. Thanks for your time.

This sounds like it could be a corrupted properties file. A friend of mine encountered a issue where he could not get Sage to start up properly. It turned out that he had to let Sage create a new properties file to get Sage to start properly. I compared the new properties file with his original and saw that a lot line lines seemed to be missing. I concluded that the properties file was probably missing a required line that Sage needed to start up.

[rwc]

What do I lose when it rebuilds the properties? (Do I need to set up favorites, etc?)

thanks,

rwc

[gplasky]

Originally Posted by rwc

What do I lose when it rebuilds the properties? (Do I need to set up favorites, etc?)rwc

No. You basically walk through the Sage setup up again. Designate directories for recordings and imports, assign tuners and channels, remotes, etc.

Gerry

[DaveWC]

Yeah, it worked. I deleted the sage.properties file and then restarted Sage. It allows me to launch the service mode without problem. All of my keymapping was still in the Client properties file so I didn't have to redo that.