monitor crash

[LaszloSebo]

My overnight open monitors usually disappear by the mornings. Not sure if its always the same issue, but here is an event viewer log:

Log Name: Application
Source: Application Error
Date: 1/22/2014 1:05:23 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: vcpro1014.scanlinevfxla.local
Description:
Faulting application name: deadlinemonitor.exe, version: 6.1.0.54584, time stamp: 0x52dfdd34
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7b325
Exception code: 0xc0000374
Fault offset: 0x00000000000c6ab2
Faulting process id: 0x20f0
Faulting application start time: 0x01cf17b389e5d06a
Faulting application path: C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e853663e-83a8-11e3-b6a9-005056c00008
Event Xml:



1000
2
100
0x80000000000000

104291
Application
vcpro1014.scanlinevfxla.local



deadlinemonitor.exe
6.1.0.54584
52dfdd34
ntdll.dll
6.1.7600.16695
4cc7b325
c0000374
00000000000c6ab2
20f0
01cf17b389e5d06a
C:\Program Files\Thinkbox\Deadline6\bin\deadlinemonitor.exe
C:\Windows\SYSTEM32\ntdll.dll
e853663e-83a8-11e3-b6a9-005056c00008

No info in the monitor log

[rrussell]

Hey Laszlo,

In another thread (the one where you reported the slow monitor startup), I had asked you to try reinstalling the Deadline client. Just curious if that’s something you’ve tried yet. I wonder if maybe a bad auto-upgrade has left the client in an unstable state.

We haven’t seen a Monitor crash here when leaving it running for a while, so it’s interesting that it happens so reliable for you.

We’ll start leaving monitors open here though over the weekend to see if it’s still running come Monday.

Cheers,
Ryan

[LaszloSebo]

Ill be doing a clean reinstall next week (rolling out rc3 this weekend, so im getting randomly auto updated to different versions right now depending on which repo i connect to) and see if it changes the situation