I've been having a few BSODs recently caused by DrivePool. I'm running the latest Windows 10 creators' update, v10.0.16299 - I believe this only started happening after I updated to it. DrivePool is v2.2.0.852.
In this instance I was working on my work PC over remote desktop, saved a file into my DropBox folder which synced it back to my PC (located on my pool) , and it instantly crashed ntfs.sys. I also had this the other week when I was trying to save an excel file locally on my desktop (also located on my pool).
If I move my DropBox folder outside my pool it works fine.
Here's the crash dump, let me know if you want me to send you the full .dmp.:
CrashDumpAnalysis provided by OSR OpenSystemsResources,Inc.(http://www.osr.com)OnlineCrashDumpAnalysisServiceSee http://www.osronline.com for more informationWindows8KernelVersion16299 MP (4 procs)Free x64
Product:WinNt, suite:TerminalServerSingleUserTSBuilt by:16299.15.amd64fre.rs3_release.170928-1534MachineName:Kernel base =0xfffff800`23a83000PsLoadedModuleList=0xfffff800`23de4fd0Debug session time:SunNov1217:30:08.5912017(UTC -5:00)SystemUptime:6 days 22:32:59.653**********************************************************************************BugcheckAnalysis**********************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1:00000000c0000005,Exception code that caused the bugcheck
Arg2: fffff8053a9b9215,Address of the instruction which caused the bugcheck
Arg3: ffffb7094451d4a0,Address of the context record for the exception that caused the bugcheck
Arg4:0000000000000000, zero.DebuggingDetails:------------------
TRIAGER:Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE:(NTSTATUS)0xc0000005-The instruction at "0x%08lx" referenced memory at "0x%08lx".The memory could not be "%s".
FAULTING_IP:
NTFS!NtfsDecodeFileObject+49
fffff805`3a9b92158b4804 mov ecx,dword ptr [rax+4]
CONTEXT: ffffb7094451d4a0 --(.cxr 0xffffb7094451d4a0)
rax=0000000000000000 rbx=ffff82090fd7a4a0 rcx=0000000000000000
rdx=ffffb7094451e118 rsi=ffffcc0f31c1b590 rdi=ffff82090ac464b8
rip=fffff8053a9b9215 rsp=ffffb7094451de90 rbp=0000000000000000
r8=ffffb7094451df48 r9=ffffb7094451df10 r10=ffffb7094451e0b8
r11=ffff82090ac464b8 r12=0000000000000005 r13=ffffcc0f3bb6de50
r14=ffffb7094451e118 r15=ffff82090fd7a4a0
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
NTFS!NtfsDecodeFileObject+0x49:
fffff805`3a9b92158b4804 mov ecx,dword ptr [rax+4] ds:002b:00000000`00000004=00000000Resettingdefault scope
CUSTOMER_CRASH_COUNT:1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR:0x3B
PROCESS_NAME:Dropbox.exe
CURRENT_IRQL:0
LAST_CONTROL_TRANSFER: from fffff8053aab994c to fffff8053a9b9215
STACK_TEXT:
ffffb709`4451de90 fffff805`3aab994c: ffff8209`0a2018d0 ffff8209`0a201750 ffff8209`0a201830 fffff805`399969da: NTFS!NtfsDecodeFileObject+0x49
ffffb709`4451ded0 fffff805`3aab7091:00000000`0000000000000000`00000000 ffff8208`febe44f0 ffff8208`febee550 : NTFS!NtfsFindTargetElements+0x48
ffffb709`4451df40 fffff805`3aad2cef: ffff8209`0ac46401 ffff8209`0ac464b8 ffffcc0f`00000000 ffff8208`00000000: NTFS!NtfsSetRenameInfo+0x2d5
ffffb709`4451e340 fffff805`3aad2488: ffff8209`0ac464b8 ffff8209`17ef2370 ffff8209`17ef2300 ffff8209`0d4d3a00: NTFS!NtfsCommonSetInformation+0x76f
ffffb709`4451e420 fffff800`23ad9339: ffff8209`0a0d91e0 ffff8209`17ef2370 ffff8209`0ac464b8 ffffb709`4451e460: NTFS!NtfsFsdSetInformation+0xd8
ffffb709`4451e4c0 fffff805`3c105473: ffff8209`0a0d91e0 ffff8209`17b620d000000000`00000000 ffff8209`17b620d0: nt!IofCallDriver+0x59
ffffb709`4451e500 ffff8209`0a0d91e0: ffff8209`17b620d000000000`00000000 ffff8209`17b620d0 ffff8209`00000078: covefs+0x55473
ffffb709`4451e508 ffff8209`17b620d0:00000000`00000000 ffff8209`17b620d0 ffff8209`00000078 fffff805`3c0e3c10:0xffff8209`0a0d91e0
ffffb709`4451e51000000000`00000000: ffff8209`17b620d0 ffff8209`00000078 fffff805`3c0e3c1000000000`00000000:0xffff8209`17b620d0
FOLLOWUP_IP:
covefs+55473
fffff805`3c105473898424e8000000 mov dword ptr [rsp+0E8h],eax
SYMBOL_STACK_INDEX:6
SYMBOL_NAME: covefs+55473
FOLLOWUP_NAME:MachineOwner
MODULE_NAME: covefs
IMAGE_NAME: covefs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:59bb1a02
STACK_COMMAND:.cxr 0xffffb7094451d4a0; kb
FAILURE_BUCKET_ID: X64_0x3B_covefs+55473
BUCKET_ID: X64_0x3B_covefs+55473Followup:MachineOwner---------
Question
akiller
Hi,
I've been having a few BSODs recently caused by DrivePool. I'm running the latest Windows 10 creators' update, v10.0.16299 - I believe this only started happening after I updated to it. DrivePool is v2.2.0.852.
In this instance I was working on my work PC over remote desktop, saved a file into my DropBox folder which synced it back to my PC (located on my pool) , and it instantly crashed ntfs.sys. I also had this the other week when I was trying to save an excel file locally on my desktop (also located on my pool).
If I move my DropBox folder outside my pool it works fine.
Here's the crash dump, let me know if you want me to send you the full .dmp.:
Thanks
Link to comment
Share on other sites
19 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.