Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - mrxsmb10 - FAILURE_ID_HASH_STRING: km:x64_0x27_mrxsmb10!mrxsmb

08 Oct 2015   #1
samehh

Windows 7 Pro x64
 
 
BSOD - mrxsmb10 - FAILURE_ID_HASH_STRING: km:x64_0x27_mrxsmb10!mrxsmb

Hi,

We are getting this BSOD error on one of our PC's but have been unable to resolve this.

We have tried updating the network adapter, anti virus scan, malware scan, system file check and amended the network adapters settings to not power save.

Any ideas why this is occurring?


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
OK C:\windows\symbol_cache
Symbol search path is: SRV*C:\Windows\symbol_cache*404 - File or directory not found.
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03092730
Debug session time: Wed Oct 7 16:23:20.855 2015 (UTC + 1:00)
System Uptime: 0 days 7:47:03.430
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 27, {baad0073, fffff8800901ad08, fffff8800901a560, fffff88003da85be}

Probably caused by : mrxsmb10.sys ( mrxsmb10!MRxSmbBuildWriteRequest+25e )

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

1: 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: 00000000baad0073
Arg2: fffff8800901ad08
Arg3: fffff8800901a560
Arg4: fffff88003da85be

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


EXCEPTION_RECORD: fffff8800901ad08 -- (.exr 0xfffff8800901ad08)
ExceptionAddress: fffff88003da85be (mrxsmb10!MRxSmbBuildWriteRequest+0x000000000000025e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT: fffff8800901a560 -- (.cxr 0xfffff8800901a560;r)
rax=fffff88003dae310 rbx=fffffa80073e6410 rcx=0000000000000000
rdx=0000000000000002 rsi=fffffa80073e6410 rdi=fffffa80075d7010
rip=fffff88003da85be rsp=fffff8800901af40 rbp=0000000000000000
r8=0000000000000aff r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000800 r13=fffffa80075d0000
r14=0000000000000000 r15=0000000000000800
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210297
mrxsmb10!MRxSmbBuildWriteRequest+0x25e:
fffff880`03da85be 450fb74608 movzx r8d,word ptr [r14+8] ds:002b:00000000`00000008=????
Last set context:
rax=fffff88003dae310 rbx=fffffa80073e6410 rcx=0000000000000000
rdx=0000000000000002 rsi=fffffa80073e6410 rdi=fffffa80075d7010
rip=fffff88003da85be rsp=fffff8800901af40 rbp=0000000000000000
r8=0000000000000aff r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000800 r13=fffffa80075d0000
r14=0000000000000000 r15=0000000000000800
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210297
mrxsmb10!MRxSmbBuildWriteRequest+0x25e:
fffff880`03da85be 450fb74608 movzx r8d,word ptr [r14+8] ds:002b:00000000`00000008=????
Resetting default scope

PROCESS_NAME: winword.exe

CURRENT_IRQL: 0

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

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000008

READ_ADDRESS: 0000000000000008

FOLLOWUP_IP:
mrxsmb10!MRxSmbBuildWriteRequest+25e
fffff880`03da85be 450fb74608 movzx r8d,word ptr [r14+8]

FAULTING_IP:
mrxsmb10!MRxSmbBuildWriteRequest+25e
fffff880`03da85be 450fb74608 movzx r8d,word ptr [r14+8]

BUGCHECK_STR: 0x27

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DEVICE_OBJECT: fffffa8004b75490

DRIVER_OBJECT: 0000000000000000

LAST_CONTROL_TRANSFER: from fffff88003da8a1c to fffff88003da85be

STACK_TEXT:
fffff880`0901af40 fffff880`03da8a1c : 00000000`00000a01 fffff8a0`05e30000 fffffa80`073e6400 00000000`00000000 : mrxsmb10!MRxSmbBuildWriteRequest+0x25e
fffff880`0901b060 fffff880`03da097d : 00000000`00000000 fffffa80`057d6b00 fffffa80`073e6410 fffffa80`0564e460 : mrxsmb10!SmbPseExchangeStart_Write+0x2c4
fffff880`0901b0f0 fffff880`03da8151 : fffffa80`06b75ba0 fffffa80`057d6bb0 fffffa80`05b96e70 fffff880`03da8758 : mrxsmb10!SmbCeInitiateExchange+0x4a1
fffff880`0901b170 fffff880`04013a1c : fffffa80`075d7001 00000000`00000000 fffff8a0`00000001 00000000`00000000 : mrxsmb10!MRxSmbWrite+0x3e9
fffff880`0901b220 fffff880`02d3cc69 : 00000000`00000001 fffff880`00000001 00000000`00000000 fffff800`00000800 : csc!CscWrite+0x3ac
fffff880`0901b330 fffff880`02d4ba3b : fffffa80`075d7010 fffff880`02d31110 fffffa80`04b752a0 00000000`00000000 : rdbss!RxLowIoSubmit+0x291
fffff880`0901b390 fffff880`02d23541 : 00000000`00000a01 fffff880`0901b5a0 fffffa80`075d7010 fffffa80`00000000 : rdbss!RxLowIoWriteShell+0x7f
fffff880`0901b3c0 fffff880`02d4b96e : fffffa80`075d7010 fffffa80`04b752a0 fffff8a0`0492d610 fffff8a0`05e11498 : rdbss!RxCommonFileWrite+0x1be9
fffff880`0901b530 fffff880`02d1a6a0 : 00000000`00000000 fffff880`0901b5a0 01d10114`19756700 00000000`00000001 : rdbss!RxCommonWrite+0xe6
fffff880`0901b560 fffff880`02d37bb4 : fffffa80`04b752a0 fffffa80`06284004 00000000`c0000016 fffff880`010ab1b5 : rdbss!RxFsdCommonDispatch+0x870
fffff880`0901b650 fffff880`03d582c4 : fffffa80`04b752a0 00000000`c0000016 fffffa80`04b753b8 fffffa80`06284040 : rdbss!RxFsdDispatch+0x224
fffff880`0901b6c0 fffff880`01900c79 : fffffa80`03a80c50 fffffa80`04b752a0 fffffa80`053494c0 fffff8a0`002fc0d0 : mrxsmb!MRxSmbFsdDispatch+0xc0
fffff880`0901b700 fffff880`018ff175 : fffff8a0`002fc0d0 fffffa80`03a80c50 00000000`00000103 00000000`00000000 : mup!MupiCallUncProvider+0x169
fffff880`0901b770 fffff880`01901001 : fffffa80`04b752a0 fffff880`018fd118 fffffa80`064f5780 00000000`00000000 : mup!MupStateMachine+0x165
fffff880`0901b7c0 fffff880`01060bcf : fffffa80`04b75448 fffffa80`03a80c50 fffff880`0901b860 fffffa80`06e31cb0 : mup!MupFsdIrpPassThrough+0x12d
fffff880`0901b810 fffff880`0105f6df : fffffa80`04302900 00000000`00000001 fffffa80`04302900 fffffa80`04b752a0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0901b8a0 fffff800`031c76db : 00000000`00000001 fffffa80`064f5780 00000000`00000001 fffffa80`04b752a0 : fltmgr!FltpDispatch+0xcf
fffff880`0901b900 fffff800`031d3103 : fffffa80`04b75490 00000000`00000000 fffffa80`064f5780 fffff880`009e8180 : nt!IopSynchronousServiceTail+0xfb
fffff880`0901b970 fffff800`02ebd853 : ffffffff`00000001 00000000`00000000 00000000`00000000 00000000`003c24cc : nt!NtWriteFile+0x7e2
fffff880`0901ba70 00000000`75052e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0014e908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75052e09


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: mrxsmb10!MRxSmbBuildWriteRequest+25e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: mrxsmb10

IMAGE_NAME: mrxsmb10.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 55afc883

STACK_COMMAND: .cxr 0xfffff8800901a560 ; kb

FAILURE_BUCKET_ID: X64_0x27_mrxsmb10!MRxSmbBuildWriteRequest+25e

BUCKET_ID: X64_0x27_mrxsmb10!MRxSmbBuildWriteRequest+25e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x27_mrxsmb10!mrxsmbbuildwriterequest+25e

FAILURE_ID_HASH: {e454b02a-a3ef-39ed-ffa5-d09145fcc547}

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


My System SpecsSystem Spec
.
08 Oct 2015   #2
axe0

Windows 10 Pro
 
 

Hi samehh,

Welcome to the 7forums.

Can you put the output of Windbg in code tags? That would make it easier to read.

Please read BSOD Posting Instructions & How to upload files
My System SpecsSystem Spec
08 Oct 2015   #3
samehh

Windows 7 Pro x64
 
 

Hi Axe0

Thank you!

I can re-run this but I might need to do this a little later on today; as this is a PC in a corporate environment.

Can you confirm whether I would just need to save the output in windbg to get the code tags you mentioned?
My System SpecsSystem Spec
.

08 Oct 2015   #4
axe0

Windows 10 Pro
 
 

Copy/paste the output in the tags is enough
My System SpecsSystem Spec
09 Oct 2015   #5
samehh

Windows 7 Pro x64
 
 

Hi axe0,

The setup has re-directed folders and running the tool does not create the folder on the C:\ desktop or the re-directed server desktop - not sure why but presumably this is due to the environment.

The windbg in the thread is already a copy/paste of this; sorry if this is very stupid but how do I get this into code tags as you mentioned?
My System SpecsSystem Spec
09 Oct 2015   #6
axe0

Windows 10 Pro
 
 

Please follow this tutorial, Minidump - How to configure - Windows 10 Help Forums and confirm the settings are correct.

Just select the text you want to put into code tags and click on the button as shown in the image below
My System SpecsSystem Spec
09 Oct 2015   #7
samehh

Windows 7 Pro x64
 
 

Code:
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
OK                                             C:\windows\symbol_cache
Symbol search path is: SRV*C:\Windows\symbol_cache*404 - File or directory not found.
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03092730
Debug session time: Wed Oct  7 16:23:20.855 2015 (UTC + 1:00)
System Uptime: 0 days 7:47:03.430
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 27, {baad0073, fffff8800901ad08, fffff8800901a560, fffff88003da85be}

Probably caused by : mrxsmb10.sys ( mrxsmb10!MRxSmbBuildWriteRequest+25e )

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

1: 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: 00000000baad0073
Arg2: fffff8800901ad08
Arg3: fffff8800901a560
Arg4: fffff88003da85be

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


EXCEPTION_RECORD:  fffff8800901ad08 -- (.exr 0xfffff8800901ad08)
ExceptionAddress: fffff88003da85be (mrxsmb10!MRxSmbBuildWriteRequest+0x000000000000025e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT:  fffff8800901a560 -- (.cxr 0xfffff8800901a560;r)
rax=fffff88003dae310 rbx=fffffa80073e6410 rcx=0000000000000000
rdx=0000000000000002 rsi=fffffa80073e6410 rdi=fffffa80075d7010
rip=fffff88003da85be rsp=fffff8800901af40 rbp=0000000000000000
 r8=0000000000000aff  r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000800 r13=fffffa80075d0000
r14=0000000000000000 r15=0000000000000800
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210297
mrxsmb10!MRxSmbBuildWriteRequest+0x25e:
fffff880`03da85be 450fb74608      movzx   r8d,word ptr [r14+8] ds:002b:00000000`00000008=????
Last set context:
rax=fffff88003dae310 rbx=fffffa80073e6410 rcx=0000000000000000
rdx=0000000000000002 rsi=fffffa80073e6410 rdi=fffffa80075d7010
rip=fffff88003da85be rsp=fffff8800901af40 rbp=0000000000000000
 r8=0000000000000aff  r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000800 r13=fffffa80075d0000
r14=0000000000000000 r15=0000000000000800
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210297
mrxsmb10!MRxSmbBuildWriteRequest+0x25e:
fffff880`03da85be 450fb74608      movzx   r8d,word ptr [r14+8] ds:002b:00000000`00000008=????
Resetting default scope

PROCESS_NAME:  winword.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000008

READ_ADDRESS:  0000000000000008 

FOLLOWUP_IP: 
mrxsmb10!MRxSmbBuildWriteRequest+25e
fffff880`03da85be 450fb74608      movzx   r8d,word ptr [r14+8]

FAULTING_IP: 
mrxsmb10!MRxSmbBuildWriteRequest+25e
fffff880`03da85be 450fb74608      movzx   r8d,word ptr [r14+8]

BUGCHECK_STR:  0x27

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DEVICE_OBJECT: fffffa8004b75490

DRIVER_OBJECT: 0000000000000000

LAST_CONTROL_TRANSFER:  from fffff88003da8a1c to fffff88003da85be

STACK_TEXT:  
fffff880`0901af40 fffff880`03da8a1c : 00000000`00000a01  fffff8a0`05e30000 fffffa80`073e6400 00000000`00000000 :  mrxsmb10!MRxSmbBuildWriteRequest+0x25e
fffff880`0901b060 fffff880`03da097d : 00000000`00000000  fffffa80`057d6b00 fffffa80`073e6410 fffffa80`0564e460 :  mrxsmb10!SmbPseExchangeStart_Write+0x2c4
fffff880`0901b0f0 fffff880`03da8151 : fffffa80`06b75ba0  fffffa80`057d6bb0 fffffa80`05b96e70 fffff880`03da8758 :  mrxsmb10!SmbCeInitiateExchange+0x4a1
fffff880`0901b170 fffff880`04013a1c : fffffa80`075d7001  00000000`00000000 fffff8a0`00000001 00000000`00000000 :  mrxsmb10!MRxSmbWrite+0x3e9
fffff880`0901b220 fffff880`02d3cc69 : 00000000`00000001  fffff880`00000001 00000000`00000000 fffff800`00000800 :  csc!CscWrite+0x3ac
fffff880`0901b330 fffff880`02d4ba3b : fffffa80`075d7010  fffff880`02d31110 fffffa80`04b752a0 00000000`00000000 :  rdbss!RxLowIoSubmit+0x291
fffff880`0901b390 fffff880`02d23541 : 00000000`00000a01  fffff880`0901b5a0 fffffa80`075d7010 fffffa80`00000000 :  rdbss!RxLowIoWriteShell+0x7f
fffff880`0901b3c0 fffff880`02d4b96e : fffffa80`075d7010  fffffa80`04b752a0 fffff8a0`0492d610 fffff8a0`05e11498 :  rdbss!RxCommonFileWrite+0x1be9
fffff880`0901b530 fffff880`02d1a6a0 : 00000000`00000000  fffff880`0901b5a0 01d10114`19756700 00000000`00000001 :  rdbss!RxCommonWrite+0xe6
fffff880`0901b560 fffff880`02d37bb4 : fffffa80`04b752a0  fffffa80`06284004 00000000`c0000016 fffff880`010ab1b5 :  rdbss!RxFsdCommonDispatch+0x870
fffff880`0901b650 fffff880`03d582c4 : fffffa80`04b752a0  00000000`c0000016 fffffa80`04b753b8 fffffa80`06284040 :  rdbss!RxFsdDispatch+0x224
fffff880`0901b6c0 fffff880`01900c79 : fffffa80`03a80c50  fffffa80`04b752a0 fffffa80`053494c0 fffff8a0`002fc0d0 :  mrxsmb!MRxSmbFsdDispatch+0xc0
fffff880`0901b700 fffff880`018ff175 : fffff8a0`002fc0d0  fffffa80`03a80c50 00000000`00000103 00000000`00000000 :  mup!MupiCallUncProvider+0x169
fffff880`0901b770 fffff880`01901001 : fffffa80`04b752a0  fffff880`018fd118 fffffa80`064f5780 00000000`00000000 :  mup!MupStateMachine+0x165
fffff880`0901b7c0 fffff880`01060bcf : fffffa80`04b75448  fffffa80`03a80c50 fffff880`0901b860 fffffa80`06e31cb0 :  mup!MupFsdIrpPassThrough+0x12d
fffff880`0901b810 fffff880`0105f6df : fffffa80`04302900  00000000`00000001 fffffa80`04302900 fffffa80`04b752a0 :  fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0901b8a0 fffff800`031c76db : 00000000`00000001  fffffa80`064f5780 00000000`00000001 fffffa80`04b752a0 :  fltmgr!FltpDispatch+0xcf
fffff880`0901b900 fffff800`031d3103 : fffffa80`04b75490  00000000`00000000 fffffa80`064f5780 fffff880`009e8180 :  nt!IopSynchronousServiceTail+0xfb
fffff880`0901b970 fffff800`02ebd853 : ffffffff`00000001  00000000`00000000 00000000`00000000 00000000`003c24cc :  nt!NtWriteFile+0x7e2
fffff880`0901ba70 00000000`75052e09 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13
00000000`0014e908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75052e09


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  mrxsmb10!MRxSmbBuildWriteRequest+25e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mrxsmb10

IMAGE_NAME:  mrxsmb10.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55afc883

STACK_COMMAND:  .cxr 0xfffff8800901a560 ; kb

FAILURE_BUCKET_ID:  X64_0x27_mrxsmb10!MRxSmbBuildWriteRequest+25e

BUCKET_ID:  X64_0x27_mrxsmb10!MRxSmbBuildWriteRequest+25e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x27_mrxsmb10!mrxsmbbuildwriterequest+25e

FAILURE_ID_HASH:  {e454b02a-a3ef-39ed-ffa5-d09145fcc547}

Followup: MachineOwner
---------
My System SpecsSystem Spec
09 Oct 2015   #8
axe0

Windows 10 Pro
 
 

Please follow the BSOD Posting Instructions as requested earlier!
The driver blamed is a Windows driver which are very rare the real cause and with just that information we won't be able to determine the cause.
My System SpecsSystem Spec
09 Oct 2015   #9
samehh

Windows 7 Pro x64
 
 

I have tried to run the tool as per (Blue Screen of Death (BSOD) Posting Instructions) but this is not generating the file on the machine to the desktop.

I'll see if I can get this working by using a local account.
My System SpecsSystem Spec
Reply

 BSOD - mrxsmb10 - FAILURE_ID_HASH_STRING: km:x64_0x27_mrxsmb10!mrxsmb




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD playing Diablo 3, error relating to mrxsmb.sys and nvlddmkm.sys
Good day Recently i got a random blue screen/lockup while playing Diablo 3. This is the first one that i have gotten since around March if this year so it struck me as very random. The most common lockup being the black screen issue where i have to shut down and restart my pc. This...
BSOD Help and Support
BSOD, Win 7 Update SP1, error 0x27, mrxsmb.sys,
So, this computer has been out of commission since November, at that point, I had started getting errors, BSOD in particular, all of which were different STOP codes, so I gave up on it then, Stuck it in the closet and pulled out the old iMac, slow as hell, but it squeezed by and got the job done,...
BSOD Help and Support
BSOD when using Office, error 0x00000027 mrxsmb10.sys
Hi, One of the computers on our office network is encountering a BSOD every couple of days or so. I believe every time it has occurred Microsoft Office (Word/Excel) has been running. This computer is connected to a server running Windows Small Business Server 2003. Unfortunately the SF...
BSOD Help and Support
BSOD on 3 of 4 Win7 Machines - Cause mrxsmb10.sys
I am getting a BSOD on 3 of 4 PC's in the office. This started occurring in early Feb. I have tried updated all the video drives and network drivers on the workstations and servers. Tried to run the hotfix related to mrxsmb10.sys (says update not necessary or something to that effect). This is...
BSOD Help and Support
BSOD on RDR_FILESYSTEM with mrxsmb10.sys
It seems I am the only one who is suffering from this - can't find any other reference. Quite frequently, but not always, when I try to open a Word or Excel document on a Buffalo NAS, my Windows 7 dies away with a blue screen. Seems that I have to get rid of that piece of hardware?! Kai
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:18.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App