Windows 10 WHEA-logger event 18 black screen reboots

  • Thread starter Thread starter Jay323243
  • Start date Start date
J

Jay323243

A while back I posted about this issue and I wasn't quite able to find a solution myself but I think I've narrowed it down to a possible driver problem, using the verifier it seems to be a driver related problem and I ran the verifier on all my drivers except the Windows drivers. It always comes back to ntsokrnl.exe using WhoCrashed to look at the LiveKernelReports, this error doesn't seem to be cause by my .dmp folder so they go there but I've shared with GoogleDrive. The problem first began back in mid-late September according to EventViewer and from there it comes and goes, sometimes not happening for a few days to a week or two.





OS Name Microsoft Windows 10 Pro

Version 10.0.19042 Build 19042

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name DESKTOP-QUU67B6

System Manufacturer Gigabyte Technology Co., Ltd.

System Model B450M DS3H

System Type x64-based PC

System SKU Default string

Processor AMD Ryzen 5 3600 6-Core Processor, 3593 Mhz, 6 Core(s), 12 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. F60c, 10/29/2020

SMBIOS Version 3.3

Embedded Controller Version 255.255

BIOS Mode UEFI

BaseBoard Manufacturer Gigabyte Technology Co., Ltd.

BaseBoard Product B450M DS3H-CF

BaseBoard Version x.x

Platform Role Desktop

Secure Boot State Off

PCR7 Configuration Binding Not Possible

Windows Directory C:\WINDOWS

System Directory C:\WINDOWS\system32

Boot Device \Device\HarddiskVolume4

Locale United States

Hardware Abstraction Layer Version = "10.0.19041.488"

User Name DESKTOP-QUU67B6\User1

Time Zone Eastern Standard Time

Installed Physical Memory (RAM) 16.0 GB

Total Physical Memory 15.9 GB

Available Physical Memory 10.8 GB

Total Virtual Memory 20.7 GB

Available Virtual Memory 12.9 GB

Page File Space 4.75 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 No

Hyper-V - Data Execution Protection Yes












Continue reading...
 
Back
Top