Several BSOD's on new build

[dingledong]

Most of the crashes seem to be memory related. I've done several memtest+86 passes on my single stick 8GB DDR4 RAM and it's come up with 0 errors, so I'm not sure if it's the memory that is causing this problem. It's gotten worse in the past week as well. I'm pretty sure all my drivers and Windows are up to date.
Here is a screenshot of my WhoCrashed window.
https://i.gyazo.com/12616c98f3b9e0d3e72aed73a31b39b0.png

It's driving me mad, I'll appreciate any help I can get.

 

[The_Prophecy]

What are the rest of the specs for your system?

 

[dingledong]

Operating System
Windows 10 Pro 64-bit
CPU
Intel Core i5 6600K @ 3.50GHz
Skylake 14nm Technology
RAM
8.00GB Single-Channel Unknown @ 1200MHz (16-16-16-39)
Motherboard
Gigabyte Technology Co. Ltd. Z170M-D3H-CF (U3E1)
Graphics
DELL E2211H (1920x1080@59Hz)
S24C230 (1920x1080@60Hz)
8192MB ATI Radeon RX 480 Graphics (XFX Pine Group)
Storage
931GB Seagate ST1000DM003-1ER162 (SATA)
Optical Drives
No optical disk drives detected
Audio
Realtek High Definition Audio

 

[dingledong]

bump with whocrashed log

On Sat 5/27/2017 2:57:29 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052717-24625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1C7 (0x0, 0xFFFF850BB0138000, 0x64F2EB3C, 0xF9B1AB7C)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 5/27/2017 2:57:29 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1C7 (0x0, 0xFFFF850BB0138000, 0x64F2EB3C, 0xF9B1AB7C)
Error: CUSTOM_ERROR
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 5/26/2017 8:10:44 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052617-29984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x154 (0xFFFFAA83B5204000, 0xFFFFE40198E187F0, 0x1, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 5/26/2017 7:29:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052617-27906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x1A (0x41201, 0xFFFFB98112C70098, 0x81000000B5117867, 0xFFFFBE031BFFAA20)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 5/22/2017 9:33:47 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052217-26281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x6BD, 0x836EF3C0, 0xFFFFBB818156B000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[The_Prophecy]

First I would try running a memory test, Start with the Windows Memory Diagnostic (since it is integrated into Windows and is actually decent at properly identifying issues). You can type Windows Memory Diagnostic into the start menu and it should appear. Restart and run it right away if you can, schedule it to run at next restart if you can't reboot right away.

You can also try MemTest86. "MemTest86+" should probably be avoided at this point, as it has not been updated in several years, and the original MemTest86 still has a free version available that is now maintained by PassMark Software.

 

[dingledong]

First I would try running a memory test, Start with the Windows Memory Diagnostic (since it is integrated into Windows and is actually decent at properly identifying issues). You can type Windows Memory Diagnostic into the start menu and it should appear. Restart and run it right away if you can, schedule it to run at next restart if you can't reboot right away.

You can also try MemTest86. "MemTest86+" should probably be avoided at this point, as it has not been updated in several years, and the original MemTest86 still has a free version available that is now maintained by PassMark Software.

I did the windows memory diagnostic test with no errors, and MemTest86 for 10 passes with no errors. what could possibly still be the issue here?

 

[The_Prophecy]

Of the error codes you posted, 0x1C7 doesn't exist, 0x154 is actually "UNEXPECTED_STORE_EXCEPTION", 0x12B and 0x1A point to memory problems.

First, make sure you are running the latest version of WhoCrashed (5.54): http://www.resplendence.com/download/whocrashedSetup.exe

There is no definitive solution for the UNEXPECTED_STORE_EXCEPTION crash, so we'll start with making sure you're completely up to date on Windows (install the Creators Update, and all post build 1704 released hotfixes). Once Windows Update shows no more updates, open an administrative command prompt or PowerShell and enter the command "sfc /scannow" without quotes. If issues are found, System File Checker will attempt to repair them and advise you when it is complete. If errors are found, restart the computer and then continue on.

Next I would suggest opening the Command Prompt / PowerShell again and running the chkdsk tool. Use the command "chkdsk /r c:", again without quotes. The window will advise that it cannot lock the drive and to schedule the scan to run at next reboot. Indicate Yes, hit enter, and then restart the machine.

 

[dingledong]

Of the error codes you posted, 0x1C7 doesn't exist, 0x154 is actually "UNEXPECTED_STORE_EXCEPTION", 0x12B and 0x1A point to memory problems.

First, make sure you are running the latest version of WhoCrashed (5.54): http://www.resplendence.com/download/whocrashedSetup.exe

There is no definitive solution for the UNEXPECTED_STORE_EXCEPTION crash, so we'll start with making sure you're completely up to date on Windows (install the Creators Update, and all post build 1704 released hotfixes). Once Windows Update shows no more updates, open an administrative command prompt or PowerShell and enter the command "sfc /scannow" without quotes. If issues are found, System File Checker will attempt to repair them and advise you when it is complete. If errors are found, restart the computer and then continue on.

Next I would suggest opening the Command Prompt / PowerShell again and running the chkdsk tool. Use the command "chkdsk /r c:", again without quotes. The window will advise that it cannot lock the drive and to schedule the scan to run at next reboot. Indicate Yes, hit enter, and then restart the machine.

Did sfc /scannow with no issues.
Then I did chkdsk and checked the logs and windows found no errors.