winXP OS crash

[karthik]

WindowsXP os crashed with bug check BugCheck 1000008E, {c000001d, 8844cfdd, 9fa2c8f4, 0}

I have attatched the minidump, and the analysis report is as follows.

1: 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: c000001d, The exception code that was not handled Arg2: 8844cfdd, The address that the exception occurred at Arg3: 9fa2c8f4, Trap Frame Arg4: 00000000

Debugging Details:

---

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP: +ffffffff8844cfdd 8844cfdd 0f01db vmsave eax

TRAP_FRAME: 9fa2c8f4 -- (.trap 0xffffffff9fa2c8f4) ErrCode = 00000000 eax=08784000 ebx=88443880 ecx=08784000 edx=00000000 esi=88443880 edi=8877d000 eip=8844cfdd esp=9fa2c968 ebp=9fa2c994 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 8844cfdd 0f01db vmsave eax Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: VirtualBox.exe

LAST_CONTROL_TRANSFER: from 8844e538 to 8844cfdd

FAILED_INSTRUCTION_ADDRESS: +ffffffff8844cfdd 8844cfdd 0f01db vmsave eax

STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 9fa2c994 8844e538 08784000 00000000 0877d000 0x8844cfdd 9fa2cba4 8844bc8d 8841f000 88443580 88443880 0x8844e538 9fa2cbd4 8845697c 8841f000 88443580 00000000 0x8844bc8d 9fa2cc08 9f985e95 8841f000 00000000 00000001 0x8845697c 9fa2cc1c 9f985741 00228107 00000000 88964c18 VBoxDrv+0xe95 9fa2cc40 804ef19f 00964b60 88843bc0 806e6410 VBoxDrv+0x741 9fa2cc64 805807f7 88964b60 8895ae70 89a57cb8 ntMiFlushSectionInternal+0x256 9fa2cd00 80579274 00000f90 00000000 00000000 ntNtSetInformationThread+0x125 9fa2cd34 8054162c 00000f90 00000000 00000000 ntSepOpenTokenOfThread+0x87 9fa2cd64 7c90e514 badb0d00 0228fda8 a08a9d98 nt!RtlIpv4StringToAddressExW+0xad 9fa2cd78 00000000 00000000 00000000 00000000 0x7c90e514

STACK_COMMAND: kb

FOLLOWUP_IP: VBoxDrv+e95 9f985e95 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: VBoxDrv+e95

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: VBoxDrv

IMAGE_NAME: VBoxDrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a202585

FAILURE_BUCKET_ID: 0x8E_BAD_IP_VBoxDrv+e95

BUCKET_ID: 0x8E_BAD_IP_VBoxDrv+e95

Followup: MachineOwner

---

Karthik SG

[karthik]

OS dump

[Sander van Leeuwen]

Try again with 3.0.6 please.

[Sander van Leeuwen]

If it happens with that version as well, then please also attach VBox.log from that session.

[Sander van Leeuwen]

Also make sure you do not run any virtualization software (e.g. VMWare/VPC) at the same time.

[Technologov]

No answer.

Please Close as INVALID.

-Technologov