farisr99/imlcgui

Intel Memory Latency Checker GUI

imlcgui's Issues

[BUG] Download button not working

Description

GUI fails to extract the downloaded MLC archive.

Steps to Reproduce

Steps to reproduce the behaviour:

1. Go to the Configure tab
2. Click on Download
3. Error is reported in logs

Logs

[26/09/2022 19:54:09] [INFO]: File moved, extracting to "C:\Users\faris\AppData\Local\Temp\mlc"
[26/09/2022 19:54:09] [INFO]: Deleting "C:\Users\faris\AppData\Local\Temp\mlc_v3.9a.tgz"...
[26/09/2022 19:54:09] [WARN]: Failed to locate extracted directory at "C:\Users\faris\AppData\Local\Temp\mlc\Windows"

Screenshots

Additional Information

• Operating System: Windows 11
• CPU: i9 10900K
• Software Version [e.g. 1.0.0]: 1.0.21

[BUG] Bandwidth test failing on some systems

Description

Bandwidth test does not do anything on some systems.

Steps to Reproduce

Steps to reproduce the behaviour:

1. Go to the Bandwidth tab
2. Click on Run
3. Nothing changes on the GUI and an error is reported in the logs

Logs

Additional Information

• Operating System: Windows 11
• CPU: i9 12900K
• Software Version [e.g. 1.0.0]: 1.0.1

Reported by ksof on Discord.

[BUG] Run button does not work after one run

Describe the bug
Cannot run benchmarks after running a benchmark once/a few times.

To Reproduce
Steps to reproduce the behaviour:

1. Click on Run in the Quick tab
2. Wait for test to complete
3. Run again
4. If it works, keep running a few times and it should stop working

Logs

[16/12/2022 21:28:03] [INFO]: Running "mlc --bandwidth_matrix"
[16/12/2022 21:28:03] [PROCESS]: Intel(R) Memory Latency Checker - v3.9a
[16/12/2022 21:28:03] [PROCESS]: Command line parameters: --bandwidth_matrix 
[16/12/2022 21:28:03] [PROCESS]: 
[16/12/2022 21:28:03] [PROCESS]: Using buffer size of 100.000MiB/thread for reads and an additional 100.000MiB/thread for writes
[16/12/2022 21:28:04] [PROCESS]: *** Unable to access mlcdrv.sys to modify prefetchers
[16/12/2022 21:28:04] [PROCESS]: *** So, enabling random access for latency measurements
[16/12/2022 21:28:04] [PROCESS]: Measuring Memory Bandwidths between nodes within system 
[16/12/2022 21:28:04] [PROCESS]: Bandwidths are in MB/sec (1 MB/sec = 1,000,000 Bytes/sec)
[16/12/2022 21:28:04] [PROCESS]: Using all the threads from each core if Hyper-threading is enabled
[16/12/2022 21:28:04] [PROCESS]: Using Read-only traffic type
[16/12/2022 21:28:04] [PROCESS]: 		Numa node
[16/12/2022 21:28:04] [PROCESS]: Numa node	     0	
[16/12/2022 21:28:12] [PROCESS]:        0	51827.4	
[16/12/2022 21:28:12] [INFO]: Running "mlc --latency_matrix"
[16/12/2022 21:28:12] [PROCESS]: Intel(R) Memory Latency Checker - v3.9a
[16/12/2022 21:28:12] [PROCESS]: Command line parameters: --latency_matrix 
[16/12/2022 21:28:12] [PROCESS]: 
[16/12/2022 21:28:12] [PROCESS]: Using buffer size of 200.000MiB
[16/12/2022 21:28:13] [PROCESS]: *** Unable to access mlcdrv.sys to modify prefetchers
[16/12/2022 21:28:13] [PROCESS]: *** So, enabling random access for latency measurements
[16/12/2022 21:28:13] [PROCESS]: Measuring idle latencies (in ns)...
[16/12/2022 21:28:13] [PROCESS]: 		Numa node
[16/12/2022 21:28:13] [PROCESS]: Numa node	     0	
[16/12/2022 21:28:17] [PROCESS]:        0	  55.8	
[16/12/2022 21:28:17] [ERROR]: Failed to run Intel MLC quick test:
[16/12/2022 21:28:17] [ERROR]: Process has exited, so the requested information is not available.
[16/12/2022 21:28:24] [DEBUG]: User requested cancellation, killing MLC...
[16/12/2022 21:28:24] [ERROR]: Failed to kill MLC process:
[16/12/2022 21:28:24] [ERROR]: Process with an Id of 2656 is not running.
[16/12/2022 21:28:25] [DEBUG]: User requested cancellation, killing MLC...
[16/12/2022 21:28:25] [ERROR]: Failed to kill MLC process:
[16/12/2022 21:28:25] [ERROR]: Process with an Id of 2656 is not running.

Additional Information:

• Operating System: Windows 11, fresh install, latest update to date
• CPU: i9 13900K
• Software Version [e.g. 1.0.0]: 1.1.0

This issue seems to not be reproducible on some systems. It works on my main OS install but doesn't work on a fresh install.

[BUG] Latest MLC does not use mlcdrv.sys by default

Describe the bug
When I run latency check I hard wall on 50ns. When I run using Admin CMD I need to use the -e0 parameter to use Windows Driver to get the correct reading of 41.*ns.

mlc --latency_matrix -e0