[INFO] Setting up Debugging

Hi All, just wanted to share this link with you: http://msdn.microsoft.com/en-us/library/windows/hardware/hh450944(v=vs.85).aspx. It contains a wealth of information about how to setup various debug connections, for example from Visual Studio, or WinDbg, or ntsd, etc. Enjoy!


[INFO] Troubleshooting Pool Corruption

Hello All, time for another post, this time on Pool Corruption. Many of the STOP errors we in Support see are pool-related. For example, the one I saw some days ago: X64_0x3B_nt!ExDeferredFreePool+249 Other common pool-related STOP errors include 0x1E, 0x50, 0xA, and 0x8E. Quite often, the stack in such cases reveals an offending (third party)…


Some basic debugging steps… KB315263

Just came across this pretty old KB, that still applies though: 315263 How to read the small memory dump file that is created by Windows if a crash occurshttp://support.microsoft.com/kb/315263/EN-US   \Rob 


[RESOLVED] Win2012: STOP 0xD1 in MsLbfoProvider!lbfoSetMacAddrVmsPortMapping+b4

Status: Resolved   After installing the v1 version of the now infamous KB 2855336, your machine can crash with a STOP 0xD1 after performing a Live Migration (and when you’re using LBFO). This is documented in: 2866029 “0x000000D1” Stop error when you perform a live migration of a virtual machine on a Windows Server 2012-based clusterhttp://support.microsoft.com/kb/2866029/EN-US ..and…


Win2008R2: STOP 0x27 in mrxsmb10!SmbCeFindOrConstructSessionEntry+931

Status: in Progress…   130716: I’m writing this post to see if there are any people out there also experiencing the issue one of our customers is experiencing. We have seen this before in the past, and it is fixed on Win2012, but not (yet) on Win2008R2…Mail me when you have this STOP! FAILURE_BUCKET_ID:  X64_0x27_mrxsmb10!SmbCeFindOrConstructSessionEntry+931…



Hello dear Readers, I’ve just updated my profile with my LinkedIn URL. Feel free to Link! 🙂 


Windows does not create a memory dump file when a Stop error occurs in Windows 8 or Windows Server 2012 (KB 2853466)

All, make sure you implement this hotfix on Win2012 machines with MPIO: 2853466 – Windows does not create a memory dump file when a Stop error occurs in Windows 8 or Windows Server 2012http://support.microsoft.com/kb/2853466/EN-US This issue occurs because Windows Crash Dump Driver does not use the correct MPIO path to create the dump log.  …


[RESOLVED] Win2012: STOP 0xD1 in msdsm!DsmpQueryLoadBalancePolicy+2a1

Status: Resolved Note: the hotfix now also includes an update for Windows Server 2008 R2. 130624: over the past few months I’ve seen this bugcheck occur with quite a few customers so I figured perhaps it would help some of you out there as well… I’ve also added this as a response under Online Crash Analysis….


[RESOLVED] Win2012: STOP 0x9F_4_IMAGE_CsvFs.sys

Status: Resolved. 130624: Turns out this issue was caused by a storage problem. 130211: This issue is triggered when a machine is handling a surprise removal for a Csv volume. Nothing conclusive yet, but I wanted to see if there is anyone out there with the same issue. The 0x9F code indicates that a driver has failed…


[RESOLVED] Win2012: STOP 0xAB with tag Gla4

Status: Resolved 130624: Finally, some time to update this blog post! Sorry for the delay… this particular issue is resolved in the May Rollup: http://support.microsoft.com/kb/2836988. 130211: we have asked the customer to implement the GDICaptureStackTraceForObjectType registry value to obtain additional information in subsequent dumps… fingers crossed!   Hi All,   Finally, my first post of…