Windows problem reporting and solutions

Steps to check problem reports in Windows Step 1: Type problem in the search box on desktop, and click View all problem reports on the list. Step 2: See the problem reports in …. Enter services. Find Windows Error Reporting Service and then right-click or tap-and-hold on that entry from the list.

Choose the Properties option from the context menu. Next to Startup type, select Disabled from the drop down menu. Can't select it? This happens because the process is using up an unusually high amount of CPU, slowing your computer down.

The process is also referred to as Werfault. The event name is WinSetupDiag Developers can …. Bug in windows searchbar popup menu 1; hibernate 1; Outlook 1; fingerprint 1; GPU 1; Windows Update 1; power 1; Location 1; virtual desktop 1; home screens 1; dock 1; Windows.

Make your title clear, concise, and as descriptive as possible. Toggle navigation Cordylink. Access : Microsoft employees and contingent staff may access the error reports to maintain Windows Error Reporting or to improve Microsoft products. They may not use the reports for other purposes.

If the error report indicates that one or more non-Microsoft products were involved in causing the issue, Microsoft may send the report to the respective companies if the companies agree to abide by the terms of the privacy statement. Software or hardware developers employed by Microsoft or one of its partners may analyze the fault data and try to identify and correct the problem.

Details that are related to privacy of data are presented in Types of data collected later in this section. Ability to disable : The feature can be disabled through Group Policy or on an individual computer. You can also control the feature as described in Overview: Using Windows Error Reporting and the Problem Reports and Solutions feature in a managed environment earlier in this section, and Controlling Windows Error Reporting to prevent the flow of information to and from the Internet later in this section.

This section provides an overview of the data that Windows Error Reporting collects and information about data that might be collected from four sources:. Windows Error Reporting collects information about the computer configuration, what the software was doing when the problem occurred, and other information directly related to the issue.

It is possible that such information may be captured in memory or in the data that is collected from open files, but Microsoft does not use it to identify users. Windows Error Reporting collects Internet Protocol IP addresses, but the addresses are not used to identify users, and in many cases, they are the address of a network address translation NAT computer or proxy server, not a specific client behind that NAT computer or proxy server.

IP address information is used in aggregate by the operators who maintain the servers that receive error reports. In rare cases, such as issues that are especially difficult to solve, Microsoft may request additional data, including sections of memory which may include memory that is shared by any or all applications that were running at the time the issue occurred , some registry settings, and one or more files from your computer.

When additional data is requested, users can review the data and choose whether to send the information. Any application can be written in a way that uses the Error Reporting functionality. If an application error occurs for which Error Reporting is available, and you choose to send the report, the following information is included:. Information regarding the condition of the computer and the application at the time the error occurred.

This may include data that is stored in memory and stacks, information about files in the application's directory, the operating system version, and the computer hardware in use. You can use a registry setting to configure Windows Error Reporting so that it collects full user-mode dumps and stores them locally after a user-mode application stops responding.

This configuration option in Windows Error Reporting does not involve communication across the Internet. If users encounter a handwriting recognition error while using the Tablet PC Input Panel, they can start the error reporting tool and then select recently corrected handwriting samples to send in an error report. The samples are handled according to the consent-level setting, and in most cases, they are sent only with explicit consent.

No personal information is intentionally collected; however, the samples that are chosen may include personal information. This information will not be used to personally identify the person.

You can disable the reporting of handwriting recognition errors by using a specific Group Policy setting, as described in Setting for disabling Windows Error Reporting later in this section. The reports are like error reports, but they record a word or word pair to improve the selection of the ideograms that are displayed.

Word registration reports can include the information that is provided in the Add Word dialog box about the words being reported, and the software version number for IME.

Each time such a report is generated, the user is asked whether to send the report to Microsoft and can view the information that is contained in the report before sending it. Microsoft uses the information to help improve IME. Personal information might unintentionally be collected, but Microsoft does not use the information to identify or contact the person. If you configure Windows Error Reporting as described in Procedures to configure Windows Error Reporting later in this section, you can control word registration reports in the same way that you control error reports.

When a kernel-mode system error occurs a Stop message is displayed and diagnostic information is written to a memory dump file. When someone restarts the computer by using normal mode or Microsoft Windows Safe Mode with networking , and then signs in as an administrator, Windows Error Reporting responds. As with other errors, Windows Error Reporting uses the consent-level setting to determine when to prompt you before sending a kernel fault report.

Windows kernel fault reports contain information about what the operating system was doing when the problem occurred. These event reports contain the minimum information that can help identify why the operating system stopped unexpectedly.

If you choose to send the report, it includes the following:. Operating system language as represented by the locale identifier LCID — for example, the standard international numeric abbreviation, , for United States English. Loaded and recently unloaded drivers. These identify the modules that were in use by the kernel when the Stop error occurred and the modules that were used recently.

Processor context for the process that stopped. This includes the processor, hardware state, performance counters, multiprocessor packet information, deferred procedure call information, and interrupts that is, requests from software or devices for processor attention.

Process information and kernel context for the halted process. This includes the offset location of the directory table and the database that maintains the information about every physical page block of memory in the operating system. Process information and kernel context for the thread that stopped. This information identifies registers data-storage blocks of memory in the processor and interrupt-request levels, and it includes pointers to data structures for operating system data.

Kernel-mode call stack for the interrupted thread. This is a data structure that consists of a series of memory locations and one or more pointers. To control the flow of information to and from the Internet when users or administrators report errors, you can configure Windows Error Reporting by using an answer file with an unattended installation or by using Group Policy.

The following subsections provide more details. You can control the consent level for Windows Error Reporting by using an answer file with an unattended installation. To configure a consent level of Always ask before sending data , confirm that your answer file includes the following line:.

For more information, see To control the consent level for Windows Error Reporting by using an answer file with an unattended installation later in this section. This section provides information about a small set of the Group Policy settings that are available for Windows Error Reporting.

For information about viewing these and other Group Policy settings, see To locate Group Policy settings for configuring Windows Error Reporting later in this section. Two settings in the Advanced Error Reporting Settings refer to the "Report Queue" and the "Report Archive" These refer to information that is stored on the local computer.

The Report Queue temporarily stores error reports that are waiting to be sent. The Report Archive stores reports so that the Problem Reports and Solutions interface can display them. You can control the degree to which Windows Error Reporting prompts you for consent before data is sent. Configure Default consent: If you enable this setting, you can select one of the following consent levels:. Always ask before sending data : Windows Error Reporting always prompts for consent before sending an error report.

Send parameters : Windows Error Reporting automatically sends the minimum data required to check for an existing solution, as well as data which Windows has determined within a high probability does not contain personally identifiable data and prompts the user for consent to send any additional data requested by Microsoft.

Send parameters and safe additional data : Windows Error Reporting sends the minimum data required to check for an existing solution in addition to data that the developer of the program has designated as being highly unlikely to contain personal information. Windows Error Reporting then prompts for consent before sending any additional data that is requested by Microsoft. Send all data : Any data requested by Microsoft is sent without prompts. You can use a Group Policy setting to specifically disable reports for handwriting recognition errors.

Right-click the selected servers, and then click Configure Windows Automatic Feedback. Under Choose when to check for solutions to problem reports , view or change the basic error reporting settings as described earlier in this document.

Click Change report settings for all users. These settings can be used to configure error reporting for all users of the computer or to allow each user to choose their settings the default. Click Select programs to exclude from reporting : This setting allows you to manage the list of programs for which Windows Error Reporting is enabled.