Severe browser lag and cursor stuttering at 165Hz on MS Edge (Disappears at 144Hz / D3D ANGLE backend issue)

Vivek Singh 191 Reputation points
2026-08-09T19:10:09.5666667+00:00

Hi everyone, I have a 165Hz Gaming Monitor. Whenever I used to run my PC at 165Hz, I experienced sudden and severe lag in my web browser, and the mouse cursor would also stutter/freeze. To fix this, I took help from an AI, which suggested going to edge://flags and changing the 'Choose ANGLE graphics backend' setting from Default to either 'OpenGL' or 'D3D9'. So, I set it to D3D9, and after that, the severe browser lag was fixed.

However, a few days ago, after updating MS Edge Stable to the latest version, I checked the 'Choose ANGLE graphics backend' setting again and saw it was set to D3D11WARP, and my browser started lagging again. So, I changed it back to D3D11... the regular browser lag went away, but the severe lag issue returned.

Also, when I run my monitor at 144Hz, this severe lag doesn't happen—it only occurs at 165Hz. Why does this happen, and how can I fix it? Please help.

Microsoft Edge | Speed and responsiveness | Windows 11
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Carl-L 20,460 Reputation points Microsoft External Staff Moderator
    2026-08-19T13:14:12.79+00:00

    Hello Vivek Singh,

    I fully understand if you don't want to go with the registry way. For your information, if you have a backup of the current registry, you can use that the restore normal entries if anything happen.

    Disclaimer: Let’s try performing an in-place install or in-place upgrade which will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up before making large system changes. If you want to back up your data first, please do so. Once you are done backing up, you can follow the steps in the following guides:

    How to run In-place upgrade in Windows 11 - Microsoft Community

    Was this answer helpful?

  2. Carl-L 20,460 Reputation points Microsoft External Staff Moderator
    2026-08-14T13:45:37.8533333+00:00

    Hello Vivek Singh,

    Thank you for your patience.

    In this case, let try to disable the Multiplane Overlay to see if it helps.

    Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.

    • Type "regedit" in the search bar and press Enter.
    • Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm
    • Change the value of OverlayTestMode to 5. If it doesn't exist, create a DWORD (32-bit) with its name.
    • Restart your computer.

    If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

  3. Carl-L 20,460 Reputation points Microsoft External Staff Moderator
    2026-08-12T07:34:40.75+00:00

    Hello Vivek Singh,

    Welcome to Microsoft Q&A forum.

    Before we proceed, may I know if you can still see D3D9 or OpenGL in the options? May I know if the issue persists there if they do? As you described, I suspect a bug or issue between the GPU driver with D3D11 when run in 165hz. I'd also want to know which model of GPU are you using and when did the issue start?

    I'm waiting for your reply.

    Was this answer helpful?

  4. AI answer

    2026-08-09T19:10:32.48+00:00

    Work through these checks in order, and after each one, run Edge for a few minutes at 165Hz to see whether the lag and cursor stutter stop.

    1. Identify the process causing the spike
      • In Edge, press Shift+Esc to open Browser Task Manager.
      • Sort by CPU or Memory.
      • Find the tab, extension, subframe, or utility process that spikes when the issue happens.
      • Select it and choose End process.
      • If system load drops, the problem is tied to that process rather than all of Edge.
    2. Turn off all extensions
      • Open edge://extensions/.
      • Disable every extension.
      • Test Edge again at 165Hz.
      • If the issue stops, re-enable extensions one at a time until the problematic one is identified.
    3. Verify hardware acceleration status
      • Open edge://gpu.
      • Check Graphics Feature Status.
      • Confirm hardware acceleration is being used.
      • If items show software-only rendering:
        • Update the GPU driver.
        • Open edge://settings/system and make sure Use graphics acceleration when available is turned on.
    4. Turn off background activity
      • Open edge://settings/system.
      • Turn off Continue running background extensions and apps when Microsoft Edge is closed.
      • This helps if Edge keeps consuming CPU after windows are closed.
    5. Turn on sleeping tabs
      • Open edge://settings/system/managePerformance.
      • Turn on Save resources with sleeping tabs.
      • Set an inactivity timeout.
      • Add sites to the exception list if they should never sleep.
    6. Reset Edge settings
      • Open edge://settings/reset.
      • Select Restore settings to their default values.
      • This preserves bookmarks, history, and saved passwords.
      • It resets pinned tabs, startup page, search engine, and extensions.
    7. Collect diagnostics if the issue continues
      • Open edge://settings/help and note the full Edge version.
      • In Browser Task Manager, take one screenshot sorted by CPU and another sorted by Memory.
      • Open edge://discards and save the output.

    The available guidance supports checking whether the issue is caused by a busy Edge process, an extension, background activity, or software rendering. It also supports verifying that hardware acceleration is active and resetting Edge settings if needed. The provided material does not document a specific cause for 165Hz-only behavior or a supported fix based on changing the ANGLE backend.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.