Status: Resolved Note: a workaround to provide relief to your users is to disconnect sessions instead of logging them off. Update 111012: GOOD NEWS! The hotfix for this issue has been rolled up in the QFE version of MS11-077 . Install this using...

Status: Unresolved, customer discontinued. Opening the dump shows: BugCheck 9E, {fffffa807d98bb30, 4b0, 0, 0} Probably caused by : netft.sys ( netft!NetftWatchdogTimerDpc+b9 ) Note that the 0x9E indicates a timeout, triggered by the netft driver...

Status: Resolved Update 120531: Yes! The Private is approved. We are releasing the hotfix in the July Release Cycle, under KB2719704. Update 120510: We are now testing a private at several customers... fingers crossed this fixes this long-runner...

Status: Resolved Update 120111: The update is now available from Download Center: http://www.microsoft.com/download/en/details.aspx?id=28651. Update 111102: The private has been approved, and we are working on the public hotfix now. Issue resolved...

Status: Resolved Final Update 110823: The hotfix will be released in the October timeframe (HTP11-10). Update 110815: We will now proceed with building a private hotfix package. As soon as that gets approved, we will release a public hotfix under...

Status: Resolved Update 110815: The KB for this STOP error has gone live. You can find it here . Update 110522: I am still trying to replicate the circumstances that triggered this problem to happen so often at one customer, but not for millions...

Status: Resolved. Update 110606: We have determined that the STOP 0x19 has the same root cause as the STOP 0x7E described in KB2460912. This leaves us with the STOP 0x7E of Update 110527, for which I will create a new post. Update 110527: Another...

Status: Unresolved, workaround provided. Update 121122: Closing the loop... this was never actually resolved, and our customer agreed to use the workaround of disabling scardhook.dll. Update 110818: Citrix found that it's likely that a cryptographic...

Status: Unresolved Update 111128: The customer decided to stop troubleshooting efforts on this issue, and first bring their environment up-to-date with various updates of various vendors. If the issue then reoccurs, we will continue where we left off...

Status: Resolved. Update 110617: The KB is now public at http://support.microsoft.com/kb/2526870 . Update 110518: For both Windows Vista and Windows 7, the KB will be 2526870. This is scheduled to be released as part of HTP11-06, and will also be...

Just a quick post on an issue brought to my attention by Nuno, one of my Portugese collegues. Thanks! :) The issue: whenever the laptop was docked, CPU usage % would go up to a 100%, without being able to attribute this to a particular process. I always...

Status: Resolved Update 111206: After discussing this with our customer they agreed to accept the workaround of increasing memory for the impacted machines. Update 110823: Finally I found the trigger for this STOP error: memory pressure. Further...

Status: Resolved Update 120112: Closing the loop on this one. Finally, after some delays, the hotfix is released and available from http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2619041&kbln=en-us. Update 110930: The customer running...

Status: Resolved Just an informational post regarding: Update 110803: Thanks to one of the readers of the blog I found out I should have updated this post some time ago, since the fix that addresses this on Win2008R2 SP1 is now public on http:/...

Status: Resolved Update 110930: The KB article for this will be 2592339. Issue resolved, case closed. ;) Update 110811: Customer confirmed the workaround is working! :) Now we wait for the hotfix... scheduled for HTP11-10. Update 110808: As a...

Status: Resolved. Update 110610: We identified SLDOTNETSSO.EXE as the cause for the crashes in various applications. Additional information is here . Update 110522: Further dump analysis identified a third party component that is likely to be responsible...

Status: Resolved Update 120314: Closing the loop on this: the hotfix is now publicly available. It may take some time for the corresponding KB to be available as well. Update 120207: We have a private ready for testing. We're shipping this off to...

Status: Resolved. Update 120301: Private is approved, Public is scheduled for REL12-04, to be released mid-April. Update 120217: The private is ready! Update 120215: other customer came in hitting this, private is in the works. This should be...

Status: Resolved Update 111019: Finally an update on this... KB2584874 will be released in November timeframe (HTP11-11) for this. We've come across a couple of customers who have machines hitting a STOP 0x27 with the following stack: 5: kd>...

Status: Resolved. Update 110713: The customer confirmed that the issue went away after they updated the (very outdated) HBA driver for their Fibre Channel adapter. This again stresses the importance of keeping up-to-date with revisions of various drivers...

Status: Resolved Update 120130: Closing the loop on this: the KB (2624677) for this is now available through Microsoft Support, the public release is scheduled for this February. Update 111116: Sonny found the issue using instrumentation/private...

Status: Resolved Update 121122: Finally! After many rounds of instrumentation we nailed this nasty bug as well! :D It's now resolved in KB2786447, to be released in January 2013 (REL13-01). Update 120417: We currently have a new round of instrumentation...

Status: Resolved. Update 110809: As part of the HTP11-10 releases, we are releasing KB2585233, which addresses a problem that results in STOP 0xAB errors. Do note that not all of these errors have the same cause. In general, have a look at outdated...

Status: Resolved, external. Update 121122: Shame on me for not updating this yet... Citrix eventually resolved this issue, please contact them when you encounter the issue below. At the moment we are working together with Citrix on an issue where...

Status: Resolved. Update 110608: The problem is caused by the fact that the volume is larger than 64TB, which is not supported in the current design of volsnap. This is documented in KB950241 . As mentioned in a previous post, I've received a STOP...