topic Re: Hardware Event-Based Sampling fails to run in Analyzers

Hardware Event-Based Sampling fails to run

Takap — Wed, 21 May 2025 04:56:13 GMT

When running VTune under the following conditions, the entire OS crashes about 2 out of every 3 times.

Environment: OS: Windows 10 IoT 21H1
CPU: Intel Xeon Gold 6548N

----------

VTune Profiler:

- Version: 2025.3.0
- Type: Hotspots
- Hardware Event-Based Sampling
- CPU sampling interval: The same issue occurs at any value between 1 and 100
- Collect stacks: ON/OFF does not matter
- Launch VTune Profiler.
- Select Hotspots analysis.
- Start collection.

Before the crash occurs, the following logs may appear in the console:

vcs\collectunits1\tmu\src\tmu.c:425 write_trace: Assertion 'err.error_code == TMU_ERROR_SUCCESS' failed.
tmu425: err.error_code == TMU_ERROR_SUCCESS : BUG! : Cannot write magic record to trace, err=2 syserr=0

Event Viwer StopCode: 0xc0000409

----------

Execution result: amplxe-sepreg.exe -s

Checking sepdrv5 driver path...OK
Checking sepdrv5 service...
Driver status: the sepdrv5 service is running
Checking sepdal driver path...OK
Checking sepdal service...
Driver status: the sepdal service is running
Checking socperf3 driver path...OK
Checking socperf3 service...
Driver status: the socperf3 service is running
Checking vtss driver path...OK
Checking vtss service...OK

----------

Execution result: vtune-self-checker.bat

Intel(R) VTune(TM) Profiler Self Check Utility
Copyright (C) 2009 Intel Corporation. All rights reserved.
Build Number: 630104

HW event-based analysis (counting mode)...
HW event-based analysis (counting mode) (Intel driver)
Example of analysis types: Performance Snapshot
Collection: Ok
Running finalization...
Finalization: Ok
Report: Ok

Instrumentation based analysis check...
Instrumentation based analysis check
Example of analysis types: Hotspots and Threading with user-mode sampling
Collection: Ok
Running finalization...
Finalization: Ok
Report: Ok

HW event-based analysis check...
HW event-based analysis check (Intel driver)
Example of analysis types: Hotspots with HW event-based sampling, HPC Performance Characterization, etc.
Collection: Ok
Running finalization...
Finalization: Ok
Report: Ok

HW event-based analysis check...
HW event-based analysis check (Intel driver)
Example of analysis types: Microarchitecture Exploration
Collection: Ok
Running finalization...
Finalization: Ok
Report: Ok

HW event-based analysis with uncore events...
HW event-based analysis with uncore events (Intel driver)
Example of analysis types: Memory Access
Collection: Ok
Running finalization...

** ---- The OS crashes at this point. ----

----

Is this a known issue? Are there any workarounds or additional diagnostics I can try?
If you need more information, please let me know.

Thank you.

Re: Hardware Event-Based Sampling fails to run

yuzhang3_intel — Wed, 21 May 2025 06:13:43 GMT

When it crashes, are there any log files generated?

Re: Hardware Event-Based Sampling fails to run

Takap — Wed, 21 May 2025 08:26:58 GMT

When the PC does not crash, I see the following logs:

In the application console, I get these outputs:

> vcs\collectunits1\tmu\src\tmu.c:425 write_trace: Assertion 'err.error_code == TMU_ERROR_SUCCESS' failed.
> tmu425: err.error_code == TMU_ERROR_SUCCESS : BUG! : Cannot write magic record to trace, err=2 syserr=0

A log file is also generated in the project directory:
C:\Users<>\Documents\VTune\Projects<>\r008hs\log\perfrun-2025.05.21-15h48m35s.1428.log

Additionally, log files are created in the temporary folder:
C:\Users<>\AppData\Local\Temp\amplxe-log-SubPOT\2025-05-21-15-48-35-103.amplxe-runss.exe
amplxe-2025.05.21-15h48m35s.1428.log

It seems that no logs are saved when the OS crashes, so these are the logs collected from cases where the crash did not occur.
Thank you.

Re: Hardware Event-Based Sampling fails to run

yuzhang3_intel — Thu, 22 May 2025 01:09:16 GMT

Thanks for providing the logs, need to check.

When you run self-check utility, are there any logs generated?

Re: Hardware Event-Based Sampling fails to run

Takap — Thu, 22 May 2025 04:55:58 GMT

Yes, after running the following checker program:

> C:\Program Files (x86)\Intel\oneAPI\vtune\2025.3\bin64
> vtune-self-checker.bat

the log files were output to the following location, so I am attaching them as files:

C:\Users\<<MyUserName>>\AppData\Local\Temp\vtune-tmp-<<MyUserName>>\self-checker-YYYY.MM.DD_HH.MM.SS

Just like with VTune Profiler, running this checker program sometimes causes the PC to crash. Sometimes it completes normally, and other times it results in a crash.

I am uploading both types of logs:

1) log(Completed normally).txt
2) log(PC Crashed).txt

Thank you.

Re: Hardware Event-Based Sampling fails to run

yuzhang3_intel — Thu, 22 May 2025 05:37:02 GMT

Please attach the whole folder. In addition to the crash log, some other log files are recorded in the folder.

C:\Users\<<MyUserName>>\AppData\Local\Temp\vtune-tmp-<<MyUserName>>\