Jump to content
Covecube Inc.
  • Announcements

    • Christopher (Drashna)

      Login issues   11/07/17

      If you have issues with logging in, make sure you use your display name and not the "username" or email.  Or head here for more info.   http://community.covecube.com/index.php?/topic/3252-login-issues/  
    • Christopher (Drashna)

      Getting Help   11/07/17

      If you're experiencing problems with the software, the best way to get ahold of us is to head to https://stablebit.com/Contact, especially if this is a licensing issue.    Issues submitted there are checked first, and handled more aggressively. So, especially if the problem is urgent, please head over there first. 
  • 0
akiller

Windows 10: BSOD caused by covefs.sys

Question

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.:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff800`23a83000 PsLoadedModuleList = 0xfffff800`23de4fd0
Debug session time: Sun Nov 12 17:30:08.591 2017 (UTC - 5:00)
System Uptime: 6 days 22:32:59.653
*******************************************************************************
*                                                                             *
*                        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: 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.

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

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`3a9b9215 8b4804          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`3a9b9215 8b4804          mov     ecx,dword ptr [rax+4] ds:002b:00000000`00000004=00000000
Resetting default 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`00000000 00000000`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`17b620d0 00000000`00000000 ffff8209`17b620d0 : nt!IofCallDriver+0x59
ffffb709`4451e500 ffff8209`0a0d91e0 : ffff8209`17b620d0 00000000`00000000 ffff8209`17b620d0 ffff8209`00000078 : covefs+0x55473
ffffb709`4451e508 ffff8209`17b620d0 : 00000000`00000000 ffff8209`17b620d0 ffff8209`00000078 fffff805`3c0e3c10 : 0xffff8209`0a0d91e0
ffffb709`4451e510 00000000`00000000 : ffff8209`17b620d0 ffff8209`00000078 fffff805`3c0e3c10 00000000`00000000 : 0xffff8209`17b620d0


FOLLOWUP_IP: 
covefs+55473
fffff805`3c105473 898424e8000000  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+55473

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

 

 

Thanks :)

Share this post


Link to post
Share on other sites

19 answers to this question

Recommended Posts

  • 0

Interesting. I'm currently on 10.0.15063 on my server. I'm not having any issues overall, but I believe my server does want me to install some updates, so we'll see.

I am running 10.0.16299 on my desktop computer and it seems OK as well. It is running DP, but only 1 small, 2-drive pool.

UPDATE: I had to manually trigger the update, but my server is now at 10.0.16299. So far, so good, but we'll see.

Share this post


Link to post
Share on other sites
  • 0

I'm getting this same same ntfs.sys crash on 1709.  If I save a file with Excel 2010 back to the drivepool it crashes.  I can save to the raw drive, I can even save to a different filename on the drivepool, but if I save back to the same filename I opened it crashes.  For some reason, my ability to roll back was gone so I reinstalled Windows 10 from scratch.  I installed just Drivepool and Office 2010 and as soon as I upgraded to the Fall Creators Update (1709 16299.19) I got the same crash.  I've now rolled back to the Creators Update from March (1703 15063.674) and this no longer happens.

thanks,

-tom

Share this post


Link to post
Share on other sites
  • 0
8 hours ago, tomb10 said:

I'm getting this same same ntfs.sys crash on 1709.  If I save a file with Excel 2010 back to the drivepool it crashes.  I can save to the raw drive, I can even save to a different filename on the drivepool, but if I save back to the same filename I opened it crashes.  For some reason, my ability to roll back was gone so I reinstalled Windows 10 from scratch.  I installed just Drivepool and Office 2010 and as soon as I upgraded to the Fall Creators Update (1709 16299.19) I got the same crash.  I've now rolled back to the Creators Update from March (1703 15063.674) and this no longer happens.

thanks,

-tom

 

Interesting, I think I'm on Excel 2016 not 2010 but apart from that it's the same.

Hopefully this means there's more chance of it getting fixed as I don't want to revert to the older version of Windows 10. Everything else that uses my pool seems to work fine though.

Share this post


Link to post
Share on other sites
  • 0

It's interesting how this problem seems to be so specific to certain programs. Maybe I haven't had any issues because I don't use Dropbox at all, and I haven't had a reason to use Excel since getting the Fall Creators update. Sometimes this tech stuff seems so mysterious, like maybe we need a seance or something to fix them.

Share this post


Link to post
Share on other sites
  • 0

I had no idea there are multiple ways to open files. I have a feeling that the details would get ultra-nerdy in a hurry.

Oh, and no crashes on my server overnight.

Share this post


Link to post
Share on other sites
  • 0
21 hours ago, Christopher (Drashna) said:

Yeah, I believe this issue has already been fixed. 

Try this build and see if it fixes the issue:
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.877_x64_BETA.exe

 

I've installed that version and fingers crossed my DropBox has synced and not crashed, cheers :).

Your main website is still showing 852, not sure if this is intended!

 

 

Share this post


Link to post
Share on other sites
  • 0
On 11/14/2017 at 5:58 AM, ikon said:

I had no idea there are multiple ways to open files. I have a feeling that the details would get ultra-nerdy in a hurry.

Oh, and no crashes on my server overnight.

hahaha,  You have no edea. :)

Run, while you can! :P

But yeah, file systems are super complicated and complex!

 

And glad to hear it! 

On 11/14/2017 at 9:59 AM, akiller said:

I've installed that version and fingers crossed my DropBox has synced and not crashed, cheers :).

Your main website is still showing 852, not sure if this is intended!

Intentional (See below)

4 hours ago, ikon said:

I have noticed that the main download page rarely, if ever, shows the latest Beta version.

Public vs internal betas.  The public ones go through a testing  cycle, while the internal ones do not. 

The internal ones are to deal with issues immediately, so we can verify fixes, and get people's systems back up and running immediately (as possible)

1 hour ago, HS86 said:

The seems to be similar to the issue I was having: 

I am still on build 870 and I can't reproduce the issue anymore.

 

Glad to hear it! 

Share this post


Link to post
Share on other sites
  • 0

I'm on Windows 10 Pro, version 1709. Assuming that is the Fall Creators Update, I can still report that it has not crashed. I don't know exactly when it was upgraded because I can't seem to find a place where the dates are shown.

Share this post


Link to post
Share on other sites
  • 0

Had a BSOD related to ntfs.sys while saving a Word document in a drivepool drive.

Downloading the beta right now!

Edit: similar minidump that the one @akiller posted 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 16299 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff800`d0a1f000 PsLoadedModuleList = 0xfffff800`d0d80fb0
Debug session time: Fri Nov 17 16:14:49.785 2017 (UTC - 5:00)
System Uptime: 0 days 21:55:58.649
*******************************************************************************
*                                                                             *
*                        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: fffff80292029215, Address of the instruction which caused the bugcheck
Arg3: ffffa98713eec4a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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
fffff802`92029215 8b4804          mov     ecx,dword ptr [rax+4]

CONTEXT:  ffffa98713eec4a0 -- (.cxr 0xffffa98713eec4a0)
rax=0000000000000000 rbx=ffffab8e83f19360 rcx=0000000000000000
rdx=ffffa98713eed118 rsi=ffff8080f4b31150 rdi=ffffab8e828c07f8
rip=fffff80292029215 rsp=ffffa98713eece90 rbp=0000000000000000
 r8=ffffa98713eecf48  r9=ffffa98713eecf10 r10=ffffa98713eed0b8
r11=ffffab8e828c07f8 r12=0000000000000005 r13=ffff8080f9f6b400
r14=ffffa98713eed118 r15=ffffab8e83f19360
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:
fffff802`92029215 8b4804          mov     ecx,dword ptr [rax+4] ds:002b:00000000`00000004=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  WINWORD.EXE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8029212994c to fffff80292029215

STACK_TEXT:  
ffffa987`13eece90 fffff802`9212994c : ffffab8e`994694e0 ffffab8e`99469360 ffffab8e`99469440 fffff802`908169da : NTFS!NtfsDecodeFileObject+0x49
ffffa987`13eeced0 fffff802`92127091 : 00000000`00000000 00000000`00000000 ffffab8e`84ed0df0 ffffab8e`84e75010 : NTFS!NtfsFindTargetElements+0x48
ffffa987`13eecf40 fffff802`92142cef : ffffab8e`828c0701 ffffab8e`828c07f8 ffff8081`00000000 ffffab8e`00000000 : NTFS!NtfsSetRenameInfo+0x2d5
ffffa987`13eed340 fffff802`92142488 : ffffab8e`828c07f8 ffffab8e`82c2c730 ffffab8e`82c2c700 ffffab8e`8ae58200 : NTFS!NtfsCommonSetInformation+0x76f
ffffa987`13eed420 fffff800`d0a578d9 : ffffab8e`81c38190 ffffab8e`82c2c730 ffffab8e`828c07f8 ffffa987`13eed460 : NTFS!NtfsFsdSetInformation+0xd8
ffffa987`13eed4c0 fffff802`92a85473 : ffffab8e`81c38190 ffffab8e`8a73bcb0 00000000`00000000 ffffab8e`8a73bcb0 : nt!IofCallDriver+0x59
ffffa987`13eed500 ffffab8e`81c38190 : ffffab8e`8a73bcb0 00000000`00000000 ffffab8e`8a73bcb0 ffffab8e`00000078 : covefs+0x55473
ffffa987`13eed508 ffffab8e`8a73bcb0 : 00000000`00000000 ffffab8e`8a73bcb0 ffffab8e`00000078 fffff802`92a63c10 : 0xffffab8e`81c38190
ffffa987`13eed510 00000000`00000000 : ffffab8e`8a73bcb0 ffffab8e`00000078 fffff802`92a63c10 00000000`00000000 : 0xffffab8e`8a73bcb0


FOLLOWUP_IP: 
covefs+55473
fffff802`92a85473 898424e8000000  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 0xffffa98713eec4a0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_covefs+55473

BUCKET_ID:  X64_0x3B_covefs+55473

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

 

Share this post


Link to post
Share on other sites
  • 0
On 11/13/2017 at 12:46 PM, Christopher (Drashna) said:

Yeah, I believe this issue has already been fixed. 

Try this build and see if it fixes the issue:
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.877_x64_BETA.exe

Wow, glad I found this thread quickly.  I woke up to find my desktop had rebooted overnight.    I got the BSoD soon after logging in.   When I saw NTFS and realized Windows 10 had a big update I suspected DrivePool needed an update.   

I was in a catch 22.  I couldn't install the DrivePool update fast enough without BSoD.   I tried Start, Run, MSCONFIG and selected Minimum startup environment.   Well after that I couldn't' even log into Windows!  (it just froze)   I used my Windows USB Recovery Stick and was able to do a system restore point.   I was then able to at least log back in, but again only had a short time before BSoD kicked in.   I clicked start, typed settings, clicked Update & Security, Recovery, and was able to roll back to the previous version of Windows 10.   After that I was able to finally complete the install of the latest Stable Bit Drive Pool beta.  (version shows 2.2.0.877 Beta)   

Should it be safe to try updating Windows 10 again at this point?

What could I have done differently than the above? (without restore point and rolling back Windows 10)

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, Alejandro said:

Had a BSOD related to ntfs.sys while saving a Word document in a drivepool drive.

Downloading the beta right now!

Edit: similar minidump that the one @akiller posted 

Upgrade to the version linked above. 
http://dl.covecube.com/DrivePoolWindows/beta/download/StableBit.DrivePool_2.2.0.877_x64_BETA.exe

It the issue persists, then do this:
http://wiki.covecube.com/StableBit_DrivePool_System_Crashes

 

Posting the text above isn't really helpful, as there isn't really any real info in the post. 

42 minutes ago, JazJon said:

Wow, glad I found this thread quickly.  I woke up to find my desktop had rebooted overnight.    I got the BSoD soon after logging in.   When I saw NTFS and realized Windows 10 had a big update I suspected DrivePool needed an update.   

I was in a catch 22.  I couldn't install the DrivePool update fast enough without BSoD.   I tried Start, Run, MSCONFIG and selected Minimum startup environment.   Well after that I couldn't' even log into Windows!  (it just froze)   I used my Windows USB Recovery Stick and was able to do a system restore point.   I was then able to at least log back in, but again only had a short time before BSoD kicked in.   I clicked start, typed settings, clicked Update & Security, Recovery, and was able to roll back to the previous version of Windows 10.   After that I was able to finally complete the install of the latest Stable Bit Drive Pool beta.  (version shows 2.2.0.877 Beta)   

Should it be safe to try updating Windows 10 again at this point?

What could I have done differently than the above? (without restore point and rolling back Windows 10)

Unplug the drives.  That should stop the issue, at least temporarily.  Then upgrade

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, Christopher (Drashna) said:

Unplug the drives.  That should stop the issue, at least temporarily.  Then upgrade

 

Ah that's a good obvious idea for next time.    My huge tower case is a tight fit between the wall and my desk so not easy to open up very fast though. (but you do what you have to do, and I'll try that instead for future similar issues)

I'll also be careful not to rush any "major" Windows upgrades before checking drivepool updates are ready to rock.    I'm always on the latest beta but this fresh beta build was unreleased as you said.

Share this post


Link to post
Share on other sites
  • 0

I remember there used to be something called Safe Mode. My father talked me through how to use it over the phone one time when my computer wouldn't boot properly. I wondered if Windows 10 still had it. It does, but it seems different from what I remember; maybe a bit more involved. Anyway, here's what an article on the Microsoft site says:

Quote

 

Start your PC in safe mode in Windows 10

Safe mode starts Windows in a basic state, using a limited set of files and drivers. It can help you troubleshoot problems on your PC. For example, if the problem doesn't happen in safe mode, you'll know default settings and basic device drivers aren't causing the issue.

There are two versions of safe mode: Safe Mode and Safe Mode with Networking. They're quite similar, but Safe Mode with Networking includes the network drivers and services you'll need to access the Internet and other computers on your network.

The following sections describe how to start your PC in safe mode.

From Settings
  1. Press Windows logo key Windows logo key  + I on your keyboard to open Settings. If that doesn't work, select the Start  button in the lower-left corner of your screen, then select Settings .
  2. Select Update & security  > Recovery .
  3. Under Advanced startup, select Restart now.
  4. After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.
  5. After your PC restarts, you'll see a list of options. Select 4 or F4 to start your PC in Safe Mode. Or if you'll need to use the Internet, select 5 or F5 for Safe Mode with Networking.
From the sign-in screen
  1. Restart your PC. When you get to the sign-in screen, hold the Shift key down while you select Power> Restart.
  2. After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.

  3. After your PC restarts, you'll see a list of options. Select 4 or F4 to start your PC in Safe Mode. Or if you'll need to use the Internet, select 5 or F5 for Safe Mode with Networking.

 

Share this post


Link to post
Share on other sites
  • 0
On 11/17/2017 at 4:07 PM, JazJon said:

Ah that's a good obvious idea for next time.    My huge tower case is a tight fit between the wall and my desk so not easy to open up very fast though. (but you do what you have to do, and I'll try that instead for future similar issues)

I'll also be careful not to rush any "major" Windows upgrades before checking drivepool updates are ready to rock.    I'm always on the latest beta but this fresh beta build was unreleased as you said.

Yup. Otherwise, it's more complicated

On 11/18/2017 at 7:49 AM, ikon said:

I remember there used to be something called Safe Mode. My father talked me through how to use it over the phone one time when my computer wouldn't boot properly. I wondered if Windows 10 still had it. It does, but it seems different from what I remember; maybe a bit more involved. Anyway, here's what an article on the Microsoft site says:

Yup.  Win8 and up .... it's much harder to get into, in part because the OS boots so bloody fast. 

And ghe pool still loads in safe mode. So ... it may not help.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×