In Windows Server 2016 Cluster also makes sure to exclude from the livedump CSV Cache. The kind of livedump that cluster collects for you also would not have pages consumed by Hypervisor. It will not include pages from stand by list and file caches. LiveDump does not include all kernel memory, it excludes information which is not valuable in debugging. Taking this snapshot will NOT cause bugcheck so no downtime. For the purpose of this discussion you can think of LiveDump as an OS feature that allows you to create a consistent snapshot of kernel memory and save it to a dump file for the future analysis. Live Dump was a new feature added in Windows Server 2012 R2. The good news is that LiveDump solves both of these issues. On a system with a lot of memory, you might not have enough space on your system drive for OS to save the dump You might have at least two challenges with kernel dump.īugcheck halts the system resulting in downtimeĮntire contents of memory are dumped to a file. Some of you are probably familiar with kernel crash dumps In this post we will discuss how to troubleshoot it using LiveDumps, which enables debugging the system with no downtime for your system.įirst let’s discuss what is the LiveDump. In particular, we discussed the reason for auto-pause due to STATUS_IO_TIMEOUT (c00000b5), and some options on how to troubleshoot it. We discussed what a Cluster Shared Volumes (CSV) event ID 5120 means, and how to troubleshoot it.
