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.
Browsers crashing on 25272 to 25300 - Display Resolution Bug - Temporarily Solved
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
135 answers
Sort by: Newest
-
Anonymous
2023-01-13T02:56:43+00:00 -
Anonymous
2023-01-12T19:31:47+00:00 This issue persist on build 25276
Opening any browser or any random app crashes the system with no way to recover.
Switching to MS basic display driver may or may not fix it.
Yes, still the same behavior as 25272.
-
Anonymous
2023-01-12T19:24:27+00:00 This issue persist on build 25276
Opening any browser or a random app crashes the system with no way to recover.
Using the recommended display resolution or switching to MS basic display driver may or may not fix it.
Kernel-Power errors are the two forced shutdowns I had to make in order to exit the OS
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2023-01-11T23:08:09+00:00 I have the exact same issue on a Surface Pro 4, know it is not officially supported, but this is the first real issue I have had on the Pro 4 with Windows 11. Remove the graphic drive as suggested in these posts and it worked fine, well it did until windows updated it back to the Intel (R) Iris(R) Graphics 540, then the problem came back...
Don't have this issue on my Surface Pro 9.