D
Digikid
My pc has been giving BSOD's 6 times in the past couple of days. I
open up windb and it displays the following. Any and all help is
appreciated...thank you:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini041705-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sun Apr 17 17:36:00.453 2005 (GMT-7)
System Uptime: 0 days 13:25:17.071
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe -
Loading Kernel Symbols
.......................................................................................................................................
Loading unloaded module list
...............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8057a7aa, eb8fabe0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
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: 8057a7aa, The address that the exception occurred at
Arg3: eb8fabe0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!LpcRequestPort+205
8057a7aa f6472702 test byte ptr [edi+0x27],0x2
TRAP_FRAME: eb8fabe0 -- (.trap ffffffffeb8fabe0)
ErrCode = 00000000
eax=00000000 ebx=866a5880 ecx=0007ffd7 edx=866a58ac esi=866a5790
edi=00000000
eip=8057a7aa esp=eb8fac54 ebp=eb8fac68 iopl=0 nv up ei pl zr na
po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
nt!LpcRequestPort+0x205:
8057a7aa f6472702 test byte ptr [edi+0x27],0x2
ds:0023:00000027=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 8057a8ba to 8057a7aa
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may
be wrong.
eb8fac68 8057a8ba 866a5790 7ffd7000 857e4888 nt!LpcRequestPort+0x205
eb8fad14 8057a46a 00000000 00000000 857e4888 nt!LpcRequestPort+0x315
eb8fad34 8057aa43 857e4888 00000000 eb8fad64
nt!ExWaitForRundownProtectionRelease+0x399
eb8fad54 804de7ec 00000000 00000000 00b5ffb4 nt!LpcRequestPort+0x49e
eb8fad64 7c90eb94 badb0d00 00b5ff7c 08038000 nt!ZwYieldExecution+0xb78
00b5ffb4 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
open up windb and it displays the following. Any and all help is
appreciated...thank you:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini041705-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sun Apr 17 17:36:00.453 2005 (GMT-7)
System Uptime: 0 days 13:25:17.071
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe -
Loading Kernel Symbols
.......................................................................................................................................
Loading unloaded module list
...............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8057a7aa, eb8fabe0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
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: 8057a7aa, The address that the exception occurred at
Arg3: eb8fabe0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!LpcRequestPort+205
8057a7aa f6472702 test byte ptr [edi+0x27],0x2
TRAP_FRAME: eb8fabe0 -- (.trap ffffffffeb8fabe0)
ErrCode = 00000000
eax=00000000 ebx=866a5880 ecx=0007ffd7 edx=866a58ac esi=866a5790
edi=00000000
eip=8057a7aa esp=eb8fac54 ebp=eb8fac68 iopl=0 nv up ei pl zr na
po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
nt!LpcRequestPort+0x205:
8057a7aa f6472702 test byte ptr [edi+0x27],0x2
ds:0023:00000027=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 8057a8ba to 8057a7aa
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may
be wrong.
eb8fac68 8057a8ba 866a5790 7ffd7000 857e4888 nt!LpcRequestPort+0x205
eb8fad14 8057a46a 00000000 00000000 857e4888 nt!LpcRequestPort+0x315
eb8fad34 8057aa43 857e4888 00000000 eb8fad64
nt!ExWaitForRundownProtectionRelease+0x399
eb8fad54 804de7ec 00000000 00000000 00b5ffb4 nt!LpcRequestPort+0x49e
eb8fad64 7c90eb94 badb0d00 00b5ff7c 08038000 nt!ZwYieldExecution+0xb78
00b5ffb4 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------