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

Anonymous

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.

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

Anonymous

2023-01-10T03:09:36+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 or something else.
Was this answer helpful?

0 comments No comments
Anonymous

2023-01-10T02:39:20+00:00

Great, now we just have to wait for a MS fix of the resolution bug. 😎

There's a new twist.

If I close the lid or select "Show only on 2" the bug comes back even on 1920 x 1080.

I have to keep the lid open or select "Duplicate these displays". 🤷‍♂️

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. 🤣🤣🤣🤷‍♂️
Was this answer helpful?

0 comments No comments
Anonymous

2023-01-10T02:15:56+00:00

Great, now we just have to wait for a MS fix of the resolution bug. 😎

There's a new twist.

If I close the lid or select "Show only on 2" the bug comes back even on 1920 x 1080.

I have to keep the lid open or select "Duplicate these displays". 🤷‍♂️

Hi Sibro,

Yet another variation of the bug. 😎

One thing is not clear to me.

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?

I know that with multiple screen the resolution can be different on each extended display, but on duplicate it is supposed to be the same.
Was this answer helpful?

0 comments No comments
Anonymous

2023-01-10T01:47:09+00:00

Great, now we just have to wait for a MS fix of the resolution bug. 😎

There's a new twist.

If I close the lid or select "Show only on 2" the bug comes back even on 1920 x 1080.

I have to keep the lid open or select "Duplicate these displays". 🤷‍♂️
Was this answer helpful?

0 comments No comments
Anonymous

2023-01-09T22:03:14+00:00

Hi fg,

I borrowed a monitor, using 1920 x 1080 via HDMI and everything is working normally.

The built-in HD Graphics 520 doesn't output via HDMI using the MS driver. 🤷‍♂️

Great, now we just have to wait for a MS fix of the resolution bug. 😎
Was this answer helpful?

0 comments No comments