According to the dump, one of your CPUs was hung up and not responding to a clock interrupt request:
Code:
0: kd> !thread
GetPointerFromAddress: unable to read from fffff800028f7000
THREAD fffffa8005e45060 Cid 1be8.0dd4 Teb: 000007fffff8c000 Win32Thread: fffff900c2da8c30 RUNNING on processor 0
IRP List:
Unable to read nt!_IRP @ fffffa800c08b8f0
Not impersonating
GetUlongFromAddress: unable to read from fffff80002835b74
Owning Process fffffa800bd42760 Image: VirtualBox.exe
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 616026
Context Switch Count 10996810 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address 0x0000000074973810
Stack Init fffff8800e142db0 Current fffff8800e1425b0
Base fffff8800e143000 Limit fffff8800e13c000 Call 0
Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
fffff880`0e142188 fffff800`0266d453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b8180 : nt!KeBugCheckEx
fffff880`0e142190 fffff800`026c7de7 : 00000000`00000000 fffff800`00000001 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`0e142220 fffff800`02610895 : fffff800`02635460 fffff880`0e1423d0 fffff800`02635460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0e142320 fffff800`026bbc33 : 00000000`00000001 00000000`4f903cec fffff800`026cbb25 fffff880`0e1422b8 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0e142350 fffff800`0276f546 : fffff800`02839e80 00000000`00000000 fffff880`00b41000 fffff880`0afc36d6 : nt!KiInterruptDispatchNoLock+0x163 (TrapFrame @ fffff880`0e142350)
fffff880`0e1424e0 fffff880`0461ed83 : fffff880`0461ed40 00000000`00000000 00000000`00000002 fffff880`00b41000 : nt!KeIpiGenericCall+0x136
fffff880`0e142550 fffff880`0461ed40 : 00000000`00000000 00000000`00000002 fffff880`00b41000 fffff880`00b420a8 : VBoxDrv+0x12d83
fffff880`0e142558 00000000`00000000 : 00000000`00000002 fffff880`00b41000 fffff880`00b420a8 fffff880`0461efa7 : VBoxDrv+0x12d40
0: kd> lmvm VBoxDrv
start end module name
fffff880`0460c000 fffff880`0463bec0 VBoxDrv T (no symbols)
Loaded symbol image file: VBoxDrv.sys
Image path: \SystemRoot\system32\DRIVERS\VBoxDrv.sys
Image name: VBoxDrv.sys
Timestamp: Thu Aug 05 08:02:51 2010 (4C5AA86B)
CheckSum: 00031C73
ImageSize: 0002FEC0
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 4000
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 26 Stepping 5
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
Update Signature = REG_BINARY 0,0,0,0,11,0,0,0
Update Status = REG_DWORD 0
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 1100000000
Processor may be overclocked!
Expected Frequency: 2670
Actual Frequency: 4000
Overclock Ratio: 1.49
You might want to start by removing the overclock and seeing if the problem continues.
Quote