multiple BSOD errors all different

[nkasterz]

Hello, I just build my first pc following all the instructions and everything, installing all the software and drivers and windows 10 but every time I try to do something appears BSOD, try multiple fixes , reinstall windows multiple times, got the computer stable for a couple hours, using playing games or others, but still keeps appearing BSOD every time, I need help I' m not sure what is failing.
My Specs are:
Motherboard: Msi z170a pro carbon
Psu: evga 750w G2
Graphics: Asus Turbo Nvidia GeForce gtx 1080 8G
CPU: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz
RAM: 2x 8GB corsair vengeance lpx ddr4 3000 mhz
HDD: Seagate 1TB Barracuda Sata 6GB/s
Cooler : H100i v2
Windows 10 Home (for the moment)


Not overclocking*
Checked windows memory diagnostic*
Verifier starts another BSOD i/o *
used ccleaner**
tried to troubleshoot and repair*

 

[Colif]

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

 

[nkasterz]

Computer name: DESKTOP-J5R9JD5
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: MS-7A12, MSI, Z170A GAMING PRO CARBON (MS-7A12)
CPU: GenuineIntel Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17137545216 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 3/27/2017 1:56:19 AM your computer crashed
crash dump file: C:\Windows\Minidump\032717-18750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xF7 (0x140FBBCE3440, 0x1E73DDEE5C88, 0xFFFFE18C2211A377, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 3/27/2017 1:56:19 AM 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: 0xF7 (0x140FBBCE3440, 0x1E73DDEE5C88, 0xFFFFE18C2211A377, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Colif]

A driver overran a stack-based buffer (or local variable) in a way that would have overwritten the function's return address and jumped back to an arbitrary address when the function returned.
This is the classic "buffer overrun" hacking attack. The system has been brought down to prevent a malicious user from gaining complete control of it.

Bug Check 0xF7: DRIVER_OVERRAN_STACK_BUFFER

Error is pointing at the kernel in both cases, it means the error occurred on windows wide of transaction but its a driver error (it says it in name) so just need to work out which one.

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[nkasterz]

Here is the dump file
https://drive.google.com/file/d/0B4oHYZWSiVbVcHBVVlBHbDJIVXM/view?usp=sharing

Thank you for the help

 

[nkasterz]

I just got a new BSOD saying *attempted execute of noexecute memory* trying to run a malwarebytes scan, windows and malwarebytes both turn off after reset
'aw snap' messages in Chrome*
BSOD Page Fault In Nonpaged Area*

 

[Colif]

If no one reads dumps in next 24 hours I would follow the posting instructions on the following link and ask them. https://www.tenforums.com/bsod-crashes-debugging/

I would suggest driver verifer but you already tried that., Someone at Tenforums should be able to help you fix this.

 

[nkasterz]

ok thank you