Updates crash computer

anaron · 13 Nov 2021

Laptop requests to restart computer to complete update KB5007186. Computer restarts and at around 30% I get a bsod “System thread exception not handled”. Same on the 2^nd reboot. Same on the 3^rd reboot, hit F8, 5 to start in safe mode receiving message “We couldn’t complete the update. Undoing changes to your computer" then restarts again with the same bsod. 2^nd reboot same bsod. 3^rd reboot F8>5. Laptop now boots to safe mode but has a message on the desk top “Keep USB drive plugged in only remove it after your pc shuts down completely. Otherwise, your Windows To Go workspace might crash and you could lose data.” I have never used WTG and there are no usb drives plugged in. Cannot do a direct boot to the operating system but must go thru the same above procedure very time just to access in safe mode. The only way I can do a normal boot or reboot is to restore any of my last 3 operating system backups.
As I previously posted Fyi kb5006738, it also did this with the optional update KB 5006738 that I attempted 10/30/21 after doing my last backup. At the time, I thought the update was the problem but now I think it’s an issue with my laptop as it seems to be any Windows 10 update after my 10/30/21 backup which works perfectly. Not sure what to look for as nothing has been changed since the 10/30/21 backup.

Win10 Pro version 20H2 build 19042.1288

dalchina · 13 Nov 2021

Hi, sounds like back to basics for starters.

Please post a screenshot of your partitions using a 3rd party partition manager e.g, Minitool Partition Wizard.

Check your disks- get a copy of Hard Disk Sentinel (excellent functional trial, valid for SSDs). Green is good. Check tab for each installed disk.

If ok, run
chkdsk c: /scan
from an admin command prompt.
Advise if that passes. (Don't post the whole thing).

If ok similarly run
SFC /SCANNOW
Advise if that passes. (Don't post the whole thing).

If all ok, run a RAM check. (Tutorial available).

I'm looking at your specs, but you say this is a laptop. What is the make, model, type of disk and approximate age?
Are you running any particular security software or unusual 3rd party programs?
Have you ever had it boot anything other than a single Windows installation?

Thanks.

f23948 · 13 Nov 2021

Do you get boot loop? Do you have extra spare computer and extra flash drive larger than 8 GB?

then

BSOD - Posting Instructions

anaron · 14 Nov 2021

dalchina, here is what I have so far: chkdsk c: /scan = No Problems
SFC /SCANNOW = No integrity violations
Memtest not looking good - 4 passes 1881 errors 14 hrs and still going
Laptop info:
4/2013 Puget M750i 17” Notebook
2 Samsung 840 Pr0 256gb ssds
Geforce GTX 670mx 3gb Video Card
2 ea. Kingston DDR3-1600 8gb Ram
Intel i7 Mobile ProcessorOriginally Win7 then was upgraded to Win10 Pro
Only booted single windows installs
Windows Defender only security software
All 3^rd party programs are ones I have used for years on all my computers with no issues.

dalchina · 14 Nov 2021

Thanks for working thru that.

Hmm... the RAM...??? It is an older laptop too... (2013) (but so's this 2nd hand ex-business one... 9s boot to lock screen, not complaining

)

f23948 · 14 Nov 2021

It's time to replace new RAM memory

anaron · 15 Nov 2021

f23948, got to agree as Memtest is now on pass 10 with 4608 errors. Curious to see what the final report will be!

Just got a response from Puget. They also agree the ram is bad. They do however feel that the Windows 10 recent update issue is due to the non existence of Microsoft verified Windows 10 drivers as the latest drivers for this computer is Windows 8.

Thanks everybody for your response. Looks as if age has not only got me, it is getting my computers too!

Ron

anaron · 19 Nov 2021

Kingston rma'd the ram and await the new replacements
Puget was correct in their thought that some of the drivers were not Microsoft verified for Windows 10 there fore Windows update would not complete the update. Downloaded a 3rd party driver program which updated over 14 drivers. Reboot was perfect with no issues. Kind of makes me wonder why there were driver issues when Window Updates supposedly was updating the drivers!