You may want (if possible) to change it from automatically rebooting on
crash to not while you get the "blue acreen" information off the monitor
(stop code and the paramaters after it and the description) before you
reboot it. This may help point in a direction that you can do something
with, but you would really need to probably contact MS to debug the dump to
determine the exact cause.
Don't know what might have changed just prior to this happening, or what was
added/changed since it's last scheduled reboot, but that could be important.
Also try running a different "flavor" of AV on the box to see what you get
(some free versions from web are available). Some are better at picking
some things up that others miss, and I've worked with numerous customers
that have done that, and to their surpirse found things they didn't know
about. Not saying it is that, but doesn't hurt to be sure.
You might also open task mgr (poor mans's performance monitor) and monitor
it during that 67 min just to see if anything starts taking large amounts of
cpu or mem prior.
--
David Brandt
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
