I have a machine with XP SP2 that pretty much runs fine. I also use VMWare which has also run fine. Whenever I start a virtual machine the machine crashes and reboots.
In the event viewer I also see:
Error code 1000008e, parameter1 c0000005, parameter2 f76f9c5d, parameter3 af982b48, parameter4 00000000.
Don't know if it's related.
Here is a dump analysis with Windbg:
!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: c0000005, The exception code that was not handled
Arg2: f76f9c5d, The address that the exception occurred at
Arg3: af982b48, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ousb2hub+2c5d
f76f9c5d 0fb64804 movzx ecx,byte ptr [eax+0x4]
TRAP_FRAME: af982b48 -- (.trap ffffffffaf982b48)
ErrCode = 00000000
eax=00000000 ebx=88432670 ecx=8a061f58 edx=8a536520 esi=8a14fd58 edi=88395fb8
eip=f76f9c5d esp=af982bbc ebp=af982bec iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
ousb2hub+0x2c5d:
f76f9c5d 0fb64804 movzx ecx,byte ptr [eax+0x4] ds:0023:00000004=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from f76f9937 to f76f9c5d
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
af982bec f76f9937 8a05dd90 88432670 00000004 ousb2hub+0x2c5d
af982c14 f76f76dc 8a05dd90 88432670 af982c6c ousb2hub+0x2937
af982c34 804e37f7 8a05dd90 88432670 806ee2d0 ousb2hub+0x6dc
af982c34 88432670 8a05dd90 88432670 806ee2d0 nt!KeUpdateSystemTime+0xba
00000001 00000000 00000000 00000000 00000000 0x88432670
FOLLOWUP_IP:
ousb2hub+2c5d
f76f9c5d 0fb64804 movzx ecx,byte ptr [eax+0x4]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: ousb2hub+2c5d
MODULE_NAME: ousb2hub
IMAGE_NAME: ousb2hub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 410fa8ce
STACK_COMMAND: .trap ffffffffaf982b48 ; kb
FAILURE_BUCKET_ID: 0x8E_ousb2hub+2c5d
BUCKET_ID: 0x8E_ousb2hub+2c5d
Followup: MachineOwner
---------
Anyone got a notion on where I can start, where I should look? I have a Belkin USB hub on the machine, don't know if that offers any clue. It's an Abit AN7 mb.
Once the VM crashes the machine the VM file is corrupted and VMWare does not recognize the VM.
HELP!!!!
In the event viewer I also see:
Error code 1000008e, parameter1 c0000005, parameter2 f76f9c5d, parameter3 af982b48, parameter4 00000000.
Don't know if it's related.
Here is a dump analysis with Windbg:
!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: c0000005, The exception code that was not handled
Arg2: f76f9c5d, The address that the exception occurred at
Arg3: af982b48, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
ousb2hub+2c5d
f76f9c5d 0fb64804 movzx ecx,byte ptr [eax+0x4]
TRAP_FRAME: af982b48 -- (.trap ffffffffaf982b48)
ErrCode = 00000000
eax=00000000 ebx=88432670 ecx=8a061f58 edx=8a536520 esi=8a14fd58 edi=88395fb8
eip=f76f9c5d esp=af982bbc ebp=af982bec iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
ousb2hub+0x2c5d:
f76f9c5d 0fb64804 movzx ecx,byte ptr [eax+0x4] ds:0023:00000004=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from f76f9937 to f76f9c5d
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
af982bec f76f9937 8a05dd90 88432670 00000004 ousb2hub+0x2c5d
af982c14 f76f76dc 8a05dd90 88432670 af982c6c ousb2hub+0x2937
af982c34 804e37f7 8a05dd90 88432670 806ee2d0 ousb2hub+0x6dc
af982c34 88432670 8a05dd90 88432670 806ee2d0 nt!KeUpdateSystemTime+0xba
00000001 00000000 00000000 00000000 00000000 0x88432670
FOLLOWUP_IP:
ousb2hub+2c5d
f76f9c5d 0fb64804 movzx ecx,byte ptr [eax+0x4]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: ousb2hub+2c5d
MODULE_NAME: ousb2hub
IMAGE_NAME: ousb2hub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 410fa8ce
STACK_COMMAND: .trap ffffffffaf982b48 ; kb
FAILURE_BUCKET_ID: 0x8E_ousb2hub+2c5d
BUCKET_ID: 0x8E_ousb2hub+2c5d
Followup: MachineOwner
---------
Anyone got a notion on where I can start, where I should look? I have a Belkin USB hub on the machine, don't know if that offers any clue. It's an Abit AN7 mb.
Once the VM crashes the machine the VM file is corrupted and VMWare does not recognize the VM.
HELP!!!!
