Re: SBS 2003 BOSD (mrxdav.sys), Help Needed Please

Well the unit is located at our DataCenter, so I would have to go onsite to
check. But maybe you misunderstood, the unit did boot and working is fine
now, but I wanted to make sure we did not have a driver or major issue that
we need to correct before it got worst and not repairable.

"Cris Hanna [SBS - MVP]" wrote:

Again, can you boot to safe mode or last know good configuration?

--
Cris Hanna [SBS - MVP]
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.
"Webspeedway" <Webspeedway@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F1D214D2-0A71-4973-99C4-918124EB7A10@xxxxxxxxxxxxxxxx
Well I was doing a mant. reboot last night.. and the system just sat at
applying computer setiings for 15-20 minutes; logging DCOM erros in the
system event log, before it went off the grid. Then rebooted and came back
in
with the notfication of a BSOD.

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 8/4/2008
Time: 9:50:00 PM
User: NT AUTHORITY\SYSTEM
Computer: SERVER
Description:
The application-specific permission settings do not grant Local Launch
permission for the COM Server application with CLSID
{9DA0E103-86CE-11D1-8699-00C04FB98036}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission
can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


"Cris Hanna [SBS - MVP]" wrote:

Guess the question is...what happened right before this started?
This driver is related to WebDAV. Are you able to start the server in
"last
known good config"?

--
Cris Hanna [SBS - MVP]
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.
"Webspeedway" <Webspeedway@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:326BF7BB-E690-4CD6-9F3D-089F6E3E5B19@xxxxxxxxxxxxxxxx
Got the following BSOD this evening.. Point to mrxdav.sys

Debugging info:

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


Loading Dump File [C:\****\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:
SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs)
Free
x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer
SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_sp2_gdr.070304-2240
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Mon Aug 4 21:35:52.199 2008 (GMT-4)
System Uptime: 0 days 1:20:53.531
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for
details
Loading unloaded module list
.....
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 27, {baad0080, b669994c, b6699648, 80959d1f}

Page 11af14 not present in the dump file. Type ".hh dbgerr004" for
details
Page 11b280 not present in the dump file. Type ".hh dbgerr004" for
details
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for
details
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for
details
Probably caused by : mrxdav.sys ( mrxdav!MRxDAVOuterStop+92 )

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

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

RDR_FILE_SYSTEM (27)
If you see RxExceptionFilter on the stack then the 2nd and 3rd
parameters are the
exception record and context record. Do a .cxr on the 3rd parameter
and
then kb to
obtain a more informative stack trace.
The high 16 bits of the first parameter is the RDBSS bugcheck code,
which is defined
as follows:
RDBSS_BUG_CHECK_CACHESUP = 0xca550000,
RDBSS_BUG_CHECK_CLEANUP = 0xc1ee0000,
RDBSS_BUG_CHECK_CLOSE = 0xc10e0000,
RDBSS_BUG_CHECK_NTEXCEPT = 0xbaad0000,
Arguments:
Arg1: baad0080
Arg2: b669994c
Arg3: b6699648
Arg4: 80959d1f

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

Page 11af14 not present in the dump file. Type ".hh dbgerr004" for
details
Page 11b280 not present in the dump file. Type ".hh dbgerr004" for
details
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for
details
PEB is paged out (Peb.Ldr = 7ffd600c). Type ".hh dbgerr001" for
details

EXCEPTION_RECORD: b669994c -- (.exr 0xffffffffb669994c)
ExceptionAddress: 80959d1f (nt!RtlDestroyHeap+0x00000023)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00e30050
Attempt to read from address 00e30050

CONTEXT: b6699648 -- (.cxr 0xffffffffb6699648)
eax=89b69404 ebx=00e30050 ecx=b8b70f00 edx=00000000 esi=89b69404
edi=00e30000
eip=80959d1f esp=b6699a14 ebp=b6699a24 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!RtlDestroyHeap+0x23:
80959d1f 8b33 mov esi,dword ptr [ebx]
ds:0023:00e30050=????????
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced
memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS: 00e30050

BUGCHECK_STR: 0x27

LAST_CONTROL_TRANSFER: from b8b723dc to 80959d1f

STACK_TEXT:
b6699a24 b8b723dc 00e30000 00000000 8716cc80 nt!RtlDestroyHeap+0x23
b6699a5c b8b7266c 8716cc80 00000000 8716cc80
mrxdav!MRxDAVOuterStop+0x92
b6699a9c b8b7cbd7 0116cc80 b8b7eb9a 883ed4c8
mrxdav!MRxDAVDevFcbXXXControlFile+0x204
b6699ab4 b8b7cf83 8716cc80 883ed4c8 883ed55c
mrxdav!RxXXXControlFileCallthru+0x67
b6699ad8 b8b68f72 8716cc80 00000000 872c26a8
mrxdav!RxCommonDevFCBFsCtl+0x8d
b6699b68 b8b7c852 b8b700f0 883ed4c8 872c26a8
mrxdav!RxFsdCommonDispatch+0x320
b6699b88 b8b75fc4 89b69030 883ed4c8 89b6cee8 mrxdav!RxFsdDispatch+0xd4
b6699bfc 8081df65 89b69030 883ed4c8 883ed4c8
mrxdav!MRxDAVFsdDispatch+0x1f0
b6699c10 f725e6c1 883ed4c8 883ed4c8 8b2a8b48 nt!IofCallDriver+0x45
b6699c3c 8081df65 89b6cee8 883ed4c8 872c26a8 fltmgr!FltpFsControl+0xd7
b6699c50 808f5437 883ed55c 872c26a8 883ed4c8 nt!IofCallDriver+0x45
b6699c64 808f61bf 89b6cee8 883ed4c8 872c26a8
nt!IopSynchronousServiceTail+0x10b
b6699d00 808eed3c 000002ec 00000000 00000000 nt!IopXxxControlFile+0x5e5
b6699d34 8088978c 000002ec 00000000 00000000 nt!NtFsControlFile+0x2a
b6699d34 7c8285ec 000002ec 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be
wrong.
00f6ff20 00000000 00000000 00000000 00000000 0x7c8285ec


FOLLOWUP_IP:
mrxdav!MRxDAVOuterStop+92
b8b723dc 6800800000 push 8000h

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: mrxdav!MRxDAVOuterStop+92

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: mrxdav

IMAGE_NAME: mrxdav.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47665423

STACK_COMMAND: .cxr 0xffffffffb6699648 ; kb

FAILURE_BUCKET_ID: 0x27_mrxdav!MRxDAVOuterStop+92

BUCKET_ID: 0x27_mrxdav!MRxDAVOuterStop+92

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

3: kd> lmvm mrxdav
start end module name
b8b66000 b8b99000 mrxdav (pdb symbols)
c:\windows\symbols\mrxdav.pdb\50370B2C712F4E05BFB18E74F73491261\mrxdav.pdb
Loaded symbol image file: mrxdav.sys
Image path: \SystemRoot\system32\DRIVERS\mrxdav.sys
Image name: mrxdav.sys
Timestamp: Mon Dec 17 05:49:07 2007 (47665423)
CheckSum: 0002EFF2
ImageSize: 00033000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0




.

Relevant Pages

  • Re: SBS 2003 BOSD (mrxdav.sys), Help Needed Please
    ... Cris Hanna [SBS - MVP] ... MVPs do not work for Microsoft ... > exception record and context record. ...
    (microsoft.public.windows.server.sbs)
  • Re: Where are MVPs when you need them???
    ... Please understand that you are not talking to Microsoft here. ... With an occasional rare ... exception, there are no Microsoft employees here. ... MVP title is an award made to those people who have demonstrated ...
    (microsoft.public.windowsxp.general)
  • RE: "not handled in user code" dialog
    ... In debugging mode, the VS2005 will popup a Managed Debugging ... Assistants dialog for the exception. ... Microsoft Online Community Support ...
    (microsoft.public.vsnet.debugging)
  • Re: Html project
    ... Microsoft C++ exceptions are normal to occur. ... Microsoft - MVP ... > hate access errors and was wondering if anyone has seen information on ... > C++ Exception. ...
    (microsoft.public.vc.mfc)
  • Re: How to fix broken security in Windows 2000?
    ... Years ago, way back when the MVP program was useful, I would ask ... I am quite sincerely interested in how Microsoft ... > knowledge database that their paid support technicians use when you ...
    (microsoft.public.win2000.windows_update)