- Thread Author
-
- #1
dump
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: c0000005, The exception code that was not handled
Arg2: bf8ed7f7, The address that the exception occurred at
Arg3: a8e824f8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
win32k!XLATE: fnXlateBetweenBitfields+6
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
TRAP_FRAME: a8e824f8 -- (.trap 0xffffffffa8e824f8)
ErrCode = 00000000
eax=ffffffc2 ebx=04580140 ecx=00000000 edx=00000000 esi=001a00a8 edi=0000000a
eip=bf8ed7f7 esp=a8e8256c ebp=a8e825a0 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
win32k!XLATE: fnXlateBetweenBitfields+0x6:
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h] ds:0023:00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: LinkMain.exe
LAST_CONTROL_TRANSFER: from bf966c5a to bf8ed7f7
STACK_TEXT:
a8e82568 bf966c5a 00000000 00000011 e266c018 win32k!XLATE: fnXlateBetweenBitfields+0x6
a8e825a0 bf836b4e bf9a5ea8 00000000 0019fea8 win32k!vSrcCopyS16D24+0x4e
a8e827b4 bf844f5f e3397b50 00000000 00000000 win32k!EngCopyBits+0x51a
a8e82870 bf8455d9 00000018 00000000 00000011 win32k!GreGetDIBitsInternal+0x79f
a8e82908 8054161c 05010161 0605027f 00000000 win32k!NtGdiGetDIBitsInternal+0x27e
a8e82908 7c90e4f4 05010161 0605027f 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00115274 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!XLATE: fnXlateBetweenBitfields+6
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!XLATE: fnXlateBetweenBitfields+6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
FAILURE_BUCKET_ID: 0x8E_win32k!XLATE: fnXlateBetweenBitfields+6
BUCKET_ID: 0x8E_win32k!XLATE: fnXlateBetweenBitfields+6
Followup: MachineOwner
---------
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: c0000005, The exception code that was not handled
Arg2: bf8ed7f7, The address that the exception occurred at
Arg3: a8e824f8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"
FAULTING_IP:
win32k!XLATE:
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
TRAP_FRAME: a8e824f8 -- (.trap 0xffffffffa8e824f8)
ErrCode = 00000000
eax=ffffffc2 ebx=04580140 ecx=00000000 edx=00000000 esi=001a00a8 edi=0000000a
eip=bf8ed7f7 esp=a8e8256c ebp=a8e825a0 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
win32k!XLATE:
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h] ds:0023:00000010=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: LinkMain.exe
LAST_CONTROL_TRANSFER: from bf966c5a to bf8ed7f7
STACK_TEXT:
a8e82568 bf966c5a 00000000 00000011 e266c018 win32k!XLATE:
a8e825a0 bf836b4e bf9a5ea8 00000000 0019fea8 win32k!vSrcCopyS16D24+0x4e
a8e827b4 bf844f5f e3397b50 00000000 00000000 win32k!EngCopyBits+0x51a
a8e82870 bf8455d9 00000018 00000000 00000011 win32k!GreGetDIBitsInternal+0x79f
a8e82908 8054161c 05010161 0605027f 00000000 win32k!NtGdiGetDIBitsInternal+0x27e
a8e82908 7c90e4f4 05010161 0605027f 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00115274 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!XLATE:
bf8ed7f7 8b4910 mov ecx,dword ptr [ecx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!XLATE:
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
FAILURE_BUCKET_ID: 0x8E_win32k!XLATE:
BUCKET_ID: 0x8E_win32k!XLATE:
Followup: MachineOwner
---------
Solution
Hi,
thanks for posting the dmp file. If possible it's always better for us if you can send more than one. Looking through the dmp you sent i see your using XP. I also notice that non of your drivers are older than 2008 and may need updating. Can you also read the thread found here and post the results:
Link Removed
thanks for posting the dmp file. If possible it's always better for us if you can send more than one. Looking through the dmp you sent i see your using XP. I also notice that non of your drivers are older than 2008 and may need updating. Can you also read the thread found here and post the results:
Link Removed
- Thread Author
-
- #3
This is dump file.Can you post the actual dump file instead of just the analysis?
Attachments
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Hi,
thanks for posting the dmp file. If possible it's always better for us if you can send more than one. Looking through the dmp you sent i see your using XP. I also notice that non of your drivers are older than 2008 and may need updating. Can you also read the thread found here and post the results:
Link Removed
thanks for posting the dmp file. If possible it's always better for us if you can send more than one. Looking through the dmp you sent i see your using XP. I also notice that non of your drivers are older than 2008 and may need updating. Can you also read the thread found here and post the results:
Link Removed
Last edited:
- Thread Author
-
- #5
This is dump file.
I have just one dump file. so next time if I have more dump file, I will make compressed file.Hi,
thanks for posting the dmp file. If possible it's always better for us if you can send more than one. Looking through the dmp you sent i see your using XP. I also notice that non of your drivers are older than 2008 and may need updating. Can you also read the thread found here and post the results:
Link Removed
Thank you your notice.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Hi,
thanks for your post. Could you please read the web page i mentioned and post the results as it will be a real help especially as we have only one dmp file.
I/We need to know what machine (make and model) your using and posting the results will give us that info.
thanks for your post. Could you please read the web page i mentioned and post the results as it will be a real help especially as we have only one dmp file.
I/We need to know what machine (make and model) your using and posting the results will give us that info.
- Thread Author
-
- #7
Hi,Hi,
thanks for your post. Could you please read the web page i mentioned and post the results as it will be a real help especially as we have only one dmp file.
I/We need to know what machine (make and model) your using and posting the results will give us that info.
This is System infomatino file, I used cpu-z as a guide. If you have more information, just let me know.
Thank you for help.
Attachments
- Thread Author
-
- #8
Hi,Hi,
thanks for posting the dmp file. If possible it's always better for us if you can send more than one. Looking through the dmp you sent i see your using XP. I also notice that non of your drivers are older than 2008 and may need updating. Can you also read the thread found here and post the results:
Link Removed
I tried to use W7F Diagnostic Tool, but it doesn't work, just only one able to use the driver verifier.
Thank you.
- Thread Author
-
- #11
Yep!! I run as Administrator. But it not different before I tried to run.You need to right click it and choose "Run As Administrator".
error message Like this:
Link Removed this path can't find........
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Leeinhwa why not using this application here to find drivers as they really need updating:
http://www.aida64.com/downloads
As you can see from my screenshot, it will provide links if available.
Link Removed
http://www.aida64.com/downloads
As you can see from my screenshot, it will provide links if available.
Link Removed
Similar threads
- Replies
- 7
- Views
- 2K
- Solved
Windows 10
Problem with Windows 10 Symbols in windbg?
- Replies
- 3
- Views
- 7K
- Replies
- 4
- Views
- 3K
- Solved
- Replies
- 1
- Views
- 1K
- Solved
- Replies
- 2
- Views
- 2K