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-10T03:18:51+00:00

    If you select duplicate, are both screens working correctly?

    Even the one that only supports 1366 x 768, or is the resolution set differently on each display?

    Yes both screens work correctly.

    The resolution is the same on both even though the laptop doesn't support 1920 x 1080 by itself. 🤷‍♂️

    But wait! it gets better.

    I found a VGA cable and I'm using 1366 x 768 with Intel driver on both displays and without the bug.

    Now I wonder if my problem has anything to do with the resolution bug, or maybe the resolution bug isn't about resolution after all but something to do with HDMI output.

    Hi Sibro,

    I don't know, something changed today, with Nvidia I cannot even reproduce the original problem with a single screen the way it was failing before with the browser. 😎🤷‍♂️

    I will have to try again with the Intel adapter to see if I can reproduce it or not. Originally it failed with intel but not with Nvidia, maybe when I switch to the other adapter it remembers or crews up some of the settings. 🤷‍♂️

    Edit:

    As I switched to the Intel adapter it failed again.

    Overlapping screens with different sizes. 🤣🤣🤣

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-10T03:22:40+00:00

    Unplugged the VGA cable, using the laptop by itself the bug came back, had to shutdown to recover. 🤷‍♂️

    This is beyond resolution, there's something else going on with this build.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-10T03:44:28+00:00

    Unplugged the VGA cable, using the laptop by itself the bug came back, had to shutdown to recover. 🤷‍♂️

    This is beyond resolution, there's something else going on with this build.

    One last thing, I will try getting the old intel driver 27.20.100.9664 Dated 6/1/2021 that is usually downloaded every time Windows updates to a new build and see what happens with that. 😎

    Edit:

    Same bug with old Intel Graphics Driver which is the default one installed by W.U. 🤐🤷‍♂️

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-01-10T04:15:08+00:00

    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.

    That is very telling that there's more to this story.

    Fun fact: I haven't seen those multiple windows not even once.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-01-10T04:24:31+00:00

    That is very telling that there's more to this story.

    Yes, MS just screwed up bad. 🤣🤣🤣🤣🤐

    As I switched back from Intel to Nvidia display adapter, I could get the same bug again. 🤣🤣🤣🤷‍♂️

    Was this answer helpful?

    0 comments