chamelious
-
Posts
11 -
Joined
-
Last visited
Posts posted by chamelious
-
-
Uploaded to your dropbox. Standard win10 AV, stablebit drivescan. Memory was tested for 24 hours+ recently.
-
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.747Thanks
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:\WINDOWS\system32\drivers\covefs.sys
product: CoveFS
company: Covecube Inc.
description: CoveFS File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: covefs.sys (CoveFS File System Driver, Covecube Inc.).
Google query: Covecube Inc. KMODE_EXCEPTION_NOT_HANDLED
On Mon 12/06/2017 09:14:03 your computer crashed
crash dump file: C:\WINDOWS\memory.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:\WINDOWS\system32\drivers\covefs.sys
product: CoveFS
company: Covecube Inc.
description: CoveFS File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: covefs.sys (CoveFS File System Driver, Covecube Inc.).
Google query: Covecube Inc. KMODE_EXCEPTION_NOT_HANDLED
On Mon 12/06/2017 09:10:57 your computer crashed
crash dump file: C:\WINDOWS\Minidump\061217-17062-01.dmp
This was probably caused by the following module: covefs.sys (covefs+0x34D04)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF85A54CC7, 0x0, 0x30020248)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\covefs.sys
product: CoveFS
company: Covecube Inc.
description: CoveFS File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: covefs.sys (CoveFS File System Driver, Covecube Inc.).
Google query: Covecube Inc. KMODE_EXCEPTION_NOT_HANDLED
On Sun 11/06/2017 14:12:27 your computer crashed
crash dump file: C:\WINDOWS\Minidump\061117-17656-01.dmp
This was probably caused by the following module: covefs.sys (covefs+0x34D04)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFFFF86564CC7, 0x0, 0x30020248)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\covefs.sys
product: CoveFS
company: Covecube Inc.
description: CoveFS File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: covefs.sys (CoveFS File System Driver, Covecube Inc.).
Google query: Covecube Inc. KMODE_EXCEPTION_NOT_HANDLED
Conclusion
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
covefs.sys (CoveFS File System Driver, Covecube Inc.) -
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
-
Disk 3 is indeed the pool i'll ignore these. Will let you know if i have another crash.
-
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.
-
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.
-
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.
-
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:
-
Results from fltmc:
Filter Name Num Instances Altitude Frame------------------------------ ------------- ------------ -----wcnfs 0 409900 0MBAMProtector 6 328800 0WdFilter 6 328010 0storqosflt 0 244000 0wcifs 1 189900 0FileCrypt 0 141100 0luafv 1 135000 0npsvctrig 1 46000 0FileInfo 6 45000 0Wof 4 40700 0 -
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 description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: covefs.sys .
Google query: covefs.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M"And memory.dmp shows this:
"On Mon 24/04/2017 21:18:57 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x8E (0xFFFFFFFFC0000047, 0xFFFFFFFF81CAF7AD, 0xFFFFFFFF88CEA398, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe KERNEL_MODE_EXCEPTION_NOT_HANDLED"Can anyone help please?!
All HDs connected to the system have been vigorously and repeatedly checked. Ram has had memtest run for 4 hours. PSU is fine....system was fine before drivepool.
Network I/O boost is UNCHECKED on drivepool.
covecube.sys causing Win 10 crashes again
in General
Posted