Please note the importance/priority in fixing:
1) the bios
2) backing up your files (pending the evaluation of the drive)
Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) 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
4) Make sure that there is no over clocking while troubleshooting.
5) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date American Megatrends Inc. V22.4, 12/21/2015
6) Please check to see if this is the most up to date version.
7) To ensure that there are no improper bios settings please reset the bios.
8) 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 brand new 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.
Some testing was already done but there may have been overclocking and there were no images posted in the thread.
Once the bios is reset and there is no overclocking:
13) 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) 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
15) Record maximum temperatures and duration of testing.
16) Please use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
17) Run memtest86+ version 5.01 for at least 8 passes.
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a pass when there is malfunctioning RAM.
There is 16 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
Again the more passes the better.
If both RAM pass when tested 1 at a time after failing when tested together test the next DIMM with 1 RAM module for 8 or more passes. This will help to differentiate malfunctioning RAM from malfunctioning DIMM /Motherboard.
Memtest86+ - Advanced Memory Diagnostic Tool
Microsoft Community
18) When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image of the results to post into the thread.
MemTest86+ - Test RAM Windows 10 BSOD Tutorials
MemTest86+ needs to be run for at least 8 complete passes for conclusive results.
19) Run HD Sentinel:
Hard Disk Sentinel - HDD health and temperature monitoring
When it has completed please use the Microsoft snipping to make images and post them into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
20) 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
21) All of these test should be done with the bios reset and no over clocking.
22) For each of the above tests please record maximum temperatures.
24) 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
23) Please update the information on the computer specifications:
Ten Forums System Specificiations (Specs)
Please fill in your system specs
Please follow this tutorial and download the tool.
System Info - See Your System Specs - Windows 7 Help Forums
The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling, case, and other used stuff like mouse, keyboard, joystick, xbox, headphone, printer, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
24) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
This may take many hours to run so plan to run it overnight.
25) Post the chkdsk results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Code:
Event[31469]: Log Name: System Source: Microsoft-Windows-HAL Date: 2184-07-15T17:24:22.976 Event ID: 12 Task: N/A Level: Error Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: Adam-PC Description: The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system.
Code:
Event[24891]: Log Name: System Source: Microsoft-Windows-Eventlog Date: 2017-05-29T20:10:27.831 Event ID: 106 Task: N/A Level: Error Opcode: Info Keyword: Service availability User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Adam-PC Description: Corruption was detected in the log for the Microsoft-Windows-PowerShell/Operational channel and some data was erased.
Code:
Event[12916]: Log Name: System Source: Ntfs Date: 2017-02-16T18:46:39.774 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Adam-PC Description: A corruption was discovered in the file system structure on volume ??.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x3300000003adcc. The name of the file is "<unable to determine file name>".
Code:
Event[13378]: Log Name: System Source: Microsoft-Windows-FilterManager Date: 2017-02-22T12:39:00.062 Event ID: 4 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Adam-PC Description: File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T16:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy5'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.
Code:
Event[5213]: Log Name: System Source: disk Date: 2016-12-02T20:38:23.244 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Adam-PC Description: The device, \Device\Harddisk1\DR1, has a bad block.
Code:
Event[32773]: Log Name: System Source: Microsoft-Windows-FilterManager Date: 2017-07-19T14:11:03.171 Event ID: 4 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Adam-PC Description: File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T17:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy1'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.
Code:
8/28/2017 7:17 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffe1012fd38000
P3: 0
P4: fffff80cbc1ff82a
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\082817-26515-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
Analysis symbol:
Rechecking for solution: 1
Report Id: 78540759-972c-4077-bbe6-f01d3ca17591
Report Status: 2048
Hashed bucket:8/28/2017 7:07 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffe1012fd38000
P3: 0
P4: fffff80cbc1ff82a
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\082817-26515-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_bb1576da6ebae565bdfbf35be1c619e2d59ff123_00000000_cab_1fc78fed
Analysis symbol:
Rechecking for solution: 0
Report Id: 78540759-972c-4077-bbe6-f01d3ca17591
Report Status: 2048
Hashed bucket:8/28/2017 7:06 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffe1012fd38000
P3: 0
P4: fffff80cbc1ff82a
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\082817-26515-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_bb1576da6ebae565bdfbf35be1c619e2d59ff123_00000000_02f73365
Analysis symbol:
Rechecking for solution: 0
Report Id: 78540759-972c-4077-bbe6-f01d3ca17591
Report Status: 4
Hashed bucket:8/28/2017 7:17 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffe60e97fe9000
P3: 0
P4: fffff80cbc38f82a
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\082817-26296-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
Analysis symbol:
Rechecking for solution: 1
Report Id: 9dd8c2c2-0f3f-4c4c-8fb0-2056b570eca4
Report Status: 2048
Hashed bucket:8/28/2017 7:07 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffe60e97fe9000
P3: 0
P4: fffff80cbc38f82a
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\082817-26296-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_4cc86828ed99255948c41cfcdc5354830fc7579_00000000_cab_1fc79905
Analysis symbol:
Rechecking for solution: 0
Report Id: 9dd8c2c2-0f3f-4c4c-8fb0-2056b570eca4
Report Status: 2048
Hashed bucket:8/28/2017 7:06 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffe60e97fe9000
P3: 0
P4: fffff80cbc38f82a
P5: 0
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\082817-26296-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_4cc86828ed99255948c41cfcdc5354830fc7579_00000000_02f733b3
Analysis symbol:
Rechecking for solution: 0
Report Id: 9dd8c2c2-0f3f-4c4c-8fb0-2056b570eca4
Report Status: 4
Hashed bucket:8/28/2017 7:17 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: c2
P2: 7
P3: 44696457
P4: 40b0008
P5: ffffd70180cc5670
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\080517-32359-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
Analysis symbol:
Rechecking for solution: 1
Report Id: be3f6911-5d4a-4d75-b613-2578f230228d
Report Status: 2048
Hashed bucket:8/28/2017 7:14 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: c2
P2: 7
P3: 44696457
P4: 40b0008
P5: ffffd70180cc5670
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\080517-32359-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
Analysis symbol:
Rechecking for solution: 1
Report Id: be3f6911-5d4a-4d75-b613-2578f230228d
Report Status: 2048
Hashed bucket:8/28/2017 7:07 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: c2
P2: 7
P3: 44696457
P4: 40b0008
P5: ffffd70180cc5670
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\080517-32359-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_c2_28734d14eccfaf151f74e3a18c2ab8a0b5f866a1_00000000_cab_1fc79b66
Analysis symbol:
Rechecking for solution: 0
Report Id: be3f6911-5d4a-4d75-b613-2578f230228d
Report Status: 2048
Hashed bucket:8/28/2017 7:06 PM Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: c2
P2: 7
P3: 44696457
P4: 40b0008
P5: ffffd70180cc5670
P6: 10_0_14393
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\WINDOWS\Minidump\080517-32359-01.dmp
\\?\C:\Windows\Temp\WER-144812-0.sysdata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_c2_28734d14eccfaf151f74e3a18c2ab8a0b5f866a1_00000000_02f73421
Analysis symbol:
Rechecking for solution: 0
Report Id: be3f6911-5d4a-4d75-b613-2578f230228d
Report Status: 4
Hashed bucket:
Code:
kd> !errrec ffff8784222b28f8===============================================================================Common Platform Error Record @ ffff8784222b28f8-------------------------------------------------------------------------------Record Id : 01d2e81bebee0b27Severity : Fatal (1)Length : 928Creator : MicrosoftNotify Type : Machine Check ExceptionTimestamp : 6/18/2017 10:16:30 (UTC)Flags : 0x00000002 PreviousError===============================================================================Section 0 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffff8784222b2978Section @ ffff8784222b2a50Offset : 344Length : 192Flags : 0x00000001 PrimarySeverity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : BUS errorOperation : GenericFlags : 0x00Level : 3CPU Version : 0x0000000000100f53Processor ID : 0x0000000000000000===============================================================================Section 1 : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor @ ffff8784222b29c0Section @ ffff8784222b2b10Offset : 536Length : 128Flags : 0x00000000Severity : FatalLocal APIC Id : 0x0000000000000000CPU Id : 53 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17 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 @ ffff8784222b2b10===============================================================================Section 2 : x86/x64 MCA-------------------------------------------------------------------------------Descriptor @ ffff8784222b2a08Section @ ffff8784222b2b90Offset : 664Length : 264Flags : 0x00000000Severity : FatalError : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4) Status : 0xfa00000000070f0f
Code:
BugCheck 124, {0, ffff8784222b28f8, 0, 0}Probably caused by : AuthenticAMD
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: ffff8784222b28f8, Address of the WHEA_ERROR_RECORD structure.Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.