How to perform hardware health checks in Windows

Case



You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows.



Solution



Carry out the steps below.



- Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine.

- Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console.



- Check the health of all your disks, either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-check-disk-health-in-windows/.

- Check the health of your CPU with the Intel Processor Diagnostic tool or the AMD System Monitor tool.



- Check the health of your RAM memory by running the Windows mdsched.exe command line tool. An alternative free memory test command line tool for Windows is Memtest86. This tool boots from a USB flash drive to test the RAM in your computer for faults.



After the Windows Memory Diagnostic tool has rebooted the system and completed its checks, look in the Windows System Event log for relevant logged events (with Source "MemoryDiagnostics-Results"), to determine if the tool has found any RAM memory errors or not.





- Run the free PC Doctor Toolbox tool to scan your Windows computer for any operating system or application issues. The PC Doctor Toolbox tool can be downloaded at: https://www.pc-doctor.com/solutions/toolbox. Another free health check tool which performs an overall health check of your Windows computer is ESET SysInspector and can downloaded at: https://www.eset.com/int/support/sysinspector/. This, among other checks, carries out a health check of the Windows registry.



- Use Windows Performance Monitor and Windows Reliability Monitor to detect any performance or operating system stability issues.

- Make use of free tools such as HWInfo and OpenHardwareMonitor to retrieve a detailed view of your computer's hardware components.

- Run a full antivirus/antimalware check by using the Microsoft free Malicious Software Removal tool which is available at https://www.microsoft.com/en-us/download/details.aspx?id=9905. You can supplement this with the free MalwareBytes engine.

- Ensure that you have applied the latest Windows Updates and application updates via a tool such as PatchMyPC.




https://stefanos.cloud/kb/how-to-perform-hardware-health-checks-in-windows/

Comments

Post a Comment

Popular posts from this blog

FsLogix 2201 Public Preview release

Image
The FsLogix 2201 Public Preview release is now available for download from Microsoft. The change log is as follows: - Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. - The OfficeFileCache folder located at %LOCALAPPDATA%MicrosoftOffice16.0OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. - Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. - Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. - FSLogix now correctly handles cases where
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom
Read more