Need help with Windbg log


L

L

I have been having Blue Screen errors & I was able to open the dmp files
with Windbg.

Can someone look at the file & ell me what the problem could be?


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols
http://msdl.microsoft.com/download/symbols;SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Mar 16 22:57:35.937 2009 (GMT-4)
System Uptime: 0 days 0:03:02.515
Loading Kernel Symbols
................................................................
.................................................................
.............
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf82436a, f6da79f8, 0}

Probably caused by : win32k.sys ( win32k!SpeedHitTest+1c )

Followup: MachineOwner
---------

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: bf82436a, The address that the exception occurred at
Arg3: f6da79f8, 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:
win32k!SpeedHitTest+1c
bf82436a f6462310 test byte ptr [esi+23h],10h

TRAP_FRAME: f6da79f8 -- (.trap 0xfffffffff6da79f8)
ErrCode = 00000000
eax=bc6406e8 ebx=000001d3 ecx=e368a3a0 edx=00007f03 esi=3c684e08 edi=000001c0
eip=bf82436a esp=f6da7a6c ebp=f6da7a78 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!SpeedHitTest+0x1c:
bf82436a f6462310 test byte ptr [esi+23h],10h
ds:0023:3c684e2b=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from bf8243c8 to bf82436a

STACK_TEXT:
f6da7a78 bf8243c8 bc6406e8 000001c0 000001d3 win32k!SpeedHitTest+0x1c
f6da7a8c bf885998 804e37aa 00000001 00000000 win32k!zzzSetFMouseMoved+0x42
f6da7ad4 bf89fc64 00000022 006efff4 bf801087
win32k!ProcessQueuedMouseEvents+0x1c8
f6da7d30 bf884635 f6db7490 00000002 f6da7d54 win32k!RawInputThread+0x5b9
f6da7d40 bf8010aa f6db7490 f6da7d64 006efff4
win32k!xxxCreateSystemThreads+0x60
f6da7d54 804dd99f 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f6da7d54 7c90e4f4 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SpeedHitTest+1c
bf82436a f6462310 test byte ptr [esi+23h],10h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SpeedHitTest+1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9

FAILURE_BUCKET_ID: 0x8E_win32k!SpeedHitTest+1c

BUCKET_ID: 0x8E_win32k!SpeedHitTest+1c

Followup: MachineOwner
 
Ad

Advertisements

L

L

L said:
I have been having Blue Screen errors & I was able to open the dmp files
with Windbg.

Can someone look at the file & ell me what the problem could be?


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols
http://msdl.microsoft.com/download/symbols;SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Mar 16 22:57:35.937 2009 (GMT-4)
System Uptime: 0 days 0:03:02.515
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf82436a, f6da79f8, 0}

Probably caused by : win32k.sys ( win32k!SpeedHitTest+1c )

Followup: MachineOwner
---------

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: bf82436a, The address that the exception occurred at
Arg3: f6da79f8, 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:
win32k!SpeedHitTest+1c
bf82436a f6462310 test byte ptr [esi+23h],10h

TRAP_FRAME: f6da79f8 -- (.trap 0xfffffffff6da79f8)
ErrCode = 00000000
eax=bc6406e8 ebx=000001d3 ecx=e368a3a0 edx=00007f03 esi=3c684e08 edi=000001c0
eip=bf82436a esp=f6da7a6c ebp=f6da7a78 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!SpeedHitTest+0x1c:
bf82436a f6462310 test byte ptr [esi+23h],10h
ds:0023:3c684e2b=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from bf8243c8 to bf82436a

STACK_TEXT:
f6da7a78 bf8243c8 bc6406e8 000001c0 000001d3 win32k!SpeedHitTest+0x1c
f6da7a8c bf885998 804e37aa 00000001 00000000 win32k!zzzSetFMouseMoved+0x42
f6da7ad4 bf89fc64 00000022 006efff4 bf801087
win32k!ProcessQueuedMouseEvents+0x1c8
f6da7d30 bf884635 f6db7490 00000002 f6da7d54 win32k!RawInputThread+0x5b9
f6da7d40 bf8010aa f6db7490 f6da7d64 006efff4
win32k!xxxCreateSystemThreads+0x60
f6da7d54 804dd99f 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f6da7d54 7c90e4f4 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SpeedHitTest+1c
bf82436a f6462310 test byte ptr [esi+23h],10h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SpeedHitTest+1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9

FAILURE_BUCKET_ID: 0x8E_win32k!SpeedHitTest+1c

BUCKET_ID: 0x8E_win32k!SpeedHitTest+1c

Followup: MachineOwner
---------

Thanks, L

i Have 3 other files as well that I do not know what the problem could be-
 
Ad

Advertisements

J

John

You should try Google, and search for BugCheck 1000008E

L said:
L said:
I have been having Blue Screen errors & I was able to open the dmp files
with Windbg.

Can someone look at the file & ell me what the problem could be?


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini031609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols
http://msdl.microsoft.com/download/symbols;SRV*C:\tempfolder*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Mar 16 22:57:35.937 2009 (GMT-4)
System Uptime: 0 days 0:03:02.515
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf82436a, f6da79f8, 0}

Probably caused by : win32k.sys ( win32k!SpeedHitTest+1c )

Followup: MachineOwner
---------

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: bf82436a, The address that the exception occurred at
Arg3: f6da79f8, 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:
win32k!SpeedHitTest+1c
bf82436a f6462310 test byte ptr [esi+23h],10h

TRAP_FRAME: f6da79f8 -- (.trap 0xfffffffff6da79f8)
ErrCode = 00000000
eax=bc6406e8 ebx=000001d3 ecx=e368a3a0 edx=00007f03 esi=3c684e08 edi=000001c0
eip=bf82436a esp=f6da7a6c ebp=f6da7a78 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!SpeedHitTest+0x1c:
bf82436a f6462310 test byte ptr [esi+23h],10h
ds:0023:3c684e2b=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: csrss.exe

LAST_CONTROL_TRANSFER: from bf8243c8 to bf82436a

STACK_TEXT:
f6da7a78 bf8243c8 bc6406e8 000001c0 000001d3 win32k!SpeedHitTest+0x1c
f6da7a8c bf885998 804e37aa 00000001 00000000 win32k!zzzSetFMouseMoved+0x42
f6da7ad4 bf89fc64 00000022 006efff4 bf801087
win32k!ProcessQueuedMouseEvents+0x1c8
f6da7d30 bf884635 f6db7490 00000002 f6da7d54 win32k!RawInputThread+0x5b9
f6da7d40 bf8010aa f6db7490 f6da7d64 006efff4
win32k!xxxCreateSystemThreads+0x60
f6da7d54 804dd99f 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f6da7d54 7c90e4f4 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SpeedHitTest+1c
bf82436a f6462310 test byte ptr [esi+23h],10h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SpeedHitTest+1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9

FAILURE_BUCKET_ID: 0x8E_win32k!SpeedHitTest+1c

BUCKET_ID: 0x8E_win32k!SpeedHitTest+1c

Followup: MachineOwner
---------

Thanks, L

i Have 3 other files as well that I do not know what the problem could be-
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

windbg symbols 2
Operate WinDbg remotely? 0
How to use WinDbg 1
windbg - symbols error 2
Stop 0x50 w/ Verifier & WinDBG loaded 8

Top