Vista - BSOD on W2K8 running on Virtual Server

I have a W2k3 x64 with 3 virtual mach: 2 are W2K8 and one W2k3. Almost at
the same random time, the two W2K8 virtual machines reset itself and reboot,
however the W2K3 stays up and running. This process repeats itself every
night. Looks like the error is on 0x8E_nt!PoIdle+34b but searching gives me
no clue
Your advise is highly appreciated.



Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini122308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\backup*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1)
UP Checked x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 6001.18000.x86chk.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x81817000 PsLoadedModuleList = 0x81c0c310
Debug session time: Tue Dec 23 03:35:18.417 2008 (GMT-5)
System Uptime: 50 days 15:53:14.749 (checked kernels begin at 49 days)
Loading Kernel Symbols
................................................................
.................................................................
.........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000420, 82079564, 81990bb0, 0}

Probably caused by : ntkrnlmp.exe ( nt!PoIdle+34b )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000420, The exception code that was not handled
Arg2: 82079564, The address that the exception occurred at
Arg3: 81990bb0, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000420 - <Unable to get error code text>

FAULTING_IP:
hal!HalpGenerateConsistentPmTimerRead+46
82079564 cd2c int 2Ch

TRAP_FRAME: 81990bb0 -- (.trap 0xffffffff81990bb0)
ErrCode = 00000000
eax=004b4954 ebx=0000000a ecx=00000000 edx=00000408 esi=004b29b5 edi=00000000
eip=82079564 esp=81990c24 ebp=81990c78 iopl=0 nv up di pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000046
hal!HalpGenerateConsistentPmTimerRead+0x46:
82079564 cd2c int 2Ch
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0x8E

PROCESS_NAME: System

CURRENT_IRQL: 1c

LAST_CONTROL_TRANSFER: from 8207979f to 82079564

STACK_TEXT:
81990c2c 8207979f 8207fe16 81993b00 00000000
hal!HalpGenerateConsistentPmTimerRead+0x46
81990c78 82080b0e 8185da02 00000030 81990d50
hal!HalpQueryBrokenPmTimerCount+0x55
81990c78 8207fe16 8185da02 00000030 81990d50 hal!Halp8254ClockInterrupt+0x11a
81990cf8 81929023 00000000 81997100 81993b00 hal!HalProcessorIdle+0x2
81990d50 8196efef 00000000 0000000e 00000000 nt!PoIdle+0x34b
81990d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xf

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PoIdle+34b
81929023 5f pop edi

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!PoIdle+34b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 479185e5

FAILURE_BUCKET_ID: 0x8E_nt!PoIdle+34b

BUCKET_ID: 0x8E_nt!PoIdle+34b

Followup: MachineOwner
---------