Quantization Range issu

[franciscomnunes]

I've recently encountered an issue with Quantization Range, it sets for Limited (washed screen) when returning the laptop from suspension mode. Opening Intel Graphics Software and selecting Screen tab reverts the screen to normal.

I've got an HP Laltop Windows 11 25H2 with Arc A370M and Intel Iris Xe.

Arc A370M driver: gfx_win_101.8425_101.8362

Intel Xe driver: gfx_win_101.7084

Intel Graphics Software: 25.50.2012.5

Any solution to this?

Thank you

[VonM_Intel]

Hi franciscomnunes,
Thank you for posting in our Community. There is an issue with the Intel Graphics Software (IGS) where the Default Quantization Range value unexpectedly changes from Full to Limited after altering the refresh rate, particularly noted for 8-bit displays. Additionally, users have reported that the quantization range setting resets to blank after a power cycle, requiring manual adjustment back to full each time. To better isolate the cause, may I ask a few quick questions:

• Does this happen every time the laptop resumes from sleep, or only occasionally?
• Is the issue occurring on the internal laptop display, an external monitor, or both?
• Are you using HDMI or DisplayPort for any external display?
• Does toggling HDR on/off in Windows change the behavior?
• In Windows Advanced Display settings, is the refresh rate set to a fixed value?
• If you've performed any other tests, please provide the details so we can avoid going over the same steps again.

Have a nice day!

Best regards,

Von M.
Intel Customer Support Technician

[franciscomnunes]

Hi Von,

Thank you for your answer.

Regarding your questions:

• it happens every time the laptop resumes from sleep;
• it occurs on internal laptop display; haven't tried with external monitor and I don't use one
• my laptop only supports HDR for video transmission, and the issue occurs both on/off;
• the option is grayed out in Advance Display options and the issue occurs both at 60 Hz or 120 Hz; it's usually set to 120 Hz
• in IGS I've got a similar option called Panel Self Refresh and it's set to On, but it still happens either it's on or off

I've recently updated Arc A370M to version gfx_win_101.8509 and IGS to version 25.52.2110.4 and the issue still persists.

Thank you,

Best regards,

Francisco

[VonM_Intel]

Hello franciscomnunes,

Thank you for providing the detailed information. I’ll need to perform further research on this issue regarding the Quantization Range reverting to Limited after sleep/resume. Once I have more information or a potential resolution, I’ll post an update directly on this thread so you’ll be the first to know.

I appreciate your patience while I investigate this further.

Best regards,

Von M.
Intel Customer Support Technician

[franciscomnunes]

Hi Von,

Thank you for your answer.

Looking forward to hear from you.

Best regards,

Francisco

[VonM_Intel]

Hello franciscomnunes,

Thank you for your patience. As part of my next step, I would like to verify whether the OEM (Original Equipment Manufacturer) graphics driver works properly on your system. OEM drivers are customized by your system manufacturer to match the specific hardware configuration, so testing with it will help me determine if the issue is driver-related or system-related. Could you please install the latest graphics driver available from your system manufacturer’s official support website and let me know:

• Does the issue still occur with the OEM driver installed?

• Or does the system work properly after installing it?

I’ll be waiting for your update.

Best regards,

Von M.
Intel Customer Support Technician

[franciscomnunes]

Hi Von,

Thank you for your answer.

Latest driver for which graphics, iGPU or dGPU? Because now Intel has different drivers for both graphics and versions are different for each one.

With latest OEM iGPU driver the issue does not occur. Nevertheless, with latest drivers versions IGS also updated no newer version and it's the newer version with the option regarding Quantization Range that's been causing the issue. Older IGS versions (don't know which) don't have Quantization Range option and the issue doesn't occur, so I guess it might be related to IGS specifically.

Best regards,

Francisco

[VonM_Intel]

Hello franciscomnunes,

Thank you for the detailed clarification. I see your question regarding whether the latest driver refers to the iGPU or dGPU, and I appreciate you outlining the behavior differences between the OEM iGPU driver and the newer versions, particularly in relation to the Quantization Range option and IGS version changes.

Allow me to review this internally to ensure I provide you with a precise and technically accurate response, especially regarding driver differentiation and the IGS behavior you’re seeing.

I’ll get back to you as soon as possible with a clear update.

Best regards,

Von M.
Intel Customer Support Technician

[franciscomnunes]

Hi Von, 

Thank you. Looking forward to hearing from you.

Francisco

[BrenzL_Intel]

Hello franciscomnunes,

We noticed that your system is currently using generic drivers for both the integrated GPU (iGPU) and the dedicated GPU (dGPU). To ensure optimal performance and full compatibility with your device, we recommend installing the OEM‑provided drivers for both components.

OEM drivers include the specific technology, settings, customizations, and features that the manufacturer has designed and validated for your system. Using these drivers helps ensure stability, proper functionality, and the best overall performance.

Please visit your system manufacturer’s support page to download and install the latest OEM drivers for both the iGPU and dGPU.

Best regards,

Brenz L.

Intel Customer Support Technician

[franciscomnunes]

Hi Brenz,

Thank you for your answer.

OEM drivers are quite a few versions behind lastest product drivers, with many features and important performance enhancements absent.

You're suggesting I revert to OEM drivers with a previous IGS version where this issue was not occurring and loose functionality and performance tuned in newer versions?

As you may understand, this definitely doesn't seem like a proper resolution to the issue. It's a loose loose situation.

Best regards,

Francisco

[BrenzL_Intel]

Hello franciscomnunes,

I completely understand your point regarding the significant differences between the OEM driver and the Intel generic driver—especially when it comes to feature availability, performance improvements, and version gaps. However, please take into consideration that your device is an OEM‑configured system, and the drivers intended for it are specifically designed and customized by the OEM. These OEM‑provided drivers are tailored to your device’s hardware configuration, firmware, and supported features, ensuring stability and compatibility.

As mentioned previously, while Intel generic drivers can sometimes serve as an alternative, they are not optimized for OEM‑specific implementations. This is why the issue appeared when using the Intel generic driver, whereas it did not occur with the earlier OEM‑supported version.

To further investigate this concern and proceed with a driver‑level review, please provide the following information:

• All Intel Iris Xe generic driver versions you have tested
• All Intel Iris Xe OEM graphics driver versions you have tested
• All Intel Arc A370M generic driver versions you have tested
• All Intel Arc A370M OEM graphics driver versions you have tested
• Please confirm whether you used DDU (Display Driver Uninstaller) before installing any of the drivers

Once I have this information, we will proceed with a detailed driver investigation and review the driver versions involved.

Best regards,

Brenz L.

Intel Customer Support Technician

[franciscomnunes]

Hi Brenz,

Thank you for your answer.

I've been updating all graphics drivers since I have the laptop and while the first ones were really messy and with a some annoying bugs, in the latest ones the issues were resolved. This issue with QR is recent at least for me and it first appeared out of nowhere, not right after some driver update. I only install WHQL drivers and I believe I started experiencing this issue with version  32.0.101.8425 and 32.0.101.8362 WHQL . Don't know why but this bundles always seem to have some kind of bug.

To answer your questions

• I've tried all generic Xe and Arc A370M drivers for the last 2 years per Intel's official website
• I've tried all OEM Xe and ARC A370M driver per Windows Update
• This last time I used DDU to install new drivers but I rarely use it, as I believe you might be aware DDU is not a tool you should be using any time you need to update your graphics drivers.

As said before, this is something that started occurring with version  32.0.101.8425 and 32.0.101.8362 WHQL .

Thank you for your effort and let me know if you need anything else.

Best regards,

Francisco

[VonM_Intel]

Hello franciscomnunes,

Thank you for reporting this issue. We will continue to improve our software performance and compatibility throughout this year and beyond. While we can’t accommodate your request at this time, please watch on our website for any possible changes to this situation.

Best regards,

Von M.
Intel Customer Support Technician

[franciscomnunes]

Hi Von,

Thank you for your time.

So there's no other way than to wait next versions correct this issue. Will keep on monotoring.

Thank you

Francisco