Question Constant Blue Screens

Sep 7, 2019
3
0
10
0
I built a PC and now Win 10 blue screens randomly. There is nothing that I do consistently to cause the system to fail. When I go into event viewer I have critical error of AppModal-Runtime event id 79 as well as various errors.

I am not sure how to fix it. I could use some help. Please let me know what else you need. Some PC specs are below.

OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer To Be Filled By O.E.M.
System Model To Be Filled By O.E.M.
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor AMD Ryzen 5 2600X Six-Core Processor, 3600 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P1.70, 12/17/2018
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASRock
BaseBoard Product B450M-HDV
BaseBoard Version
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.267"
User Name DESKTOP-TFVJGTI\Kaich
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 11.6 GB
Total Virtual Memory 18.3 GB
Available Virtual Memory 11.2 GB
Page File Space 2.38 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
 

Colif

Win 10 Master
Moderator
What PSU do you have?
Its not that simple, Kernel event 41 (63) is a reaction, not a cause.
When windows starts, it runs a report. If it finds the previous shutdown wasn't normal it creates Event 41.
Windows doesn't know why it restarted

Event viewer will always have errors, even in perfectly working systems. 99% of them can be ignored.

So are you getting BSOD or just restarts?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 
Reactions: PC Tailor

ASK THE COMMUNITY

Latest posts