Bluescreen and System restart

[Tweak3D]

I started having an issue a few days ago and i'm not sure of the exact cause, but the crash is indicating that covefs.dll is causing my problem. I've noted twice now while read and writing at the same time to the disk, after some time, the system bluescreens and reboots. Here are some details

 

File Server is a virtual machine (esxi), its running Server 2012 R2 with all applicable updates.It was moved a few weeks ago from one host to another. This was when I began using drivepool (which I am overall very happy with). I am running the beta version 2.2.0.651. The normal version was giving me some issues. If the suggestion is downgrading to the stable version, that is acceptable, but I wanted to report this none the less.

 

Here are the details from the crash and windows dump file:

 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000047, 0xfffff800dfb0d7dc, 0xffffe00011db6d70, 0x0000000000007183). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 010116-30359-01.

 

 

Microsoft ® Windows Debugger Version 10.0.10586.567 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [N:\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

 

Symbol search path is: srv*

Executable search path is: 

Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64

Product: Server, suite: TerminalServer SingleUserTS

Built by: 9600.18146.amd64fre.winblue_ltsb.151121-0600

Machine Name:

Kernel base = 0xfffff800`dfa14000 PsLoadedModuleList = 0xfffff800`dfce8630

Debug session time: Fri Jan  1 22:54:24.978 2016 (UTC - 8:00)

System Uptime: 0 days 14:19:44.344

Loading Kernel Symbols

...............................................................

................................................................

............................

Loading User Symbols

 

Loading unloaded module list

..................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1E, {ffffffffc0000047, fffff800dfb0d7dc, ffffe00011db6d70, 7183}

 

*** ERROR: Module load completed but symbols could not be loaded for covefs.sys

Probably caused by : covefs.sys ( covefs+361bd )

 

Followup:     MachineOwner

---------

 

2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck.  Usually the exception address pinpoints

the driver/function that caused the problem.  Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000047, The exception code that was not handled

Arg2: fffff800dfb0d7dc, The address that the exception occurred at

Arg3: ffffe00011db6d70, Parameter 0 of the exception

Arg4: 0000000000007183, Parameter 1 of the exception

 

Debugging Details:

------------------

 

 

DUMP_CLASS: 1

 

DUMP_QUALIFIER: 401

 

BUILD_VERSION_STRING:  9600.18146.amd64fre.winblue_ltsb.151121-0600

 

SYSTEM_MANUFACTURER:  VMware, Inc.

 

VIRTUAL_MACHINE:  VMware

 

SYSTEM_PRODUCT_NAME:  VMware Virtual Platform

 

SYSTEM_VERSION:  None

 

BIOS_VENDOR:  Phoenix Technologies LTD

 

BIOS_VERSION:  6.00

 

BIOS_DATE:  09/30/2014

 

BASEBOARD_MANUFACTURER:  Intel Corporation

 

BASEBOARD_PRODUCT:  440BX Desktop Reference Platform

 

BASEBOARD_VERSION:  None

 

DUMP_TYPE:  1

 

BUGCHECK_P1: ffffffffc0000047

 

BUGCHECK_P2: fffff800dfb0d7dc

 

BUGCHECK_P3: ffffe00011db6d70

 

BUGCHECK_P4: 7183

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

 

FAULTING_IP: 

nt!RtlRaiseStatus+18

fffff800`dfb0d7dc 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

 

EXCEPTION_PARAMETER1:  ffffe00011db6d70

 

EXCEPTION_PARAMETER2:  0000000000007183

 

BUGCHECK_STR:  0x1E_c0000047

 

CPU_COUNT: 4

 

CPU_MHZ: 893

 

CPU_VENDOR:  GenuineIntel

 

CPU_FAMILY: 6

 

CPU_MODEL: 3e

 

CPU_STEPPING: 4

 

CPU_MICROCODE: 6,3e,4,0 (F,M,S,R)  SIG: 428'00000000 (cache) 428'00000000 (init)

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

PROCESS_NAME:  System

 

CURRENT_IRQL:  0

 

ANALYSIS_SESSION_HOST:  DESKTOP-JUSTIN

 

ANALYSIS_SESSION_TIME:  01-02-2016 08:33:30.0292

 

ANALYSIS_VERSION: 10.0.10586.567 x86fre

 

LAST_CONTROL_TRANSFER:  from fffff800dfb91b8f to fffff800dfb628a0

 

STACK_TEXT:  

ffffd000`20e749f8 fffff800`dfb91b8f : 00000000`0000001e ffffffff`c0000047 fffff800`dfb0d7dc ffffe000`11db6d70 : nt!KeBugCheckEx

ffffd000`20e74a00 fffff800`dfa89dd4 : 00000000`00000000 00000000`0003fc88 ffffa768`6fccda0f fffff800`c0aa4829 : nt! ?? ::FNODOBFM::`string'+0x1edcf

ffffd000`20e750f0 fffff800`dfb631db : 00040054`ffffffff ffffe000`10eaba00 ffffe000`10ea9880 ffffe000`10eaba00 : nt!KiRaiseException+0x1a4

ffffd000`20e75230 fffff800`dfb6e0b3 : ffffd000`20e75750 fffff800`c0c29180 ffffe000`1160b840 00000000`00000000 : nt!NtRaiseException+0x7b

ffffd000`20e75370 fffff800`dfb0d7dc : fffff800`c0c29180 00000000`00000002 00000000`c0000047 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

ffffd000`20e75510 fffff800`dfb9c620 : ffffe000`16e421b0 ffffe000`1328d880 00000000`00000000 ffffe000`100952c0 : nt!RtlRaiseStatus+0x18

ffffd000`20e75ab0 fffff800`c099c1bd : fffff800`00000000 ffffe000`00000001 ffffe000`00000000 fffff800`c099bb60 : nt! ?? ::FNODOBFM::`string'+0x29860

ffffd000`20e75b70 fffff800`c04d2b1e : ffffe000`10f96040 ffffe000`12ce2160 ffffe000`12ce2168 ffffe000`12ce2190 : covefs+0x361bd

ffffd000`20e75c30 fffff800`c04d10c2 : ffffd000`20e75cf0 ffffe000`10f41390 ffffe000`1230d3b0 ffffe000`12ce2160 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2ce

ffffd000`20e75cd0 fffff800`c21400b2 : ffffe000`1230d6d0 ffffe000`1230d6d0 ffffd000`20e75e80 ffffe000`1230d3b0 : fltmgr!FltpDispatch+0xb2

ffffd000`20e75d30 fffff800`c213ea86 : ffffd000`20e75e80 fffff800`c2135010 ffffe000`13642a38 ffffe000`1230d6d0 : srv2!Smb2ExecuteRead+0x1c2

ffffd000`20e75dc0 fffff800`c213e607 : ffffe000`1230d3b0 ffffe000`1230d3b0 ffffe000`11c8f830 ffffe000`1230d3b0 : srv2!Smb2ExecuteProviderCallback+0x56

ffffd000`20e75e20 fffff800`c213c19f : ffffe000`11c8e160 ffffe000`11c8e160 00000000`00000002 ffffe000`1230d3b0 : srv2!SrvProcessPacket+0xed

ffffd000`20e75ee0 fffff800`dfb661f7 : ffffe000`11c8e160 ffffe000`00000001 ffffe000`00000004 d30726b6`000000a3 : srv2!SrvProcpWorkerThreadProcessWorkItems+0x18f

ffffd000`20e75f80 fffff800`dfb661bd : fffff800`c213df01 00000000`0000c000 00000000`00000003 fffff800`dface16d : nt!KxSwitchKernelStackCallout+0x27

ffffd000`20749a00 fffff800`dface16d : 00000000`00000012 fffff800`c213df01 00000000`00000006 ffffe000`1328d880 : nt!KiSwitchKernelStackContinue

ffffd000`20749a20 fffff800`c20fc926 : fffff800`c213c010 ffffe000`11c8e160 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x2fd

ffffd000`20749b10 fffff800`dfaa34bf : fffff800`c213dfdc ffffe000`1328d880 ffffe000`11c8e1b8 00000000`00000000 : srv2!SrvProcWorkerThreadCommon+0x66

ffffd000`20749b50 fffff800`dfb10554 : ffffd000`20749c80 ffffe000`1328d880 00000000`00000080 ffffe000`1328d880 : nt!ExpWorkerThread+0x69f

ffffd000`20749c00 fffff800`dfb68ec6 : fffff800`dfd12180 ffffe000`1328d880 ffffe000`0ff62040 fffff800`dfaf8f63 : nt!PspSystemThreadStartup+0x58

ffffd000`20749c60 00000000`00000000 : ffffd000`2074a000 ffffd000`20744000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

 

 

STACK_COMMAND:  kb

 

THREAD_SHA1_HASH_MOD_FUNC:  5a288c5295cacb528a1b5792210a27b37096b3f9

 

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d1e647a267c887b7d4a11a9b33a3fd37c66b9aaa

 

THREAD_SHA1_HASH_MOD:  dbe42daf39ced1d826bb55701a412aab928b12de

 

FOLLOWUP_IP: 

covefs+361bd

fffff800`c099c1bd 488d4c2478      lea     rcx,[rsp+78h]

 

FAULT_INSTR_CODE:  244c8d48

 

SYMBOL_STACK_INDEX:  7

 

SYMBOL_NAME:  covefs+361bd

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: covefs

 

IMAGE_NAME:  covefs.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  5600cdca

 

BUCKET_ID_FUNC_OFFSET:  361bd

 

FAILURE_BUCKET_ID:  0x1E_c0000047_covefs!Unknown_Function

 

BUCKET_ID:  0x1E_c0000047_covefs!Unknown_Function

 

PRIMARY_PROBLEM_CLASS:  0x1E_c0000047_covefs!Unknown_Function

 

TARGET_TIME:  2016-01-02T06:54:24.000Z

 

OSBUILD:  9600

 

OSSERVICEPACK:  0

 

SERVICEPACK_NUMBER: 0

 

OS_REVISION: 0

 

SUITE_MASK:  272

 

PRODUCT_TYPE:  3

 

OSPLATFORM_TYPE:  x64

 

OSNAME:  Windows 8.1

 

OSEDITION:  Windows 8.1 Server TerminalServer SingleUserTS

 

OS_LOCALE:  

 

USER_LCID:  0

 

OSBUILD_TIMESTAMP:  2015-11-21 08:42:09

 

BUILDDATESTAMP_STR:  151121-0600

 

BUILDLAB_STR:  winblue_ltsb

 

BUILDOSVER_STR:  6.3.9600.18146.amd64fre.winblue_ltsb.151121-0600

 

ANALYSIS_SESSION_ELAPSED_TIME: 606

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:0x1e_c0000047_covefs!unknown_function

 

FAILURE_ID_HASH:  {08ffa9ab-93bb-e569-dbe3-f1f7b741b09a}

 

Followup:     MachineOwner

---------

 

Are there any other logs or details I can provide to assist with this issue? Its difficult to reproduce, but has occurred twice in the past 2 days to me.

 

Thanks,

 

Justin

 

[Christopher (Drashna)]

Well, looks to be related to or caused by StableBit DrivePool. 

 

You've already opened a ticket, but I'll repsond here as well:

 

 

 

 

Could you upload the memory dump from the system? 

The dumps include detailed information about what the system was doing at the time of the crash.  This may help us to identify specifically what is going wrong. 

http://wiki.covecube.com/StableBit_DrivePool_System_Crashes

 

Additionally, any time you experience BSODs, it's always a good idea to run a memory test, just in case.

http://wiki.covecube.com/StableBit_DrivePool_Q537229

 

 

Additionally, are you using any antivirus, backup or disk tools on the system?

And could you do this: http://wiki.covecube.com/StableBit_DrivePool_Q2159701