Windows 10 startup errors on new build

Lukeval89

Commendable
Mar 20, 2016
2
0
1,510
0
Hello Team!

This is my first post on here but I have been reading forum posts and answers for years now which have helped me without even having to ask anything!

I have recently built a gaming PC and overall I am blown away by it. Its my first tower and after years of laptops it is awesome!

Sometimes though when starting up the PC I get What looks like a BSOD error but there are changes in what the errors are. It is a blue screen on windows loadup with following errors:

1: ''System thread exception not handled FLTMGR SYS''
2: ''Memory Managment''

I am running an overclocked I5 4690K at 4.2Ghz with an Asus Z97-P motherboard and windows 10.

Do you guys think it is a Hardware or software issue with windows?
 

Lukeval89

Commendable
Mar 20, 2016
2
0
1,510
0
Hi Colif,

Thanks for your post, I have ran the program and pasted the results below. Interestingly I have disabled turbo in the BIOS and since then It has not happened as of yet. It offered to let me use win thruster and run a scan and it found around 200+ issues. Do you have any experience with this program?

Thanks in advance!



Computer name: LUKEVAL
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z97-P
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8530006016 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 20/03/2016 10:41:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032016-3843-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680FEDBEF50, 0x40000, 0x0)
Error: MEMORY_MANAGEMENT
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.
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 20/03/2016 10:41:22 GMT 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: 0x1A (0x41792, 0xFFFFF680FEDBEF50, 0x40000, 0x0)
Error: MEMORY_MANAGEMENT
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.
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 14/03/2016 15:13:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031416-4609-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!GetContextFromStreamList+0x58)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8002D939CE8, 0xFFFFD00138F7D208, 0xFFFFD00138F7CA20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 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 Mon 14/03/2016 11:12:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031416-5515-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!MiDemoteCombinedPte+0x39)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8001591B73D, 0xFFFFD0010719B3A8, 0xFFFFD0010719ABC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 Sun 13/03/2016 09:23:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031316-4734-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x19 (0x20, 0xFFFFE001FBB81170, 0xFFFFE001FBB811C0, 0x4050017)
Error: BAD_POOL_HEADER
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.
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 12/03/2016 13:42:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031216-4484-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x6000, 0xFFFFE001D327C270, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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.
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 05/03/2016 09:25:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030516-4796-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsDeleteScb+0x409)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800ED01D429, 0xFFFFD000244B1468, 0xFFFFD000244B0C80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 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 Thu 03/03/2016 20:31:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030316-5953-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!ExFreeToNPagedLookasideList+0x46)
Bugcheck code: 0x139 (0x3, 0xFFFFD000222FE420, 0xFFFFD000222FE378, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 Tue 01/03/2016 16:45:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-7312-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsDeleteScb+0xDB)
Bugcheck code: 0x139 (0x3, 0xFFFFD000246B0550, 0xFFFFD000246B04A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 Mon 29/02/2016 16:15:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022916-5609-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x9909)
Bugcheck code: 0x50 (0xFFFFF6FB40000000, 0x0, 0x0, 0x6)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: Avast Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA





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

37 crash dumps have been found and analyzed. Only 10 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:

aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)

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.


 

ASK THE COMMUNITY