Jump to content











Photo
- - - - -

BSOD Crashes Windows 10 since May Update

bsod crash update windows 10

  • Please log in to reply
2 replies to this topic

#1 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 07 June 2020 - 05:49 AM

After a fresh install of Windows 10x64 version 2004 I experienced in a few days 3 times a BSOD System Crash  :ph34r:
 
The May Update can make Windows 10 instable as described in
 
 
 
I decided to boot with Win10XPE and use WinNTSetup to Attach and Format the System VHD
and to Apply my April Capture of Windows 10x64 version 1909 to the mounted VHD. 
After reboot Windows Update can be postponed for 35 days using Advanced Settings.
In my case System and User Data are well separated so that I can easily change the System.
 
Attached File  Win10_Install.pdf   1.09MB   664 downloads

 

Mayday ... Mayday comes from the French m'aider ('help me')  ;)


#2 quarky42

quarky42

    Member

  • Members
  • 38 posts
  •  
    United States

Posted 11 June 2020 - 05:12 PM

I have, what I believe to be, the same problem with the same update on my HP Omen Obelisk tower.  (I mention the model because this appears to affect this particular model of computer, but I am not assuming it is limited to this.)

 

For me, I have reinstalled Windows 10, applied all updates, and went back to having the same problem.  For 2 or 3 days after the update the computer is usable, but it eventually starts to crash and then it starts to crash with a KMODE EXCEPTION BSOD immediately upon logging into my profile.  Once that starts, it is stuck in that loop.

 

It appears that disabling Windows Defender, uninstalling the update in question, and disabling Windows Update, as well, appears to solve the problem.   Since doing that, my computer has been up and running non-stop for 2 weeks.

 

I found the info on the HP Forum here.



#3 quarky42

quarky42

    Member

  • Members
  • 38 posts
  •  
    United States

Posted 11 June 2020 - 05:21 PM

Having not read the rest of that thread I linked to for the past 2 weeks (or so), I just skimmed through the last few pages of it, it it appears that disabling Windows Defender seems to take care of it and has been continuing to work well for others.  I hope that this info helps.

 

To date, I have had major system corrupting problems over the years with Symantic / Norton, McAfee, AVG Free Edition, AdAware, and now Windows Defender.  It seems like the cat and mouse game that is antivirus / antimalware detection is resulting in the cure being just as damaging as the disease at times.   (I'm not using these products at  the same time, just saying that over the years I have used each of these at some point and at some point each one has damaged the Windows installation so severely that I had to stop using it.   AVG, several times, has released updates to their antivirus client that would prevent the system from booting, had to be manually removed at the command prompt or via a secondary computer editing the drive, and then reinstalled.   I got to the point where I won't use any of those products any more because they corrupt the system to fully.   Now Windows Defender is on the same path, and you'd think if anyone could prevent this sort of scenario it should have been Microsoft themselves.   :(





Also tagged with one or more of these keywords: bsod, crash, update, windows 10

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users