[Bug]: CPU plugin crashes silently on Intel Xeon 6740E (OpenVINO 2024.5/2024.6/2025.3.0, Windows Server 2025)

[zazor1911]

OpenVINO Version

2025.3

Operating System

Windows System

Device used for inference

CPU

Framework

None

Model used

No response

Issue description

CPU plugin crashes silently on Intel Xeon 6740E (OpenVINO 2024.5/2024.6/2025.3.0, Windows Server 2025)

Description

When using OpenVINO (versions 2024.5, 2024.6, and 2025.3.0) on an Intel Xeon 6740E CPU, the CPU plugin crashes immediately upon initialization.
No devices or version information are printed when the CPU plugin is present. The GPU plugin works correctly.
Removing or renaming openvino_intel_cpu_plugin.dll allows the GPU to initialize and display properly.

Steps to Reproduce

1. Install OpenVINO 2024.5, 2024.6, or 2025.3.0 runtime on Windows Server 2025 Standard Evaluation 24H2.
2. Run the sample hello_query_device.exe or the following minimal code:

#include <openvino/openvino.hpp>
#include <iostream>

int main() {
    try {
        ov::Core core;
        auto devices = core.get_available_devices();
        std::cout << "Available devices:" << std::endl;
        for (const auto& dev : devices) {
            std::cout << " - " << dev << std::endl;
        }
    } catch (const std::exception& e) {
        std::cerr << "Exception caught: " << e.what() << std::endl;
    }
}

3. Observe that no output is printed when the CPU plugin is present.

Expected Behavior

The CPU plugin should initialize correctly, and get_available_devices() should list the CPU and GPU devices.

Actual Behavior

The program silently crashes or exits without printing any devices or version info when the CPU plugin is present.
Only removing or renaming openvino_intel_cpu_plugin.dll allows GPU devices to be detected and printed.

Environment

• CPU: Intel Xeon 6740E
• OS: Windows Server 2025 Standard Evaluation 24H2
• OpenVINO versions: 2024.5, 2024.6, 2025.3.0
• Compiler: MSVC 14.16 (VS2017)
• oneDNN: bundled with OpenVINO
• Hypervisor: not present (HYPERVISOR flag is -)
• Observed on: both hello_query_device.exe and custom OpenVINO C++ code

Notes / Additional Info

• Enabling logging via environment variables (OV_LOG_LEVEL=DEBUG, DNNL_VERBOSE=1) produces no additional output before crash.
• Removing the CPU plugin DLL allows GPU devices to initialize normally.
• CPU ISA: AVX2 (Xeon 6740E), AVX-512 not fully supported on this CPU.

Step-by-step reproduction

No response

Relevant log output

Issue submission checklist

• I'm reporting an issue. It's not a question.
• I checked the problem with the documentation, FAQ, open issues, Stack Overflow, etc., and have not found a solution.
• There is reproducer code and related data files such as images, videos, models, etc.

[wangleis]

Hi @zazor1911, could you run attached tools and share the log for debugging?

test_info.zip

[zazor1911]

Hi @zazor1911, could you run attached tools and share the log for debugging?

test_info.zip

Hi, @wangleis

Please find the results attached below.

test_data.txt

[wangleis]

Hi @zazor1911, thank you for your information.

Could you also share the log of https://learn.microsoft.com/en-us/sysinternals/downloads/coreinfo?

[zazor1911]

Hi @zazor1911, thank you for your information.

Could you also share the log of https://learn.microsoft.com/en-us/sysinternals/downloads/coreinfo?

Hi @wangleis, the result

coreinfo_output.txt

[zazor1911]

Hi @wangleis,

Thank you for reviewing the logs.

I am still unable to run any OpenVINO models on the CPU backend on this system (Intel Xeon 6740E, Windows Server 2025). Even the hello_query_device.exe crashes immediately when the CPU plugin is loaded, while GPU-only works. This happens across OpenVINO versions 2024.5, 2024.6, and 2025.3.

Could you please advise if there is any known workaround, patch, or build configuration that allows OpenVINO CPU plugin to run on this processor? Any guidance to at least get the CPU backend running would be greatly appreciated.

Thank you in advance for your help!

[wangleis]

Hi @zazor1911 ,

Since the CPU information in system is not right, I create #32304 as WA. Please try it.