första omstarten:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052505-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed May 25 17:45:52.406 2005 (GMT+2)
System Uptime: 0 days 0:00:47.109
Loading Kernel Symbols
.........................................................................................................................................................
Loading unloaded module list
....
Loading User Symbols
Unable to load image SAVRT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for SAVRT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SAVRT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, ed16cc9d, 85b72b6c, 0}
Probably caused by : SAVRT.SYS ( SAVRT+34c9d )
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: ed16cc9d, The address that the exception occurred at
Arg3: 85b72b6c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p "0x%08lx" refererade till minnet p "0x%08lx". Det gick inte att utf ra en minnes tg rd. F ljande fel returnerades: The memory could not be "%s".
FAULTING_IP:
SAVRT+34c9d
ed16cc9d 0000 add [eax],al
TRAP_FRAME: 85b72b6c -- (.trap ffffffff85b72b6c)
ErrCode = 00000002
eax=00000001 ebx=e129e8d6 ecx=00000003 edx=00000032 esi=e1298210 edi=00017eff
eip=ed16cc9d esp=85b72be0 ebp=e1298008 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
SAVRT+0x34c9d:
ed16cc9d 0000 add [eax],al ds:0023:00000001=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from e1235828 to ed16cc9d
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
e1298008 e1235828 00000000 00000000 00000000 SAVRT+0x34c9d
e1237008 00000000 00000000 00000000 00000000 0xe1235828
FOLLOWUP_IP:
SAVRT+34c9d
ed16cc9d 0000 add [eax],al
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: SAVRT+34c9d
MODULE_NAME: SAVRT
IMAGE_NAME: SAVRT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 422cda85
STACK_COMMAND: .trap ffffffff85b72b6c ; kb
FAILURE_BUCKET_ID: 0x8E_SAVRT+34c9d
BUCKET_ID: 0x8E_SAVRT+34c9d
Followup: MachineOwner
---------
