i just installed a new vm guest running windows 2008 enterprise 32bit sp2 integrated and all windows updates. it also has vmware tools installed.
the server is running active directory but doesnt hold any fsmo roles yet. it uses 1GB ram, 30GB hard drive space.
it seems to randomly blue screen and i am not able to figure out why it does this.
the host system is a Pentium 4 with Hyper Threading single core 3ghz and 4gb ram. i setup the vm to use 2 cpu's since the host has HT enabled.but the host cpu does lack VT on the cpu and bios....
now my question is, what can i do about this? i need vmware guests to work on this computer. i know i cant run x64 guests, but 32bit "should" work fine....
anyways the memory.dmp file output from windbg is as follows:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File C:\Windows\MEMORY.DMP
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRVc:\localsymbolshttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: LanManNt, suite: Enterprise TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x81638000 PsLoadedModuleList = 0x8174fc70
Debug session time: Thu Jul 16 05:52:55.538 2009 (GMT-4)
System Uptime: 0 days 4:08:55.953
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*
Bugcheck Analysis *
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {1002, 2, 1, 847092ff}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2e1 )
Followup: MachineOwner
-
1: kd> !analyze -v
*******************************************************************************
*
Bugcheck Analysis *
*
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00001002, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 847092ff, address which referenced memory
Debugging Details:
-
WRITE_ADDRESS: 00001002
CURRENT_IRQL: 2
FAULTING_IP:
+6dd4952f02d5dba0
847092ff c60001 mov byte ptr ,1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 803ecc78 -- (.trap 0xffffffff803ecc78)
ErrCode = 00000002
eax=00001002 ebx=847092c8 ecx=803d2b08 edx=0000281e esi=803d2b00 edi=803d1120
eip=847092ff esp=803eccec ebp=803ecd50 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
847092ff c60001 mov byte ptr ,1 ds:0023:00001002=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 847092ff to 81685fb9
STACK_TEXT:
803ecc78 847092ff badb0d00 0000281e 816155ec nt!KiTrap0E+0x2e1
WARNING: Frame IP not in any known module. Following frames may be wrong.
803ecce8 816e26a2 847092c8 091f4060 00000000 0x847092ff
803ecd50 816e087d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
803ecd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+2e1
81685fb9 833d846c768100 cmp dword ptr ,0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+2e1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2e1
BUCKET_ID: 0xD1_nt!KiTrap0E+2e1
Followup: MachineOwner