Browsers crashing on 25272 to 25300 - Display Resolution Bug - Temporarily Solved

Anonymous
2023-01-05T21:10:46+00:00

Chrome, Edge & Firefox, all crash and the OS becomes unresponsive, I can't recover it unless I shutdown.

Anyone else seeing this?

Update:

A temporary solution is to use recommended display resolution or change to MS basic display driver.

Known issues

[NEW] We’re investigating reports that some Insiders are experiencing freezes when using the browser and certain other apps after the previous Dev Channel flight.

Update:

I added build 25290 to the tiltle because even though the blog calls it fixed, some users are still experiencing this bug.

Fixes[General]

  • Fixed an issue causing some Insiders to experience freezes when using the browser and certain other apps in recent Dev Channel builds.
Windows Insider program | Windows Insider preview | Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

135 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-13T03:03:29+00:00

    Negative results with the VM.

    Everything works normally at any display resolution. 🤷‍♂️

    No sign of the bug after updating this VM to 25276

    It'd be nice to find out exactly why is the VM immune to this bug.

    Completely different display driver used for VM.

    No problem also when I use a Wi-Fi connected display on a real machine. 🤷‍♂️

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-13T03:19:40+00:00

    Completely different display driver used for VM.

    No problem also when I use a Wi-Fi connected display on a real machine. 🤷‍♂️

    I thought that we've already established that the bug isn't driver specific as long as the default recommended resolution is used.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-13T03:27:25+00:00

    Completely different display driver used for VM.

    No problem also when I use a Wi-Fi connected display on a real machine. 🤷‍♂️

    I thought that we've already established that the bug isn't driver specific as long as the default recommended resolution is used.

    Not all the drivers fail, but I had problems both with Intel and Nvidia.

    I cannot fail when I use a Wi-Fi connected display.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-01-13T03:35:33+00:00

    Not all the drivers fail, but I had problems both with Intel and Nvidia.

    I cannot fail when I use a Wi-Fi connected display.

    I must've misunderstood your previous posts then.

    I thought that your failures with different drivers were induced by changing the resolution.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-01-13T03:45:23+00:00

    Not all the drivers fail, but I had problems both with Intel and Nvidia.

    I cannot fail when I use a Wi-Fi connected display.

    I must've misunderstood your previous posts then.

    I thought that your failures with different drivers were induced by changing the resolution.

    Back on page 4, I replied to you:

    Hi Sibro,

    This is interesting, I tried yet another case using a second screen as wireless display in duplicate mode, and in that case, they both work fine even if I use a resolution different from the recommended one. 🤣

    I even tried 1366 x 768, and in that case, both screens worked correctly without the bug we have seen with a single screen. 🤣🤣🤣🤷‍♂️

    And on page 5:

    B.T.W.

    With the old MSI GT70 Laptop (Non-Compliant) I don't have any issue with any resolution that I select. 🤣🤣🤣🤷‍♂️

    Was this answer helpful?

    0 comments