Hi savoukos,
Welcome to Ten Forums.
Some of the BSOD mini dump files displayed WHEA errors which is almost always a hardware problem.
The event log indicated that Windows failed fast startup.
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
6) Make sure that there is no over clocking while troubleshooting.
Sometimes there are problems in the bios that produce bsod.
The bios in your computer: BIOS Version/Date American Megatrends Inc. 3003, 10/28/2015
7) Please check to see if this is the most up to date version.
8) To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios.
9) So please make sure your files are backed up.
10) Please make a backup image with Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Your Image is Everything
11) And please create a restore point.
How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
12) When testing for WHEA hardware errors we need to systematically check CPU, GPU, memory and drive.
13) Once the bios is reset and there is no overclocking:
Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
14) download and install the Intel Processor Diagnostic Tool
When the test completes please use the Microsoft snipping tool to post an image into the thread.
Download Intel® Processor Diagnostic Tool:
Download Intel® Processor Diagnostic Tool
The Intel® Processor Diagnostic Tool: The Intel® Processor Diagnostic Tool
15) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Please use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
16) Run memtest86+ version 5.01 for at least 8 passes.
This may take hours so plan to run it overnight. (It may take more than 16 hours for 16 GB of RAM)
(If you cannot be without the computer for this duration of time you can run 1 RAM at a time in the same DIMM but this decreases the value of the testing for dual channel ram) So please plan to run the Memtest86+ for a long duration of time so that you have at least 8 passes. Anything less than 8 passes is an invalid test as the incidence of false negatives is too high. Please make sure that you have made > 8 passes and then submit a photo.
Memtest86+ - Advanced Memory Diagnostic Tool
https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
When Memtest86+ has completed 8 or more passes make an image of the results to post into the thread.
MemTest86+ - Test RAM Windows 10 BSOD Tutorials
We're looking for zero errors here.
Even a single error will indicate RAM failure.
Using a camera or a smart phone camera make a photo of the result and post it.
If you have 1 error you can abort the testing for both RAM and test 1 at a time in the same DIMM to determine which RAM is malfunctioning. If both RAM pass in the same DIMM then perform the testing in another DIMM.
17) Run HD Sentinel:
Hard Disk Sentinel - HDD health and temperature monitoring
When it has completed please use the Microsoft snipping to make an image and post into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
18) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
All of these test should be done with the bios reset and no over clocking.
For each of the above tests please record maximum temperatures.
And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
19) turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials
core temp
Code:
BugCheck 101, {30, 0, ffffdf800e035180, 1}Probably caused by : memory_corruption
Code:
WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffd98b2afb7028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
Code:
1: kd> !errrec ffffd98b2afb7028===============================================================================Common Platform Error Record @ ffffd98b2afb7028-------------------------------------------------------------------------------Record Id : 01d30a4693326f3bSeverity : Fatal (1)Length : 928Creator : MicrosoftNotify Type : Machine Check ExceptionTimestamp : 7/31/2017 22:05:22 (UTC)Flags : 0x00000000===============================================================================Section 0 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffffd98b2afb70a8Section @ ffffd98b2afb7180Offset : 344Length : 192Flags : 0x00000001 PrimarySeverity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : Cache errorOperation : GenericFlags : 0x00Level : 0CPU Version : 0x00000000000306c3Processor ID : 0x0000000000000002===============================================================================Section 1 : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor @ ffffd98b2afb70f0Section @ ffffd98b2afb7240Offset : 536Length : 128Flags : 0x00000000Severity : FatalLocal APIC Id : 0x0000000000000002CPU Id : c3 06 03 00 00 08 10 02 - bf fb fa 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00Proc. Info 0 @ ffffd98b2afb7240===============================================================================Section 2 : x86/x64 MCA-------------------------------------------------------------------------------Descriptor @ ffffd98b2afb7138Section @ ffffd98b2afb72c0Offset : 664Length : 264Flags : 0x00000000Severity : FatalError : DCACHEL0_WR_ERR (Proc 1 Bank 1) Status : 0xbf80000000000124 Address : 0x000000012e0e5380 Misc. : 0x0000000000000086
Code:
BugCheck 124, {0, ffffd98b2afb7028, bf800000, 124}Probably caused by : GenuineIntel
Code:
BugCheck 101, {30, 0, ffffbb80df82e180, 1}Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Code:
BugCheck 9C, {0, ffffb60067b4a820, 0, 0}Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+7b )
Code:
BugCheck 9C, {0, fffff80353bbeba0, 0, 0}Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )
Code:
Windows failed fast startup with error status 0xC00000D4.
Code:
Event[3715]: Log Name: System Source: Service Control Manager Date: 2017-06-27T11:51:06.320 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-5LVHCU4 Description: The ALSysIO service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
Code:
Startup Repair failed.