Jump to content
Covecube Inc.

chamelious

Members
  • Content Count

    11
  • Joined

  • Last visited

  1. Filter Name Num Instances Altitude Frame ------------------------------ ------------- ------------ ----- wcnfs 0 409900 0 WdFilter 6 328010 0 storqosflt 0 244000 0 wcifs 1 189900 0 FileCrypt 0 141100 0 luafv 1 135000 0 npsvctrig 1 46000 0 Fi
  2. Uploaded to your dropbox. Standard win10 AV, stablebit drivescan. Memory was tested for 24 hours+ recently.
  3. Went for a month or two without this happening, now its started up again. No new software installed, machine is basically a file server. Win10 full upto date, drivepool ver 2.2.0.747 Thanks Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Mon 12/06/2017 09:14:03 your computer crashed crash dump file: C:\WINDOWS\Minidump\061217-16750-01.dmp This was probably caused by the following module: covefs.sys (covefs+0x34D04) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF85CF4CC7, 0x0, 0x30020248) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\WIND
  4. FYI this happened again today to me. Utorrent no longer installed, have a different BT client but it wasn't running at the time. I do also have a dropbox client installed on my system, though i haven't noticed any mention of it on the bugchecks or logs. Will install the beta listed above if you can provide x86....Nm i changed the link and grabbed the exe. Going to try removing dropbox also, as its not essential that it runs on this machine
  5. Disk 3 is indeed the pool i'll ignore these. Will let you know if i have another crash.
  6. After installing the beta, on startup i get a bunch of warnings in the event log like this: "The IO operation at logical block address 0x21 for Disk 3 (PDO name: \Device\00000029) was retried." Event ID 153.
  7. Thanks, unfortunately i did have another crash this morning, so i've installed the beta, and will see how i get on with that. I've also set my BT client to download to a folder on my C: drive (not part of the pool) and then move it to the pool after, so i think this will probably rule out the BT client directly causing this issue.
  8. Thanks! I recently switched BT clients, and i haven't actually had a crash since, i wonder if it was something to do with the way my old client was writing to the disk. Anyway as soon as/if i have another i will try the beta.
  9. I get this warning in event viewer on every startup. I understand its pretty normal in W10 and probably not related, though i've tried every fix i could find for it anyway: "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{8ffa07ba-1680-11e7-924c-001d6054fdd9}#0000000002004400." - event ID 219 Memory.dmp file: https://www.dropbox.com/s/jrka7tv9d3xvvhl/MEMORY.zip?dl=0
  10. Results from fltmc: Filter Name Num Instances Altitude Frame ------------------------------ ------------- ------------ ----- wcnfs 0 409900 0 MBAMProtector 6 328800 0 WdFilter 6 328010 0 storqosflt 0 244000 0 wcifs 1 189900 0 FileCrypt 0 141100 0 luafv 1 1
  11. Been pulling my hair out with this. Sometimes it'll be a few hours, sometimes it can be 3-4 days, but sooner or later my machine will reboot without warning. 4 times out of 5 theres no dump, but other times its always the same: The minidump shows this: "On Mon 24/04/2017 21:18:57 your computer crashed crash dump file: C:\WINDOWS\Minidump\042417-10515-01.dmp This was probably caused by the following module: covefs.sys (covefs+0x27DDC) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000047, 0xFFFFFFFF81CAF7AD, 0xFFFFFFFF88CEA398, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M Bug check desc
×
×
  • Create New...