Green Screens of Death build 176

%3CLINGO-SUB%20id%3D%22lingo-sub-2721760%22%20slang%3D%22en-US%22%3EGreen%20Screens%20of%20Death%20build%20176%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2721760%22%20slang%3D%22en-US%22%3E%3CP%3EWin%2011%20build%20176%2C%20this%20is%20the%20jankiest%20build%20I've%20seen%20since%20Vista.%20Watching%20a%20youtube%20video%20crashes%20my%20computer%2C%20it%20crashes%20when%20in%20sleep%20mode%2C%20crashes%20when%20trying%20to%20play%20games%20like%20FO4%20or%20Minecraft.%20Green%20screen%20of%20death%20over%20and%20over%20again%20and%20I%20can't%20even%20screen%20record%20to%20show%20this%20happening.%20I'm%20on%20a%20brand%20new%20computer%20top%20of%20the%20line%20gaming%20setup%20(Ryzen%205%205600x%2C%20Radeon%20RX%206800%20XT%2032%20gb%20of%20DDR4%20Ram%2C%20NVME%204.0%20boot%20drive).%26nbsp%3B%20All%20drivers%20are%20up%20to%20date.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EHow%20do%20I%20fix%20this%20problem%3F%20No%20dump%20files%20are%20created%20for%20these%20crashes.%20Especially%20when%20they%20happen%20three%2C%20four%2C%20five%20times%20in%20a%20row%20like%20what%20happened%20to%20me%20this%20morning%20(9%2F5%2F21).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2721760%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBuild%20176%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Egreen%20screen%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%2011%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%2011%20Bugs%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2721813%22%20slang%3D%22en-US%22%3ERe%3A%20Green%20Screens%20of%20Death%20build%20176%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2721813%22%20slang%3D%22en-US%22%3ERevert%20back%20to%2022000.168%20if%20you%20can.%20Here%20is%20how%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fwindows%2Frecovery-options-in-windows-31ce2444-7de3-818c-d626-e3b5a3024da5%23bkmk_remove_installed_windows_update%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fwindows%2Frecovery-options-in-windows-31ce2444-7de3-818c-d626-e3b5a3024da5%23bkmk_remove_installed_windows_update%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20can't%20do%20that%20try%20downloading%20and%20installing%20the%2022000.132%20iso%20from%20Microsofts%20ISO%20page%2C%20and%20turning%20off%20Windows%20Update%20into%20the%20next%20Beta%20Channel%20build%20is%20released.%20Here%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2Fwindowsinsiderpreviewiso%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2Fwindowsinsiderpreviewiso%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20anything%20else%20just%20wait%20into%20the%20next%20Beta%20Channel%20build.%20Keep%20in%20mind%20Insider%20Program%20builds%20will%20have%20bugs%2C%20glitches%2C%20unstable%20builds%20at%20times%20which%20Microsoft%20is%20clear%20about%3A%20Info%3A%20%3CA%20href%3D%22https%3A%2F%2Finsider.windows.com%2Fen-us%2Funderstand-flighting%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Finsider.windows.com%2Fen-us%2Funderstand-flighting%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2721944%22%20slang%3D%22en-US%22%3ERe%3A%20Green%20Screens%20of%20Death%20build%20176%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2721944%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F373791%22%20target%3D%22_blank%22%3E%40Anthony%3C%2FA%3E%26nbsp%3B%20I%20understand%20they'll%20have%20bugs%2C%20but%20it's%20one%20thing%20to%20have%20a%20few%20bugs%2C%20a%20feature%20that%20doesn't%20work%2C%20and%20another%20where%20it's%20so%20unstable%20that%20something%20as%20simple%20as%20playing%20a%20video%20on%20youtube%20or%20opening%20a%20new%20tab%20causes%20a%20crash.%20Such%20crashes%20typically%20indicate%20incorrect%20allocation%20of%20RAM%2C%20or%20incorrect%20addressing%20of%20system%20resources.%20I%20can%20try%20to%20revert%20back%20to%20an%20earlier%20build%2C%20but%20if%20the%20underlying%20issue%20isn't%20addressed%20and%20persists%20with%20future%20builds%20then%20that's%20a%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Win 11 build 176, this is the jankiest build I've seen since Vista. Watching a youtube video crashes my computer, it crashes when in sleep mode, crashes when trying to play games like FO4 or Minecraft. Green screen of death over and over again and I can't even screen record to show this happening. I'm on a brand new computer top of the line gaming setup (Ryzen 5 5600x, Radeon RX 6800 XT 32 gb of DDR4 Ram, NVME 4.0 boot drive).  All drivers are up to date. 

How do I fix this problem? No dump files are created for these crashes. Especially when they happen three, four, five times in a row like what happened to me this morning (9/5/21). 

4 Replies

Revert back to 22000.168 if you can. Here is how (click Windows 10 tab for now which has the info): https://support.microsoft.com/en-us/windows/recovery-options-in-windows-31ce2444-7de3-818c-d626-e3b5...

If you can't do that try downloading and installing the 22000.132 iso from Microsoft's ISO page, and turning off Windows Update into the next Beta Channel build is released. Here: https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso

If anything else just wait into the next Beta Channel build. Keep in mind Insider Program builds will have bugs, glitches, unstable builds at times which Microsoft is clear about: Info: https://insider.windows.com/en-us/understand-flighting

@Anthony  I understand they'll have bugs, but it's one thing to have a few bugs, a feature that doesn't work, and another where it's so unstable that something as simple as playing a video on youtube or opening a new tab causes a crash. Such crashes typically indicate incorrect allocation of RAM, or incorrect addressing of system resources. I can try to revert back to an earlier build, but if the underlying issue isn't addressed and persists with future builds then that's a problem.

I'll probably be resolved in the next build or upcoming future builds. It's really what the Insider Program is all about. Identifying these bug issues in Dev and Beta builds then reporting them so that these issue dont make their way into stable builds. Same with Edge Canary/Dev. Don't forget to report your founding bugs on Feeback Hub. Feedback Hub is located in Start Menu under All Apps.
I do report them, the problem is I can't provide any meaningful input as to the exact issue, ask I can't record it, trying to tends to cause the crash as well and the recording is corrupted (screen recording), and it doesn't produce a dump file with any meaningful info as to the cause. Saying it will "probably be fixed" is a problem for me, because it's not a guarantee. Again, it's one thing for an app to be bugged or some feature to be bugged, it's another thing entirely when seemingly a core aspect of the OS is bugged to the point that it's not functional.