Saturday, 26 August 2023

Microsoft Investigates ‘Blue Screen of Death’ Issue in Windows 10 and 11 Caused by Processor Incompatibility

Investigation Underway: Windows 10 and 11 Users Face “Blue Screen of Death” Incompatibility Issue

Microsoft has recently been investigating a concerning problem that Windows 10 and 11 users have been encountering. A notorious “blue screen of death” error message has been popping up, pointing towards processor incompatibility.

Many users have reported that this issue started occurring after installing recent updates, despite having computers with supported processors. The unexpected crashes take a toll on the operating system, resulting in the dreaded blue screen of death, commonly known as BSOD, displaying an error message stating “UNSUPPORTED_PROCESSOR.”

Recognizing the gravity of the situation, Microsoft has acknowledged the problem and has urged affected users to provide feedback through the Feedback Hub app. Microsoft’s prompt action is a step towards finding a solution to this discouraging glitch.

Reports received by Microsoft point out that the issue mostly affects MSI motherboards utilizing Intel 600 and 700 series processors. On the other hand, motherboards from companies like Asus and Gigabyte appear to be relatively less affected.

Gigabyte, a well-known manufacturer of computer components, has advised users to temporarily resolve the problem by reverting the BIOS to a previous version. Additionally, they recommend removing updates KB5029351 from Windows 11 and KB5029331 from Windows 10.

While Microsoft is relentlessly working to identify the root causes behind this distressing issue, a conclusive understanding of why the recent updates result in Windows system crashes remains elusive.

The post Microsoft Investigates ‘Blue Screen of Death’ Issue in Windows 10 and 11 Caused by Processor Incompatibility appeared first on asumetech.



from Technology - asumetech https://asumetech.com/microsoft-investigates-blue-screen-of-death-issue-in-windows-10-and-11-caused-by-processor-incompatibility/

No comments:

Post a Comment