PVRX2 has encountered a problem and needs to close

[fletcher1717]

Hi,

I am having a problem that is happening all of the time and causing PVRX2 to crash all of the time. I have had a quick look through my logs. I think that it has something to do with the following entry in my logs.

Code:

2008-09-30 14:20:22.609    VERBOSE    [1]    System.ArgumentOutOfRangeException: Value to add was out of range.
Parameter name: value
   at System.DateTime.Add(Double value, Int32 scale)
   at System.DateTime.AddMilliseconds(Double value)
   at GBPVRX2.x0061b801bdf12d35.xdb012c437aec4a40(Boolean xd23bf32f3b17e3be)
   at GBPVRX2.x0061b801bdf12d35.xbaa4f05aaa83b591()
   at GBPVRX2.xdd215986d9a64c86.SwitchInsetToFullscreen()
   at GBPVRX2.Players.xb3e61f7448c39547.x4276385f71addb51(Channel xee500015fb4a65b6)
   at GBPVRX2.Players.xb3e61f7448c39547.x4276385f71addb51()
   at GBPVRX2.x4a212861656a24dd.x3852f96f8dab4cab()
   at GBPVRX2.MenuTask.x9006c1ed9ccb79de.OnKeyDown(KeyEventArgs e)
   at GBPVRX2.x0061b801bdf12d35.xdae9991ab918b397(Object xdf2e3583f942db7b, KeyEventArgs xc4f45905cb1fc7ba)
   at System.Windows.Forms.Control.OnKeyDown(KeyEventArgs e)
   at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
   at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
   at System.Windows.Forms.Control.WmKeyChar(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at GBPVRX2.x0061b801bdf12d35.WndProc(Message& m)

I have attached my full logs in case I have it wrong.

Thanks in advance for any help.

Ritchie

[sub]

We've seen this a few times recently. Its a bug in the MDAPI filter which seems to be trampling some memory in the .net runtime. It only seems to affect some users - I'm not sure why.

[fletcher1717]

Hi Sub, thanks for the quick reply.

I have done a bit more fiddling with this. Here is what I have found. I did a complete rebuild of my system, v 1.2.13 as before and found that I still had the same problem. I then did another rebuild, this time with v1.2.9 and hey presto, it started to work again. I have sat for around half an hour constantly changing the channel and it seems to have resolved my issue.

Could this be a similar problem to the crashes that some users experience (including me) when scanning with 1.2.13? I only ask as I got this problem after a rebuild following a new motherboard installation (MA78GM). I did not apply the patch as I had saved my gbpvr.db3 and scan-1.cache files to save me waiting on a scan.

Obviously I would like to use the most recent version so I you think it would sort it, I would 1.2.13 with the gbpvrtsmon patch, I am reluctant to screw too much with a working system, should I just wait for the next release?

Again, thanks in advance.

[fletcher1717]

Sorry for the bump but I would really like to know what is happening here.

Thanks

[sub]

Sorry, I really dont know. Multidec works fine for me, but I'm using an older version.