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
Code:
BugCheck 1000007E, {ffffffffc0000005, fffff80a83f497f8, ffff9900b5696908, ffff9900b5696150}Probably caused by : iaStorAV.sys ( iaStorAV+97f8 )
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
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
Code:
BugCheck 124, {0, ffffce820a346028, b2000000, 70005}Probably caused by : GenuineIntel
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.
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
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
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
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
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
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
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
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: