Burn In Mode

[zenmota]

Ok, thanks for looking into it and all the info on the Battery Test.

[Simon (PassMark)]

Any info on the Enable Testing With Constant Work Per Unit Time in the Battery Test where if I uncheck both, run Battery Test then go back and look at it, both will be checked (even though I unchecked both). If I only check CPU run test go back look at it, both or checked again. If only check Disk, run test and go back and look at it, only Disk is checked.

We are able to reproduce the issue, will be fixed for the next build

[zenmota]

Thanks, I guess I missed in the help file.

Still not sure if this is normal:

Any info on the Enable Testing With Constant Work Per Unit Time in the Battery Test where if I uncheck both, run Battery Test then go back and look at it, both will be checked (even though I unchecked both). If I only check CPU run test go back look at it, both or checked again. If only check Disk, run test and go back and look at it, only Disk is checked. By checking I mean the Disk and CPU options.

[David (PassMark)]

It is in the help file. Just not very well linked.

Yes, we did have laptop battery testing in mind when we added this feature.

[zenmota]

Any info on the Enable Testing With Constant Work Per Unit Time in the Battery Test where if I uncheck both, run Battery Test then go back and look at it, both will be checked (even though I unchecked both). If I only check CPU run test go back look at it, both or checked again. If only check Disk, run test and go back and look at it, only Disk is checked.

Thanks for all the info. Not too worried about the Battery Test in Windows with a UPS/Desktop system. Seems to me the Battery Test is more for Laptops.

Thanks

[David (PassMark)]

Somewhat ironic that the vendor supplied driver is worse than the generic Windows driver.

what does Enable Testing With Constant Work Per Unit Time do

The default behavior of BurnInTest is to do as much work as possible (depending on limits imposed by the duty cycle setting and the hardware).
So as en example, a Xeon CPU with 200 CPU cores would do many more calculations per second that a Laptop CPU with 2 cores. It would also use more electrical power.

Setting Constant Work Per Unit Time changes the behavior of BIT to do a constant number of calculation per second (or constant MB/s for the disk, etc..).
Having Constant Work Per Unit Time allow for better comparison of battery capacity and power usage of a system. That is to say it can be used to calculate the electrical efficiency of a system. Which in turn defines how long a battery will last when doing the same amount of work.

[zenmota]

Seems that's what is was. I uninstalled the CyperPower software and the went to Device Manager and removed the Battery and choose to uninstall the driver (which was a CyperPower driver). Rebooted and now Batter Shows as a HID UPS Battery and BurnIn Test detects it and will test it in Windows now.

One question, what does Enable Testing With Constant Work Per Unit Time do (nothing in Help File I could find)? Seems if I uncheck both, run Battery Test then go back and look at it, both will be checked (even though I unchecked both). If I only check CPU run test go back look at it, both or checked again. If only check Disk, run test and go back and look at it, only Disk is checked.

Thanks

[zenmota]

Maybe it's the driver from CyberPower that is loading in Windows that BurnIn Test isn't loading/reading, so it reports no Battery. However, when BurnIn Test is running in Windows PE mode it is using a default Windows driver (not the CyberPower driver) and BurnIn Test is able to report that. Just a thought.

Thanks

[David (PassMark)]

It depends on how the device drivers behave and how "smart" the battery is. For example, a UPS can function as a UPS without Windows being aware of the current charge level of the battery.

[zenmota]

Strange how the battery shows in Device Manager and shows in Windows PE version of BurnIn Test. I do know the Battery/UPS shows in programs like HWiNFO64, SIW and AIDA64. However, in Nirsoft BatteryInfoView it shows no Battery. Thanks for checking.

[Richard (PassMark)]

LOG NOTE:     2025-07-01 15:40:56, No system battery detected

The BatteryFlag in the SYSTEM_POWER_STATUS returned via the Windows API call GetSystemPowerStatus is set to the value 128, which means No system battery.

[zenmota]

It's showing in Device Manager. See Screenshot. I attached a zip file with everything the debug mode made.

Thanks

[Richard (PassMark)]

Do you have a battery device shown in the Battery category of Device Manager? If your UPS is not listed, then it likely won't get detected.

BurnInTest uses Windows API, GetSystemPowerStatus, to determine if the system is running on battery or have battery installed. If Windows reports that a battery is available, then it will enumerate the batteries on the system.

You can run BurnInTest in debug mode and send in the logs, it may indicate which step the battery detection is failing for system.

[zenmota]

It's a CyberPower CP1500PFCLCDa UPS.

Thanks

[zenmota]

I installed the software for the UPS in Windows 11 and BurnIn Test running in Windows still shows no battery.

Thanks