Windows 10: BSOD after installing new I7-7820x CPU

I just changed my cpu yesterday to a Core I7-7820x and I have gotten 3 screens of death since, is this a sign the processor is bad?

:)

 

Desktop Computer won't go to sleep after recent fall update the PC will close the screen but immediately go to log on screen

It ran finding no problems yet it still persists

The computer is an i7-7820x with an asus gtx 1080 16GB ddr4 ram AIO watercooler and 750W power supply

 

Just installed a new motherboard, memory and CPU. I keep getting this BSOD KERNEL_SECURITY_CHECK_FAILURE Windows 10.

Original Title - kernel_security_check_failure

Just installed a new motherboard, memory and CPU.

I keep getting this BSOD KERNEL_SECURITY_CHECK_FAILURE.

I am using a fresh install of Windows 10 Home.

My specifications are:

Intel i7-6700

ASUS H170 Pro Gaming

Corsair Vengeance DDR4 2133

the memory.dmp right after the most recent crash is:

https://onedrive.live.com/redir?res...1626&authkey=!AGUpA-bEFV2R49g&ithint=file,DMP

Thanks in advance

 

Hello Calhawk2000,

Welcome to Tenforums *Smile

Normally we would not jump to conclusions but given that you have just changed the CPU and the last two BSOD errors are hardware errors it does look likely to be a CPU problem.

Both x124 WHEA errors are indicating that the CPU is reporting an unknown error:

Code: 6: kd> !errrec ffffd6065a146028 =============================================================================== Common Platform Error Record @ ffffd6065a146028 ------------------------------------------------------------------------------- Record Id : 01d30af6189a4a9f Severity : Fatal (1) Length : 864 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/1/2017 20:06:54 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffd6065a1460a8 Section @ ffffd6065a146180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x0000000000050654 Processor ID : 0x0000000000000006 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffd6065a1460f0 Section @ ffffd6065a146240 Offset : 536 Length : 64 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000006 CPU Id : 54 06 05 00 00 08 10 06 - bf fb fe 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 00 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffd6065a146138 Section @ ffffd6065a146280 Offset : 600 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Unknown (Proc 6 Bank 0) Status : 0xb200000000070005[/quote] Code: 3: kd> !errrec ffffce820a346028 =============================================================================== Common Platform Error Record @ ffffce820a346028 ------------------------------------------------------------------------------- Record Id : 01d30ba9f5c999bb Severity : Fatal (1) Length : 864 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/2/2017 16:33:04 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffce820a3460a8 Section @ ffffce820a346180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x0000000000050654 Processor ID : 0x0000000000000003 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffce820a3460f0 Section @ ffffce820a346240 Offset : 536 Length : 64 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000003 CPU Id : 54 06 05 00 00 08 10 03 - bf fb fe 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 00 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffce820a346138 Section @ ffffce820a346280 Offset : 600 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Unknown (Proc 3 Bank 0) Status : 0xb200000000070005[/quote]
I notice that it is not the same processor involved in the two errors, this makes me a little hesitant to immediately condemn the CPU so please run a CPU test to see if this can confirm the diagnosis (make sure you are not overclocking the CPU):

CPU TEST
*Arrow Run Prime95 - Stress Test Your CPU - Windows 10 Forums



Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

I ran prime95 for over 3 hours and no errors, now what do you think the problem could be?

 

I also forgot to say that the processor is not overclocked. It is running stock speed. I also have run memtest and no errors in the memory either.

 

Did you clean install WIndows 10 after changing the CPU? If not you might want to try that. Save you data first though.

 

Also, do you have the latest BIOS update?

 

Yes I have the latest BIOS, but I didn't do a clean install of windows.

 

One of the BSOD related drivers in windows error reporting was: iaStorAV.sys
The report is included in the code tags wrap.
Intel(R) SATA RAID Controller Driver
It was not listed in the win dbg as that was WHEA 124

This driver could be updated.

Code: 8/2/2017 5:41 AM Windows Error Reporting Fault bucket AV_iastorav!TransportSrbExtension::isBypass, type 0 Event Name: BlueScreen Response: Not available Cab Id: 0c0bbed2-166e-4608-aeea-7f5f0ab19773 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff80a83f497f8 P4: ffff9900b5696908 P5: ffff9900b5696150 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\080217-11906-01.dmp \\?\D:\Temp\Files\WER-13421-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CAB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CAC.tmp.txt \\?\D:\Temp\Files\WER71F4.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_361cf5b7d975566c2d2fd0fe888d6cf2aee17b4c_00000000_cab_1a88735b Analysis symbol: Rechecking for solution: 0 Report Id: 54b919e9-1588-4965-a8b5-840afe9c6771 Report Status: 268435456 Hashed bucket:[/quote]
Code: iaStorAV Intel(R) SATA RAID Con Intel(R) SATA RAID Con Kernel Manual Stopped OK FALSE FALSE 4,096 593,920 0 2/19/2015 7:08:39 AM C:\Windows\system32\drivers\iaStorAV.sys 4,096[/quote] iaStorAV.sys Intel Rapid Storage Technology SATA RAID Controller driver Drivers & Software

 

You could try a reset instead of a clean install or install the chipset drivers for your new system board.
See here: http://www.dowdandassociates.com/blo...g-motherboard/
It's for Windows 7 but the same process holds true for Windows 10.

1. Get the chipset drivers, expand them and place on a flash drive.
2 Boot your install DVD or flash drive, take the Repair your computer path then use

dism /image:c:\ /add-driver /Driver:X:\ /recurse

command to add the new chipset drivers then reboot and wait while the new drivers are install. Can take a while but it may boot properly. If you have problems, read the first response by Spriggan for a possible fix.

Something to think about at least.

 

I reinstalled Windows 10 Pro and it didn't crash until I had almost all of the drivers reinstalled then it crashed twice. Here is the dump files. What do you suggest now?

 

There were multiple bsod mini dump files debugged.
They displayed again the WHEA 124 error.
In addition there were multiple misbehaving drivers.
After the fresh install there were numerous entries for Windows error reporting.
One was USB device enumeration failure. The significance of this is unclear to me and if anyone had troubleshooted this before please comment.

1) Update or reinstall the chipset drivers.
2) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the Nvidia website.
When using the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.

https://www.wagnardsoft.com/Display Driver Uninstaller Download version 17.0.7.2

Display Driver Uninstaller: How to use - Windows 7 Help Forums[2]=Hardware%20and%20Drivershttp://www.nvidia.com/Download/index.aspx

3) Uninstall all Norton and Symantic products using control panel and the software manufacturer uninstall tools.
Uninstall Symantec Endpoint Protection
Uninstall and Reinstall Norton product using the Norton Remove and Reinstall tool

4) Turn on windows defender

5) Run memtest86+ version 5.01 for at least 8 runs.
It is best to test dual channel RAM with 2 RAM at the same time.
If it is single channel RAM then you can test 1 RAM at a time.
To check the RAM please download and install either CPU-Z or HWINFO
CPU-Z | Softwares | CPUID
HWiNFO - Download
There is 64 GB of RAM on the computer so test 32 GB at a time if it is dual channel.
It may take 1 - 2 hours / GB of RAM so plan to perform the testing when there is significant time to make 8 or more passes.
If the time period to test 32 GB of RAM is too long then you can test 16 GB in the same DIMM but you will not have the benefit of checking the dual channel.
There are significant false negatives if less than 8 passes are made so those tests then need to be repeated.
A false negative is when the testing indicates that the RAM passes and the RAM malfunctions.
During the RAM testing 1 error is a fail. So if you see 1 error you can abort testing and then test 1 RAM at a time in the same DIMM.
After each test please use a camera or smart phone camera to take a picture and post the image into the thread.
Memtest86+ - Advanced Memory Diagnostic Tool
https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
MemTest86+ - Test RAM Windows 10 BSOD Tutorials


Code: ffff9900`b56971a0 fffff80a`87379550Unable to load image nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x6a9550[/quote] Code: BugCheck 1000007E, {ffffffffc0000005, fffff80a83f497f8, ffff9900b5696908, ffff9900b5696150}Probably caused by : iaStorAV.sys ( iaStorAV+97f8 )[/quote]
iaStorAV.sys Intel Rapid Storage Technology SATA RAID Controller driver Drivers & Software

nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops
Code: ffffbc00`8c174598 fffff801`97158daaUnable to load image IDSvia64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for IDSvia64.sys*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys IDSvia64+0x48daa[/quote] IDSvia64.sys Norton Internet Security NORTON™ - Antivirus Software and Spyware Removal
ffffbc00`8c173cb8 fffff801`970a4290Unable to load image SYMNETS.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for SYMNETS.SYS*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS SYMNETS+0x24290

SYMNETS.SYS Symantec/ Norton NIS/ N360 Network Security driver NORTON™ - Antivirus Software and Spyware Removal
Code: BugCheck 124, {0, ffffce820a346028, b2000000, 70005}Probably caused by : GenuineIntel[/quote] 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: ffffce820a346028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000070005, Low order 32-bits of the MCi_STATUS value.[/quote] Code: 3: kd> !errrec ffffce820a346028===============================================================================Common Platform Error Record @ ffffce820a346028-------------------------------------------------------------------------------Record Id : 01d30ba9f5c999bbSeverity : Fatal (1)Length : 864Creator : MicrosoftNotify Type : Machine Check ExceptionTimestamp : 8/2/2017 16:33:04 (UTC)Flags : 0x00000000===============================================================================Section 0 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffffce820a3460a8Section @ ffffce820a346180Offset : 344Length : 192Flags : 0x00000001 PrimarySeverity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : Micro-Architectural ErrorFlags : 0x00CPU Version : 0x0000000000050654Processor ID : 0x0000000000000003===============================================================================Section 1 : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor @ ffffce820a3460f0Section @ ffffce820a346240Offset : 536Length : 64Flags : 0x00000000Severity : FatalLocal APIC Id : 0x0000000000000003CPU Id : 54 06 05 00 00 08 10 03 - bf fb fe 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 00===============================================================================Section 2 : x86/x64 MCA-------------------------------------------------------------------------------Descriptor @ ffffce820a346138Section @ ffffce820a346280Offset : 600Length : 264Flags : 0x00000000Severity : FatalError : Unknown (Proc 3 Bank 0) Status : 0xb200000000070005[/quote] Code: ffffe501`8e563ed8 fffff803`d7028360Unable to load image SYMEFASI64.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for SYMEFASI64.SYS*** ERROR: Module load completed but symbols could not be loaded for SYMEFASI64.SYS SYMEFASI64+0x28360[/quote] SYMEFASI64.SYS Symantec Extended File Attributes Symantec Enterprise Technical Support
Code: 2: kd> !errrec ffffac851837c028===============================================================================Common Platform Error Record @ ffffac851837c028-------------------------------------------------------------------------------Record Id : 01d30ce8a809f971Severity : Fatal (1)Length : 864Creator : MicrosoftNotify Type : Machine Check ExceptionTimestamp : 8/4/2017 6:25:48 (UTC)Flags : 0x00000000===============================================================================Section 0 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffffac851837c0a8Section @ ffffac851837c180Offset : 344Length : 192Flags : 0x00000001 PrimarySeverity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : Micro-Architectural ErrorFlags : 0x00CPU Version : 0x0000000000050654Processor ID : 0x0000000000000002===============================================================================Section 1 : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor @ ffffac851837c0f0Section @ ffffac851837c240Offset : 536Length : 64Flags : 0x00000000Severity : FatalLocal APIC Id : 0x0000000000000002CPU Id : 54 06 05 00 00 08 10 02 - bf fb fe 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 00===============================================================================Section 2 : x86/x64 MCA-------------------------------------------------------------------------------Descriptor @ ffffac851837c138Section @ ffffac851837c280Offset : 600Length : 264Flags : 0x00000000Severity : FatalError : Unknown (Proc 2 Bank 0) Status : 0xb200000000070005[/quote] BHDrvx64.sys Symantec Heuristics Driver Symantec Enterprise Technical Support
Code: ffffb181`1f773ac8 fffff800`eb380020Unable to load image SYMEVENT64x86.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS SYMEVENT64x86+0x20[/quote] SYMEVENT64x86.SYS Norton Internet Security NORTON™ - Antivirus Software and Spyware Removal
Code: ffffb181`1f7739b8 fffff800`e0a49999Unable to load image BHDrvx64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for BHDrvx64.sys*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys BHDrvx64+0x19999[/quote] BHDrvx64.sys Symantec Heuristics Driver Symantec Enterprise Technical Support
Code: ffffb181`1f773438 fffff800`e0988a00Unable to load image SYMEFASI64.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for SYMEFASI64.SYS*** ERROR: Module load completed but symbols could not be loaded for SYMEFASI64.SYS SYMEFASI64+0x128a00[/quote] SYMEFASI64.SYS Symantec Extended File Attributes Symantec Enterprise Technical Support
Code: 2: kd> !errrec ffff9d0aacb81028===============================================================================Common Platform Error Record @ ffff9d0aacb81028-------------------------------------------------------------------------------Record Id : 01d30ceea93bbfffSeverity : Fatal (1)Length : 864Creator : MicrosoftNotify Type : Machine Check ExceptionTimestamp : 8/4/2017 6:58:43 (UTC)Flags : 0x00000000===============================================================================Section 0 : Processor Generic-------------------------------------------------------------------------------Descriptor @ ffff9d0aacb810a8Section @ ffff9d0aacb81180Offset : 344Length : 192Flags : 0x00000001 PrimarySeverity : FatalProc. Type : x86/x64Instr. Set : x64Error Type : Micro-Architectural ErrorFlags : 0x00CPU Version : 0x0000000000050654Processor ID : 0x0000000000000002===============================================================================Section 1 : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor @ ffff9d0aacb810f0Section @ ffff9d0aacb81240Offset : 536Length : 64Flags : 0x00000000Severity : FatalLocal APIC Id : 0x0000000000000002CPU Id : 54 06 05 00 00 08 10 02 - bf fb fe 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 00===============================================================================Section 2 : x86/x64 MCA-------------------------------------------------------------------------------Descriptor @ ffff9d0aacb81138Section @ ffff9d0aacb81280Offset : 600Length : 264Flags : 0x00000000Severity : FatalError : Unknown (Proc 2 Bank 0) Status : 0xb200000000070005[/quote]


Code: 8/4/2017 7:02 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 18be056d-ce12-4523-b92b-03657881abc0 Problem signature: P1: 144 P2: 3003 P3: ffffc601e4017178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0230.dmp \\?\D:\Temp\Files\WER-15515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44BD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44C1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44C2.tmp.txt \\?\D:\Temp\Files\WER1787.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_9f4a84ca16eb2d6f57831e8377e6c3346bd1e_00000000_cab_193d1884 Analysis symbol: Rechecking for solution: 0 Report Id: fbfab396-9d36-421a-877a-08a2de0432c7 Report Status: 268435456 Hashed bucket:8/4/2017 6:26 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 31ac3f17-09ad-4d69-a0c4-935d6870dea7 Problem signature: P1: 144 P2: 3003 P3: ffff98011474f178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0226.dmp \\?\D:\Temp\Files\WER-12828-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4258.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4268.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4278.tmp.txt \\?\D:\Temp\Files\WER6300.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_538941e913d9101d102c6b9538cd593acfcdbb5_00000000_cab_1a806929 Analysis symbol: Rechecking for solution: 0 Report Id: 0d8dc94f-f047-4460-997c-67053e71f55e Report Status: 268435456 Hashed bucket: 8/4/2017 7:02 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 3fc9c191-b194-4c2e-8da8-1c5577998629 Problem signature: P1: 144 P2: 3003 P3: ffffc281e6063178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0248.dmp \\?\D:\Temp\Files\WER-15515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER447C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER447D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER448D.tmp.txt \\?\D:\Temp\Files\WERA656.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_9e31c9ae28ca663ff11eacc4d7698ef3f31b35_00000000_cab_193cab24 Analysis symbol: Rechecking for solution: 0 Report Id: 7f6db50c-e6be-42e7-82ac-ae9c833d663e Report Status: 268435456 Hashed bucket: 8/4/2017 7:02 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 4a6af810-22d7-4cf7-a4f4-33e2730849a4 Problem signature: P1: 144 P2: 3003 P3: ffffe5802d777178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0235.dmp \\?\D:\Temp\Files\WER-15515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER449D.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44B0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44B1.tmp.txt \\?\D:\Temp\Files\WERF42E.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_6dcdcef8951fcc565345bac24b2c3d2cfa1c3c94_00000000_cab_193cf52d Analysis symbol: Rechecking for solution: 0 Report Id: 13f4f194-7de6-4def-b8c7-2de87157a51d Report Status: 268435456 Hashed bucket: 8/4/2017 6:04 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 633367b9-d3fe-491a-8099-b9e490550a3a Problem signature: P1: 144 P2: 3003 P3: ffffe6000303f178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0204.dmp \\?\D:\Temp\Files\WER-567843-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB128.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB138.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB139.tmp.txt \\?\D:\Temp\Files\WERC86A.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_4163c182995d9b572acb9194c5e946ea6d6370_00000000_cab_1fd0c9e0 Analysis symbol: Rechecking for solution: 0 Report Id: 1bb31622-9873-4eb3-adeb-5a601a4f7e9e Report Status: 268435456 Hashed bucket: 8/4/2017 6:13 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 8b6f926e-f449-41a0-8f03-a7f7f81ad7b6 Problem signature: P1: 144 P2: 3003 P3: ffffe5018c5c7178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0213.dmp \\?\D:\Temp\Files\WER-53953-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD9D5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD9D5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD9D6.tmp.txt \\?\D:\Temp\Files\WER317D.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_df213954dc33fb73268d73b0a87f5b4ecbd8c_00000000_cab_225d36e9 Analysis symbol: Rechecking for solution: 0 Report Id: 153dc5d3-665e-47ff-a789-da9741f7e60c Report Status: 268435456 Hashed bucket: 8/4/2017 7:02 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 8d1d36bc-3d6b-4879-9d8e-93c069e19adb Problem signature: P1: 144 P2: 3003 P3: ffffa0007ee67178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0246.dmp \\?\D:\Temp\Files\WER-15515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER448C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER448E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER449F.tmp.txt \\?\D:\Temp\Files\WERC7FA.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_3897fd9f28264661e99668e4b9179ca136d84295_00000000_cab_193cc8fd Analysis symbol: Rechecking for solution: 0 Report Id: f4329ee1-576b-4915-818f-c0a34cacdfc8 Report Status: 268435456 Hashed bucket: 8/4/2017 6:26 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 96109962-b309-435c-ad23-82338f336e75 Problem signature: P1: 144 P2: 3003 P3: ffffe5018c5cf178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0212.dmp \\?\D:\Temp\Files\WER-12828-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4278.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4289.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER428A.tmp.txt \\?\D:\Temp\Files\WER8169.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_99e0a3cae2d9eccd64ff69476c77df2981f6af3_00000000_cab_1a8085ba Analysis symbol: Rechecking for solution: 0 Report Id: fdfd65b3-941c-4c4e-b944-072015bfb868 Report Status: 268435456 Hashed bucket: 8/4/2017 7:02 AM Windows Error Reporting Fault bucket LKD_0x144_USBHUB3_DEVICE_ENUMERATION_FAILURE_UsbHub3!TelemetryData_CreateReport_VEN_1A40_DEV_0201_REV_0100, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: ee7d59a6-1eaf-4aa9-b5a7-97fdfbaed839 Problem signature: P1: 144 P2: 3003 P3: ffffb1811d44f178 P4: 40010000 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\USBHUB3\USBHUB3-20170804-0255.dmp \\?\D:\Temp\Files\WER-15515-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER444C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER446B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER446C.tmp.txt \\?\D:\Temp\Files\WER84FF.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_38eede5ea995d713583ca96e482eeca62996ad4a_00000000_cab_193c8a1f Analysis symbol: Rechecking for solution: 0 Report Id: 0cb9c501-b75c-4210-9276-67c943e70aa2 Report Status: 268435456 Hashed bucket:[/quote]

 

The two crashes are again hardware x124 errors. The errors are the same and are both on proc 2 bank 0.

Code: Error Type : Micro-Architectural Error Error : Unknown (Proc 2 Bank 0)[/quote] Contact Intel and see what they say - they may send a replacement CPU to try. There is also the Intel CPU diagnostic tool you can try.

Given that it behaved fine until the last few drivers were installed can you undo those final drivers and roll them back?

According the eventlog the last drivers to be updated before the first BSOD were:
Attachment 147047
Attachment 147048

 

You stated in your opening post that you changed your CPU and this started. What CPU did you have in this X299 motherboard before and what was your experience with it?

If you have any Gigabyte utilities installed, please uninstall every one of them.

How does it run on a clean install with no drivers other than what Windows Update installs?