The System specs are as follows. When a high volume of users are using our application. I have used windbg to review the memory dumps and have the results below.
The faulting module seems to be win32k. From the stack in the debug it seems that it is failing on a ThreadUnlock after drawing a menu bar and window frame. I found this article online but not sure if it related. I am trying to find out what the users were doing when the system crashed which might help point to the cause.
Searching Google about win32k. I am not sure how to resolve this issue. Does anybody have any ideas I could try? Please understand that to troubleshoot the blue screen issues, we usually need to perform debugging.
However, in this forum, we do not provide debugging support. To obtain the phone numbers for specific technology request, please refer to the website listed below:. Tim Quan. TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb microsoft. This problem was caused by a driver which hooks win32k. It is only an issue at 1 of our clients.
No other customers have had this issue and during our testing we could not reproduce the issue. I have a feeling that this is causing the issue as when we disable the tabdock the server does not BSOD.
The hard part is trying to figure out what line of code its failing on in the TabDock or our application as we cannot reproduce the issue on our servers. We are planning of getting a copy of our customers VM Server running the application to see if we can reproduce the issue at our offices and then can try to debug the issue.
I am still not sure how I can get a full stack trace of the issue when it crashes to show what line the code failed on in TabDock or My Application. I am not sure how to use this but until we get a copy of the VM I have not really looked into it.
Subscription auto-renews at the end of the term Learn more. Repair and Download Win32k. Average User Rating. All rights reserved. View Other win32k. Some of these errors include: win32k. The file win32k. Windows failed to start - win32k. How to Fix win32k. Step 1: Restore your PC back to the latest restore point, "snapshot", or backup image before error occurred.
In the search results, find and click System Restore. Follow the steps in the System Restore Wizard to choose a relevant restore point. Restore your computer to that backup image. If the Step 1 fails to resolve the win32k. Step 2: If recently installed Microsoft Office Access or related software , uninstall then try reinstalling Microsoft Office Access software. In the search results, find and click " Add or Remove Programs " Find the entry for Microsoft Office Access 14 and click " Uninstall " Follow the prompts for uninstallation.
So, you will be able to fix the win32kbase. Your email address will not be published. Ad blockers may interfere with some important blog features, such as comments, images, etc. Please consider disabling your ad blocker so you can have the best experience on this website.
Eunice Samson 18 October - 3 min read. Link copied. Do you like this post? You may also like 5. What if Copy and Paste are not working in Windows 10? Leave a Reply Cancel reply Your email address will not be published.
Auslogics Blog. Report abuse. Details required :. Cancel Submit. I don't know Chrome, but IE has troubleshooting modes such as disabling addons. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site.
0コメント