GBPVR Not Responding, Snaps Back, then does it again!!!

[andrew_macaluso]

Okay, for the last couple of days I have noticed GBPVR acting strangely. It won't respond to anything that I ask it to do for about 30 seconds to about 2 minutes. The video still plays normally, and recording still goes on normally (if recording), but it just doesn't do anything. Then, after a minute, it catches up on all of the commands I entered into it and then operates normally for a few minutes and then freezes again. When I Ctrl+Alt+Del it to see whats going on, it just says that GBPVR isn't responding!

Nothing else seems to be freezing, just GBPVR. And it never freezes permanently. At most maybe 2 minutes. But, it keeps doing it over and over again. Has anyone heard of this!?

[sub]

Are you using a remote, or the keyboard? If its a remote, which remote? (Hauppauge?)

[andrew_macaluso]

Yes, hauppauge.

[sub]

There is a known problem with the Hauppauge remote that can cause this behaviour, which may be the case here.

The Hauppauge remote just sends fake keypresses to GB-PVR, but the occasional user has this problem where it takes a very long time for the keypress to make its way through the Hauppauge IR driver before being eventually delivered to GB-PVR.

Next time it happens see if the keyboard works fine. This should help you determine if this is what is happening.

[andrew_macaluso]

no, it appears to be completely freeze completely and totally regardless of whether I send commands via keyboard or remote. Occassionally it delivers a message saying that the databse file has been locked?! I don't know what this means, though.

[sub]

Post the logs next time it happens and I'll take a look.

[andrew_macaluso]

Where do I find the logs?

[sub]

See the sticky thread titled 'posting support questions'.

[andrew_macaluso]

yeah, sorry, stupid question! I noticed it about 30 seconds after i posted it. sorry.

[andrew_macaluso]

Here they are. Now I have a new issue. It gives some error message pertaining to a database when I try to access the Config! I don't know whats going on, but here are the logs.