Erik Wright

Hey Christopher, Just wanted to confirm that whatever Alex changed in the 2.2.0.747 BETA update fixed the Blue Screen of Death conflict with DropBox. Awesome job guys, will keep you posted if anything else changes on the insider builds. Erik

I actually have WinDBG installed and attempted to analyze the dumpfiles myself, but only see covefs.sys in my analysis. Then again, bugchecks are a little out of my territory, and I know they're not always correct, so I'll leave it to Alex to take a look at. Just for giggles, I moved my DropBox folder to the only internal HDD not in a DrivePool disk pool and I get no bluescreens, so this further confirms the suspicion that DropBox is making calls that DrivePool doesn't like. Anywho, I'll keep an eye on this thread when you guys have an update or a beta release for me to test. No need to reply until then though. Thanks!

Hey @Christopher, thanks for looking into my bugcheck - I know Insider Builds can be rather difficult to diagnose because things change a lot. The Event Viewer does show a lot of errors related to DbxSvc, so I'm with you there. It seems to be a DropBox conflict of some kind. Failed to connect to the driver: (-2147024894) The system cannot find the file specified. Failed to open file: C:\WINDOWS\Minidump\fd50d22e-5d8d-473d-85e0-c35cbd90b141.dmp, error: (2) The system cannot find the file specified. Failed to get ANSI path for file: C:\WINDOWS\Minidump\fd50d22e-5d8d-473d-85e0-c35cbd90b141.dmp I rebooted to install Windows 10 Version 1703 Build 16188.rs_prerelease.170430-1928 after disabling the DrivePool service, just in case. It installed fine. After logging in, I went to check this forum thread, and enabled the DrivePool service. DropBox was running at the time too. I BSOD'd twice. Since then, I have done the following: Enabled the DrivePool service in services.msc and checked to see that it's running via the DrivePool app Closed and completely exited DropBox from the system tray, and disabled the DbxSvc from services.msc I've also attached the 2 additional bugchecks in another ZIP from lunchtime today, just in case they help shed some light on the situation. If you don't mind my asking, what revealed it was DropBox in my bugchecks? I want to head on over to their support community and let them know about the issue so they can fix it, as I use DropBox for work, so I kind of need it... KRYSTALOGI-2017-05-06_124604_46.zip

I hate to be that guy who posts in someone else's thread rather than starting my own, but I too just recently started having the exact same issues so I figured I'd tack on my two bits. Now, to be fair, I'm running the Fast Ring Insider Build of Windows 10, specifically Windows 10 Version 1703 Build 16179.rs_prerelease.170414-1642 so that might have something to do with it. I've had 3 BSOD's today alone (they're actually Green Screens of Death due to running Insider Preview Builds, but I digress) all pointing to covefs.sys as the culprit. If I manually disable the StableBit DrivePool service from my services.msc list, I don't experience the crashes, so that really points things in the right direction. Here's what I'm going to do though: I'll update DrivePool from 2.2.676 to the latest beta, in this case 2.2.0.746, and report back with my results. I should also check my event log as @chamelious has done to make sure nothing weird is going on, so I'll do that next reboot. Tonight I'm going to install Insider Build 16188.1000 as well, so we'll see how that goes with the updated DrivePool software. Attached is a zip containing my Minidump files and other diagnostic information as collected by the DM_log_collector tool from tenforums.com, just in case you wanted to take a look. KRYSTALOGI-2017-05-05_222545_43.zip

From my 5 years both selling consumer electronics and repairing computers in a retail situation, I've yet to come across a Seagate drive with any fancy trickery going on under the hood. Usually its the Western Digital drives that have circuit boards with hardware encryption chips built in that cause the drive to appear scrambled when not used inside its' original enclosure. A useful feature for data security and encryption for sure, but very annoying if say the enclosure or drive begins to fail and you want to try to save the data... *Western Digital drives that have these logic boards can be used outside of their enclosures, but they must be re-formatted once taken out of their enclosure.