Windows 10: Getting BSOD repeatedly after 20H2 update

I very frequently get BSOD ever since the 20H2 update


error: VIDEO_MEMORY_MANAGEMENT_INTERNAL


I have read about this from others' questions on the forum and tried the solutions provided. I have clean installed my graphics drivers after completely removing them. After re installing, the problem disappeared for a few weeks. But now it seems to have returned.



Here's the link to zipped minidump:

BSOD_Minidump

From what I have observed, I usually get this BSOD when watching Youtube videos on Edgechromium.


The BSOD doesn't even seem to complete. It goes 100% and stays stuck like that for 20 mins. I always have to force shutdown.


Don't know if this is useful but, I have set all apps to run on integrated graphics by default on Nvidia control panel. Only games and a few CAD applications can use the Nvidia GPU.

:)

 

20H2 Update BSOD Problem -While Trying the Updating

Hello,

I have a BSOD Problem. While I trying to update my Windows 10 from 1909 to 20H2 I always get BSOD at updating screen.

Already done with cmd command restore health and sfc scan but nothing happened

Here is a link of my minidump and .nfo files. bsod

Thank you all

 

Update 20h2

Hi Wicki,

I am Sumit, an Independent Advisor and a 3 year Windows Insider MVP here to help.

20H2 should not be installed right-away on your device - MS said the rollout is only to a fraction of users and would be labeled as an optional update initially. Are you enrolled in WIP?

You may uninstall 20H2 using the steps below:

https://www.yourwindowsguide.com/2020/10/uninst...

Content on the above blog is written by a Microsoft MVP so it is safe. However, do watch out for the ads.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.