Is your Chromebook appearing up? Jack Wallen introduces you to the ChromeOS Diagnostic device, with which you’ll run {hardware} checks in your Chromebook.


Picture: Jack Wallen

Typically talking, Chromebooks run easily for years. Since I’ve began utilizing these units, it has been a really uncommon event that I’ve encountered a problem. Positive, I’ve had a couple of units that could not appear to maintain a strong Bluetooth connection (the Pixelbook was one of many worst for this), however for essentially the most half, it has been easy crusing.

SEE: Change management coverage (eBioPic Premium)

That does not imply you will have the identical expertise. And when one thing goes flawed, the place do you flip? In latest builds of ChromeOS, Google has launched a brand new device that makes it extremely simple for customers to run fast checks on their units. 

The app is known as Diagnostics, and the checks included are:

So should you discover your machine battery is not lasting so long as it ought to, or should you really feel the efficiency is struggling for some unknown cause, you may launch certainly one of these checks to see if there is a {hardware} concern on the coronary heart of the issue.

Let me present you how you can use this device.

SEE: Digital communication coverage  (eBioPic Premium)

What you will want

The Diagnostics app was launched in ChromeOS 89, so you will want a Chromebook working no less than that model of the OS. That is all you want. Let’s have a look at how this device is used.

open the Diagnostics app on a Chromebook

Click on in your Chromebook menu button (backside left nook of the desktop) and sort diagnostics within the search bar. Whenever you see the Diagnostics icon (Determine A), both hit Enter in your keyboard or click on on it with the trackpad.

Determine A


The Diagnostics launcher within the ChromeOS menu.

use the Diagnostics app on a Chromebook

With the Diagnostics app open (Determine B), you will discover Run buttons for the battery discharge, CPU check and Reminiscence check. Click on a kind of buttons to launch the check. 

Determine B


The ChromeOS Diagnostics is able to check your {hardware}.

After clicking one of many buttons, the check will begin within the background. When the check completes, the outcomes will seem on the backside left of the check card (Determine C).

Determine C


The Battery Discharge check was a hit with .09% discharged in 30 seconds.

Every check will even embrace a Be taught Extra hyperlink that can open to a Chromebook Assist window. Sadly, that assist web page is not a lot assist. Your greatest guess is to take the outcomes of the check and do your individual analysis. Even then, you will in all probability need to flip to the producer of your Chromebook to seek out out what’s the regular discharge fee for the battery. But when the outcomes return a “success,” you have to be OK.

SEE: Why the PS5 is the must-have gaming console of the yr and the whole lot you want to find out about it (free PDF) (eBioPic)

The CPU diagnostic will run the next checks (which takes round 4 to 5 minutes):

  • Stress check
  • Cache check
  • Floating-point accuracy check
  • Prime search check

It ought to be vital to know that, whereas working the CPU check, you should not use your Chromebook. In truth, you will discover the machine onerous to make use of whereas working this explicit check. 

The Reminiscence check takes the longest of the three. You must count on round 30 minutes for completion (relying on how a lot reminiscence your machine has). Though you should utilize the Chromebook throughout this check, I’d suggest you run it when utilizing the machine is not vital.

On the finish of your check, you may click on the Save session log (Determine D) to retain a replica of the testing outcomes.

Determine D


The Reminiscence check is working, so the session log should not be saved but.

And that is all there may be to working diagnostic checks in your Chromebook. If you happen to discover the machine working poorly, and a reboot would not resolve the issue, run these three checks to see if a {hardware} concern is not the trigger.

Additionally see

Leave a Reply