I receive a blue bosd, this is the analysys of my memory.dmp with WinDbg. I need your help. What happens????
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [H:\Program Files\Debugging Tools for Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 = 0x80800000 PsLoadedModuleList = 0x8087c1a0
Debug session time: Fri Jul 28 13:47:03.250 2006 (GMT+3)
System Uptime: 0 days 0:03:49.853
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {c0000005, 8089fb3f, b9aaf9f0, 0}
Probably caused by : hardware ( nt!IopParseDevice+1e3 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 8089fb3f, The address that the exception occurred at
Arg3: b9aaf9f0, 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!IopParseDevice+1e3
8089fb3f 0000 add byte ptr [eax],al
TRAP_FRAME: b9aaf9f0 -- (.trap ffffffffb9aaf9f0)
ErrCode = 00000002
eax=00100003 ebx=863938b8 ecx=0000bb40 edx=00000004 esi=8627b9c8 edi=850792b0
eip=8089fb3f esp=b9aafa64 ebp=b9aafb3c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!IopParseDevice+0x1e3:
8089fb3f 0000 add byte ptr [eax],al ds:0023:00100003=??
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: smc.exe
MISALIGNED_IP:
nt!IopParseDevice+1e3
8089fb3f 0000 add byte ptr [eax],al
LAST_CONTROL_TRANSFER: from 80825973 to 80821925
STACK_TEXT:
b9aaf5b8 80825973 0000008e c0000005 8089fb3f nt!KeBugCheckEx+0x1b
b9aaf980 80866251 b9aaf99c 00000000 b9aaf9f0 nt!KiDispatchException+0x3b1
b9aaf9e8 80866202 b9aafb3c 8089fb3f badb0d00 nt!CommonDispatchException+0x4d
b9aafa34 8089fb17 b9aafb2c 00000030 850792b0 nt!KiExceptionExit+0x18a
b9aafb3c 808dc642 868248b8 00000000 8627b9c8 nt!IopParseDevice+0x1bb
b9aafbc4 808d8b23 00000000 b9aafc04 00000040 nt!ObpLookupObjectName+0x56a
b9aafc18 8089311d 00000000 00000000 00000001 nt!ObOpenObjectByName+0xeb
b9aafc94 80893a94 036de4b0 00100003 036de488 nt!IopCreateFile+0x407
b9aafcf0 80896166 036de4b0 00100003 036de488 nt!IoCreateFile+0x8e
b9aafd30 80865808 036de4b0 00100003 036de488 nt!NtCreateFile+0x30
b9aafd30 7c90eb94 036de4b0 00100003 036de488 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
036de5bc 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!IopParseDevice+1e3
8089fb3f 0000 add byte ptr [eax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IopParseDevice+1e3
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [H:\Program Files\Debugging Tools for Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 = 0x80800000 PsLoadedModuleList = 0x8087c1a0
Debug session time: Fri Jul 28 13:47:03.250 2006 (GMT+3)
System Uptime: 0 days 0:03:49.853
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {c0000005, 8089fb3f, b9aaf9f0, 0}
Probably caused by : hardware ( nt!IopParseDevice+1e3 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 8089fb3f, The address that the exception occurred at
Arg3: b9aaf9f0, 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!IopParseDevice+1e3
8089fb3f 0000 add byte ptr [eax],al
TRAP_FRAME: b9aaf9f0 -- (.trap ffffffffb9aaf9f0)
ErrCode = 00000002
eax=00100003 ebx=863938b8 ecx=0000bb40 edx=00000004 esi=8627b9c8 edi=850792b0
eip=8089fb3f esp=b9aafa64 ebp=b9aafb3c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!IopParseDevice+0x1e3:
8089fb3f 0000 add byte ptr [eax],al ds:0023:00100003=??
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: smc.exe
MISALIGNED_IP:
nt!IopParseDevice+1e3
8089fb3f 0000 add byte ptr [eax],al
LAST_CONTROL_TRANSFER: from 80825973 to 80821925
STACK_TEXT:
b9aaf5b8 80825973 0000008e c0000005 8089fb3f nt!KeBugCheckEx+0x1b
b9aaf980 80866251 b9aaf99c 00000000 b9aaf9f0 nt!KiDispatchException+0x3b1
b9aaf9e8 80866202 b9aafb3c 8089fb3f badb0d00 nt!CommonDispatchException+0x4d
b9aafa34 8089fb17 b9aafb2c 00000030 850792b0 nt!KiExceptionExit+0x18a
b9aafb3c 808dc642 868248b8 00000000 8627b9c8 nt!IopParseDevice+0x1bb
b9aafbc4 808d8b23 00000000 b9aafc04 00000040 nt!ObpLookupObjectName+0x56a
b9aafc18 8089311d 00000000 00000000 00000001 nt!ObOpenObjectByName+0xeb
b9aafc94 80893a94 036de4b0 00100003 036de488 nt!IopCreateFile+0x407
b9aafcf0 80896166 036de4b0 00100003 036de488 nt!IoCreateFile+0x8e
b9aafd30 80865808 036de4b0 00100003 036de488 nt!NtCreateFile+0x30
b9aafd30 7c90eb94 036de4b0 00100003 036de488 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
036de5bc 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!IopParseDevice+1e3
8089fb3f 0000 add byte ptr [eax],al
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IopParseDevice+1e3
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------