Hyper-V Virtual Machine Management service terminates unexpectedly

rebuilt server windows 2008 enterprise , hyper-v role.  migrated several vms old vs2005 r2 environment.  receiving following errors in system , application event logs several times day.  allowing server report errors microsoft.  fact 1 of hyper-v management services restarting leaves me more little concerned system's stablity. 

has seen these errors , have suggestions on solutions??

thanks in advance help!
todd

system event log:
log name:      system
source:        service control manager
date:          8/18/2008 4:03:53 pm
event id:      7031
task category: none
level:         error
keywords:      classic
user:          n/a
computer:      server1.domain.local
description:
the hyper-v virtual machine management service terminated unexpectedly.  has done 1 time(s).  following corrective action taken in 120000 milliseconds: restart service.
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <system>
    <provider name="service control manager" guid="{removed guid}" eventsourcename="service control manager" />
    <eventid qualifiers="49152">7031</eventid>
    <version>0</version>
    <level>2</level>
    <task>0</task>
    <opcode>0</opcode>
    <keywords>0x80000000000000</keywords>
    <timecreated systemtime="2008-08-18t23:03:53.000z" />
    <eventrecordid>7934</eventrecordid>
    <correlation />
    <execution processid="0" threadid="0" />
    <channel>system</channel>
    <computer>server1.domain.local</computer>
    <security />
  </system>
  <eventdata>
    <data name="param1">hyper-v virtual machine management</data>
    <data name="param2">1</data>
    <data name="param3">120000</data>
    <data name="param4">1</data>
    <data name="param5">restart service</data>
  </eventdata>
</event>

application log:
log name:      application
source:        application error
date:          8/18/2008 4:03:50 pm
event id:      1000
task category: (100)
level:         error
keywords:      classic
user:          n/a
computer:      server1.domain.local
description:
faulting application vmms.exe, version 6.0.6001.18016, time stamp 0x484fc22e, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000374, fault offset 0x00000000000a6e97, process id 0xf94, application start time 0x01c9017605710543.
event xml:
<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <system>
    <provider name="application error" />
    <eventid qualifiers="0">1000</eventid>
    <level>2</level>
    <task>100</task>
    <keywords>0x80000000000000</keywords>
    <timecreated systemtime="2008-08-18t23:03:50.000z" />
    <eventrecordid>368</eventrecordid>
    <channel>application</channel>
    <computer>server1.domain.local</computer>
    <security />
  </system>
  <eventdata>
    <data>vmms.exe</data>
    <data>6.0.6001.18016</data>
    <data>484fc22e</data>
    <data>ntdll.dll</data>
    <data>6.0.6001.18000</data>
    <data>4791adec</data>
    <data>c0000374</data>
    <data>00000000000a6e97</data>
    <data>f94</data>
    <data>01c9017605710543</data>
  </eventdata>
</event>

mike,
i found source of issue don't understand why.

one of vms have runs utility apps such wsus, symantec system center, , spiceworks (system monitoring via wmi).  turns out everytime spiceworks scan ran, caused the hyper-v virtual machine management service terminate unexpectedly.  scheduled scan ran every 2 hours , mirrored times of failures.  verified behavior disabling scheduled scans , running couple of scans manually.  since disabling scheduled scans failures i've encountered during 2 manual scans.  it's been 24hrs.

the wmi related changes have made default windows 2008 installation enable remote hyper-v management vista sp1 desktop following instructions in john howard's blog (http://blogs.technet.com/jhoward/archive/2008/03/28/part-1-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx).  account running spiceworks network scan in domain security group used configuration.

does make sense?  don't understand how scenario can cause management service terminate.

thanks,
todd

Windows Server  >  Hyper-V