GBPVR .NET 2.0 runtime error at midnight

[Gedanken]

I am seeing the following error in the Windows Event Viewer almost every night right at midnight. My MVP drops its connection and spins while DW20.exe runs to collect the crash information

[INDENT]Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 1/7/2007
Time: 12:00:14 AM
User: N/A
Computer: GILGAMESH
Description:
EventType clr20r3, P1 gbpvr.exe, P2 1.0.2547.35214, P3 f, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 2284, P8 66, P9 system.argumentoutofrange, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 67 00 62 00 70 00 .g.b.p.
0018: 76 00 72 00 2e 00 65 00 v.r...e.
0020: 78 00 65 00 2c 00 20 00 x.e.,. .
0028: 31 00 2e 00 30 00 2e 00 1...0...
0030: 32 00 35 00 34 00 37 00 2.5.4.7.
0038: 2e 00 33 00 35 00 32 00 ..3.5.2.
0040: 31 00 34 00 2c 00 20 00 1.4.,. .
0048: 66 00 2c 00 20 00 6d 00 f.,. .m.
0050: 73 00 63 00 6f 00 72 00 s.c.o.r.
0058: 6c 00 69 00 62 00 2c 00 l.i.b.,.
0060: 20 00 32 00 2e 00 30 00 .2...0.
0068: 2e 00 30 00 2e 00 30 00 ..0...0.
0070: 2c 00 20 00 34 00 33 00 ,. .4.3.
0078: 33 00 33 00 61 00 62 00 3.3.a.b.
0080: 38 00 30 00 2c 00 20 00 8.0.,. .
0088: 32 00 32 00 38 00 34 00 2.2.8.4.
0090: 2c 00 20 00 36 00 36 00 ,. .6.6.
0098: 2c 00 20 00 73 00 79 00 ,. .s.y.
00a0: 73 00 74 00 65 00 6d 00 s.t.e.m.
00a8: 2e 00 61 00 72 00 67 00 ..a.r.g.
00b0: 75 00 6d 00 65 00 6e 00 u.m.e.n.
00b8: 74 00 6f 00 75 00 74 00 t.o.u.t.
00c0: 6f 00 66 00 72 00 61 00 o.f.r.a.
00c8: 6e 00 67 00 65 00 20 00 n.g.e. .
00d0: 4e 00 49 00 4c 00 0d 00 N.I.L...
00d8: 0a 00 .. [/INDENT]

[HtV]

My guess would be to find out which program is (trying) starting at 00.00.
Maybe antivirus, or a plugin?

[liteswap]

I et this error most times when I try to start 99.5 - 98.13 was fine. It takes me half a dozen tries at starting gbpvr.exe before it'll start without generating the standard MS crash error dialogue.

[sub]

Zip and attach the logs and I'll take a look.

[Gedanken]

Sorry for the long delay in following up.

It turns out thatt the crash was being caused by an old version of the weather plugin which appears to be making an invalid call. Updating to the most recent version appears to have cleared that issue up.

The reason my response is so delayed, however, is that GBPVR appears to be crashing several times a day causing the logs to cycle off the list. I'll provide details and logs for the other crashes in a separate thread.

Thanks!