Probably caused by : sr.sys ( sr!SrpGetFileName+b4 )

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


Loading Dump File [c:\windows\minidump\Mini060908-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\windows\symbols
Executable search path is: c:\windows\i386
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Jun 9 20:50:51.265 2008 (GMT+3)
System Uptime: 0 days 7:04:13.866
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
Unable to load image sr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sr.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

Probably caused by : sr.sys ( sr!SrpGetFileName+b4 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: ashWebSv.exe

LAST_CONTROL_TRANSFER: from f74178ae to 804daf84

STACK_TEXT:
b075b6d4 f74178ae b075b7fc b075b7d2 0000004e nt!RtlPrefetchCopyMemory+0x31
b075b6f4 f7418723 0000002e 0000007c 00000052 sr!SrpGetFileName+0xb4
b075b708 f74187a0 8a03dc80 87a22778 00040020 sr!SrpExpandFileName+0x45
b075b730 f74113e2 8a03dc80 87a22778 0141b500 sr!SrIsFileEligible+0x5a
b075b8d0 f7411aef 8a03dc80 87a22778 00040020 sr!SrCreateContext+0x13e
b075b8fc f7415169 00000000 8a03dd78 00040020 sr!SrGetContext+0xc9
b075b948 f7413a22 8a03dc80 00040020 87a22778 sr!SrHandleEvent+0x35
b075b9ac 804e13c9 00000000 00000002 87956bf0 sr!SrCreate+0x2fc
b075b9ac 87946008 00000000 00000002 87956bf0 nt!KiTrap0D+0x483
WARNING: Frame IP not in any known module. Following frames may be wrong.
87956dc8 00000000 00000000 00000000 00000000 0x87946008


STACK_COMMAND: kb

FOLLOWUP_IP:
sr!SrpGetFileName+b4
f74178ae ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: sr!SrpGetFileName+b4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sr

IMAGE_NAME: sr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 480252c2

FAILURE_BUCKET_ID: 0x7f_d_sr!SrpGetFileName+b4

BUCKET_ID: 0x7f_d_sr!SrpGetFileName+b4

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