How to Generate a Battery Report in Windows 10
Laptops and tablets use rechargeable lithium ion batteries. Although a lithium battery doesn’t have a “memory,” like older batteries, lithium batteries do have life spans. Their performance degrades over time and eventually, the battery won’t provide charge for as long as it used to. Most lithium ion laptop batteries provide 100% performance for the first year, or longer, especially if you follow some basic tips for improving the longevity of your battery. But if you suspect that your battery is underperforming, either due to a manufacturing defect or something screwy going on with your system, you can get a battery report from Windows 10.
This handy battery report gives you a rundown of your battery specs, along with servicing options available depending on the make, model, and age of your system. For example, if your battery or laptop is still under warranty and it’s not performing up to spec, then you might be able to get a free replacement.
Getting a battery report in Windows 10 is easy. Here’s how to do it:
How to Generate a Battery Report in Windows 10
You can easily generate a battery report by running the powercfg /batteryreport command. Press Windows key + X, click Command Prompt (Admin), type powercfg /batteryreport at the command prompt then hit the Enter key. The report will be saved under C:\Windows\System32 as battery-report.
The report provides details about your battery including the name, manufacturer, serial number, chemistry and cycle count. You can also view a usage report over a period of time.
Some laptop manufacturers will sometimes include their own battery diagnostics tool you can use to check the status of the battery.
A battery report is a useful tool for investigating poor battery performance. If your battery is defective, your battery report will help you prove it when processing a warranty claim. There are also other causes for poor battery performance that are worth investigating.
Recently, owners of Microsoft Surface Pro 3 devices started experiencing issues with battery life depleting rapidly. It turns out this issue was related to the type of battery installed in the device. Microsoft has since released a firmware update, resolving the problem. This proves that not all systems are alike, even though Surface Pro 3 devices were affected, not all models included the specific battery that was experiencing the issue.
For all machines, Windows 10 includes improvements for maintaining your battery. The battery saver setting, for example, helps you squeeze as much juice out of your tablet or laptop battery. You can also perform a manual recalibration by fully charging the device, then letting it deplete. Checking the manufacturer’s website for firmware updates for your system can sometimes help improve the efficiency of your battery. Also, it’s always a good idea to check for unnecessary processes running in the background that may be causing your computer to work harder than it needs to (and therefore deplete its battery faster).
Give the battery report a try. If you find out something interesting, let us know in the comments.
3 Comments
Leave a Reply
ramon
Hi , I just bought a new battery and its not charging. I ran a battery report and this is what it shows.
COMPUTER NAME RAMON
SYSTEM PRODUCT NAME HP HP ENVY Notebook
BIOS F.88 10/13/2017
OS BUILD 16299.15.amd64fre.rs3_release.170928-1534
PLATFORM ROLE Mobile
CONNECTED STANDBY Not supported
REPORT TIME 2018-01-17 14:36:32
Installed batteries
Information about each currently installed battery
BATTERY 1
NAME Primary
MANUFACTURER Hewlett-Packard
SERIAL NUMBER –
CHEMISTRY LION
DESIGN CAPACITY 38,362 mWh
FULL CHARGE CAPACITY 38,362 mWh
CYCLE COUNT –
Recent usage
Power states over the last 3 days
START TIME STATE SOURCE CAPACITY REMAINING
2018-01-16 21:17:58 Active AC 2 % 947 mWh
2018-01-17 00:37:50 Suspended 2 % 947 mWh
00:55:26 Active AC 2 % 947 mWh
03:35:00 Suspended 2 % 947 mWh
11:41:48 Active AC 2 % 947 mWh
14:36:32 Report generated AC 2 % 947 mWh
Battery usage
Battery drains over the last 3 days
START TIME STATE DURATION ENERGY DRAINED
– – – – –
Usage history
History of system usage on AC and battery
BATTERY DURATION AC DURATION
PERIOD ACTIVE CONNECTED STANDBY ACTIVE CONNECTED STANDBY
2018-01-16 – – 2:41:58 –
Battery capacity history
Charge capacity history of the system’s batteries
PERIOD FULL CHARGE CAPACITY DESIGN CAPACITY
2018-01-16 38,362 mWh 38,362 mWh
Battery life estimates
Battery life estimates based on observed drains
AT FULL CHARGE AT DESIGN CAPACITY
PERIOD ACTIVE CONNECTED STANDBY ACTIVE CONNECTED STANDBY
2018-01-16 – – – –
Current estimate of battery life based on all observed drains since OS install
Since OS install – – – –
Please help
Zakaria Amrani
Battery report
COMPUTER NAME VIVOBOOK
SYSTEM PRODUCT NAME ASUSTeK COMPUTER INC. N552VX
BIOS N552VX.207 02/04/2016
OS BUILD 18941.1001.amd64fre.rs_prerelease.190713-1700
PLATFORM ROLE Mobile
CONNECTED STANDBY Not supported
REPORT TIME 2019-07-22 01:16:25
Installed batteries
Information about each currently installed battery
BATTERY 1
NAME ASUS Battery
MANUFACTURER ASUSTeK
SERIAL NUMBER –
CHEMISTRY LIon
DESIGN CAPACITY 48,000 mWh
FULL CHARGE CAPACITY 30,405 mWh
CYCLE COUNT 86
Recent usage
Power states over the last 3 days
START TIME STATE SOURCE CAPACITY REMAINING
2019-07-19 02:09:00 Active AC 84 % 25,545 mWh
02:34:43 Suspended 84 % 25,545 mWh
13:48:05 Active AC 83 % 25,275 mWh
19:24:04 Active Battery 83 % 25,365 mWh
19:46:01 Active AC 83 % 25,365 mWh
21:55:51 Active Battery 83 % 25,365 mWh
21:56:00 Active AC 83 % 25,365 mWh
22:08:24 Suspended 83 % 25,365 mWh
22:54:46 Active AC 83 % 25,365 mWh
23:10:00 Suspended 83 % 25,365 mWh
23:12:00 Active AC 83 % 25,365 mWh
2019-07-20 05:15:00 Suspended 83 % 25,365 mWh
06:18:18 Active AC 83 % 25,365 mWh
06:23:51 Suspended 83 % 25,365 mWh
10:55:28 Active AC 83 % 25,365 mWh
11:40:00 Suspended 83 % 25,365 mWh
11:42:45 Active AC 83 % 25,365 mWh
13:55:00 Suspended 83 % 25,365 mWh
14:02:17 Active AC 83 % 25,365 mWh
14:02:17 Suspended 83 % 25,365 mWh
14:06:44 Active AC 83 % 25,365 mWh
14:41:00 Suspended 83 % 25,365 mWh
15:02:50 Active AC 83 % 25,365 mWh
15:08:00 Suspended 83 % 25,365 mWh
15:32:40 Active AC 83 % 25,365 mWh
2019-07-21 10:01:00 Suspended 83 % 25,365 mWh
11:08:23 Active AC 83 % 25,365 mWh
11:14:00 Suspended 83 % 25,365 mWh
11:19:15 Active AC 83 % 25,365 mWh
11:41:51 Suspended 83 % 25,365 mWh
13:34:04 Active AC 83 % 25,365 mWh
16:21:24 Active Battery 83 % 25,365 mWh
16:33:00 Suspended 83 % 25,365 mWh
17:18:57 Active AC 83 % 25,365 mWh
17:30:00 Suspended 83 % 25,365 mWh
17:35:47 Active AC 83 % 25,365 mWh
23:29:26 Active Battery 83 % 25,365 mWh
23:29:35 Active AC 83 % 25,365 mWh
23:32:02 Active Battery 83 % 25,365 mWh
23:32:04 Active AC 83 % 25,365 mWh
2019-07-22 00:18:39 Active Battery 83 % 25,365 mWh
00:20:19 Active AC 83 % 25,365 mWh
00:22:28 Active Battery 83 % 25,365 mWh
00:25:15 Active AC 83 % 25,365 mWh
00:33:07 Battery changed AC – –
00:33:07 Active AC – –
00:36:05 Battery changed AC 83 % 25,365 mWh
00:36:05 Active AC 83 % 25,365 mWh
01:01:53 Active Battery 83 % 25,365 mWh
01:01:56 Active AC 83 % 25,365 mWh
01:16:22 Report generated AC 83 % 25,365 mWh
Battery usage
Battery drains over the last 3 days
START TIME STATE DURATION ENERGY DRAINED
2019-07-19 19:24:04 Active 0:21:57 – –
21:55:51 Active 0:00:08 – –
16:21:24 Active 0:11:35 – –
23:29:26 Active 0:00:08 – –
23:32:02 Active 0:00:02 – –
2019-07-22 00:18:39 Active 0:01:39 – –
00:22:28 Active 0:02:46 – –
01:01:53 Active 0:00:03 – –
Usage history
History of system usage on AC and battery
BATTERY DURATION AC DURATION
PERIOD ACTIVE CONNECTED STANDBY ACTIVE CONNECTED STANDBY
2018-10-08 – 2018-10-15 6:24:35 – 46:20:31 –
2018-10-15 – 2018-10-22 5:12:46 – 27:21:32 –
2018-10-22 – 2018-10-29 9:24:40 – 71:59:04 –
2018-10-29 – 2018-11-05 2:07:45 – 39:58:26 –
2018-11-05 – 2018-11-12 2:37:37 – 123:14:47 –
2018-11-12 – 2018-11-19 2:38:58 – 167:41:01 –
2018-11-19 – 2018-11-26 6:16:42 – 214:10:48 –
2018-11-26 – 2018-12-03 0:41:12 – 64:26:10 –
2018-12-03 – 2018-12-10 2:41:56 – 96:38:22 –
2018-12-10 – 2018-12-17 7:56:20 – 154:40:50 –
2018-12-17 – 2018-12-24 18:50:03 – 488:24:51 –
2018-12-24 – 2018-12-31 16:54:54 – 497:41:39 –
2018-12-31 – 2019-01-07 17:51:23 – 492:36:38 –
2019-01-07 – 2019-01-14 19:31:59 – 464:01:35 –
2019-01-14 – 2019-01-21 19:26:44 – 463:36:06 –
2019-01-21 – 2019-01-28 18:13:30 – 462:52:31 –
2019-01-28 – 2019-02-04 22:22:34 – 493:45:50 –
2019-02-04 – 2019-02-11 22:00:46 – 509:36:44 –
2019-02-11 – 2019-02-18 18:09:29 – 516:53:44 –
2019-02-18 – 2019-02-25 19:34:21 – 465:33:56 –
2019-02-25 – 2019-03-04 21:01:30 – 485:39:57 –
2019-03-04 – 2019-03-11 38:26:03 – 472:43:57 –
2019-03-11 – 2019-03-18 49:14:26 – 483:59:59 –
2019-03-18 – 2019-03-25 48:39:15 – 490:23:11 –
2019-03-25 – 2019-04-01 48:39:32 – 448:50:39 –
2019-04-01 – 2019-04-08 40:25:53 – 368:40:25 –
2019-04-08 – 2019-04-15 39:47:30 – 323:26:44 –
2019-04-15 – 2019-04-22 – – 18:35:37 –
2019-04-22 – 2019-04-29 34:27:10 – 260:06:24 –
2019-04-29 – 2019-05-06 13:24:39 – 247:03:54 –
2019-05-06 – 2019-05-13 13:23:16 – 257:40:50 –
2019-05-13 – 2019-05-20 0:34:46 – 262:21:10 –
2019-05-20 – 2019-05-27 0:00:04 – 16:03:51 –
2019-05-27 – 2019-06-03 0:00:01 – 54:44:17 –
2019-06-03 – 2019-06-10 1:37:25 – 46:28:01 –
2019-06-10 – 2019-06-17 1:14:31 – 70:09:31 –
2019-06-17 – 2019-06-24 0:43:50 – 77:27:47 –
2019-06-24 – 2019-07-01 0:37:16 – 74:53:19 –
2019-07-01 – 2019-07-08 3:04:18 – 61:37:08 –
2019-07-08 0:33:27 – 4:54:04 –
2019-07-09 0:00:01 – 8:44:37 –
2019-07-10 – – 6:59:42 –
2019-07-11 – – 4:57:37 –
2019-07-12 0:02:26 – 10:03:44 –
2019-07-13 0:00:17 – 14:21:52 –
2019-07-14 0:08:06 – 11:48:48 –
2019-07-15 0:00:46 – 3:57:11 –
2019-07-16 – – 13:41:20 –
2019-07-17 – – 5:46:22 –
2019-07-18 – – 10:08:03 –
2019-07-19 0:22:05 – 10:18:56 –
2019-07-20 – – 13:47:44 –
2019-07-21 0:11:45 – 7:24:11 –
Battery capacity history
Charge capacity history of the system’s batteries
PERIOD FULL CHARGE CAPACITY DESIGN CAPACITY
2018-10-08 – 2018-10-15 41,869 mWh 48,000 mWh
2018-10-15 – 2018-10-22 41,869 mWh 48,000 mWh
2018-10-22 – 2018-10-29 41,893 mWh 48,000 mWh
2018-10-29 – 2018-11-05 41,924 mWh 48,000 mWh
2018-11-05 – 2018-11-12 41,920 mWh 48,000 mWh
2018-11-12 – 2018-11-19 41,920 mWh 48,000 mWh
2018-11-19 – 2018-11-26 41,876 mWh 48,000 mWh
2018-11-26 – 2018-12-03 41,602 mWh 48,000 mWh
2018-12-03 – 2018-12-10 41,493 mWh 48,000 mWh
2018-12-10 – 2018-12-17 41,323 mWh 48,000 mWh
2018-12-17 – 2018-12-24 41,601 mWh 48,000 mWh
2018-12-24 – 2018-12-31 41,535 mWh 48,000 mWh
2018-12-31 – 2019-01-07 41,438 mWh 48,000 mWh
2019-01-07 – 2019-01-14 41,315 mWh 48,000 mWh
2019-01-14 – 2019-01-21 41,194 mWh 48,000 mWh
2019-01-21 – 2019-01-28 41,137 mWh 48,000 mWh
2019-01-28 – 2019-02-04 41,009 mWh 48,000 mWh
2019-02-04 – 2019-02-11 40,929 mWh 48,000 mWh
2019-02-11 – 2019-02-18 40,919 mWh 48,000 mWh
2019-02-18 – 2019-02-25 40,880 mWh 48,000 mWh
2019-02-25 – 2019-03-04 40,793 mWh 48,000 mWh
2019-03-04 – 2019-03-11 40,790 mWh 48,000 mWh
2019-03-11 – 2019-03-18 40,799 mWh 48,000 mWh
2019-03-18 – 2019-03-25 40,747 mWh 48,000 mWh
2019-03-25 – 2019-04-01 40,698 mWh 48,000 mWh
2019-04-01 – 2019-04-08 40,690 mWh 48,000 mWh
2019-04-08 – 2019-04-15 40,649 mWh 48,000 mWh
2019-04-15 – 2019-04-22 40,380 mWh 48,000 mWh
2019-04-22 – 2019-04-29 40,524 mWh 48,000 mWh
2019-04-29 – 2019-05-06 40,501 mWh 48,000 mWh
2019-05-06 – 2019-05-13 40,467 mWh 48,000 mWh
2019-05-13 – 2019-05-20 40,507 mWh 48,000 mWh
2019-05-20 – 2019-05-27 40,980 mWh 48,000 mWh
2019-05-27 – 2019-06-03 40,976 mWh 48,000 mWh
2019-06-03 – 2019-06-10 40,644 mWh 48,000 mWh
2019-06-10 – 2019-06-17 37,233 mWh 48,000 mWh
2019-06-17 – 2019-06-24 36,854 mWh 48,000 mWh
2019-06-24 – 2019-07-01 35,295 mWh 48,000 mWh
2019-07-01 – 2019-07-08 35,636 mWh 48,000 mWh
2019-07-08 33,096 mWh 48,000 mWh
2019-07-09 33,349 mWh 48,000 mWh
2019-07-10 35,966 mWh 48,000 mWh
2019-07-11 33,570 mWh 48,000 mWh
2019-07-12 33,570 mWh 48,000 mWh
2019-07-13 33,106 mWh 48,000 mWh
2019-07-14 31,410 mWh 48,000 mWh
2019-07-15 31,410 mWh 48,000 mWh
2019-07-16 31,410 mWh 48,000 mWh
2019-07-17 31,410 mWh 48,000 mWh
2019-07-18 30,932 mWh 48,000 mWh
2019-07-19 30,460 mWh 48,000 mWh
2019-07-20 30,405 mWh 48,000 mWh
2019-07-21 30,405 mWh 48,000 mWh
Battery life estimates
Battery life estimates based on observed drains
AT FULL CHARGE AT DESIGN CAPACITY
PERIOD ACTIVE CONNECTED STANDBY ACTIVE CONNECTED STANDBY
2018-10-08 – 2018-10-15 3:17:30 – 3:46:26 –
2018-10-15 – 2018-10-22 2:58:47 – 3:24:58 –
2018-10-22 – 2018-10-29 2:51:09 – 3:16:06 –
2018-10-29 – 2018-11-05 2:51:14 – 3:16:04 –
2018-11-05 – 2018-11-12 2:48:19 – 3:12:43 –
2018-11-12 – 2018-11-19 2:47:27 – 3:11:44 –
2018-11-19 – 2018-11-26 2:48:41 – 3:13:21 –
2018-11-26 – 2018-12-03 3:36:00 – 4:09:13 –
2018-12-03 – 2018-12-10 2:48:08 – 3:14:30 –
2018-12-10 – 2018-12-17 2:30:34 – 2:54:54 –
2018-12-17 – 2018-12-24 2:35:07 – 2:58:59 –
2018-12-24 – 2018-12-31 2:33:29 – 2:57:22 –
2018-12-31 – 2019-01-07 2:26:58 – 2:50:15 –
2019-01-07 – 2019-01-14 2:25:04 – 2:48:33 –
2019-01-14 – 2019-01-21 2:25:04 – 2:49:02 –
2019-01-21 – 2019-01-28 2:22:08 – 2:45:50 –
2019-01-28 – 2019-02-04 2:08:44 – 2:30:41 –
2019-02-04 – 2019-02-11 2:01:02 – 2:21:57 –
2019-02-11 – 2019-02-18 1:55:38 – 2:15:39 –
2019-02-18 – 2019-02-25 1:55:03 – 2:15:05 –
2019-02-25 – 2019-03-04 1:55:52 – 2:16:21 –
2019-03-04 – 2019-03-11 4:06:55 – 4:50:34 –
2019-03-11 – 2019-03-18 4:38:14 – 5:27:20 –
2019-03-18 – 2019-03-25 4:38:10 – 5:27:41 –
2019-03-25 – 2019-04-01 4:37:54 – 5:27:46 –
2019-04-01 – 2019-04-08 7:24:07 – 8:43:54 –
2019-04-08 – 2019-04-15 7:34:55 – 8:57:11 –
2019-04-15 – 2019-04-22 – – – –
2019-04-22 – 2019-04-29 12:36:37 – 14:56:12 –
2019-04-29 – 2019-05-06 5:30:53 – 6:32:09 –
2019-05-06 – 2019-05-13 5:29:11 – 6:30:28 –
2019-05-13 – 2019-05-20 1:33:58 – 1:51:21 –
2019-05-20 – 2019-05-27 0:10:42 – 0:12:32 –
2019-05-27 – 2019-06-03 0:15:10 – 0:17:46 –
2019-06-03 – 2019-06-10 1:15:13 – 1:28:50 –
2019-06-10 – 2019-06-17 2:02:15 – 2:37:36 –
2019-06-17 – 2019-06-24 35:11:40 – 45:50:19 –
2019-06-24 – 2019-07-01 6:49:45 – 9:17:15 –
2019-07-01 – 2019-07-08 2:43:29 – 3:40:13 –
2019-07-08 – – – –
2019-07-09 0:01:41 – 0:02:25 –
2019-07-10 – – – –
2019-07-11 – – – –
2019-07-12 1:35:32 – 2:16:36 –
2019-07-13 0:23:09 – 0:33:34 –
2019-07-14 – – – –
2019-07-15 – – – –
2019-07-16 – – – –
2019-07-17 – – – –
2019-07-18 – – – –
2019-07-19 – – – –
2019-07-20 – – – –
2019-07-21 – – – –
Current estimate of battery life based on all observed drains since OS install
Since OS install 2:30:46 – 3:58:01 –
Alberto Antonio Garcia
Power Efficiency Diagnostics Report
Computer Name DESKTOP-S65P24T
Scan Time 2021-04-20T16:46:58Z
Scan Duration 60 seconds
System Manufacturer Hewlett-Packard
System Product Name HP Pavilion dv6 Notebook PC
BIOS Date 01/25/2013
BIOS Version F.1C
OS Build 19042
Platform Role PlatformRoleMobile
Plugged In true
Process Count 227
Thread Count 2058
Report GUID {bedf69da-8dd0-405f-8ba9-037d1eb870c1}
Analysis Results
Errors
System Availability Requests:Execution Required Request
The program has made a request for execution-required.
Requesting Process \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
System Availability Requests:Execution Required Request
The program has made a request for execution-required.
Requesting Process \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
System Availability Requests:System Required Request
The device or driver has made a request to prevent the system from automatically entering sleep.
Requesting Driver Instance HDAUDIO\FUNC_01&VEN_111D&DEV_7605&SUBSYS_103C358B&REV_1001\4&3119f6c0&0&0001
Requesting Driver Device High Definition Audio Device
System Availability Requests:System Required Request
The device or driver has made a request to prevent the system from automatically entering sleep.
Requesting Driver Instance ـ
Requesting Driver Device
USB Suspend:USB Device not Entering Selective Suspend
This device did not enter the USB Selective Suspend state. Processor power management may be prevented when this USB device is not in the Selective Suspend state. Note that this issue will not prevent the system from sleeping.
Device Name USB Root Hub
Host Controller ID PCI\VEN_1022&DEV_7807
Host Controller Location PCI bus 0, device 19, function 0
Device ID USB\VID_1022&PID_7807
Port Path
USB Suspend:USB Device not Entering Selective Suspend
This device did not enter the USB Selective Suspend state. Processor power management may be prevented when this USB device is not in the Selective Suspend state. Note that this issue will not prevent the system from sleeping.
Device Name Validity Sensors (WBF) (PID=0018)
Host Controller ID PCI\VEN_1022&DEV_7807
Host Controller Location PCI bus 0, device 19, function 0
Device ID USB\VID_138A&PID_0018
Port Path 2
CPU Utilization:Processor utilization is high
The average processor utilization during the trace was high. The system will consume less power when the average processor utilization is very low. Review processor utilization for individual processes to determine which applications and services contribute the most to total processor utilization.
Average Utilization (%) 58.05
Warnings
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 9448
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 11456
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 9204
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 9024
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 4168
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 2720
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 8304
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 5380
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 4168
Average Utilization (%) 29.41
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 24.63
\SystemRoot\system32\ntoskrnl.exe 3.82
0.39
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name chrome.exe
PID 7404
Average Utilization (%) 16.61
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll 14.42
\SystemRoot\system32\ntoskrnl.exe 1.05
1.02
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 9024
Average Utilization (%) 1.40
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 0.79
\SystemRoot\system32\ntoskrnl.exe 0.46
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.10
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name System
PID 4
Average Utilization (%) 1.35
Module Average Module Utilization (%)
\SystemRoot\system32\ntoskrnl.exe 1.11
\SystemRoot\System32\drivers\rtwlane_13.sys 0.15
\SystemRoot\System32\Drivers\Ntfs.sys 0.00
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name chrome.exe
PID 11456
Average Utilization (%) 0.92
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll 0.58
\SystemRoot\system32\ntoskrnl.exe 0.26
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.05
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name MsMpEng.exe
PID 6728
Average Utilization (%) 0.87
Module Average Module Utilization (%)
\Device\HarddiskVolume2\ProgramData\Microsoft\Windows Defender\Definition Updates\{5F5A30CB-F7D3-4A3E-B80F-795B538165A0}\mpengine.dll 0.55
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.14
\SystemRoot\system32\ntoskrnl.exe 0.13
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name svchost.exe
PID 1928
Average Utilization (%) 0.66
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Windows\System32\sysmain.dll 0.32
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.26
\SystemRoot\system32\ntoskrnl.exe 0.05
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 5380
Average Utilization (%) 0.64
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 0.42
\SystemRoot\system32\ntoskrnl.exe 0.17
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.01
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 8252
Average Utilization (%) 0.58
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 0.44
\SystemRoot\system32\ntoskrnl.exe 0.11
0.01
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 9448
Average Utilization (%) 0.56
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 0.30
\SystemRoot\system32\ntoskrnl.exe 0.19
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.04
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 8916
Average Utilization (%) 0.43
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 0.39
\SystemRoot\system32\ntoskrnl.exe 0.03
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.00
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 2616
Average Utilization (%) 0.42
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 0.19
\SystemRoot\system32\ntoskrnl.exe 0.15
\SystemRoot\System32\win32kbase.sys 0.01
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name chrome.exe
PID 8304
Average Utilization (%) 0.38
Module Average Module Utilization (%)
\SystemRoot\system32\ntoskrnl.exe 0.20
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll 0.10
\SystemRoot\System32\Drivers\Ntfs.sys 0.01
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name audiodg.exe
PID 2452
Average Utilization (%) 0.29
Module Average Module Utilization (%)
\SystemRoot\system32\ntoskrnl.exe 0.14
\Device\HarddiskVolume2\Windows\System32\AudioEng.dll 0.07
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.02
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name chrome.exe
PID 9204
Average Utilization (%) 0.28
Module Average Module Utilization (%)
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll 0.12
\SystemRoot\system32\ntoskrnl.exe 0.11
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.01
CPU Utilization:Individual process with significant processor utilization.
This process is responsible for a significant portion of the total processor utilization recorded during the trace.
Process Name msedge.exe
PID 8348
Average Utilization (%) 0.26
Module Average Module Utilization (%)
\SystemRoot\system32\ntoskrnl.exe 0.11
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll 0.08
\Device\HarddiskVolume2\Windows\System32\ntdll.dll 0.01
Battery:Last Full Charge (%)
The battery stored less than 50% of the Designed Capacity the last time the battery was fully charged.
Battery ID Li4402A Hewlett-Packard 5100
Design Capacity 55080
Last Full Charge 23360
Last Full Charge (%) 42
Information
Platform Timer Resolution:Platform Timer Resolution
The default platform timer resolution is 15.6ms (15625000ns) and should be used whenever the system is idle. If the timer resolution is increased, processor power management technologies may not be effective. The timer resolution may be increased due to multimedia playback or graphical animations.
Current Timer Resolution (100ns units) 156250
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 9448
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 11456
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 9204
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 9024
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 4168
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 2720
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 8304
Requesting Process Path \Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\90.0.4430.72\chrome.dll
\Device\HarddiskVolume2\Program Files\Google\Chrome\Application\chrome.exe
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Platform Timer Resolution:Timer Request Stack
The stack of modules responsible for the lowest platform timer setting in this process.
Requested Period 10000
Requesting Process ID 5380
Requesting Process Path \Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
Calling Module Stack \Device\HarddiskVolume2\Windows\System32\ntdll.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\90.0.818.41\msedge.dll
\Device\HarddiskVolume2\Windows\System32\kernel32.dll
\Device\HarddiskVolume2\Windows\System32\ntdll.dll
Power Policy: Active Power Plan
The current power plan in use
Plan Name OEM Balanced
Plan GUID {381b4222-f694-41f0-9685-ff5bb260df2e}
Power Policy: Power Plan Personality (On Battery)
The personality of the current power plan when the system is on battery power.
Personality Balanced
Power Policy:Video Quality (On Battery)
Enables Windows Media Player to optimize for quality or power savings when playing video.
Quality Mode Balance Video Quality and Power Savings
Power Policy:Power Plan Personality (Plugged In)
The personality of the current power plan when the system is plugged in.
Personality Balanced
Power Policy:802.11 Radio Power Policy is Maximum Performance (Plugged In)
The current power policy for 802.11-compatible wireless network adapters is not configured to use low-power modes.
Power Policy:Video quality (Plugged In)
Enables Windows Media Player to optimize for quality or power savings when playing video.
Quality Mode Optimize for Video Quality
Battery: Battery Information
Battery ID Li4402A Hewlett-Packard 5100
Manufacturer Hewlett-Packard
Serial Number Li4402A
Chemistry LION
Long Term 1
Sealed 0
Design Capacity 55080
Last Full Charge 23360
Platform Power Management Capabilities: Supported Sleep States
Sleep states allow the computer to enter low-power modes after a period of inactivity. The S3 sleep state is the default sleep state for Windows platforms. The S3 sleep state consumes only enough power to preserve memory contents and allow the computer to resume working quickly. Very few platforms support the S1 or S2 Sleep states.
S1 Sleep Supported false
S2 Sleep Supported false
S3 Sleep Supported true
S4 Sleep Supported true
Platform Power Management Capabilities: Connected Standby Support
Connected standby allows the computer to enter a low-power mode in which it is always on and connected. If supported, connected standby is used instead of system sleep states.
Connected Standby Supported false
Platform Power Management Capabilities: Adaptive Display Brightness is supported.
This computer enables Windows to automatically control the brightness of the integrated display.
Platform Power Management Capabilities: Processor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 0
Idle State Count 2
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 1600
Maximum Performance Percentage 100
Lowest Performance Percentage 50
Lowest Throttle Percentage 50
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Platform Power Management Capabilities: Processor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 1
Idle State Count 2
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 1600
Maximum Performance Percentage 100
Lowest Performance Percentage 50
Lowest Throttle Percentage 50
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Platform Power Management Capabilities: Processor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 2
Idle State Count 2
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 1600
Maximum Performance Percentage 100
Lowest Performance Percentage 50
Lowest Throttle Percentage 50
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Platform Power Management Capabilities:Processor Power Management Capabilities
Effective processor power management enables the computer to automatically balance performance and energy consumption.
Group 0
Index 3
Idle State Count 2
Idle State Type ACPI Idle (C) States
Nominal Frequency (MHz) 1600
Maximum Performance Percentage 100
Lowest Performance Percentage 50
Lowest Throttle Percentage 50
Performance Controls Type ACPI Performance (P) / Throttle (T) States
Device Drivers: Analysis Success
Analysis was successful. No energy efficiency problems were found. No information was returned.