Advertisement
|
[x]
Attachment Details
|
||
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: 43: 44: 45: 46: 47: 48: 49: 50: 51: 52: 53: 54: 55: 56: 57: 58: 59: 60: 61: 62: 63: 64: 65: 66: 67: 68: 69: 70: 71: 72: 73: 74: 75: 76: 77: 78: 79: 80: 81: 82: 83: 84: 85: 86: |
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: 8063547f, The address that the exception occurred at Arg3: aadcc99c, 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: nt!HvpGetCellMapped+5f 8063547f 8b4304 mov eax,dword ptr [ebx+4] TRAP_FRAME: aadcc99c -- (.trap 0xffffffffaadcc99c) ErrCode = 00000000 eax=00000d00 ebx=00000d00 ecx=865e8008 edx=00000003 esi=e1037008 edi=00000020 eip=8063547f esp=aadcca10 ebp=aadcca58 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!HvpGetCellMapped+0x5f: 8063547f 8b4304 mov eax,dword ptr [ebx+4] ds:0023:00000d04=???????? Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: services.exe LAST_CONTROL_TRANSFER: from 8062de84 to 8063547f STACK_TEXT: aadcca58 8062de84 e1037008 006d0020 e1037008 nt!HvpGetCellMapped+0x5f aadcca74 80636cdc e1037008 e13c6dec e1037008 nt!CmpMarkValueDataDirty+0x44 aadcca90 80636f81 e1037008 003c59a8 e1560d9c nt!CmpMarkKeyValuesDirty+0xcc aadccaac 8063701e e1037008 003c59a8 e14059ac nt!CmpFreeKeyValues+0x17 aadccae8 8063785c e1037008 001498c0 e11898c4 nt!CmpSyncKeyValues+0x26 aadccb2c 806379cf e28be000 00000400 00000001 nt!CmpCopySyncTree2+0x1f4 aadccb5c 80624489 e1037008 000001b8 e1037008 nt!CmpCopySyncTree+0x4f aadccccc 806200da 00010002 aadccd64 aadccce8 nt!CmpSaveBootControlSet+0x2a7 aadcccdc 8054070c 00000004 aadccd64 804ff8c5 nt!NtInitializeRegistry+0x5e aadcccdc 804ff8c5 00000004 aadccd64 804ff8c5 nt!KiFastCallEntry+0xfc aadccd58 8054070c 00000004 0007fe8c 7c90eb94 nt!ZwInitializeRegistry+0x11 aadccd58 7c90eb94 00000004 0007fe8c 7c90eb94 nt!KiFastCallEntry+0xfc WARNING: Frame IP not in any known module. Following frames may be wrong. 0007fe8c 00000000 00000000 00000000 00000000 0x7c90eb94 STACK_COMMAND: kb FOLLOWUP_IP: nt!HvpGetCellMapped+5f 8063547f 8b4304 mov eax,dword ptr [ebx+4] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!HvpGetCellMapped+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 434c50c7 FAILURE_BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f BUCKET_ID: 0x8E_nt!HvpGetCellMapped+5f Followup: MachineOwner |
|
[x]
The Solution Rating System
|
||
|
With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
Your Input Matters If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
||
|
Loading Advertisement... |