S
SysopChris
I was about 3 releases behind and trying to solve latency issues so I updated to:
BIOS Version/Date American Megatrends Inc. 3802, 3/15/2018
Now, I no longer see anything but a blank screen until I get to the boot drive selection screen, then after 20 mins. I get to the logon prompt.
Has anyone else experienced this? I wasn't even sure what category to file this under.
I have tried all the regular keys to enter the BIOS with no input accepted and used a cabled USB keyboard.
I have exported my System Information here as a txt on OneDrive.
System_Information_10-19-2020.txt
System Information report written at: 11/20/20 20:34:51
System Name: ASUSZ170
[System Summary]
Item Value
OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ASUSZ170
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3504 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 3802, 3/15/2018
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product Z170-A
BaseBoard Version Rev 1.xx
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume6
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.488"
User Name ASUSZ170\sysop
Time Zone Eastern Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 8.51 GB
Total Virtual Memory 26.4 GB
Available Virtual Memory 13.4 GB
Page File Space 10.5 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, 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 - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Continue reading...
BIOS Version/Date American Megatrends Inc. 3802, 3/15/2018
Now, I no longer see anything but a blank screen until I get to the boot drive selection screen, then after 20 mins. I get to the logon prompt.
Has anyone else experienced this? I wasn't even sure what category to file this under.
I have tried all the regular keys to enter the BIOS with no input accepted and used a cabled USB keyboard.
I have exported my System Information here as a txt on OneDrive.
System_Information_10-19-2020.txt
System Information report written at: 11/20/20 20:34:51
System Name: ASUSZ170
[System Summary]
Item Value
OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ASUSZ170
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3504 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 3802, 3/15/2018
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product Z170-A
BaseBoard Version Rev 1.xx
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume6
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.488"
User Name ASUSZ170\sysop
Time Zone Eastern Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 8.51 GB
Total Virtual Memory 26.4 GB
Available Virtual Memory 13.4 GB
Page File Space 10.5 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, 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 - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Continue reading...