Several BSOD errors, please help!

[jwboutte]

I am a first timer building a new PC. I had a bit of trouble getting an install of Windows without BSOD errors. My first install of Windows 10 worked pretty flawlessly, until I had trouble with my graphics card driver, leading me to doing a fresh install. Since then I've been receiving BSOD errors consistently on my PC and I cannot pin point the issue. I believe it could be a corruption problem with my SSD after running Active Partition Recovery and it showing several overlapped sectors.

My Build:

CPU: i5-6600k
Motherboard: ASUS z170-A
RAM: G.skill Ripjaw V Series 16gb (2x8gb)
SSD: Kingston Savage 250GB
HHD: Western Blue 1TB Internal Drive
Graphics Card: MSI Radeon Rx480 8gb

On Sat 2/11/2017 11:44:32 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1F5C0C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8015BE79C0C, 0xFFFF80013023A0A8, 0xFFFF8001302398D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Sat 2/11/2017 11:44:32 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8015BE79C0C, 0xFFFF80013023A0A8, 0xFFFF8001302398D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 2/11/2017 11:37:18 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5578-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x1F281)
Bugcheck code: 0xBE (0xFFFF8B80464779E0, 0x8000000001000121, 0xFFFFA6017E578A30, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 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 Sat 2/11/2017 11:17:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5875-01.dmp
This was probably caused by the following module: npfs.sys (0xFFFFF809224CB391)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x2, 0xFFFFF809224CB391, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 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 Sat 2/11/2017 7:42:47 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5171-01.dmp
This was probably caused by the following module: fastfat.sys (fastfat+0x43DF)
Bugcheck code: 0x23 (0xE0121, 0xFFFFAE000F5655F8, 0xFFFFAE000F564E20, 0xFFFFF80BAC5CEC81)
Error: FAT_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
Bug check description: This indicates that a problem occurred in the FAT file system.
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.
Google query: Microsoft Corporation FAT_FILE_SYSTEM


I have attached first a copy of the DMP files and the error codes I received and then also the disk analysis done by Active Partition Recovery. I'm looking for any type of direction thank you!

Here is a link to my Minidump files for the BSODs: https://www.dropbox.com/sh/4qab4utr4285ii0/AACF79Tug7UjQZLazMvD6RIha?dl=0

Once again I am very grateful to anyone who can help me find a solution, I am desperate at this point!

Thank you,
Inexperienced Builder

 

[Colif]

Can you give me the summary report of who crashed? Its easier to read that that page and gives more information

Initial guess is its drivers, its always drivers... though now sure about that fat file system error

Can you also 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

I can't read the dumps but someone who can might look at them for you.

 

[jwboutte]

Can you give me the summary report of who crashed? Its easier to read that that page and gives more information

Initial guess is its drivers, its always drivers... though now sure about that fat file system error

Can you also 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

I can't read the dumps but someone who can might look at them for you.

Thank you for your help!

I have uploaded the Minidump files and updated my original post with the link, I will also include it here. I cannot thank you enough.

https://www.dropbox.com/sh/4qab4utr4285ii0/AACF79Tug7UjQZLazMvD6RIha?dl=0

 

[Colif]

can you also show the summary from who crashed? I can't read dumps but can try to help with who crashed

 

[jwboutte]

can you also show the summary from who crashed? I can't read dumps but can try to help with who crashed

What do you mean by the summary?
Does this work?

http://i.imgur.com/ZQ4vIcE.png

 

[Colif]

click on the report page, click analyze, scroll down and find something that looks like

On Sun 6/03/2016 10:55:50 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE0014E2F7330, 0xFFFFE0014E2F7350, 0x4020008)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
Google query: Malwarebytes Corporation BAD_POOL_HEADER

for each error you have received and copy/paste it in here.

 

[jwboutte]

click on the report page, click analyze, scroll down and find something that looks like

On Sun 6/03/2016 10:55:50 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE0014E2F7330, 0xFFFFE0014E2F7350, 0x4020008)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
Google query: Malwarebytes Corporation BAD_POOL_HEADER

for each error you have received and copy/paste it in here.

Ah okay, here you go! I pasted it here and updated my original post!

On Sat 2/11/2017 11:44:32 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1F5C0C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8015BE79C0C, 0xFFFF80013023A0A8, 0xFFFF8001302398D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Sat 2/11/2017 11:44:32 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8015BE79C0C, 0xFFFF80013023A0A8, 0xFFFF8001302398D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 2/11/2017 11:37:18 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5578-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x1F281)
Bugcheck code: 0xBE (0xFFFF8B80464779E0, 0x8000000001000121, 0xFFFFA6017E578A30, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 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 Sat 2/11/2017 11:17:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5875-01.dmp
This was probably caused by the following module: npfs.sys (0xFFFFF809224CB391)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x2, 0xFFFFF809224CB391, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 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 Sat 2/11/2017 7:42:47 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-5171-01.dmp
This was probably caused by the following module: fastfat.sys (fastfat+0x43DF)
Bugcheck code: 0x23 (0xE0121, 0xFFFFAE000F5655F8, 0xFFFFAE000F564E20, 0xFFFFF80BAC5CEC81)
Error: FAT_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
Bug check description: This indicates that a problem occurred in the FAT file system.
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.
Google query: Microsoft Corporation FAT_FILE_SYSTEM

 

[Colif]

First error caused by fastfat.sys - used for USB drives or sd cards (explains why you getting fat file system errors on win 10).
Named Pipe File System (Npfs.sys) - reading its description didn't help me figure out what it is.
ntfs = New Technology File System - windows has used this since XP, its the File system
ntoskrnl - New technology operating system kernel - this is brains of windows

2 file system errors + a USB error... Might be fixed if you update chipset/SATA drivers on motherboard

 

[Paul NZ]

I would uninstall malwarebytes for now. I would see if there are any driver updates for the WD drivers