Windows 10 Windows 10 freeze on startup/restart after update to 1703

  • Thread starter Thread starter KimXY
  • Start date Start date
K

KimXY

Hi,


I have a completely new computer with Windows 10 1607 installed from CD, and everything works fine until applying the 1703 Creators Update. After this, systems hangs for 6-8 minutes on booting Windows (about 2 out of 3 times), at the very start of the process (Cyan Windows logo, prior to Login Screen). It doesn't even show the spinning dots yet, so it's at the very first boot sequence. This happens both at normal startup and restart, and disabling "Fast Startup" in Windows doesn't affect the error.


BIOS and drivers are all latest versions. I can't seem to find any hardware issues, and as mentioned, this error does not occur in build 1607, and is reproducible by reinstalling>upgrading Windows.


I've searched online extensively and cannot find examples of the exact same error. I've tried foxes for somewhat related errors, but to no avail.

---------------------

OS Name Microsoft Windows 10 Home
Version 10.0.15063 Build 15063

System Type x64-based PC
System SKU SKU
Processor Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz, 4200 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 0906, 22-03-2017
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume3

Hardware Abstraction Layer Version = "10.0.15063.0"

Installed Physical Memory (RAM) 64,0 GB
Total Physical Memory 63,9 GB
Available Physical Memory 60,7 GB
Total Virtual Memory 73,4 GB
Available Virtual Memory 70,1 GB
Page File Space 9,50 GB
Page File C:\pagefile.sys
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
-----------------


Motherboard is an ASUS PRIME z270-a and the system drive is a Samsung EVO 960 500 Mb with latest manufacturer M.2 driver, and Samsung Magician reports that the drive is healthy.

Continue reading...
 
Back
Top