Freezing

[dspdrew]

It seems that about 1 out of every 4 times I wake the computer up NPVR is completely frozen and the computer ends up having to be cold booted. Is there any reason for this? I can never see anything in the logs. I do see this in the Windows application log:

Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:
P1: NextPVR.exe
P2: 1.0.0.0
P3: 4cd74294
P4: unknown
P5: unknown
P6: unknown
P7: unknown
P8:
P9:
P10:

[sub]

I dont now. Post the logs and I'll see if anything stands out. Are you sure it has focus? ie, have you tried clicking on it before pressing keys.

[gEd]

so are u actually saying that the pc is completely frozen and that this includes npvr?
what happens if u press the windows key - any response? if not the problem is outside npvr

[skinny]

I have a similar issue, although less frequent than dspdrew
The machine appears to be totally locked up, no response to any keys. The time showing on the NPVR screen is the time it last went to sleep.
I have found that if I wait long enough, usually 2-3 min, and sometimes it seems like up to 10 min everything starts to work correctly. The WAF is under pressure which possibly contributes to an exaggerated perception of time.
Cheers

[dspdrew]

Yes it is completely frozen. I try logging in via RDP and it will start to login, and then hangs until I cold boot the computer (pressing the button wont even reboot it when this happens). Ill post logs imediately after this happens the next time.

[sub]

If the machine completely frozen, then its sounding more likely to be a driver or hardware instability issue.

[dspdrew]

I know what your saying.. I guess I shouldn't have said completely frozen because I could ping it and RDP into it. It guess it was just the shell/profile that seemed to be frozen, and any other that tried to start up.

[Barsk]

Could be anything. Bad memory, overheating due to clogged fans etc.
One thing that springs to mind is bad power unit. When it is beginning to go it can fluctuate, causing instability.

One place to start though is the log viewer in Windows to see if it is caused by software. If lucky you may have some log entries to look into.

[dspdrew]

Could be anything. Bad memory, overheating due to clogged fans etc.
One thing that springs to mind is bad power unit. When it is beginning to go it can fluctuate, causing instability.

One place to start though is the log viewer in Windows to see if it is caused by software. If lucky you may have some log entries to look into.

I actually already got those errors from the event viewer.

Also, all of those things you mentioned cause complete system lockup, which is not whats happening here.


@Sub
Something very similar happened again today. This time the screen was completely black and all I had was the little spinning circle hour glass type icon. I checked the logs and it looks like NPVR started up and started processing my weather plugin stuff, so it is running, just nothing showing, and nothing responding to my mouse or keyboard. Here are the last few lines of the NPVR.log.

Code:

2010-11-23 18:40:24.314    [DEBUG][4]    Weather:    "DownloadImagesInQueue"    Downloaded 'http://vortex.accuweather.com/adc2004/common/images/locallayers/markers/KRIV_markers.gif' to 'C:\Users\Public\NPVR\Plugins\Weather\config\images\layers\local\KRIV_markers.gif'
2010-11-23 18:40:25.110    [DEBUG][4]    Weather:    "DownloadImagesInQueue"    Downloaded 'http://sirocco.accuweather.com/nxssa_r1_h_500x620d/r1h/inxr1KRIVa_h.gif' to 'C:\Users\Public\NPVR\Plugins\Weather\config\images\animated\radar\local\KRIV.gif'
2010-11-23 18:40:25.110    [DEBUG][4]    Weather:    ...releasing mutex (Auto Update Weather Information Thread).
2010-11-23 18:40:25.110    [DEBUG][4]    Weather:    "LoadUI"    ENTER
2010-11-23 18:40:25.110    [DEBUG][4]    Weather:    "LoadUI"    screen elements not initialized and background thread is alive.
2010-11-23 18:40:25.110    [DEBUG][4]    Weather:    "LoadUI"    EXIT
2010-11-23 18:40:25.110    [DEBUG][4]    Weather:    "ResetAutoUpdateTimer"    Resetting the auto updating timer...
2010-11-23 18:40:25.110    [INFO][4]    Weather:    "ResetAutoUpdateTimer"    Next auto update at: 19:00:25.1105586

Let me know if the whole log would help.

[sub]

Might be worth seeing if the problem goes away if you temporarily remove the weather plugin.