Windows 10: BSOD 2H22 upgrade

Looking at other recent posts I am having a similar problem. I have tried this three times. The first used a pre-release version of 2H22 which took a very long time to install and then I got the BSOD screens mentioning kernel problems. I went back to the prior version without problem. I tried again with the release version and tried a clean install but got into a mess with having the install end up offering me to load Windows 11 or Windows 10. So I used Acronis to go back to a working version. Last night, when the 2H22 version poped up in Windows Update, I tried the upgrade route. One thing I

:)

 

2H22 fiasco

I tried installing the 2H22 upgrade a month ago from the preview site. Very prolonged install and after kept getting crashes requiring reboots. I finally just unstalled the update and things returned to baseline. As the final version of 2H22 is available I tried to do a clean install but in spite of deleting partitions on the C: drive, installation apprently went to another NVME drive and the end result was blue screens as well as a requirement that I pick either Windows 11 or Window 10. I ended up with two boot drives. With that mess I disconnected the second NVME and SSD and used Acronis to restore the C: drive. Then reconnected the other drives, deleted the partition on the second NVME drive and reformatted. Finally restored files to that drive. I had no problem installing Windows 11 but big problems trying to install the 2H22 version. In retrospect I should have disconnected the other drives before trying the clean install. Certainly will avoid 2H22 for as long as possible. The system has a Ryzen 7 3700X processor with 32 GB RAM. Two Samsung NVME (960, 980) and a Crucial SSD.

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast:

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.