Device failed to start

[roy]

This wasnt related to your analog problem fixed earlier in the thread.

Its an occurrence of a years old problem we occasionally see in both NPVR and GBPVR where the app askes a device to stop, but that call never returns, effectively leaving the recording service frozen. I've no idea what causes it, and I've never been able to reproduce it myself.

OK, I'll hope it doesn't reoccur.

Now when other recordings started, the currently recording QAM tuner file stopped growing, but status still indicated recording. When I looked at the System plugin I got a 'refused connection' error. So I'm thinking the System plugin may be at fault. I've removed it while I test some more.

[Misko5]

bump, page 4

[Misko5]

Alright, I did the LogTSFlow set to 2 registry thing (except it was under Wow6432Node, not simply NPVR under software because NPVR under software didnt exist) I have one mon.txt files attached as well as nrecord.log However, I should point out that notepad crashes every time I try to open the mon-08710020.txt that is not attached because trying to attach made the browser crash. I'm assuming this is significant. Also, I saw the error message under nrecord.log and noticed it was exactly like an error message I saw in the forums for GB-PVR with the HVR-2250. Hopefully the card has the capability of recording two qam channels at one time with this software. I am using Win7 x64 Enterprise if it matters. Thanks.

Checked that mon.txt file that wasn't working, it was like 72 MB, possibly why it was troublesome. Set LogTSFlow to 3, started my recordings, one mon file was processing data and the other had no text. I believe the problems all revert back to the error in Nrecord.log but I have no idea what to do about it.

[roy]

Crashed again tonight, logs attached. All was well, several completed recordings, two in process to finish at 10:02 pm, problem when three recordings started at 9:58. Not all started, two files were created (Men of, Castle) but Hawaii 50 was not, but I think the status window showed only Hawaii 50 started (but I'm not sure of that) then NRecord.exe crashed. I rebooted and all three recordings have restarted correctly. The two recordings that were in process now show as failed (recording service not running at recording time) even though the files are still there.

This now seems like maybe also a tuner scheduling/padding thing? but I don't know.

[roy]

NRecord crashed again at 10:46, but I don't see it in the logs. Recordings started again after reboot.

Padding is not being honored. At 11:00 "Men of" ended and "Daily Show" started on same tuner, when other tuners were available for padding. Other recordings did end normally.

WAF is not good this evening. Do you think this is a Win XP issue only? I've been waiting for the opportunity to load Win 7, and may have to switch back to GBPVR while I load it.

[sub]

Create a c:\temp directory, and post the c:\temp\crash.mdmp next time the problem occurs.

[sub]

Alright, I did the LogTSFlow set to 2 registry thing (except it was under Wow6432Node, not simply NPVR under software because NPVR under software didnt exist) I have one mon.txt files attached as well as nrecord.log However, I should point out that notepad crashes every time I try to open the mon-08710020.txt that is not attached because trying to attach made the browser crash. I'm assuming this is significant. Also, I saw the error message under nrecord.log and noticed it was exactly like an error message I saw in the forums for GB-PVR with the HVR-2250. Hopefully the card has the capability of recording two qam channels at one time with this software. I am using Win7 x64 Enterprise if it matters. Thanks.

Checked that mon.txt file that wasn't working, it was like 72 MB, possibly why it was troublesome. Set LogTSFlow to 3, started my recordings, one mon file was processing data and the other had no text. I believe the problems all revert back to the error in Nrecord.log but I have no idea what to do about it.

That one error in your npvr.log can be ignored (PropSet Set() failed (80070492)). It doesnt matter if that doesnt happen.

There is no sign of any errors in your logs. It just looks like one tuner isnt delivering any data.

[Misko5]

Is there any way to fix that? Or is it just a faulty tuner? Also, I ready your most recent reply to roy's problem. I'm not sure if we are having the same problem or not but I too have a crash.mdmp file in my temp folder. Not sure if that file is always there no matter what but I have it attached nonetheless. Fingers crossed.

[sub]

Is there any way to fix that? Or is it just a faulty tuner?

I dont know. Its not a problem I've come across.

Also, I ready your most recent reply to roy's problem. I'm not sure if we are having the same problem or not but I too have a crash.mdmp file in my temp folder. Not sure if that file is always there no matter what but I have it attached nonetheless. Fingers crossed.

I tooks a look in this dump file, but unfortunately it didnt yield anything useful. There was clear indication of what caused that particular crash.

[Misko5]

Alright, since the 2250 dual qam wasn't working I decided to throw in my 1800 that was lying around. Installed drivers for it, opened npvr, and scanned for qam channels. None to be found. Looked through my npvr.log file and found that that all of the strengths were 41,000 and all of the qualities are 0. npvr.log attached.