Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Blank context menu with Hardware Acceleration

  • 2 replies
  • 2 have this problem
  • 2 views
  • Last reply by FredMcD

more options

I have a severely irritating problem: After reinstalling Windows 10 the right click menu in Firefox is blank when hardware acceleration is enabled. It still functions, and you can click on invisible menu items, you just can't see anything.

This only started happening after reinstalling everything on a new hard drive, I've never had this problem before in 10+ years of using Firefox. Disabling hardware acceleration is not really a "fix", it just results in a crappy browsing experience, with rough scrolling and screen tearing.

Both Firefox and graphics drivers are fully up to date, I've even tried multiple older versions of both. Tried Firefox without addons and it still occurs.

I need to know how to resolve this without sacrificing Hardware Acceleration.

I have a severely irritating problem: After reinstalling Windows 10 the right click menu in Firefox is blank when hardware acceleration is enabled. It still functions, and you can click on invisible menu items, you just can't see anything. This only started happening after reinstalling everything on a new hard drive, I've never had this problem before in 10+ years of using Firefox. Disabling hardware acceleration is not really a "fix", it just results in a crappy browsing experience, with rough scrolling and screen tearing. Both Firefox and graphics drivers are fully up to date, I've even tried multiple older versions of both. Tried Firefox without addons and it still occurs. I need to know how to resolve this without sacrificing Hardware Acceleration.

Chosen solution

Never mind, I've found the cause... somehow this was being caused by the MSI Gaming App.

Read this answer in context 👍 0

All Replies (2)

more options

Chosen Solution

Never mind, I've found the cause... somehow this was being caused by the MSI Gaming App.

more options

That was very good work. Well Done.