Issue in Windows 11 24H2 in Arrow Lake environment. Black screens and random reboots occur. Resulting from iGPUs such as the Core Ultra 9 285K and Core Ultra 7 265K. Countermeasures/solutions available

October 27, 2024CPU

In an Intel Core Ultra 200S series desktop CPU environment (codename: Arrow Lake),Windows 11 24H2 is experiencing issues like black screen or random restart.

Problem overview

In an Intel Core Ultra 200S series desktop CPU environment, there are issues such as a black screen when installing or starting Windows 11 24H2, or random crashes that require a reboot.

This issue is caused by the Intel Core Ultra 200S series desktop CPU's iGPU (graphics processing unit integrated into the CPU). In Windows 11 24H2 environment, this issue occurs because the dGPU (graphics board/grabo) and iGPU cause a conflict. (i.e. this happens if your computer has a dGPU and iGPU is enabled)

The following three CPU models with iGPU are affected by the issue.

• Core Ultra 9 285 kilos
• Core Ultra 7 265 kilos
• Core Ultra 5 245 kilos

KF models such as the Core Ultra 7 265KF and Core Ultra 5 245KF do not have an iGPU and are not affected by this issue.

How to deal with it/solutions

If this problem occurs, there are several solutions and workarounds. Please consider one of the following.

Solution A: Update BIOS

Please update the BIOS of Z890 motherboard to the latest version. If you update the BIOS to a BIOS that fixes this issue, this will basically fix the issue. Download the latest version of BIOS from each motherboard manufacturer's website, update it, and then restart your computer.

Solution B: Disable iGPU

If a BIOS update that fixes this issue has not yet been released, please disable the iGPU from the BIOS/UEFI settings as a temporary solution. This issue will not occur if you disable the iGPU.

Solution C: Use Windows11 23H2

If a BIOS update that fixes this issue has not yet been released and you want to use both a dGPU and iGPU, please consider using Windows 11 23H2.

comments

This issue occurs in basically all Z890 motherboard environments including ASUS, MSI, and Gigabyte. It is very likely that most of the motherboards from the initial batch did not have the patched BIOS applied, so the probability of this issue occurring is very high. Since a modified BIOS was likely applied from the second set onwards, the probability of this issue occurring is low.