Don't know how much help this is now that we've moved into S5R3, but one of my hosts faulted out on a 4.38 with a 105 while cleaning up it's R2 datapaks. This is the first compute error I've seen on this host in a long time which wasn't my fault, it's normally very reliable.
The "NULL pointer" message doesn't look good. However two machines finished this WU without error, so this doesn't look like a programming error (which the failed sanity check was meant to catch). Watch out for memory problems. Might have some transient problem, thiugh.
BM
Yep, the null pointer was why I posted it for you to take a look at. However I agree, this is family daily driver WinBox so virtually anything's possible, but I work pretty hard to make them as stable as possible. ;-)
Usually stuff like this happens when it's trying to tell me it would like the dust bunnies removed from it, but it just had a maintenance cycle recently so I wouldn't have even mentioned it if it hadn't been for the 105.
Like I said though, the worst part is it was 4 1/2 hours away from having this WU safely in the MSD 'bank' once and for all, but now there's someone running a trailer because of some random WinGlitch most likely. :-/
RE: RE: Don't know how
)
Yep, the null pointer was why I posted it for you to take a look at. However I agree, this is family daily driver WinBox so virtually anything's possible, but I work pretty hard to make them as stable as possible. ;-)
Usually stuff like this happens when it's trying to tell me it would like the dust bunnies removed from it, but it just had a maintenance cycle recently so I wouldn't have even mentioned it if it hadn't been for the 105.
Like I said though, the worst part is it was 4 1/2 hours away from having this WU safely in the MSD 'bank' once and for all, but now there's someone running a trailer because of some random WinGlitch most likely. :-/
Alinator