Windows 10 BSOD

[SpideySound]

Alright. I am getting constant blue screens of death. So far ive gotten Bad Pool, memory management, page on nonpage, kernel security, and thats it. It happens constantly and whenever i try to scan my hardware at all, i get another one. How in the world do i get this to stop?
Ive already unplugged every usb device i have from my pc so thats not it

 

[Colif]

Can you download and run who crashed: http://www.resplendence.com/whocrashed
it will create a summary of the BSOD and might give us an idea what you dealing with

Copy/paste results in here

 

[SpideySound]

Can you download and run who crashed: http://www.resplendence.com/whocrashed
it will create a summary of the BSOD and might give us an idea what you dealing with

Copy/paste results in here

Alright so its basically saying ntoskrnl.exe is the source along with fltmgr.sys

the conclusion states that it's my graphics card causing the problem.. but ive updated my graphics card driver several times already. I have a GTX 1060 6gb

 

[SpideySound]

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 10/30/2016 8:45:42 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\103016-5500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A3B0)
Bugcheck code: 0x139 (0x3, 0xFFFFBB81AE5643D0, 0xFFFFBB81AE564328, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/30/2016 8:45:42 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltLockUserBuffer+0x4C2)
Bugcheck code: 0x139 (0x3, 0xFFFFBB81AE5643D0, 0xFFFFBB81AE564328, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 10/30/2016 8:34:24 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\103016-5703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A3B0)
Bugcheck code: 0x19 (0x3, 0xFFFF9C0D19B60280, 0xFFFF9C0D19360280, 0xFFFF9C0D19B60280)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Sun 10/30/2016 8:29:36 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\103016-5656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A3B0)
Bugcheck code: 0x1A (0x41289, 0x7FF884F40000, 0x2A25, 0x7FF884740005)
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 Sun 10/30/2016 8:27:13 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\103016-6750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A3B0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF102536946F0, 0xD2, 0xD1)
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.





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

14 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 375.70 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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]

Have you done something like this before? http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

NTOSKRNL = New Technology Operating System Kernel. Windows stops working if it does. It gets the blame for lots of things as it has many roles, one is memory management, one is dealing with driver requests. Often it gets blame for driver errors

FltMgr.sys is a “system” file used by Windows to help control various aspects of your hard drives & files. Its official name is the “Microsoft Filesystem Filter Manager” and its main duty in the operating system is make sure that the data written to the hard drive is correct and not corrupted.

Kernel security check is a driver error
Bad Pool Header is a driver error
Memory management can be drivers or Ram

is this a custom PC or brand name? If custom, what motherboard do you have? If brand, what make/model?

you might want to run http://www.memtest86.com/ on the ram and make sure its okay, you don't want to have any errors

Apart from ram, here are a few other things to try for memory management errors

If your computer is usable, but is constantly plagued with this MEMORY_MANAGEMENT BSoD, do the following:
Update your BIOS and drivers. BIOS updates can be found on your manufacturer’s website, and driver updates can either be done manually through Device Manager (use Start Search to find it)
Check for viruses with your preferred antivirus software or Malwarebytes.
Use sfc /scannow.
If on a laptop, change power settings to High Performance.
If this problem occurs shortly after installing a new program, remove that program right away.

 

[SpideySound]

Have you done something like this before? http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

NTOSKRNL = New Technology Operating System Kernel. Windows stops working if it does. It gets the blame for lots of things as it has many roles, one is memory management, one is dealing with driver requests. Often it gets blame for driver errors

FltMgr.sys is a “system” file used by Windows to help control various aspects of your hard drives & files. Its official name is the “Microsoft Filesystem Filter Manager” and its main duty in the operating system is make sure that the data written to the hard drive is correct and not corrupted.

Kernel security check is a driver error
Bad Pool Header is a driver error
Memory management can be drivers or Ram

is this a custom PC or brand name? If custom, what motherboard do you have? If brand, what make/model?

you might want to run http://www.memtest86.com/ on the ram and make sure its okay, you don't want to have any errors

Apart from ram, here are a few other things to try for memory management errors

If your computer is usable, but is constantly plagued with this MEMORY_MANAGEMENT BSoD, do the following:
Update your BIOS and drivers. BIOS updates can be found on your manufacturer’s website, and driver updates can either be done manually through Device Manager (use Start Search to find it)
Check for viruses with your preferred antivirus software or Malwarebytes.
Use sfc /scannow.
If on a laptop, change power settings to High Performance.
If this problem occurs shortly after installing a new program, remove that program right away.

Wow! That was some great information and I'll definitely remember this if it happens again. I believe to have fixed it... What happened was (and i didnt even realize it) 1 stick of ram was 1600mhz, the other was 1866... So i had to clear CMOS and then go into bios and change the frequency to max 1866 instead of 1600 and im hoping that will fix it. If it happens again, I'll end up getting another 1866 stick of the same exact ram to make sure they line up. Thank you so much for that though, it's helped me understand how it wall works way more. And I custom built mine, I have an MSI 990 FXA gaming Motherboard

 

[Colif]

think you better off having two sticks that match each other or this will just happen again.