Browse by Tags

Status: in Progress... Update 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 the New Year! This involves a problem I've recently...

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 running... fingers crossed! Update 120323...

Status: Unresolved, workaround provided. Update 121122: Closing the loop on this one... we have also seen a slight variation on this with "RDPDD!CAutoDrvCheck::CAutoDrvCheck+0x5e" instead of offset 0x5d as shown below. A hotfix request for this was rejected, and also on Windows Server 2012 this problem...

Status: Resolved Hello All, For quite some time now we have been working on the STOP X64_0x50_win32k!vFreeKernelSectionForUserMapping+22. It's now resolved and the hotfix for it will be released in December, under KB2781406. The stack: 00 fffff880`11b9aa28 fffff960`002382d2 nt!KeBugCheckEx...

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 the private confirmed there are no further STOP...

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 /b:sp2qfe. Update 110928: There is no news on...

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 workaround, you can set the encryption level for...