Doesn't work with DokanSetup_1.0.0-RC1.exe about dokan-dotnet HOT 48 CLOSED

hi @viciousviper ,

This is made in purpose :p Sorry
See dokan-dev/dokany#129

Now dokan1.dll need to be copy into the runtime folder.

from dokan-dotnet.

Where do you expect it to be copied - to %SystemRoot%\System32 or into DokanNet.Tests\bin\%Configuration% ?

from dokan-dotnet.

@viciousviper bin%Configuration%

Like that the application can keep his dll even if dokan driver has been updated

from dokan-dotnet.

Maybe we should implement a post-build action for that - otherwise the unit tests will fail unless you intervene manually.

My bigger problem is the BSOD I'm getting whenever I try to run DokanNet.Tests against dokany 1.0.0-rc1. Haven't had this since 0.7.3, pretty sad.

Are you able to run tests locally? I recognize that AppVeyor does not seem to have a problem, but still ...

from dokan-dotnet.

You have been heard 😎
dokan-dev/dokany#129 (comment)

About DokanNet.Tests, there should be no difference but I will check when have time !

from dokan-dotnet.

Good to know.
However, I'm still getting BSODs from FltMgr.sys whenever I try to execute any ot the DokanNet.Tests, despite copying dokan1.dll, dokannp1.dll, and dokanfuse1.dll to the respective %SystemRoot%\System32 and %SystemRoot%\SysWOW64 directories.

Going back to 1.0.0-beta1 for the time being :-(

from dokan-dotnet.

Mirror. exe works fine on this machine?

from dokan-dotnet.

@viciousviper Could you remove the dokan 1.0.0-RC1 you have installed and try with
https://drive.google.com/folderview?id=0B3E9tU82h-RMMmh3RkJFamM4WTA&usp=sharing
to see if there is a difference.

You will also need to copie new dokan dll from this installer :)

from dokan-dotnet.

@marinkobabic:
No.
"C:\Program Files\Dokan\Dokan Library-1.0.0\sample\mirror\mirror.exe" /l z /r D:\Temp`

... wait for a minute or so ...

BSOD: IRQ_NOT_LESS_OR_EQUAL

This is on the dokan 1.0.0-RC1 from https://drive.google.com/folderview?id=0B3E9tU82h-RMMmh3RkJFamM4WTA&usp=sharing

from dokan-dotnet.

What is the operating system you use? Kind of architecture x86/x64? When you keep the Explorer closed and you run the mirror, do you get then a BSOD? If not, then run cmd.exe and try to access the drive, BSOD? Then open the explorer and navigate to the drive, BSOD?

Please provide as much a possible details so that we can reproduce your issue.

from dokan-dotnet.

The stack trace of the crash dump would also be interesting. You can get it using windbg → open crash dump → analyze -v

from dokan-dotnet.

@marinkobabic:
Win 10 x64

1. Install Dokany 1.0.0-RC1 from Liryna's link
2. reboot
3. "C:\Program Files\Dokan\Dokan Library-1.0.0\sample\mirror\mirror.exe" /l z /r D:\Temp`
4. No explorer.exe, no "dir z:", just wait for about a minute
5. BSOD IRQL_NOT_LESS_OR EQUAL

@!marinkobabic
Ok, I'm going to try and catch a dump, but I'm not at all happy with repeatedly crashing my working rig, just so you know.

from dokan-dotnet.

Here is the crash dump.

Once again:

1. booted into Win10 Pro x64
2. executed "C:\Program Files\Dokan\Dokan Library-1.0.0\sample\mirror\mirror.exe" /l z /r D:\Temp
3. Just sat there waiting, no explorer.exe opened, no dir z: executed
4. BSOD after roughly a minute

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\021916-4812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff8023f08c000 PsLoadedModuleList = 0xfffff8023f36ac70
Debug session time: Fri Feb 19 23:14:56.413 2016 (UTC + 1:00)
System Uptime: 0 days 0:01:58.155
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
........

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

  ---

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8023f2bc03a, ffffd00022417470, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+3a )

Followup: MachineOwner

4: kd> !analyze -v

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

  ---

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8023f2bc03a, Address of the instruction which caused the bugcheck
Arg3: ffffd00022417470, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.17.amd64fre.th2_release.151121-2308

SYSTEM_MANUFACTURER: xxxxxxxxxxxx

SYSTEM_PRODUCT_NAME: xxxxxxxxx

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: N/A

BIOS_VENDOR: xxxxxxxxxxxxxx

BIOS_VERSION: xxxxxxxxxxxxx

BIOS_DATE: xxxxxxxxxxx

BASEBOARD_MANUFACTURER: xxxxxxxxxxx

BASEBOARD_PRODUCT: xxxxxxxxxxxx

BASEBOARD_VERSION: N/A

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8023f2bc03a

BUGCHECK_P3: ffffd00022417470

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

FAULTING_IP:
nt!ExFreePoolWithTag+3a
fffff802`3f2bc03a 410fb67ef3 movzx edi,byte ptr [r14-0Dh]

CONTEXT: ffffd00022417470 -- (.cxr 0xffffd00022417470)
rax=0000000000000000 rbx=00000000128d4f00 rcx=00000000000000ff
rdx=0000000000000000 rsi=0000000000000008 rdi=ffffe00138303018
rip=fffff8023f2bc03a rsp=ffffd00022417e90 rbp=ffffd00022418018
r8=0000000000000500 r9=0000000000000018 r10=0000000000000001
r11=ffffd00022417f38 r12=00000000ffffffff r13=0000000000000000
r14=00000000000000ff r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExFreePoolWithTag+0x3a:
fffff8023f2bc03a 410fb67ef3 movzx edi,byte ptr [r14-0Dh] ds:002b:00000000000000f2=??
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: a86

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: mirror.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: xxxxxxxxxx

ANALYSIS_SESSION_TIME: 02-19-2016 23:34:20.0642

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff800cf5fe0d8 to fffff8023f2bc03a

STACK_TEXT:
ffffd00022417e90 fffff800cf5fe0d8 : 0000000000000000 00000000128d4f00 0000000000000008 0000000000000000 : nt!ExFreePoolWithTag+0x3a
ffffd00022417f70 fffff800cf62354a : 00000000128d4fb2 ffffe00138303010 0000000000000008 ffffe00138303010 : FLTMGR!FltpWaitForRundownProtectionReleaseInternal+0xbe60
ffffd00022418080 fffff800cf62a5ac : 0000000000000000 00000000c01c000b 0000000000000000 0000000000000000 : FLTMGR!FltpFreeInstance+0x1a6
ffffd00022418150 fffff800cf622e2d : ffffe00134cbcc00 ffffe001383814f0 0000000000000005 ffffd00022418250 : FLTMGR!FltpInitInstance+0x560
ffffd00022418210 fffff800cf622c31 : 0000000000000000 ffffe001383814f0 0000000000000000 fffff8020000001a : FLTMGR!FltpCreateInstanceFromName+0x1ad
ffffd000224182f0 fffff800cf623172 : ffffe00134cbcc10 ffffe00134cbcc00 ffffe00137126002 000000000000002e : FLTMGR!FltpEnumerateRegistryInstances+0x145
ffffd00022418390 fffff800cf62642c : ffffe001383814f0 ffffd00000000000 ffffe00134cbcc10 ffffe001348e3770 : FLTMGR!FltpDoFilterNotificationForNewVolume+0x126
ffffd00022418410 fffff8023f480328 : 0000000000000000 0000000000000025 0000000000000000 ffffc00034d9d701 : FLTMGR!FltpCreate+0x49c
ffffd000224184c0 fffff8023f476c96 : ffffc00034cb4198 ffffc00034cb4198 ffffd00022418790 ffffe00137d0bc00 : nt!IopParseDevice+0x7c8
ffffd00022418690 fffff8023f47569c : ffffe00137c5da01 ffffd000224188a0 fffff68000000040 ffffe00132955dc0 : nt!ObpLookupObjectName+0x776
ffffd00022418830 fffff8023f49e8c8 : ffffd00000000001 ffffe001383b5b10 0000000000000000 0000000000000000 : nt!ObOpenObjectByNameEx+0x1ec
ffffd00022418950 fffff8023f49e429 : 000000d7ad8ff5e8 000000d7ad8ff3b8 000000d7ad8ff660 000000d7ad8ff600 : nt!IopCreateFile+0x3d8
ffffd00022418a00 fffff8023f1d8fa3 : fffff6fb7da01af0 fffff6fb4035eb60 fffff6806bd6c7e8 ffff2193d9ea713f : nt!NtCreateFile+0x79
ffffd00022418a90 00007ffadc5d5884 : 00007ffad88f63da 0000000000000001 0000000000000004 000002ceaea97180 : nt!KiSystemServiceCopyEnd+0x13
000000d7ad8ff4b8 00007ffad88f63da : 0000000000000001 0000000000000004 000002ceaea97180 0000000000000000 : 0x00007ffadc5d5884 000000d7ad8ff4c0 0000000000000001 : 0000000000000004 000002ceaea97180 0000000000000000 0000000000000000 : 0x00007ffad88f63da
000000d7ad8ff4c8 0000000000000004 : 000002ceaea97180 0000000000000000 0000000000000000 0000000000000000 : 0x1
000000d7ad8ff4d0 000002ceaea97180 : 0000000000000000 0000000000000000 0000000000000000 0000000000000003 : 0x4
000000d7ad8ff4d8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000003 0000000000000001 : 0x000002ce`aea97180

THREAD_SHA1_HASH_MOD_FUNC: 49693a4d190c123db2011fdd269af2cf405c340c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d0c7da070a24b3037354834f3099deedd0ff1730

THREAD_SHA1_HASH_MOD: 4661f7637edcfeb6882ff41d2585f77f76fd5c11

FOLLOWUP_IP:
nt!ExFreePoolWithTag+3a
fffff802`3f2bc03a 410fb67ef3 movzx edi,byte ptr [r14-0Dh]

FAULT_INSTR_CODE: 7eb60f41

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExFreePoolWithTag+3a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 565189c8

IMAGE_VERSION: 10.0.10586.17

STACK_COMMAND: .cxr 0xffffd00022417470 ; kb

BUCKET_ID_FUNC_OFFSET: 3a

FAILURE_BUCKET_ID: 0x3B_nt!ExFreePoolWithTag

BUCKET_ID: 0x3B_nt!ExFreePoolWithTag

PRIMARY_PROBLEM_CLASS: 0x3B_nt!ExFreePoolWithTag

TARGET_TIME: 2016-02-19T22:14:56.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2015-11-22 10:24:24

BUILDDATESTAMP_STR: 151121-2308

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 7c2c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_nt!exfreepoolwithtag

FAILURE_ID_HASH: {e9bf84e7-1787-7560-8d27-86e1d86b6d45}

Followup: MachineOwner

from dokan-dotnet.

In WinDbg you can set the symbols path. When you run the dokany setup you can decide to install the symbols as well.

It's seems to me that operating system realized that there is a new volume. It's calls the driver for createfile. The returned data have an issue. Filter manager fails because of a NullReferenceException.

I just hope that I can reproduce your issue.

In the driver code there is a check https://github.com/dokan-dev/dokany/blob/4343350589e6c6bfce31e2675e0462c63c8618ca/sys/init.c#L931

The question is if we execute the verify of the volume in every case, if then your issue is gone.

from dokan-dotnet.

You can test it very easy. When running mirror.exe pass the parameter so that the drive is a network drive. Do you still have the issue?

I'm sorry for doing such tests on your productive machine 😢

from dokan-dotnet.

Related to dokan-dev/dokany#176 I believe.
I cannot reproduce the crash at all, whereas I tested it on multiple systems.

I'm wondering if this is not related to the environment as both users seems to use it in production. Anything particular on the system (antivirus, ...)? What's on the list if you just enter 'fltmc' command?

from dokan-dotnet.

Would be interesting to know if they have the symantec antivirus installed? In this case we should be able to reproduce the problem. Maybe is even there another filter attached before the filter manager. We could figure this out using https://www.osronline.com/article.cfm?article=97. So please provide the:

• log using symbols
• devtree information filesystems/dokany/yourdevice attached filter
• the name of used antivirus software

Like Maxhy said it's related to your environment

from dokan-dotnet.

I'll try my best to help, but I'm not sure that you can read much more from the dump analysis without reference to ntoskrnl.pdb - which I can't seem to find on my machine. If you could point me to a source of this pdb I could try producing a more detailed dump.

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\021916-4812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Program Files\Dokan\Dokan Library-1.0.0
OK C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\fltMgr.pdb\620A988036C34BAFAD3FA05B3C5E27FF1
OK C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\FLTMGR.SYS\5632D17662000
OK C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntoskrnl.exe\565189C87cc000
OK C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntkrnlmp.pdb\231AC242EEAA4DB49BDBFD91531082851
Symbol search path is: C:\Program Files\Dokan\Dokan Library-1.0.0;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\fltMgr.pdb\620A988036C34BAFAD3FA05B3C5E27FF1;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\FLTMGR.SYS\5632D17662000;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntoskrnl.exe\565189C87cc000;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\sym\ntkrnlmp.pdb\231AC242EEAA4DB49BDBFD91531082851
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff8023f08c000 PsLoadedModuleList = 0xfffff8023f36ac70
Debug session time: Fri Feb 19 23:14:56.413 2016 (UTC + 1:00)
System Uptime: 0 days 0:01:58.155
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
........

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

  ---

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8023f2bc03a, ffffd00022417470, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+3a )

Followup: MachineOwner

4: kd> !analyze -v

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

  ---

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8023f2bc03a, Address of the instruction which caused the bugcheck
Arg3: ffffd00022417470, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.17.amd64fre.th2_release.151121-2308

SYSTEM_MANUFACTURER:

SYSTEM_PRODUCT_NAME:

SYSTEM_SKU:

SYSTEM_VERSION:

BIOS_VENDOR:

BIOS_VERSION:

BIOS_DATE:

BASEBOARD_MANUFACTURER:

BASEBOARD_PRODUCT:

BASEBOARD_VERSION:

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8023f2bc03a

BUGCHECK_P3: ffffd00022417470

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

FAULTING_IP:
nt!ExFreePoolWithTag+3a
fffff802`3f2bc03a 410fb67ef3 movzx edi,byte ptr [r14-0Dh]

CONTEXT: ffffd00022417470 -- (.cxr 0xffffd00022417470)
rax=0000000000000000 rbx=00000000128d4f00 rcx=00000000000000ff
rdx=0000000000000000 rsi=0000000000000008 rdi=ffffe00138303018
rip=fffff8023f2bc03a rsp=ffffd00022417e90 rbp=ffffd00022418018
r8=0000000000000500 r9=0000000000000018 r10=0000000000000001
r11=ffffd00022417f38 r12=00000000ffffffff r13=0000000000000000
r14=00000000000000ff r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExFreePoolWithTag+0x3a:
fffff8023f2bc03a 410fb67ef3 movzx edi,byte ptr [r14-0Dh] ds:002b:00000000000000f2=??
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: a86

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: mirror.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 02-20-2016 23:27:09.0400

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff800cf5fe0d8 to fffff8023f2bc03a

STACK_TEXT:
ffffd00022417e90 fffff800cf5fe0d8 : 0000000000000000 00000000128d4f00 0000000000000008 0000000000000000 : nt!ExFreePoolWithTag+0x3a
ffffd00022417f70 fffff800cf62354a : 00000000128d4fb2 ffffe00138303010 0000000000000008 ffffe00138303010 : FLTMGR!FltpWaitForRundownProtectionReleaseInternal+0xbe60
ffffd00022418080 fffff800cf62a5ac : 0000000000000000 00000000c01c000b 0000000000000000 0000000000000000 : FLTMGR!FltpFreeInstance+0x1a6
ffffd00022418150 fffff800cf622e2d : ffffe00134cbcc00 ffffe001383814f0 0000000000000005 ffffd00022418250 : FLTMGR!FltpInitInstance+0x560
ffffd00022418210 fffff800cf622c31 : 0000000000000000 ffffe001383814f0 0000000000000000 fffff8020000001a : FLTMGR!FltpCreateInstanceFromName+0x1ad
ffffd000224182f0 fffff800cf623172 : ffffe00134cbcc10 ffffe00134cbcc00 ffffe00137126002 000000000000002e : FLTMGR!FltpEnumerateRegistryInstances+0x145
ffffd00022418390 fffff800cf62642c : ffffe001383814f0 ffffd00000000000 ffffe00134cbcc10 ffffe001348e3770 : FLTMGR!FltpDoFilterNotificationForNewVolume+0x126
ffffd00022418410 fffff8023f480328 : 0000000000000000 0000000000000025 0000000000000000 ffffc00034d9d701 : FLTMGR!FltpCreate+0x49c
ffffd000224184c0 fffff8023f476c96 : ffffc00034cb4198 ffffc00034cb4198 ffffd00022418790 ffffe00137d0bc00 : nt!IopParseDevice+0x7c8
ffffd00022418690 fffff8023f47569c : ffffe00137c5da01 ffffd000224188a0 fffff68000000040 ffffe00132955dc0 : nt!ObpLookupObjectName+0x776
ffffd00022418830 fffff8023f49e8c8 : ffffd00000000001 ffffe001383b5b10 0000000000000000 0000000000000000 : nt!ObOpenObjectByNameEx+0x1ec
ffffd00022418950 fffff8023f49e429 : 000000d7ad8ff5e8 000000d7ad8ff3b8 000000d7ad8ff660 000000d7ad8ff600 : nt!IopCreateFile+0x3d8
ffffd00022418a00 fffff8023f1d8fa3 : fffff6fb7da01af0 fffff6fb4035eb60 fffff6806bd6c7e8 ffff2193d9ea713f : nt!NtCreateFile+0x79
ffffd00022418a90 00007ffadc5d5884 : 00007ffad88f63da 0000000000000001 0000000000000004 000002ceaea97180 : nt!KiSystemServiceCopyEnd+0x13
000000d7ad8ff4b8 00007ffad88f63da : 0000000000000001 0000000000000004 000002ceaea97180 0000000000000000 : 0x00007ffadc5d5884 000000d7ad8ff4c0 0000000000000001 : 0000000000000004 000002ceaea97180 0000000000000000 0000000000000000 : 0x00007ffad88f63da
000000d7ad8ff4c8 0000000000000004 : 000002ceaea97180 0000000000000000 0000000000000000 0000000000000000 : 0x1
000000d7ad8ff4d0 000002ceaea97180 : 0000000000000000 0000000000000000 0000000000000000 0000000000000003 : 0x4
000000d7ad8ff4d8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000003 0000000000000001 : 0x000002ce`aea97180

THREAD_SHA1_HASH_MOD_FUNC: 49693a4d190c123db2011fdd269af2cf405c340c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d0c7da070a24b3037354834f3099deedd0ff1730

THREAD_SHA1_HASH_MOD: 4661f7637edcfeb6882ff41d2585f77f76fd5c11

FOLLOWUP_IP:
nt!ExFreePoolWithTag+3a
fffff802`3f2bc03a 410fb67ef3 movzx edi,byte ptr [r14-0Dh]

FAULT_INSTR_CODE: 7eb60f41

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExFreePoolWithTag+3a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 565189c8

IMAGE_VERSION: 10.0.10586.17

STACK_COMMAND: .cxr 0xffffd00022417470 ; kb

BUCKET_ID_FUNC_OFFSET: 3a

FAILURE_BUCKET_ID: 0x3B_nt!ExFreePoolWithTag

BUCKET_ID: 0x3B_nt!ExFreePoolWithTag

PRIMARY_PROBLEM_CLASS: 0x3B_nt!ExFreePoolWithTag

TARGET_TIME: 2016-02-19T22:14:56.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2015-11-22 10:24:24

BUILDDATESTAMP_STR: 151121-2308

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 436

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_nt!exfreepoolwithtag

FAILURE_ID_HASH: {e9bf84e7-1787-7560-8d27-86e1d86b6d45}

Followup: MachineOwner

from dokan-dotnet.

Devtree output:

Is this what you wanted or do you need a different view?

<rant>
BTW, OSR online is pretty much a PITA. Why should I have to register when I just want do download a tool?
</rant>

fltmc output:

C:\Windows\system32>fltmc

from dokan-dotnet.

Here how to setup Microsoft symbols http://stackoverflow.com/questions/30019889/how-to-set-up-symbols-in-windbg

What antivirus software are you using?
Did you try to mount the drive as network drive?

Thanks a lot.

from dokan-dotnet.

To me it looks like WinDBG already loaded the system symbols allright.
Explicitly reloading them by executing .symfix+ ... and .reload, then executing !analyze -v again does not change the output for me, sorry :-(

Once again: My antivir software is Avast Free Antivirus.

I'll now proceed and start mirror.exe again with the network drive option. If I don't report back in the next five minutes you can assume that there was another BSOD and that I called it a day for now.

from dokan-dotnet.

1. C:\Program Files\Dokan\Dokan Library-1.0.0\sample\mirror>mirror /n /l z /r D:\Temp
2. Waited for ~2 minutes, no BSOD 👍
3. dir z:\ -> displayed directory contents 👍
4. explorer.exe -> no drive z: present 👎

No BSOD despite dir command executed and opened explorer.exe - seems to avoid my original problem, so you probably guessed right, @marinkobabic.

from dokan-dotnet.

Maybe Liryna can prepare a setup for you where the ckeck mentioned in one of my previous comments is removed. Just to see if this fixes your BSOD. There is a small chance that it then works properly.

That the drive is not displayed in explorer may be a different issue. Thanks a lot for the detailed reports.

from dokan-dotnet.

Happy to help out in any which way - except for producing BSODs, they make me nervous 8-)

from dokan-dotnet.

#68 (comment):
That the drive is not displayed in explorer may be a different issue. Thanks a lot for the detailed reports.

Right. Probably related to dokan-dev/dokany#177

from dokan-dotnet.

Hi @viciousviper ,

Thank for helping us finding the issue of this BSOD !

I have made the changes proposed by @marinkobabic
(removing the condition)
https://github.com/dokan-dev/dokany/blob/4343350589e6c6bfce31e2675e0462c63c8618ca/sys/init.c#L931
You can find the release here:
https://drive.google.com/folderview?id=0B3E9tU82h-RMMmh3RkJFamM4WTA&usp=sharing

I hope you will not get a BSOD 😢

from dokan-dotnet.

Hi Liryna,

I just tried to run DokanNet.Tests with your private build of dokany installed.

1. mounted drive as RemoteDrive
   -> BSOD "IRQL_NOT_LESS_OR_EQUAL"
2. mounted drive as NetworkDrive by defining the NETWORK_DRIVE symbol in the .csproj
   -> BSOD "UNEXPECTED_KERNEL_MODE_TRAP"

I've had enough for the weekend 😠

from dokan-dotnet.

Does the mirror work with local fixed drive using the new build? Sorry for the frustrated situation.

from dokan-dotnet.

@viciousviper @marinkobabic , I got a bsod also on my VM with the DokanNet.Tests 😎 so I can look what is happening.

Seems like DokanNet.Tests is enough heavy to create trouble with Dokany 😄

You can stop your test @viciousviper, thank you for your help and sorry for the BSOD.

from dokan-dotnet.

@marinkobabic

It is a different BSOD 😢
It happen when I launch all the dokanNet test but one by one I have no issues.

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801abf07976, Address of the instruction which caused the bugcheck
Arg3: ffffd000fd637880, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.103.amd64fre.th2_release.160126-1819

SYSTEM_MANUFACTURER:  innotek GmbH

VIRTUAL_MACHINE:  VirtualBox

SYSTEM_PRODUCT_NAME:  VirtualBox

SYSTEM_VERSION:  1.2

BIOS_VENDOR:  innotek GmbH

BIOS_VERSION:  VirtualBox

BIOS_DATE:  12/01/2006

BASEBOARD_MANUFACTURER:  Oracle Corporation

BASEBOARD_PRODUCT:  VirtualBox

BASEBOARD_VERSION:  1.2

DUMP_TYPE:  2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff801abf07976

BUGCHECK_P3: ffffd000fd637880

BUGCHECK_P4: 0

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

FAULTING_IP: 
FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+286
fffff801`abf07976 498b7810        mov     rdi,qword ptr [r8+10h]

CONTEXT:  ffffd000fd637880 -- (.cxr 0xffffd000fd637880)
rax=0000000000000000 rbx=ffffe0012a97fc80 rcx=0000000000000000
rdx=0000000000000000 rsi=ffffe00129382ab0 rdi=ffffe00129382bc8
rip=fffff801abf07976 rsp=ffffd000fd6382a0 rbp=ffffe0012a97fc98
 r8=00000000d006e000  r9=0000000000000000 r10=0000000000000001
r11=ffffe00129382ab0 r12=0000000000000000 r13=ffffd000fd638370
r14=fffff801abf18500 r15=0000000000000008
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x286:
fffff801`abf07976 498b7810        mov     rdi,qword ptr [r8+10h] ds:002b:00000000`d006e010=????????????????
Resetting default scope

CPU_COUNT: 2

CPU_MHZ: da4

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 0'00000000 (cache) 0'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  TE.ProcessHost

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-RBPTIQA

ANALYSIS_SESSION_TIME:  02-21-2016 09:13:03.0693

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff801abf362d7 to fffff801abf07976

STACK_TEXT:  
ffffd000`fd6382a0 fffff801`abf362d7 : ffffe001`2a82cdf0 ffffd000`fd638350 ffffd000`00000000 fffff801`abf35d5d : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x286
ffffd000`fd638330 fffff802`fde8bd68 : 00000000`00000000 00000000`00000045 00000000`00000000 00000000`00000001 : FLTMGR!FltpCreate+0x347
ffffd000`fd6383e0 fffff802`fde826d6 : ffffc001`bb427598 ffffc001`bb427598 ffffd000`fd6386b0 ffffe001`2ccf9c00 : nt!IopParseDevice+0x7c8
ffffd000`fd6385b0 fffff802`fde810dc : ffffe001`2947b001 ffffd000`fd6387c0 ffffc001`00000040 ffffe001`28c9ff20 : nt!ObpLookupObjectName+0x776
ffffd000`fd638750 fffff802`fde6e2bb : ffffd000`00000001 00000025`a9ebc0c0 00007ff8`3f2d9fd0 00000000`00000028 : nt!ObOpenObjectByNameEx+0x1ec
ffffd000`fd638870 fffff802`fdbc2ca3 : ffffe001`2cd106c0 ffffe001`2b46bdb0 ffffe001`2cd106c0 ffffe001`294a6080 : nt!NtQueryFullAttributesFile+0x18b
ffffd000`fd638b00 00007ff8`bbff7694 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000025`a9ebc038 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`bbff7694


THREAD_SHA1_HASH_MOD_FUNC:  d4b72486bce108bbbb829815eecfeb9216c9a68d

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a6646cc4b56b69f9be5ce6550588535d7a0f3412

THREAD_SHA1_HASH_MOD:  41bde297fea7c488fd34fc521455080f7dc2ba97

FOLLOWUP_IP: 
FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+286
fffff801`abf07976 498b7810        mov     rdi,qword ptr [r8+10h]

FAULT_INSTR_CODE:  10788b49

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+286

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: FLTMGR

IMAGE_NAME:  FLTMGR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5632d176

IMAGE_VERSION:  10.0.10586.0

STACK_COMMAND:  .cxr 0xffffd000fd637880 ; kb

BUCKET_ID_FUNC_OFFSET:  286

FAILURE_BUCKET_ID:  0x3B_FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted

BUCKET_ID:  0x3B_FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted

PRIMARY_PROBLEM_CLASS:  0x3B_FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted

TARGET_TIME:  2016-02-21T16:45:17.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-01-26 20:38:01

BUILDDATESTAMP_STR:  160126-1819

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.103.amd64fre.th2_release.160126-1819

ANALYSIS_SESSION_ELAPSED_TIME: 22f63

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_fltmgr!fltplegacyprocessingafterprecallbackscompleted

FAILURE_ID_HASH:  {9df490df-2802-d0f1-8517-437d70f8dc5b}

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

from dokan-dotnet.

@Liryna

How I can reproduce your BSOD, any idea? You can reproduce it?

from dokan-dotnet.

@marinkobabic I got the BSOD when I was running All DokanNet.Tests.
Unfortunately It does not seems to happen always :'(

from dokan-dotnet.

@Liryna
Please can you install Avast Free Antivirus on your virtual machine and let'm know what your experience is running mirror.exe and waiting for 2 Minutes and the try to access the drive in explorer?

In my case after installing Avast, the things started to hang the whole time. Threads terminated after 2 Minutes with error -1 when I tried to access the explorer. I did not analyze the logs, but will do it tomorrow. The question is what the other guy uses as antivirus software?

from dokan-dotnet.

The problem we have here is that the Avast wants to create some files on the volume, but we have no waiters which will process the requests. So Avast blocks the waiters until it get's an expected answer from drive. The driver returns STATUS_PENDING and waits for the waiters. This is the reason why everything fails. Have made a workaround to get this work dokan-dev/dokany#181

@Liryna
Hope you can make a temporary setup so that viciousviper can test and let us know if it works with this workaround.

from dokan-dotnet.

@viciousviper here is the version with the contribution of @marinkobabic (ty ❤️ )
I have tested it with avast. I had no issue and no blue screen.
https://drive.google.com/folderview?id=0B3E9tU82h-RMMmh3RkJFamM4WTA&usp=sharing

from dokan-dotnet.

Hi @Liryna and @marinkobabic,

this latest version of dokany looks a lot better. I could repeatedly execute the DokanNet.Tests suite from VS2015 both with and without Avast Free Antivirus running in the background - and no BSOD occured so far 👍

Thanks very much for hunting this sucker down 👏
I'm still baffled by the fact that Avast is behind all this - but I suspect that there are other antivir tools that might have raised similar issues.

There seems to have been a behavioral change in dokany w.r.t. IDokanOperations.GetFileInormation("\") that presently breaks about half the unit tests. I'll look into this - and into the new IDokanOperations.FindFilesWithPattern(...) implementation - tomorrow.

from dokan-dotnet.

Thats a great news !

Thank a lot again for taking the time and facing all this BSOD for the science 😎
About the DokanNet.Tests, I faced the same behaviour as you, I think now the system try to list files directly when the device is mounted by default.

from dokan-dotnet.

Unfortunately my report from two days back was overly optimistic.

While I have not experienced a BSOD during several runs of the .NET unit test suite with the dokan volume mounted as a RemoteDrive, switching to NetworkDrive produced a BSOD almost immediately - independent of my Avast antivir tool being active or deactivated. Message was "UNEXPECTED_KERNEL_MODE_TRAP" once again.

I'll continue fixing the DokanNet.Tests suite for the RemoteDrive case, but please look into the other drive modes and get rid of this annoying instability.

from dokan-dotnet.

@viciousviper Oh :(

Do you still have the bsod dump? Could you create a new issue on dokany with all informations and OS version used?

Thank you again for your feedback!

from dokan-dotnet.

Hi @Liryna,

the BSOD in NETWORK_DRIVE mode reared its ugly head again with Dokany 1.0.0-RC3 and Dokan-Dotnet 1.0.0-RC3 😞. As soon as I mount a drive as DokanOptions.NetworkDrive, execution of the .NET test suite crashes the OS. At first glance the crash behavior in RC3 does not appear any different from RC2.
Note that I'm using only one of DokanOptions.RemoteDrive and DokanOptions.NetworkDrive at any given time, although the enum would allow a combination.

Since I can't strictly meet the condition My issue is valid with mirror default sample and not specific to my user-mode driver implementation I am not in a position to report this as a dokany issue.

Please advise on the most adequate course of action: Should we remove DokanOptions.NetworkDrive from the .NET driver or do you see any chance of getting to the root of this situation - in which case I could submit an updated crash dump.

from dokan-dotnet.

Hi @viciousviper ,

Sad to hear it 😢 do you have the same issue with the C mirror with option /n ? Is it really only with the DokanOptions.NetworkDrive option ? Did you try without DokanOptions.RemoteDrive ?

I think we should find the root of this situation than remove the option.

I propose you to try to install a new windows in virtualbox to make your test in it.

If you still have the crash dump, I would be nice if you can share the analyze ! ❤️

(it is probably another BSOD that has been fixed with RC3)

from dokan-dotnet.

Ok, I'll go for the VM and the crash dump, but that'll take a little longer.

Everything went well when using DokanOptions.RemoteDrive only - I could even toggle DokanUptions.UserModeLock with the expected result. When I switched to DokanOptions.NetworkDrive there was an immediate BSOD. I didn't try DokanOptions.RemoteDrive | DokanOptions.NetworkDrive because I view those as mutually exclusive - just like in System.IO.DriveType.Remote vs. System.IO.DriveType.Network.

The additional options I use in the tests mounter are DokanOptions.DebugMode | DokanOptions.MountManager | DokanOptions.CurrentSession - these seem to be allright.

from dokan-dotnet.

Would be nice to get more details to the BSOD. What is the message when you open the memory dump using windbg?

from dokan-dotnet.

Haven't had the time to check with mirror.exe /n - sorry.

WinDbg analysis results attached. I have a nagging suspicion that Avast Free Antivirus is involved in the crash - although I did disable it before executing the .NET test suite, and there is still the fact that all is well with DokanOptions.RemoteDrive instead of DokanOptions.NetworkDrive.

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Program Files\Dokan\Dokan Library-1.0.0
Deferred srv_https://msdl.microsoft.com/download/symbols
Symbol search path is: C:\Program Files\Dokan\Dokan Library-1.0.0;srv_https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff800bf890000 PsLoadedModuleList = 0xfffff800bfb6ecd0
Debug session time: Tue May 17 00:44:07.114 2016 (UTC + 2:00)
System Uptime: 0 days 0:46:24.854
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
.....
Loading unloaded module list
..........
Loading Wow64 Symbols
................................................................
.................

---

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

  ---

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd00223d2c4fe, 0, fffff801972295fe, 2}

*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys

"KERNELBASE.dll" was not found in the image list.
Debugger will attempt to load "KERNELBASE.dll" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=,.
Unable to add module at 00000000`00000000
Probably caused by : aswSP.sys ( aswSP+6e3d4 )

Followup: MachineOwner

5: kd> !analyze -v

---

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

  ---

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffd00223d2c4fe, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801972295fe, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

"KERNELBASE.dll" was not found in the image list.
Debugger will attempt to load "KERNELBASE.dll" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=,.
Unable to add module at 00000000`00000000

DUMP_CLASS: 1

DUMP_QUALIFIER: 402

BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

SYSTEM_MANUFACTURER:

SYSTEM_PRODUCT_NAME:

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: N/A

BIOS_VENDOR:

BIOS_VERSION:

BIOS_DATE:

BASEBOARD_MANUFACTURER:

BASEBOARD_PRODUCT:

BASEBOARD_VERSION: N/A

DUMP_TYPE: 0

BUGCHECK_P1: ffffd00223d2c4fe

BUGCHECK_P2: 0

BUGCHECK_P3: fffff801972295fe

BUGCHECK_P4: 2

READ_ADDRESS: ffffd00223d2c4fe

FAULTING_IP:
FLTMGR!FltpExpandShortNames+8e
fffff801`972295fe 410fb70c70 movzx ecx,word ptr [r8+rsi*2]

MM_INTERNAL_CODE: 2

IMAGE_NAME: aswSP.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 571e068b

MODULE_NAME: aswSP

FAULTING_MODULE: fffff801971f0000 FLTMGR

CPU_COUNT: 8

CPU_MHZ: a86

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: TE.ProcessHost

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 05-17-2016 00:48:51.0274

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

MANAGED_CODE: 1

MANAGED_ENGINE_MODULE: clr

TRAP_FRAME: ffffd00023d2c220 -- (.trap 0xffffd00023d2c220)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000002
rdx=ffffd00023d2c4e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801972295fe rsp=ffffd00023d2c3b0 rbp=0000000000000000
r8=ffffd00023d2c500 r9=ffffd00023d2c500 r10=ffffd00023d2c401
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
FLTMGR!FltpExpandShortNames+0x8e:
fffff801972295fe 410fb70c70 movzx ecx,word ptr [r8+rsi*2] ds:ffffd00023d2c500=005c
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800bf9f1395 to fffff800bf9d2760

STACK_TEXT:
ffffd00023d2bfc8 fffff800bf9f1395 : 0000000000000050 ffffd00223d2c4fe 0000000000000000 ffffd00023d2c220 : nt!KeBugCheckEx
ffffd00023d2bfd0 fffff800bf8c8e91 : 0000000000000000 ffffe0004a8459f0 ffffd00023d2c220 fffff800bf90a0af : nt! ?? ::FNODOBFM::string'+0x10295 ffffd00023d2c0c0 fffff800bf9db9bc : 0000000000000001 0000018000000000 0000000000000000 ffffd00000000800 : nt!MmAccessFault+0x5f1 ffffd00023d2c220 fffff801972295fe : 0000000000000000 0000000000000000 ffffe0004a8459f0 fffff800bf8d3a11 : nt!KiPageFault+0x13c ffffd00023d2c3b0 fffff8019723e1e4 : 0000000000000001 ffffe00000000000 ffffe0004a8459f0 ffffe0004a8459f0 : FLTMGR!FltpExpandShortNames+0x8e ffffd00023d2c440 fffff8019723dbf1 : 0000000000000000 0000000000000000 0000000000000101 ffffe0004a797a10 : FLTMGR!FltpGetNormalizedDestinationFileName+0x68 ffffd00023d2c470 fffff80197eee3d4 : 0000000000004000 0000000000100004 ffffe0004a7280e8 fffff800bf8d3a11 : FLTMGR!FltGetDestinationFileNameInformation+0x191 ffffd00023d2c650 fffff801971f6d21 : 0000000000000000 0000000000000000 ffffe0004a728010 ffffe0004db01010 : aswSP+0x6e3d4 ffffd00023d2c6c0 fffff801971f68cc : ffffd00023d2c880 0000000000000000 ffffe0004a832906 ffffe0004a797a00 : FLTMGR!FltpPerformPreCallbacks+0x2f1 ffffd00023d2c7d0 fffff801971f59fa : 0000000000000000 ffffd00023d2c880 ffffe0004a8327d0 ffffd00023d2c890 : FLTMGR!FltpPassThroughInternal+0x8c ffffd00023d2c800 fffff801971f57fe : 0000000000000000 0000000000000000 0000000000000000 0000000000000001 : FLTMGR!FltpPassThrough+0x16a ffffd00023d2c860 fffff800bf8f9137 : ffffe0004a8327d0 01d1afc47459c5d5 01d1afc47459c5d5 01d1afc47459c5d5 : FLTMGR!FltpDispatch+0x9e ffffd00023d2c8c0 fffff800bf8f900e : ffffe0004a832930 0000000000000000 ffffe0004a8327d0 000000000000003e : nt!IoCallDriverWithTracing+0x47 ffffd00023d2c920 fffff800bf8e8b7f : ffffd00023d2cb80 ffffe0004a8327d0 ffffe0004a8327d0 000000000000003e : nt!IopCallDriverReference+0x8e ffffd00023d2c950 fffff800bf9dcfa3 : 0000000000000aa4 000000000567e378 000000000567ebc0 ffff84d70000003e : nt!NtSetInformationFile+0xacf ffffd00023d2ca90 00007ffec29855b4 : 000000006fad45ae 000000000567e2b0 0000000000000000 000000000567e2f0 : nt!KiSystemServiceCopyEnd+0x13 000000000567e278 000000006fad45ae : 000000000567e2b0 0000000000000000 000000000567e2f0 000000006facc180 : ntdll!NtSetInformationFile+0x14 000000000567e280 000000006fac8db0 : 0000000000000000 000000000840f2c8 000000000577d3f0 000000006fac93ea : wow64!whNtSetInformationFile_FileRenameInformation+0x12e 000000000567e310 000000006fac6245 : 0000000000000008 00000000002b3000 000000006fac8b50 000000000577d3e4 : wow64!whNtSetInformationFile+0x260 000000000567e3d0 000000006fb11c87 : 0000002377896ccc 0000000000000023 0000000000000000 000000000577ce4c : wow64!Wow64SystemServiceEx+0x155 000000000567ec90 000000006facbdb2 : 000000000577f798 000000000567eda0 0000000000000000 000000000567eda0 : wow64cpu!ServiceNoTurbo+0xb 000000000567ed40 000000006facbcc0 : 0000000000000000 000000000567eda0 0000000000000000 0000000000000000 : wow64!RunCpuSimulation+0x22 000000000567ed70 00007ffec2956e91 : 0000000000000000 000000006facbba0 0000000000000000 0000000000000000 : wow64!Wow64LdrpInitialize+0x120 000000000567f020 00007ffec2956d5e : 000000000567f0f0 0000000000000000 0000000000290000 0000000000000000 : ntdll!_LdrpInitialize+0xdd 000000000567f0a0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: bb1c2fb3317132bd6fbf96a0229f54dfdf5ba9db

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0731279bccaf96f2142000e7b23d8b3dadaf73d4

THREAD_SHA1_HASH_MOD: add903237f466a79bb56f83a89d0ccf67f536f88

FOLLOWUP_IP:
aswSP+6e3d4
fffff801`97eee3d4 85c0 test eax,eax

FAULT_INSTR_CODE: 4478c085

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: aswSP+6e3d4

FOLLOWUP_NAME: MachineOwner

BUCKET_ID_FUNC_OFFSET: 6e3d4

FAILURE_BUCKET_ID: AV_R_INVALID_aswSP!Unknown_Function

BUCKET_ID: AV_R_INVALID_aswSP!Unknown_Function

PRIMARY_PROBLEM_CLASS: AV_R_INVALID_aswSP!Unknown_Function

TARGET_TIME: 2016-05-16T22:44:07.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-02-24 06:48:00

BUILDDATESTAMP_STR: 160223-1728

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

ANALYSIS_SESSION_ELAPSED_TIME: 1d2e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_r_invalid_aswsp!unknown_function

FAILURE_ID_HASH: {81409b58-23ad-1c5a-3ad9-cd1fdfbd1e64}

Followup: MachineOwner

from dokan-dotnet.

Please can you run each test separate to identify the test causing the BSOD when NetworkDrive is used?

Von: viciousviper [mailto:[email protected]]
Gesendet: Dienstag, 17. Mai 2016 01:10
An: dokan-dev/dokan-dotnet [email protected]
Cc: Babic Marinko [email protected]; Mention [email protected]
Betreff: Re: [dokan-dev/dokan-dotnet] Doesn't work with DokanSetup_1.0.0-RC1.exe (#68)

Haven't had the time to check with mirror.exe /n - sorry.

WinDbg analysis results attached. I have a nagging suspicion that Avast Free Antivirus is involved in the crash - although I did disable it before executing the .NET test suite, and there is still the fact that all is well with DokanOptions.RemoteDrive instead of DokanOptions.NetworkDrive.

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available

************* Symbol Path validation summary **************
Response Time (ms) Location
OK C:\Program Files\Dokan\Dokan Library-1.0.0
Deferred srvhttps://msdl.microsoft.com/download/symbols
Symbol search path is: C:\Program Files\Dokan\Dokan Library-1.0.0;srvhttps://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff800bf890000 PsLoadedModuleList = 0xfffff800bfb6ecd0
Debug session time: Tue May 17 00:44:07.114 2016 (UTC + 2:00)
System Uptime: 0 days 0:46:24.854
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
.....
Loading unloaded module list
..........
Loading Wow64 Symbols
................................................................
.................

 _____

• Bugcheck Analysis *

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd00223d2c4fe, 0, fffff801972295fe, 2}

*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys

"KERNELBASE.dll" was not found in the image list.
Debugger will attempt to load "KERNELBASE.dll" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload =,.
Unable to add module at 00000000`00000000
Probably caused by : aswSP.sys ( aswSP+6e3d4 )

Followup: MachineOwner

5: kd> !analyze -v

• Bugcheck Analysis *

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffd00223d2c4fe, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801972295fe, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

Debugging Details:

"KERNELBASE.dll" was not found in the image list.
Debugger will attempt to load "KERNELBASE.dll" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload =,.
Unable to add module at 00000000`00000000

DUMP_CLASS: 1

DUMP_QUALIFIER: 402

BUILD_VERSION_STRING: 10586.162.amd64fre.th2_release_sec.160223-1728

SYSTEM_MANUFACTURER:

SYSTEM_PRODUCT_NAME:

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: N/A

BIOS_VENDOR:

BIOS_VERSION:

BIOS_DATE:

BASEBOARD_MANUFACTURER:

BASEBOARD_PRODUCT:

BASEBOARD_VERSION: N/A

DUMP_TYPE: 0

BUGCHECK_P1: ffffd00223d2c4fe

BUGCHECK_P2: 0

BUGCHECK_P3: fffff801972295fe

BUGCHECK_P4: 2

READ_ADDRESS: ffffd00223d2c4fe

FAULTING_IP:
FLTMGR!FltpExpandShortNames+8e
fffff801`972295fe 410fb70c70 movzx ecx,word ptr [r8+rsi*2]

MM_INTERNAL_CODE: 2

IMAGE_NAME: aswSP.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 571e068b

MODULE_NAME: aswSP

FAULTING_MODULE: fffff801971f0000 FLTMGR

CPU_COUNT: 8

CPU_MHZ: a86

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: TE.ProcessHost

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME: 05-17-2016 00:48:51.0274

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

MANAGED_CODE: 1

MANAGED_ENGINE_MODULE: clr

TRAP_FRAME: ffffd00023d2c220 -- (.trap 0xffffd00023d2c220)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000002
rdx=ffffd00023d2c4e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801972295fe rsp=ffffd00023d2c3b0 rbp=0000000000000000
r8=ffffd00023d2c500 r9=ffffd00023d2c500 r10=ffffd00023d2c401
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
FLTMGR!FltpExpandShortNames+0x8e:
fffff801972295fe 410fb70c70 movzx ecx,word ptr [r8+rsi*2] ds:ffffd00023d2c500=005c
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800bf9f1395 to fffff800bf9d2760

STACK_TEXT:

ffffd00023d2bfc8 fffff800bf9f1395 : 0000000000000050 ffffd00223d2c4fe 0000000000000000 ffffd00023d2c220 : nt!KeBugCheckEx
ffffd00023d2bfd0 fffff800bf8c8e91 : 0000000000000000 ffffe0004a8459f0 ffffd00023d2c220 fffff800bf90a0af : nt! ?? ::FNODOBFM::string'+0x10295 ffffd00023d2c0c0 fffff800bf9db9bc : 0000000000000001 0000018000000000 0000000000000000 ffffd00000000800 : nt!MmAccessFault+0x5f1 ffffd00023d2c220 fffff801972295fe : 0000000000000000 0000000000000000 ffffe0004a8459f0 fffff800bf8d3a11 : nt!KiPageFault+0x13c ffffd00023d2c3b0 fffff8019723e1e4 : 0000000000000001 ffffe00000000000 ffffe0004a8459f0 ffffe0004a8459f0 : FLTMGR!FltpExpandShortNames+0x8e ffffd00023d2c440 fffff8019723dbf1 : 0000000000000000 0000000000000000 0000000000000101 ffffe0004a797a10 : FLTMGR!FltpGetNormalizedDestinationFileName+0x68 ffffd00023d2c470 fffff80197eee3d4 : 0000000000004000 0000000000100004 ffffe0004a7280e8 fffff800bf8d3a11 : FLTMGR!FltGetDestinationFileNameInformation+0x191 ffffd00023d2c650 fffff801971f6d21 : 0000000000000000 0000000000000000 ffffe0004a728010 ffffe0004db01010 : aswSP+0x6e3d4 ffffd00023d2c6c0 fffff801971f68cc : ffffd00023d2c880 0000000000000000 ffffe0004a832906 ffffe0004a797a00 : FLTMGR!FltpPerformPreCallbacks+0x2f1 ffffd00023d2c7d0 fffff801971f59fa : 0000000000000000 ffffd00023d2c880 ffffe0004a8327d0 ffffd00023d2c890 : FLTMGR!FltpPassThroughInternal+0x8c ffffd00023d2c800 fffff801971f57fe : 0000000000000000 0000000000000000 0000000000000000 0000000000000001 : FLTMGR!FltpPassThrough+0x16a ffffd00023d2c860 fffff800bf8f9137 : ffffe0004a8327d0 01d1afc47459c5d5 01d1afc47459c5d5 01d1afc47459c5d5 : FLTMGR!FltpDispatch+0x9e ffffd00023d2c8c0 fffff800bf8f900e : ffffe0004a832930 0000000000000000 ffffe0004a8327d0 000000000000003e : nt!IoCallDriverWithTracing+0x47 ffffd00023d2c920 fffff800bf8e8b7f : ffffd00023d2cb80 ffffe0004a8327d0 ffffe0004a8327d0 000000000000003e : nt!IopCallDriverReference+0x8e ffffd00023d2c950 fffff800bf9dcfa3 : 0000000000000aa4 000000000567e378 000000000567ebc0 ffff84d70000003e : nt!NtSetInformationFile+0xacf ffffd00023d2ca90 00007ffec29855b4 : 000000006fad45ae 000000000567e2b0 0000000000000000 000000000567e2f0 : nt!KiSystemServiceCopyEnd+0x13 000000000567e278 000000006fad45ae : 000000000567e2b0 0000000000000000 000000000567e2f0 000000006facc180 : ntdll!NtSetInformationFile+0x14 000000000567e280 000000006fac8db0 : 0000000000000000 000000000840f2c8 000000000577d3f0 000000006fac93ea : wow64!whNtSetInformationFile_FileRenameInformation+0x12e 000000000567e310 000000006fac6245 : 0000000000000008 00000000002b3000 000000006fac8b50 000000000577d3e4 : wow64!whNtSetInformationFile+0x260 000000000567e3d0 000000006fb11c87 : 0000002377896ccc 0000000000000023 0000000000000000 000000000577ce4c : wow64!Wow64SystemServiceEx+0x155 000000000567ec90 000000006facbdb2 : 000000000577f798 000000000567eda0 0000000000000000 000000000567eda0 : wow64cpu!ServiceNoTurbo+0xb 000000000567ed40 000000006facbcc0 : 0000000000000000 000000000567eda0 0000000000000000 0000000000000000 : wow64!RunCpuSimulation+0x22 000000000567ed70 00007ffec2956e91 : 0000000000000000 000000006facbba0 0000000000000000 0000000000000000 : wow64!Wow64LdrpInitialize+0x120 000000000567f020 00007ffec2956d5e : 000000000567f0f0 0000000000000000 0000000000290000 0000000000000000 : ntdll!_LdrpInitialize+0xdd 000000000567f0a0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: bb1c2fb3317132bd6fbf96a0229f54dfdf5ba9db

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0731279bccaf96f2142000e7b23d8b3dadaf73d4

THREAD_SHA1_HASH_MOD: add903237f466a79bb56f83a89d0ccf67f536f88

FOLLOWUP_IP:
aswSP+6e3d4
fffff801`97eee3d4 85c0 test eax,eax

FAULT_INSTR_CODE: 4478c085

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: aswSP+6e3d4

FOLLOWUP_NAME: MachineOwner

BUCKET_ID_FUNC_OFFSET: 6e3d4

FAILURE_BUCKET_ID: AV_R_INVALID_aswSP!Unknown_Function

BUCKET_ID: AV_R_INVALID_aswSP!Unknown_Function

PRIMARY_PROBLEM_CLASS: AV_R_INVALID_aswSP!Unknown_Function

TARGET_TIME: 2016-05-16T22:44:07.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-02-24 06:48:00

BUILDDATESTAMP_STR: 160223-1728

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.162.amd64fre.th2_release_sec.160223-1728

ANALYSIS_SESSION_ELAPSED_TIME: 1d2e

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_r_invalid_aswsp!unknown_function

FAILURE_ID_HASH: {81409b58-23ad-1c5a-3ad9-cd1fdfbd1e64}

Followup: MachineOwner

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com//issues/68#issuecomment-219575373 https://github.com/notifications/beacon/ADHSOHFjnTcPolO7wSr8ydargi-fLd1qks5qCPlMgaJpZM4HdfM-.gif

from dokan-dotnet.

Just to give you one example: The very first test in the cronological sequence of unit tests - ContextTests.Create_PassesContextCorrectly - causes a BSOD. I am pretty sure that many other tests will also run into the BSOD - but I can't tell you precisely which ones because I haven't had the nerve to crash my machine 93 times.
BTW forget the OverlappedTests - they fail in mode REMOTE_DRIVE, too.

from dokan-dotnet.

I can't reproduce your issue. All ContextTests work fine even if the NETWORK_DRIVE conditional compilation symbol is set. I tested it on Windows 10 x64.

@Liryna
Can you reproduce the here described BSOD on your machine?

from dokan-dotnet.

@marinkobabic
I have run all tests with NETWORK_DRIVE conditional compilation symbol set as you, no BSOD 😢

from dokan-dotnet.