Problem with Windows 11 24H2 in Arrow Lake environment. Black screens and random transitions occur. Caused by iGPUs such as Core Ultra 9 285K and Core Ultra 7 265K. Building a Niche PC Z gamer environment

October 27, 2024CPU

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

Problem summary

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

The cause of this problem is the iGPU of the Intel Core Ultra 200S series desktop CPU (built-in GPU). In the Windows 11 24H2 environment, this problem occurs because dGPU (graphic board / grabo) and iGPU conflict. (That is, it happens if your PC has a dGPU and iGPU is enabled)

The problem affects the following three CPU models equipped with iGPU.

• Prime Ultra 9 285K
• Prime Ultra 7 265K
• Prime Ultra 5 245K

KF models such as 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/techniques

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

Solution A: Update BIOS

Please update the BIOS of your Z890 motherboard to the latest version. Updating the BIOS to a BIOS that fixes this problem basically fixes the issue. Download the latest BIOS from each motherboard manufacturer’s website, update it, and restart your PC.

Solution B: Disable iGPU

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

Solution C: Use Windows11 23H2

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

references

This issue occurs basically on all Z890 motherboard environments, including ASUS, MSI, and Gigabyte. It is very likely that most motherboards did not have the corrected BIOS from the first lot, so the probability of this problem occurring is considered to be very high. Since it is likely that a modified BIOS was applied from the second batch onwards, the probability of this problem occurring is low.