covefs.sys causing my computer to crash?

[Fox01]

From my googling covefs.sys is stable bit and I'm getting BSOD with the message KERNEL_MODE_HEAP_CORRUPTION, I did uninstall stable bit and everything seems to be stable now and I did try to reinstall stable bit and the issue came back.

 

I did use WinDbg to analyze minidump files generated during the crash and that's where it pointed me to.

 

Any help would be grateful, everything is up to date Including stable bit.

[Shane]

Good to see. I'd suggest opening a ticket with StableBit to report your WinDbg analysis of the BSOD with 2.3.11 and that reverting to 2.3.8 stopped it, in case it's useful / they can ask for the dumps from the crash to trace the problem.

[Shane]

Hi Fox01, just to confirm what version of DrivePool are you running?

[Fox01]

21 minutes ago, Shane said:

Hi Fox01, just to confirm what version of DrivePool are you running?

I’m on 2.3.11.1663 and windows 11 all up to date

[Shane]

If you uninstall DrivePool 2.3.11.1663 and install DrivePool 2.3.8.1600 (download folder link) does the BSOD stop happening?

[Fox01]

53 minutes ago, Shane said:

If you uninstall DrivePool 2.3.11.1663 and install DrivePool 2.3.8.1600 (download folder link) does the BSOD stop happening?

So when I first tired to install it failed and I had to use windows troubleshooter to remove the broken install, rebooted and tried again and now so far so good. 

[Christopher (Drashna)]

Yeah, BSOD's shouldn't happen at all.  If they are, and especially with covefs.sys, that's likely a bug or bad interaction.  

I think you already have, but opening a ticket is always the best bet in this type of case. 

[surfercool]

I have exactly the same issue. BSOD around every 30Minutes 
2.3.11 1663

Statistics: 5 Drives 3X 16TB, 2x 12TB
Files: 3020618 / Folders: 5598 Size: 1175GB
with Duplication: Files 5919600 / Folders 23015 Size: 2342 GB 
avarage Filesize: 412KB (1KB - 50GB)
 

Bug Check Code	Parameter 1	Parameter 2	Parameter 3	Parameter 4	Caused By Driver	Caused By Address

0x0000013a

00000000`00000011

ffffc508`ba400140

ffffc508`c9481740

00000000`00000000

covefs.sys

covefs.sys+47000

I upload a Full Dumpfile to the provided link 

[## 289 ##] Bluescreen Covefs.sys

Thanks for your help

The Betaversion 2.3.9.1612 does not crash at all!

[surfercool]

The migration from DrivePool back to Microsoft Storage Spaces was an unavoidable necessity due to severe performance issues and extreme!!!!!!! instability when managing my now 8 million files (1.5 TB). The older DrivePool version 1600 caused significant performance degradation, especially during the measuring process, as it would lock the entire pool and leading to frequent crashes too. This meant that the process was never fully completed. The lengthy indexing times of over 24 hours were unacceptable.

In hindsight, this software investment was not worthwhile.

Unfortunately, the current version and all beta versions suffer from the same issue. The system starts, measures for 5 minutes, and then crashes with a kernel heap error, requiring a restart. This problem occurs continuously.

Even direct contact with support has not yielded a solution. Despite sending a full dump, I have not received any further communication."

[Willan]

I am getting the same crash: 

Filename    Address In Stack    From Address    To Address    Size    Time Stamp    Time String    Product Name    File Description    File Version    Company    Full Path
covefs.sys    covefs.sys+47000    fffff803`228e0000    fffff803`22931000    0x00051000    0x66f0a811    2024/09/23 01:28:17                         
ntoskrnl.exe    ntoskrnl.exe+22bb1e    fffff803`1c800000    fffff803`1d847000    0x01047000    0x3abd2e6d    2001/03/25 01:31:57                         

I have uninstalled and moved back to spaces as well.          
 

[surfercool]

Despite waiting nearly a month, I have yet not receive any updates or responses from Covecube regarding this matter. It appears that my problem are not being addressed.

Windows Spaces is currently storing approximately 18 million files, totaling 3TB. I have not experienced any issues thus far. There has been no file fragmentation, even though StablebitPool has continuously generated a significant number of file fragments through its constant balancing and moving operations. In some instances, a 200kB file contained up to 100 fragments. The SSD cache performance is underwhelming. The utilization of the SSD cache alone results in extremely slow copy speeds.

The observed slow copy speeds can be attributed to performance limitations within the DrivePool software. When utilizing PrimoCache in conjunction with Windows Storage Spaces, a substantial performance improvement was noted, with copy speeds exceeding 200MB/s for identical files. Conversely, Stablebit DrivePool exhibited significantly lower transfer rates, averaging between 10 and 20MB/s, and was accompanied by frequent errors.

It is important to highlight the pervasive instability of Stablebit DrivePool, which manifested in frequent system crashes occurring every 5 minutes or less. These system crashes, commonly known as "blue screens of death," occurred hundreds of times daily, measuring impossible.

[Shane]

Hi surfercool, it's unfortunate that you've had no response to your ticket since there seems to have been a small rash of BSOD issues with ~2.3.11. You mention 2.3.9.1612 does not crash on your system, is there any reason not to stick with it?

That you're getting such poor rates and constant crashes, and that DrivePool is being triggered to constantly perform balancing operations (I might suggest you turn off automatic balancing to see if that helps), does have me curious as to what hardware you're running DrivePool on and what software you're running alongside it. Is it something really heavy in terms of disk IO?