Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000448FlexRAID Transparent RAID[All Projects] Generalpublic2017-02-03 16:272017-02-10 15:16
Reporteradridolf 
Assigned To 
PrioritynormalSeveritycrashReproducibilityrandom
StatusnewResolutionopen 
PlatformWindowsOSServer 2012 R2OS Version
Summary0000448: Occational machine reboots with error 1001: Computer has rebooted from a bugcheck
DescriptionEvery two or three days my server "crashes" and automatically reboots. In the event log, I get the typical reboot events (e.g. 41: Kernel-Power) and Id 1001:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000005100, 0xfffff6e8001faa00, 0x0000000000000001, 0x000000056ae39963). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 020317-8421-01.

From my first primitive attempts with WinDbg I get:
[...] Probably caused by : cbfs5.sys ( cbfs5+2c3b ) [...]

Directly preceding the crash I got four warnings with ID 153: The IO operation at logical block address 0x2 for Disk 13 (PDO name: \Device\00000060) was retried. The number refers to the pool disk of my tRaid array. Note that I get between 1 and 4 of the latter warnings per day which do not always result in a crash. I also found crashes not accompanied by a 153 warning and quite frequently ones followed by a 153 warning after restart.
Also note that in contrast to a forum thread (http://forum.flexraid.com/index.php/topic,3992.msg26032.html#msg26032 [^]) the logical block for this warning is always the same "0x2".

I did not find any other warnings or errors in the event log in the time window of interest supposing a specific source of the problem.
Additional InformationI still use the service version provided for addressing the bugs I reported earlier this year. In this context it is at least interesting that the first occurrence of the problem was on January 12th, corresponding to the "builds":
NZFSB_URB_Compatibility_And_SetEndOfFile_Fix_2017-01-09.zip
and
NZFSB_Standard_URB_Extra_Logs_2017-01-12.zip
This may also be coincidence...


Information I got out of the MEMORY.DMP with WinDbg:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Built by: 9600.18505.amd64fre.winblue_ltsb.160930-0600
Machine Name:
Kernel base = 0xfffff802`14c1c000 PsLoadedModuleList = 0xfffff802`14eef630
Debug session time: Fri Feb 3 15:00:39.760 2017 (UTC + 1:00)
System Uptime: 0 days 5:22:36.125
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
....................................................Page 1a9eeb not present in the dump file. Type ".hh dbgerr004" for details
............
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff6`ff53e018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......

************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5100, fffff6e8001faa00, 1, 56ae39963}

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for fltmgr.sys -
*** ERROR: Module load completed but symbols could not be loaded for cbfs5.sys
*** ERROR: Module load completed but symbols could not be loaded for vhdmp.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 1a9d5c not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : cbfs5.sys ( cbfs5+2c3b )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6e8001faa00
Arg3: 0000000000000001
Arg4: 000000056ae39963

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 1a9d5c not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: cbfs5

FAULTING_MODULE: fffff80214c1c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5610fcb5

BUGCHECK_STR: 0x1a_5100

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff80214d90207 to fffff80214d6a3a0

STACK_TEXT:
ffffd000`3e155878 fffff802`14d90207 : 00000000`0000001a 00000000`00005100 fffff6e8`001faa00 00000000`00000001 : nt!KeBugCheckEx
ffffd000`3e155880 fffff802`14c75319 : ffffd000`00000000 00000000`00000001 00000000`00000001 ffffd000`3e155ad0 : nt!CcTestControl+0x18bb7
ffffd000`3e155a50 fffff802`14c74c5f : ffffe001`00000000 00000000`03c05000 ffffd000`3e155e28 ffffd000`3e155dfc : nt!ObReferenceObjectSafeWithTag+0x628d
ffffd000`3e155dc0 fffff802`14cfb114 : ffffe001`097bb530 ffffd000`3f516000 ffffd000`3e155f18 00000000`00000000 : nt!ObReferenceObjectSafeWithTag+0x5bd3
ffffd000`3e155eb0 fffff800`37cb366e : 00000000`00010000 ffffd000`3e1561c0 ffffc001`43153140 ffffc001`43153140 : nt!CcCopyWriteEx+0x260
ffffd000`3e155f50 fffff800`37cb6b63 : ffffe001`07421018 ffffe001`097ef300 00000000`00000000 ffffe001`07421018 : Ntfs+0x1666e
ffffd000`3e156190 fffff800`37a7bb1e : ffffe001`05d14e00 ffffe001`0ccf9bd0 00000000`00000000 ffffe001`0ccf9f70 : Ntfs+0x19b63
ffffd000`3e156250 fffff800`37a7a0c2 : ffffd000`3e156310 ffffe001`02257df0 ffffe001`01a5eaf0 ffffe001`0ccf9bd0 : fltmgr!FltIsCallbackDataDirty+0x2ee
ffffd000`3e1562f0 fffff800`38978c3b : ffffe001`09897a10 00000000`00000001 00000000`00010000 ffffe001`07421018 : fltmgr+0x10c2
ffffd000`3e156350 fffff800`389770f1 : ffffe001`003bacc0 ffffe001`09897a10 ffffe001`01a5e9a0 ffffe001`0ccf9bd0 : cbfs5+0x2c3b
ffffd000`3e156380 fffff800`37a7a101 : ffffe001`09897a10 ffffe001`0ccf9bd0 ffffe001`0ccf9fd0 ffffc001`33e68520 : cbfs5+0x10f1
ffffd000`3e1563c0 fffff800`39c230fe : ffffe001`0ccf9bd0 fffff800`37c9eba5 ffffe001`07176de0 ffffd000`3e156680 : fltmgr+0x1101
ffffd000`3e156420 fffff800`39c25b3b : ffffe001`0ccf9b30 ffffe001`008020c0 ffffe001`00909180 ffffe001`07247920 : vhdmp+0x70fe
ffffd000`3e156470 fffff800`39c4142d : ffffe001`0ccf9b30 ffffe001`0ccf9b30 ffffe001`0ccf9bd0 ffffe001`0cd0d020 : vhdmp+0x9b3b
ffffd000`3e1564b0 fffff800`39c40fc1 : 00000000`00000103 ffffe001`0cd0d0b0 ffffe001`0cd0d0b0 ffffe001`05045300 : vhdmp+0x2542d
ffffd000`3e1564e0 fffff800`39c5546f : ffffe001`0cd0d0b0 00000000`00000000 ffffd000`3e156630 ffffe001`00000000 : vhdmp+0x24fc1
ffffd000`3e156550 fffff800`39c555b3 : ffffe001`0cd0d0b0 00000000`0c205000 00000000`00005000 00000000`00000000 : vhdmp+0x3946f
ffffd000`3e1565a0 fffff800`39c55a0d : ffffe001`0cd0d0b0 ffffd000`3e156670 ffffd000`3e156630 00000000`00000000 : vhdmp+0x395b3
ffffd000`3e1565e0 fffff800`39c54933 : ffffe001`0cd0d0b0 00000000`00000000 ffffe001`0089d3f0 00000000`00000000 : vhdmp+0x39a0d
ffffd000`3e156610 fffff800`39c419c8 : ffffe001`0cd0d0b0 00000000`00000001 ffffe001`00000001 00000000`00000001 : vhdmp+0x38933
ffffd000`3e156680 fffff800`39c41e53 : ffffe001`0cd0d020 fffff800`37a7bb1e ffffe001`0cc0b601 fffff802`14eba16c : vhdmp+0x259c8
ffffd000`3e1566f0 fffff800`39c20534 : ffffe001`0cd0d020 ffffe001`0cc0b630 ffffe001`0cc0b440 fffff802`14f035c0 : vhdmp+0x25e53
ffffd000`3e156750 fffff800`39c20333 : ffffe001`0089d790 00000000`00000001 00000000`00000000 ffffe001`0cc0b440 : vhdmp+0x4534
ffffd000`3e156790 fffff800`39c930cf : 00000000`00000000 ffffe001`09376400 ffffe001`027098c0 00000000`00000103 : vhdmp+0x4333
ffffd000`3e1567e0 fffff800`39c2e273 : ffffe001`0cc0b440 ffffe001`027098c0 ffffe001`09759fa8 ffffe001`09759ec0 : vhdmp+0x770cf
ffffd000`3e156840 fffff800`39c1eed2 : ffffe001`027098c0 ffffd000`3e156941 ffffe001`07247901 ffffe001`050453a8 : vhdmp+0x12273
ffffd000`3e156870 fffff802`150b7e03 : 00000000`00000001 ffffe001`07247920 ffffe001`027098c0 00000000`00000000 : vhdmp+0x2ed2
ffffd000`3e1568c0 fffff802`14ff9936 : 00000000`00000010 00000000`00000001 ffffe001`00000000 ffffe001`027098c0 : nt!FsRtlInitializeOplock+0x32f
ffffd000`3e156990 fffff802`14d75bb3 : 00000000`00000000 00000000`00000518 00000000`00000000 0000009b`09c3f310 : nt!NtWriteFile+0x682
ffffd000`3e156a90 00007ffd`3e78073a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x34a3
0000009b`09c3ec68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`3e78073a


STACK_COMMAND: kb

FOLLOWUP_IP:
cbfs5+2c3b
fffff800`38978c3b 488b5c2438 mov rbx,qword ptr [rsp+38h]

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: cbfs5+2c3b

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: cbfs5.sys

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner
---------

TagsNo tags attached.
tRAID Version 1.0
Attached Files

- Relationships

-  Notes
(0001726)
adridolf (reporter)
2017-02-03 16:49

Memory test with Windows Memory Diagnostic Tool showed no errors.
(0001729)
adridolf (reporter)
2017-02-10 14:57

Only happens when I have a 2-way mirror running in addition to my tRaid. If the mirror is off, no crashes occur.

The system is a hyper-V host with several virtual machines. Crashes are mostly happening when the machine backup (by Windows Server Backup) is written to the 2-way mirrored drive. However, only backups of the host machine seem to trigger the crash, while the more frequent backups of the guests run fine.
(0001730)
adridolf (reporter)
2017-02-10 15:02

Just tested again: I can reproducibly trigger a bugcheck crash by running the backup task. Note that in contrast to my earlier bug reports, the mirrored drive is NTFS.
(0001731)
adridolf (reporter)
2017-02-10 15:16
edited on: 2017-02-11 13:57

Deleted the configuration and only mounted the first drive => Backup runs fine without crash.


- Issue History
Date Modified Username Field Change
2017-02-03 16:27 adridolf New Issue
2017-02-03 16:49 adridolf Note Added: 0001726
2017-02-10 14:57 adridolf Note Added: 0001729
2017-02-10 15:02 adridolf Note Added: 0001730
2017-02-10 15:16 adridolf Note Added: 0001731
2017-02-11 13:57 adridolf Note Edited: 0001731 View Revisions


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker