Vtune 2024.2 non functional

[eugeniefx]

Hi,

VTune from OneAPI 2024.2 doesn't work.  On my machine 2024.1 works fine, but on older build of windows, and stopped after update. I Installed VTune from 2024.2 hoping it will be functional again, but no success.

error message:

vtune: Error: This analysis type is not applicable to the system because VTune Profiler cannot recognize the processor. If this is an old Intel processor, please refer to the minimum hardware requirements in the release note. If this is a new Intel processor, please check for an updated version of VTune Profiler. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
vtune: Error: This analysis type is not applicable to the current machine microarchitecture.

System info:

Windows 11 Pro 64-bit
Version 23H2
OS build 22631.3737
Experience Windows Feature Experience Pack 1000.22700.1009.0
Processor 13th Gen Intel(R) Core(TM) i7-13700H 2.40 GHz

Drivers check, shows they are ok:

C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64>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

C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64>amplxe-sepreg.exe -c
Checking platform...
Platform is genuine Intel: OK
Platform has SSE2: OK
Platform architecture: INTEL64
User has admin rights: OK
Drivers will be installed to C:\Windows\System32\Drivers\
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

But, there is crash just running sep.exe, Info from execution on GDB:

(No debugging symbols found in sep)
(gdb) r
Starting program: C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64\sep.exe
[New Thread 19200.0x8034]
[New Thread 19200.0x7360]
[New Thread 19200.0x7ff4]
[New Thread 19200.0x2918]
[New Thread 19200.0x1f3c]
[New Thread 19200.0x1b00]

Thread 1 received signal SIGSEGV, Segmentation fault.
0x00007ffcb6f0c9f1 in ucrtbase!strlen () from C:\Windows\System32\ucrtbase.dll
(gdb) bt
#0 0x00007ffcb6f0c9f1 in ucrtbase!strlen () from C:\Windows\System32\ucrtbase.dll
#1 0x00007ffcafc0488d in wmi_utils!WMI_UTILS_Check_Antivirus_Signature_version () from C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64\wmi_utils.dll
#2 0x00007ffcafc039c3 in wmi_utils!WMI_UTILS_Check_Antivirus_Signature_version () from C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64\wmi_utils.dll
#3 0x00007ff62bc0f424 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Reding from zero pointer:

0x00007ffcb6f0c9f1 <+49>: mov (%rax),%rdx

rax 0x0 0
rbx 0x0 0
rcx 0x0 0
rdx 0x0 0

Please help to resolve issue. 

[yuzhang3_intel]

For the processor not recognized and no output from sep.exe, 2024.2.1 will fix the issue. The release will be public soon.

[R-Goc]

I'm getting a very similar issue, though I get a fail from vtss:

C:\Windows\System32>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...FAILED

But the failure is the same when running sep.exe:

(lldb) Process 23156 launched: 'C:\Program Files (x86)\Intel\oneAPI\vtune\2024.2\bin64\sep.exe' (x86_64)

Process 23156 stopped * thread #1, stop reason = Exception 0xc0000005 encountered at address 0x7ffe95d8c9f1: Access violation reading location 0x00000000

frame #0: 0x00007ffe95d8c9f1 ucrtbase.dll`strlen + 49 ucrtbase.dll`strlen:

-> 0x7ffe95d8c9f1 <+49>: movq (%rax), %rdx

0x7ffe95d8c9f4 <+52>: movq %r8, %r9

0x7ffe95d8c9f7 <+55>: addq $0x8, %rax

0x7ffe95d8c9fb <+59>: addq %rdx, %r9

However, I have a longer backtrace:

(lldb) bt

* thread #1, stop reason = Exception 0xc0000005 encountered at address 0x7ffe95d8c9f1: Access violation reading location 0x00000000

* frame #0: 0x00007ffe95d8c9f1 ucrtbase.dll`strlen + 49

frame #1: 0x00007ffe86f1488d wmi_utils.dll`WMI_UTILS_Check_Antivirus_Signature_version + 4797

frame #2: 0x00007ffe86f139c3 wmi_utils.dll`WMI_UTILS_Check_Antivirus_Signature_version + 1011

frame #3: 0x00007ff77043f424 sep.exe`void TB5GEN_Cleanup(void) + 148340

frame #4: 0x00007ff77043f6ad sep.exe`void TB5GEN_Cleanup(void) + 148989

frame #5: 0x00007ff770428e66 sep.exe`void TB5GEN_Cleanup(void) + 56758

frame #6: 0x00007ff77045db34 sep.exe`TB5_UTIL_Cleanup + 82964

frame #7: 0x00007ffe96d4257d kernel32.dll`BaseThreadInitThunk + 29

frame #8: 0x00007ffe9866af28 ntdll.dll`RtlUserThreadStart + 40