Windows 10: GSODs while trying to update

When updating to newer build I'm always getting GSODs. It's happening since I updated to 19028 (or I think, coz 19028 was installed just fine).

Now, while updating, when updater gets to around 70-85% it crashes and displays one of the four GSODs.
I'm ordering them from one happening the most often to the rarest:

1. KERNEL_SECURITY_CHECK_FAILURE
2. KERNEL_MODE_HEAP_CORRUPTION
3. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
4. IRQL_GT_ZERO_AT_SYSTEM_SERVICE

After 3 I checked all the drivers, but they are fine.

As I wrote, my Windows version number is 19028. It's WIndows 10 Pro x64.
Device is my 2nd system (Dell E5440). There was no changes before GSODs. After I replaced 2x4 RAM with 2x8, but even moving back to older ones did nothing, and when they were inserted it already was gsoding...
I was trying to update it manually using UUP and automatically (Windows Update). UUP made image is working fine as I use it on my 1st system and one of the tablets...

Any idea?

:)

 

Windows Updated(16299.309).KB4088776 Restart is required to complete.


Hi dalchina. Good news, I followed your suggestion and reinstalled the update and now it appears as "installed correctly" *Biggrin Maybe it was not necessary to run the Windows Update Troubleshooter or maybe if necessary. But using it I do not think it could have worsened something. The installation was very fast, unlike the first time it showed step 1 and step 2 completed.

Thanks for the suggestions and for the time to respond Best regards.


And thanks for the tip of that program, I'll have it on my list.

 

Help! Windows 10 GSOD! CRITICAL_SERVICE_FAILED!

My PC is running slowly. I disabled Superfetch. and my PC Crashes. after that, I got a GSOD NTFS_FILE_SYSTEM. Soon it's repaired.

BUT THIS IS THE REAL PROBLEM. AFTER 10 MINUTES OF USING IT, IT GOT A GSOD CRITICAL_SERVICE_FAILED! AND IT HAPPENS EVERY TIME!

What should I do?

 

Anyway to report GSOD's on this section

Hi there
shows something about kernel security -- This one occurs when trying to start a guest OS when running VMWARE (player or workstation) on the latest skip ahead windows build -- (290) -- there's a number of issues that have caused this defect with other applications too so ms (and vmware) are now aware of it.

The GSOD occurs almost immediately on starting the guest OS and at next boot the log info isn't available.

Photo on phone is a good idea -- never thought of that -- I'm actually a keen photographer (with real cameras) so I'm not particularly OK with mobile phone "snaps" !!!! - but this is a case where it would be OK.

I'll mark the thread as solved as my Q was about how to present GSOD info rather than solving this particular GSOD itself

Thanks for your suggestion though.

Cheers
jimbo