Follow-up: Verifying Driver-Level Blocks for ReBAR and HAGS on Intel Arc 140T (Arrow Lake-H)

PCs, Processors & Graphics Graphics & Gaming
,
1

Subject:

Hi Intel team & @Mike_Intel ,

I am opening a new thread to follow up on my previous request regarding performance optimization and driver-level limitations for the Intel Arc 140T GPU (integrated into the Intel Core Ultra 7 255H on a Motorola MotoBook 60 Pro). My previous thread, linked:

Engineering Request: Remove “DISABLE_HWSCH” Flag & Enable ReBAR for Intel Arc 140T (Arrow Lake-H)

was automatically closed due to inactivity, but the underlying performance bottlenecks remain unresolved.

In your last response, you suggested downgrading to the OEM-provided graphics drivers from Motorola. I want to confirm that I thoroughly tested this approach, and unfortunately, downgrading to the OEM version did not help at all - the features remained restricted. I have since updated back to the absolute latest generic Intel graphics driver, version 32.0.101.8826, which is what I am currently running.

To provide deeper technical evidence beyond the DxDiag and SSU logs previously submitted, I have run diagnostics using TechPowerUp’s GPU-Z (v2.6.9.0) utility. The findings clearly illustrate that key architectural features are being restricted at the driver level.

1. WDDM & Hardware-Accelerated GPU Scheduling (HAGS)

As shown in the attached diagnostics, under the WDDM configuration:

  • Hardware Accelerated GPU: Explicitly reads “Off (not supported)”.

  • Despite the Arc 140T being a modern Xe-LPG+ architecture running on a fully updated Windows 11 environment, the driver continues to flag this feature as unsupported rather than simply disabled, preventing any manual override in Windows graphics settings.

2. PCIe Resizable BAR Status

The advanced PCIe diagnostics expose a complex problem regarding Resizable BAR implementation on this platform:

  • Graphics Driver Support: Explicitly reads “No”.

  • Platform Status: The utility confirms that GPU Hardware Support, Above 4G Decode, CSM Disabled, and UEFI Boot are all properly configured and supported (Yes).

  • BIOS Status: Interestingly, Resizable BAR enabled in BIOS reads “No”.

System Configuration:

  • ​Device: Motorola MotoBook 60 Pro (Model 83NY)
  • ​Processor: Intel Core Ultra 7 255H
  • ​GPU: Intel Arc 140T (16GB Shared Memory, 32 GB Total)
  • ​OS: Windows 11 Home 64-bit

My Questions for the Intel Engineering Team:

While I understand that OEM manufacturers customize firmware, the GPU-Z data reveals a two-part lock. Even if the system BIOS layer requires an update from the OEM to toggle ReBAR on, the Intel graphics driver itself is proactively reporting “No” for driver support on this specific silicon.

  1. Is the “No” under Graphics Driver Support a deliberate architectural omission by Intel for the mobile Arc 140T line, or is the driver dynamically disabling support because it detects the OEM BIOS has it locked?

  2. Can the engineering team confirm if a future generic Intel driver release will remove the DISABLE_HWSCH blocklist flag to allow HAGS testing on Arrow Lake-H systems?

lorem ipsum

I am fully prepared to loop in the laptop manufacturer (Motorola) regarding their system BIOS deployment, but I need clear confirmation from Intel regarding what is an intentional driver-level restriction versus a firmware limitation.

Thank you for your time, and I look forward to your engineering team’s insight.

Best regards,

Tanush Satarawala

Screenshot 2026-06-11 000557
Screenshot 2026-06-11 000557710×990 29.7 KB

Screenshot 2026-06-11 000548
Screenshot 2026-06-11 000548710×990 28.6 KB

2

Hi TanushSatarawala,

Thanks for the detailed follow-up and for taking the time to run those GPU-Z diagnostics - that’s really helpful technical evidence that clearly shows what’s happening with the HAGS and Resizable BAR restrictions on your Arc 140T.

I can see you’ve put a lot of effort into documenting this issue, and we definitely want to get to the bottom of it. We will check this with our engineering team for investigation.

To help them dig into this properly, could you please grab us:

What we need:

About your questions:

On the ReBAR driver support showing “No” - You’re right that this could be either an intentional restriction for mobile Arc 140T or the driver reacting to BIOS limitations. It usually comes down to OEM configuration, but we’ll check with our team to get you the accurate information.

On the HAGS blocklist flag - We’ll definitely ask our development team about the roadmap for enabling HAGS on Arrow Lake-H systems and whether that’s something planned for future driver releases.

Once I have your updated logs, I’ll get this over to our engineering team and we’ll give you an update as soon as possible.

Looking forward to hearing back from you!

Best regards

Jonzyl B.

Intel Customer Support Technician

3

Hi @Jonzyl_Intel,

Thank you for the prompt and thorough response. I truly appreciate your willingness to investigate this with the engineering and development teams, as well as your transparency regarding how the driver interacts with OEM BIOS limitations and the HAGS blocklist roadmap.

As requested in your reply above, I have generated fresh system diagnostics to accompany my previous GPU-Z findings. Please find the following updated files attached to this message:

  • Intel_SSU_Log_Arc_140T.txt (Generated via the Intel® System Support Utility)

  • DxDiag_Report_Arc_140T.txt (Updated DirectX Diagnostic tool output)

Both files reflect the current system environment running on the latest generic driver version 32.0.101.8826.

Hopefully, these logs provide the engineering team with the data points they need to pinpoint the restriction layers. Please let me know if they require any further testing, registry dumps, or specific system details from my end.

Looking forward to hearing your updates!

Best regards,

Tanush Satarawala

Intel_SSU_Log_Arc_140T.txt (302.5 KB)

DxDiag_Report_Arc_140T.txt (115.6 KB)

5

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut id nisl vel eros placerat laoreet. Aenean non orci sed justo imperdiet lacinia eu sit amet lorem. Nam nisl dolor, eleifend sit amet libero dignissim, vestibulum cursus velit. Donec sed gravida elit. Nulla sodales iaculis justo, eu tempus neque consectetur in. Sed euismod non magna vel efficitur. Aenean efficitur laoreet elit, ut cursus purus convallis at. Aenean tempor odio tellus, in mollis mi imperdiet sed. Aliquam tincidunt risus in sem cursus, id dictum felis lacinia. Sed accumsan diam ut imperdiet blandit. Curabitur faucibus nulla nec aliquam aliquam.

6

Suspendisse non mollis tortor. Aliquam ultrices quis nibh dignissim pellentesque. Nullam nunc elit, facilisis quis nisl id, accumsan rutrum sem. Fusce porttitor ante id mauris lobortis, quis iaculis ex feugiat. Curabitur ultrices imperdiet libero a aliquet. Fusce et sollicitudin velit, et venenatis lectus. Etiam ullamcorper egestas augue. Donec facilisis purus quis erat molestie hendrerit. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Etiam volutpat turpis quis ipsum ultrices, ut auctor ipsum porttitor. Morbi varius, quam eleifend ullamcorper eleifend, tortor lacus condimentum mauris, quis facilisis diam dui sed dolor. Duis accumsan sapien in ante malesuada, nec scelerisque nunc lobortis.