Intel® Xeon® Processor and Server Products
Intel® Xeon® Processors, Data Center Products including boards, integrated systems, and RAID Storage
5248 Discusiones

Intel Processor Identification Utility does not work

Vassily
Principiante
763 Vistas

This topic is related to previous one,  about incorrect indication of base processor frequency in a  notebook ASUS (1.7 GHz instead of 2.4)    https://community.intel.com/t5/Intel-Xeon-Processor-and-Server/Intel-i7-13620H-base-frequency/m-p/1725058/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufE1ITVJRRlM2U1BRRUlTfDE3MjUwNTh8U1VCU0NSSVBUSU9OU3xoSw#M26910 

ASUS released BIOS update and now base frequency is displayed correctly, so that topic can be closed.

But now Intel Processor Identification Utility does not workFail.png

0 kudos
3 Respuestas
Vik3
Empleados
717 Vistas

Hello Vassily,


Greetings!!


We would like to inform you that your case has been routed to the concerned team for further review. They will look into the issue and assist you accordingly. You can expect a response from them within 24–48 hours.


Thank you for your patience and understanding.


Regards,

Vikas_Intel


DeancR_Intel
Moderador
678 Vistas

Hi Vassily,


Thank you for the update on your previous topic regarding the base processor frequency display issue. I'm glad to hear that ASUS released a BIOS update that resolved the incorrect frequency indication (1.7 GHz instead of 2.4 GHz), and I'll make sure that topic gets closed.


Regarding the new issue with Intel Processor Identification Utility not working after the BIOS update, I'd like to help you resolve this.


Have you tried reinstalling the Intel Processor Identification Utility since the BIOS update? Sometimes BIOS changes can affect how system identification tools interact with the processor, and a fresh installation might resolve the compatibility issue.


Best regards,


Dean R.

Intel Customer Support Technician



Vassily
Principiante
662 Vistas

Hi Dean,

I've just unisntalled the Utility, downloaded it from the Intel site and installed again.

Unfortunally, it did not help. I still see the same error message ("...has encountered an unexpected condition...")

 

Best regards,

Vassily

 

Responder