Mark Minasi's Tech Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 74
Reply with quote  #1 
Our network consists of 10 Windows 10 x64 clients.  All the Microsoft updates have been installed.  In the last two weeks six of the clients have blue screened on startup "Windows was unable to start" message, after which the OS launches automatic repair which doesn't repair anything.  I go to the command prompt window, run chkdak /r /x which takes anywhere from 1 - 2 hours and then sfc /scannow.  (Procedures are recommendations from Microsoft).  After that I boot from a Comodo Recovery CD and do a scan for malware which turns up no malware.  No obvious problems are uncovered so I wind up having to restore from a backup and then having to use powershell to update the machines credentials since it will not allow me to log onto the client (restarting after the restore requires the network cable to be unplugged - expired credentials).  That would be well and good if it was a final fix but... today, two of the machines I just "fixed" are experiencing the same issue.

All workstations are in UEFI mode and are machines that I installed the OS from scratch over a year ago.  All workstations ran without any problems up until one of the last updates.  Any ideas where to look, what to correct?
0
donoli

Senior Member
Registered:
Posts: 598
Reply with quote  #2 
Did you happen to make a note of the stop message? Most people don't bother to read what it said much less copy it. Other than that, reset the BIOS/EFI to default settings.
0
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 74
Reply with quote  #3 
No message was displayed other than the "unable to start" and then presenting the different options for troubleshooting.  I do not believe it to be a driver problem seeings how the atypical blue screen message with a lengthy description accompanied by a hexadecimal address is not present.  After all the client nightly backups have been performed, I have the server issue a shutdown command to the clients.  I have been doing this now for a couple years and am beginning to think that the OS is not closing files that reside in the UEFI stack and this is causing the corruption.  But yes, today I turned off UEFI in the CMOS settings for the client that crashed today and am setting them all to MBR when and if the case presents itself again.
0
Pieter

Avatar / Picture

Senior Member
Registered:
Posts: 247
Reply with quote  #4 
There was something to do about the Meltdown and Spectre problem/patches with antivirus software, resulting in BSOD.

I don't know the details, but you could start here : https://support.microsoft.com/en-us/help/4072699/january-3-2018-windows-security-updates-and-antivirus-software

__________________
Pieter Demeulemeester
0
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 74
Reply with quote  #5 
Quote:
There was something to do about the Meltdown and Spectre problem/patches with antivirus software, resulting in BSOD.


I checked this and several other posts but there doesn't seem to be any explanation for the problem except that the UEFI boot loader seems to becoming corrupted.  I followed the procedures for using diskpart but each time I reached the command line bootrec /fixboot, I would get a access denied message and wasn't able to proceed beyond that and that was even after booting from the Windows 10 installation disk.  I wound up each time setting the machines back to BIOS boot method, reinstalling the OS and programs and then a restore of all the data files.  Microsoft hasn't had an awful lot to say about it except they are looking into it.
0
Mafervus

Grumpy Old Men
Registered:
Posts: 32
Reply with quote  #6 
Hate to say it, but i would take another look at hardware/drivers.  I'd look to see if there were any differences between the machines with and without issues, assuming that they were all purchased around the same time from the same manufacturer. 
__________________
The problem with troubleshooting is that trouble shoots back. ~Author Unknown
0
Jon_AK

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 74
Reply with quote  #7 
Quote:
Hate to say it, but i would take another look at hardware/drivers.  I'd look to see if there were
any differences between the machines with and without issues, assuming that they were all purchased around the same time from the same manufacturer.


Hi Mafervus, I did go back and check for hardware / driver issues and even tried a couple different utilities but nothing stood out as causing a problem.  I have been working with Microsoft on this for a couple weeks and everything is trial and error at this point.  After two of the client computers failed twice in a row, I removed UEFI support and set them both to MBR mode and I haven't had a problem in 2 weeks with them.  Still projecting on it though.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.