W7x64 NextPVR crashing when using plugin System

[Graham]

I used to "pop in" to the System plugin to look at disk usage and immediately hit the Back button. Too often, NPVR would freeze completely when I did this. I learned to wait until everything was being displayed (CPU, temp and all that) before I hit Back.

I have tried to re-create the freeze today so that I could post some logs ... but (inevitably, cos it's intermittent) I can't get it to behave badly when I want it too.

[imilne]

Actually, it's not Math.round, it's the equivalent of this code:

Code:

PerformanceCounter cpuCounter = new PerformanceCounter();
cpuCounter.CategoryName = "Processor";
cpuCounter.CounterName = "% Processor Time";
cpuCounter.InstanceName = "_Total";

// This is the bit that causes the exception
float value = cpuCounter.NextValue();

The value was being passed into Math.round, but it's actually failing on the NextValue() call. Consider me stumpified.

@Graham, I've not seen this happen, but if you get it to crash again (and have debug on for the plugin's logs) then I'll happily look into it for you.

Iain

[bavan]

With the original System plugin version I've got a NPVR crashed Windows message 1 or 2 second after opening the System plugin. AT that moment the System plugin info is still on the screen and only after hitting the BACK key NPVR is finally closed by W7.
Don't know if this makes sence?

Imilne could you confirm you have disabled the CPU load measuring in the 2 modified versions you have posted here? Just for me to understand why the modified versions don't crash NPVR.
Tx.

[imilne]

Imilne could you confirm you have disabled the CPU load measuring in the 2 modified versions you have posted here? Just for me to understand why the modified versions don't crash NPVR.

No, it's not disabled, it just has additional exception handling code wrapped around the bit of code that goes wrong to stop it from crashing. If you look at your log file you'll see lots of the System.FormatException messages being printed out (one a second as that's how often it polls the CPU).

The reason it shows 0% CPU is because I just made it say that if it couldn't read its value. What I can't figure out is why it can't read it in your case. I'll do some googling and see if I can come up with a solution...

Iain

[imilne]

Found a hit almost straight away - http://stackoverflow.com/questions/31216...at-c-sharp - but the link to a possible solution (that you'd have to run bavan) is timing out for me.

Iain

[bavan]

The URL is also timing out for me so probably the link is broken.
I would be more than happy if a new System plugin version had the option, via NPVR plugin settings, to independently disable CPU or memory or Internet speed to get around the problem.
As I mentioned before for me these are less used indicators so I wouldn't mind as long as Disk space, pending recordings & Power options are still available.

[Graham]

Did you find this ...

http://blogs.technet.com/b/yongrhee/arch...008r2.aspx

[bavan]

I found this article http://support.microsoft.com/default.asp...-us;300956
I'm not sure what to do next. Is it something I have to fix myself or is something to be changed in the System plugin program code?
If I need to fix the problem myself on my system what do I need to do?
I have a bit of programming notice but I'm not an expert so fidling with W7x64 registry and other stuff always scares me off.
PS: Forgive me for the language mistakes but I'm dutch speaking.

[imilne]

If you wanted to follow up on those instructions, then by all means do so, but I agree it doesn't seem that trivial. Hopefully it would solve your issues with the System plugin though. It is something you'd have to do though; there's nothing I can do about it in the plugin other than catch the error.

Alternatively, you can ignore it and just keep using the version I've posted above (although I'd disable debug logging again). I'll post a proper update in due course but it'll pretty much be identical to the one here as I don't think there's anything else I can do.

Iain

[bavan]

That's what I was afraid of so I'll read the articles again and see if I can sort it out. I'm just wondering why things got corrupted to avoid getting back in the same situation?
I still have some W7 backups which I could try to reinstall but if I'm right nothing guarantees me for not getting back in the same situation (which program screws my PC ??? GRRR).
I've checked windows Taskbar CPU and memory indicators to find out if they have troubles but they seem to run fine.
If in a future System plugin release there would be a settings option to disable CPU & Memory usage, just in case, it might prove a usefull workaround.

Thank you all for giving me advice. I'm on my own now (I guess) to get things fixed.