The frame rate value '159.08.00' in HWiNFO64 CSV logs is a parsing artifact caused by Excel interpreting the European decimal comma as a list separator. The actual frame rate is 159.08 FPS, where the middle segment represents fractional seconds and the trailing zeros are formatting artifacts from the CSV structure. This guide explains how to correctly interpret these values for accurate performance analysis.
Understanding the CSV Structure
HWiNFO64 exports sensor data into Comma Separated Values (CSV) format, which is designed for maximum compatibility across different operating systems and software applications. When you enable the "Text Columns" feature in your logging settings, HWiNFO64 ensures that all numeric values are exported as text strings rather than raw numbers. This prevents automatic formatting changes but introduces specific challenges when opening the file in spreadsheet software like Microsoft Excel.
The core issue arises from regional settings. In many European countries, the standard decimal separator is a comma (,) rather than a period (.). However, the CSV delimiter is also a comma. When Excel opens a file generated on a system with different regional settings, it may misinterpret the decimal comma as a field separator. This causes a single logical value to split across multiple columns or cells, creating the confusing multi-dot appearance such as 159.08.00. It is critical to understand that this is not a native HWiNFO64 format quirk but a result of how the importing application parses the text.
Distinguishing Real Data from Artifacts
To accurately diagnose performance issues, you must distinguish between the actual metric and the display artifact. The primary integer part, 159, represents the whole frames per second. The subsequent parts are fragments of the decimal fraction. In a correctly parsed view, the value would appear as 159,08. The extra segments often result from the CSV parser treating the decimal point as a new column boundary because it expects commas to separate distinct fields.
If you are troubleshooting high CPU temperatures, as discussed in our guide on Troubleshooting High CPU Temperature Values, precise timestamping and metric accuracy are equally important. Misinterpreting frame rates can lead to incorrect conclusions about thermal throttling or GPU bottlenecks. Ensuring your data import method is robust prevents false positives in your diagnostic reports.
Correctly Importing the Data in Excel
The most reliable way to resolve this issue is to avoid simply double-clicking the CSV file. Instead, use Excel's dedicated Text Import Wizard. This tool allows you to explicitly define the delimiter and the decimal separator, overriding the default regional settings of your operating system.
- Open Excel: Launch Microsoft Excel without opening any existing file. Go to the Data tab on the ribbon menu.
- Select From Text/CSV: Click on the From Text/CSV button located in the Get & Transform Data group. Browse to your HWiNFO64 log file and select it.
- Configure Delimiters: In the preview window, ensure that Comma is selected as the delimiter. You should see the data columns align correctly in the preview pane.
- Set Decimal Separator: Look for the option labeled "Decimal separator." Change this from the default (often a period) to a comma if your region uses commas, or vice versa depending on how HWiNFO64 was configured. If HWiNFO64 outputs commas for decimals, setting the decimal separator to comma will keep the value intact in a single cell.
- Load Data: Click Load to import the data into a new worksheet. The frame rate values should now appear as single, coherent numbers like
159.08or159,08.
Alternative Interpretation Methods
If you cannot use the Text Import Wizard, you can manually clean the data using Excel formulas. If the value appears split across columns A, B, and C as 159, 08, and 00, you can reconstruct the number using the formula =A1 + (B1/100). This assumes the middle column represents hundredths of a second. However, this method is prone to error if the precision varies between log entries.
Another approach is to change the global regional settings of Windows before opening the file. By temporarily switching your system locale to a region that uses periods for decimals, Excel will treat the comma in the CSV as a true delimiter, potentially restoring the expected column structure. However, this affects all other applications and is less convenient than using the import wizard. For users investigating complex hardware interactions, such as those described in Understanding Strange Behavior of ALBLC Registers, maintaining consistent data formats across different diagnostic tools is essential for correlating events.
Verifying Frame Rate Accuracy
Once the data is correctly imported, verify the frame rate against known benchmarks. A stable game running at 144 Hz should show values hovering around 144.00. Significant deviations, such as sudden drops to single digits, may indicate stuttering or driver crashes. Consistent low values might suggest insufficient hardware resources or background processes interfering with rendering.
It is also worth noting that HWiNFO64 calculates frame rates based on time deltas between frames. If the logging interval is too short, noise in the measurement can cause erratic fluctuations. Increasing the logging frequency or averaging the values over a longer period can provide a smoother and more representative picture of performance stability.
Frequently Asked Questions
Why does my CSV file have extra empty columns?
Extra empty columns usually appear when the decimal separator is misinterpreted as a field delimiter. Excel splits the number at the comma, leaving the remaining parts in adjacent cells. Using the Text Import Wizard to specify the correct decimal separator resolves this by keeping the entire number in one cell.
Can I export HWiNFO64 data with periods instead of commas?
HWiNFO64 respects the regional settings of the host system. To force periods, you would need to change your Windows regional settings to use periods for decimals before starting HWiNFO64. Alternatively, you can post-process the CSV file using a script to replace commas with periods if the delimiter remains consistent.
Does this issue affect other sensor readings like temperature?
Yes, any numerical sensor reading that includes a decimal fraction will be affected if the decimal separator conflicts with the CSV delimiter. Temperatures, voltages, and clock speeds will all exhibit similar splitting issues if not imported correctly.
Is there a way to automate this fix for large log files?
You can use Power Query in Excel to create a reusable query. Once you configure the import steps correctly, save the query. Future imports can be refreshed automatically, applying the same delimiter and decimal settings without manual intervention.
What should I do if the frame rate values still look wrong after importing?
Check the source configuration in HWiNFO64. Ensure that the "Use comma as decimal separator" option is disabled if you prefer standard US formatting. Also, verify that no custom formatting rules in Excel are overriding the imported text values by converting them back to numbers incorrectly.