Windows Troubleshooting – Special Pool

The Windows Support team has a new YouTube channel, “Windows Troubleshooting”.  The first set of videos cover debugging blue screens. In this video, Bob Golding, Senior Escalation Engineer, describes how the Special Pool Windows diagnostics tool catches drivers that corrupt memory. Bob also introduces how memory is organized in the system for allocating memory for…

1

Hate to see you go, but it’s time to move on to greener pastures. A farewell to Authorization Manger aka AzMan

Hi all, Jason here. Long time reader, first time blogger. AzMan is Microsoft’s tool to manage authorization to applications based on a user’s role. AzMan has been around since 2003 and has had a good run. Now it’s time to send it out to pasture. If you haven’t seen thisarticle, AzMan has been added to…

1

Go the modern (app) way

Hello everyone, This is Ashfana from the Windows Performance team. I’m here to talk about the basic philosophy behind Windows Store Apps which were introduced in Windows 8 and Windows 8.1. Windows Store apps were originally called Metro or modern apps before the RTM of the product. These are apps developed using a variety of…

1

Deciphering Storport Traces 101

Welcome back to the CORE Team Blog — Paul Reynolds here. In previous blogs, I wrote about how to capture Storport traces in Windows 8 and Windows 2012. Please see: Tracing with Storport in Windows 2012 and Windows 8 with KB2819476 hotfix And Tracing with Storport in Windows 2012 and Windows 8 without KB2819476 hotfix…

1

WMI: How to Troubleshoot WMI High Handle Count

Scenario Windows Management Instrumentation Service (Winmgmt) or WMI provider (wmiprvse.exe) is experiencing high handle count Your first thing to do is check the Application Event log for following event: Source: Microsoft-Windows-WMI Event 5612 Wmiprvse.exe exceeding handle quota limit Event WMI has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum…

1

WMI: How to troubleshoot High CPU Usage by WMI Components

Scenario Windows Management Instrumentation Service (Winmgmt) or WMI provider (wmiprvse.exe) is consuming high amounts of CPU. In the directions below, you may have already broken out WMI Service to troubleshoot your issue.  By default, WMI runs in the main shared networking svchost process with several other services. If it is a svchost process showing high…

1

WMI: High Memory Usage by WMI Service or Wmiprvse.exe

Scenario Windows Management Instrumentation Service (Winmgmt) or WMI provider (wmiprvse.exe) is consuming high amounts of memory. There are many reasons why WMI might experience high memory consumptions. This can occur in the WMI (Windows Management Instrumentation) service (winmgmt) or in the WMI provider hosting vehicle wmiprvse.exe. Both scenarios will be addressed below. High memory usage…

1

WMI: Missing or Failing WMI Providers or Invalid WMI Class

Scenario Windows Management Instrumentation fails due to receiving an event or error concerning missing or failure to load WMI Provider, or Invalid WMI class, or WMI Invalid Namespace. Below are some common errors indicating issues with a WMI Provider or Class: Failed to initialize all required WMI classes Win32_processor: WMI: Invalid namespace Win32_WMISetting: WMI: Invalid…

1

WMI: Repository Corruption, or Not?

Scenario Windows Management Instrumentation failing due to repository being corrupted The WMI Repository (%windir%System32\Wbem\Repository) is the database that stores meta-information and definitions for WMI classes; in some cases the repository also stores static class data as well. If Repository becomes corrupted, then the WMI service will not be able to function correctly. Before grabbing that…

1