unusual crash

[shaunpatrick77]

Hi Sub

Had a crash I haven't seen before, i suspect I had and issue with the recording service but just thought I'd post it in case it was a some value. I was trying to cancel a recording that had actually finished hours ago, but npvr thought was still in progress.

Cheers

[johnsonx42]

it might be helpful if you'd say what recording it was, when it started and was supposed to stop, and when it was that you were trying to cancel it.

[shaunpatrick77]

I included a screen shot that showed some of the info, but it's academic now as the entire system became completely unstable later that day and I had to rebuild it from scratch last night.

I think what happened was a crash of undetermined origin during an early morning recording forced a system reboot, and that the recording service didn't correctly restart.

At a wild stab it looked like npvr's unhanded exception seemed to be related to npvr trying to talk to the recoding service that either wasn't there, or more likely was responding with garbage.

Anyhoo, new memory, new power supply, new drivers and a fresh install and fingers crossed!

[johnsonx42]

I included a screen shot that showed some of the info, but it's academic now as the entire system became completely unstable later that day and I had to rebuild it from scratch last night.

I think what happened was a crash of undetermined origin during an early morning recording forced a system reboot, and that the recording service didn't correctly restart.

At a wild stab it looked like npvr's unhanded exception seemed to be related to npvr trying to talk to the recoding service that either wasn't there, or more likely was responding with garbage.

yes, sorry, I skipped right past the screen shot and went into the logs directory. the logs and error message indicate it simply died during the recording at some point, but no, it didn't reboot. trying to cancel it had nothing to do with the problem, NRecord was gone by then. essentially, whenever you get that "connection could not be made to 127.0.0.1 - the target machine actively refused it" error from .net, it means NRecord has gone teets up.

I'd like to ask if anything showed up in the Windows Event log between 04:55 and 05:30, but as you've rebuilt the machine it's too late for that.

You should make sure you have a c:\temp directory. If it's there and NRecord crashes, it'll make a quick deathbed confession into c:\temp\crash.mdmp about what it was doing that got it killed and maybe even who killed it (I suppose it's written in the digital equivalent of blood). sub may be able to use the crash dump to fix the issue if it was cause by an NRecord bug.

[shaunpatrick77]

Will do, thanks for the advice!