Running DrivePool v2.1.1.561 on a Thecus W5000 with a fully patched Windows Storage Server 2012 R2 Essentials and received my first BSOD (the new, less useful, pastel blue screen). Checking the dump using WINDBG I see the finger pointed at covefs.sys and therefore my first post here is for a potential bug, which is a shame but the nature of support forums.
The results of my limited interactions with the debugger are:
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`3b017000 PsLoadedModuleList = 0xfffff802`3b2f0250
Debug session time: Tue Mar 17 21:38:39.888 2015 (UTC + 0:00)
System Uptime: 6 days 12:44:33.719
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for covefs.sys
Probably caused by : covefs.sys ( covefs+c813 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8023b18a490 to fffff8023b1679a0
STACK_TEXT:
ffffd000`bac77c88 fffff802`3b18a490 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffd000`bac77c90 fffff802`3b06a2c1 : ffffe000`f8600700 00000000`02270c6e 00000000`00000000 ffffe000`f89e3a00 : nt! ?? ::FNODOBFM::`string'+0x125e0
ffffd000`bac77d20 fffff802`3b7b37b5 : ffffc001`6ed98b00 ffffd000`22c0c4c8 00000000`00000000 00000000`00000001 : nt!KeClockInterruptNotify+0x91
ffffd000`bac77f40 fffff802`3b0fceb3 : ffffd000`22c0c340 fffff802`3b117af3 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffd000`bac77f70 fffff802`3b168e2a : ffffe000`f8600700 ffffd000`22c0c4c8 00000000`00000000 ffffc001`6ed98b00 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd000`bac77fb0 fffff802`3b16920f : ffffe000`f8446180 00000000`bbd85590 ffffd000`22c0c4c8 fffff802`3b066c96 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`22c0c2c0 fffff802`3b04e153 : ffffc001`6978e1e2 00000000`00000000 ffffc001`6ed98b00 00000000`00000001 : nt!KiInterruptDispatchLBControl+0x11f
ffffd000`22c0c450 fffff801`3590e813 : ffffe000`fbd24330 ffffd000`22c0c6d0 ffffe000`fbd24330 fffff801`3590ea73 : nt!KxWaitForLockOwnerShip+0x27
ffffd000`22c0c480 fffff801`3591b6bc : ffffe000`fbd24330 ffffe000`f9112bd0 ffffe000`fe1e0018 00000000`00000001 : covefs+0xc813
ffffd000`22c0c500 fffff802`3b0b836a : 00000000`00000000 ffffe000`fbd24330 ffffe000`f9112bd0 fffff802`3b0769de : covefs+0x196bc
ffffd000`22c0c5d0 fffff801`34c506a5 : 00000000`00000001 ffffe000`fe1e0001 ffffd000`22c0cb80 ffffe000`fe1e0198 : nt!IopfCompleteRequest+0x2ea
ffffd000`22c0c710 fffff801`34d09559 : ffffd000`22c0cb80 ffffc001`6eba9670 00000000`00000000 00000000`00000000 : Ntfs!NtfsExtendedCompleteRequestInternal+0x135
ffffd000`22c0c750 fffff801`34d24652 : ffffe000`fbd24330 00000000`00000000 ffffe000`f8446030 00000000`00000001 : Ntfs!NtfsQueryDirectory+0x2180
ffffd000`22c0cb00 fffff801`34c3ed7d : 00000000`00000000 ffffe000`fe1e0018 ffffe000`fe1e0018 ffffe000`fdb37140 : Ntfs!NtfsCommonDirectoryControl+0xa2
ffffd000`22c0cb40 fffff802`3b0c23ac : fffff802`3b0bfa60 fffff801`34c3ebb8 ffffe000`fdb37040 fffff802`3b2c9300 : Ntfs!NtfsFspDispatch+0x1c5
ffffd000`22c0cc90 fffff802`3b0ef280 : 00000000`00000000 ffffe000`fdb37040 00000000`00000080 ffffe000`fdb37040 : nt!ExpWorkerThread+0x28c
ffffd000`22c0cd40 fffff802`3b16dfc6 : ffffd000`b71c0180 ffffe000`fdb37040 ffffd000`b71cc2c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`22c0cda0 00000000`00000000 : ffffd000`22c0d000 ffffd000`22c07000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
covefs+c813
fffff801`3590e813 90 nop
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: covefs+c813
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: covefs
IMAGE_NAME: covefs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53935b14
FAILURE_BUCKET_ID: 0x133_ISR_covefs+c813
BUCKET_ID: 0x133_ISR_covefs+c813
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_covefs+c813
FAILURE_ID_HASH: {bb6e4205-c311-4323-ca4f-d3d109d19a07}
Followup: MachineOwner
---------
3: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00001e00 00000000`00000000 00000000`00000000
3: kd> kn
# Child-SP RetAddr Call Site
00 ffffd000`bac77c88 fffff802`3b18a490 nt!KeBugCheckEx
01 ffffd000`bac77c90 fffff802`3b06a2c1 nt! ?? ::FNODOBFM::`string'+0x125e0
02 ffffd000`bac77d20 fffff802`3b7b37b5 nt!KeClockInterruptNotify+0x91
03 ffffd000`bac77f40 fffff802`3b0fceb3 hal!HalpTimerClockIpiRoutine+0x15
04 ffffd000`bac77f70 fffff802`3b168e2a nt!KiCallInterruptServiceRoutine+0xa3
05 ffffd000`bac77fb0 fffff802`3b16920f nt!KiInterruptSubDispatchNoLockNoEtw+0xea
06 ffffd000`22c0c2c0 fffff802`3b04e153 nt!KiInterruptDispatchLBControl+0x11f
07 ffffd000`22c0c450 fffff801`3590e813 nt!KxWaitForLockOwnerShip+0x27
08 ffffd000`22c0c480 fffff801`3591b6bc covefs+0xc813
09 ffffd000`22c0c500 fffff802`3b0b836a covefs+0x196bc
0a ffffd000`22c0c5d0 fffff801`34c506a5 nt!IopfCompleteRequest+0x2ea
0b ffffd000`22c0c710 fffff801`34d09559 Ntfs!NtfsExtendedCompleteRequestInternal+0x135
0c ffffd000`22c0c750 fffff801`34d24652 Ntfs!NtfsQueryDirectory+0x2180
0d ffffd000`22c0cb00 fffff801`34c3ed7d Ntfs!NtfsCommonDirectoryControl+0xa2
0e ffffd000`22c0cb40 fffff802`3b0c23ac Ntfs!NtfsFspDispatch+0x1c5
0f ffffd000`22c0cc90 fffff802`3b0ef280 nt!ExpWorkerThread+0x28c
10 ffffd000`22c0cd40 fffff802`3b16dfc6 nt!PspSystemThreadStartup+0x58
11 ffffd000`22c0cda0 00000000`00000000 nt!KiStartSystemThread+0x16
Fascinating stuff, I'm sure, but next to useless to me I've found instructions elsewhere on these forums, and therefore the dump (in 7Zip format) is uploading as I type this.
Question
Steve Pitts
Folks,
Running DrivePool v2.1.1.561 on a Thecus W5000 with a fully patched Windows Storage Server 2012 R2 Essentials and received my first BSOD (the new, less useful, pastel blue screen). Checking the dump using WINDBG I see the finger pointed at covefs.sys and therefore my first post here is for a potential bug, which is a shame but the nature of support forums.
The results of my limited interactions with the debugger are:
Fascinating stuff, I'm sure, but next to useless to me I've found instructions elsewhere on these forums, and therefore the dump (in 7Zip format) is uploading as I type this.
Link to comment
Share on other sites
24 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.